\

User Experience Research

User Experience Research

Understanding what's going on before you make design decisions.

\

User Experience Research

User Experience Research

Understanding what's going on before you make design decisions.

\

User Experience Research

User Experience Research

Understanding what's going on before you make design decisions.

Image
Image
Image

Software doesn't exist in a bubble. People rely on it to get their work done, using existing processes, systems, and guidelines. UX Research helps us understand how that works in practiceโ€”and where things go wrong. We look beyond what users simply say they need. We observe how they actually work, the information they rely on, the obstacles they run into, and the requirements set by the organization and technology. Then, we bring all of those insights straight into the design.

Software doesn't exist in a bubble. People rely on it to get their work done, using existing processes, systems, and guidelines. UX Research helps us understand how that works in practiceโ€”and where things go wrong. We look beyond what users simply say they need. We observe how they actually work, the information they rely on, the obstacles they run into, and the requirements set by the organization and technology. Then, we bring all of those insights straight into the design.

Software doesn't exist in a bubble. People rely on it to get their work done, using existing processes, systems, and guidelines. UX Research helps us understand how that works in practiceโ€”and where things go wrong. We look beyond what users simply say they need. We observe how they actually work, the information they rely on, the obstacles they run into, and the requirements set by the organization and technology. Then, we bring all of those insights straight into the design.

Research whenever you need it

For us, UX Research isn't just a fixed phase at the start of a project. Sometimes we kick off with it because there are still a lot of open questions. Other times, we already have a design and want to see how it works in practice. We also keep researching throughout the process. An initial design often brings up new questions, or a prototype reveals insights that didn't come up in an interview. When that happens, we explore further and keep refining our designs.

Research whenever you need it

For us, UX Research isn't just a fixed phase at the start of a project. Sometimes we kick off with it because there are still a lot of open questions. Other times, we already have a design and want to see how it works in practice. We also keep researching throughout the process. An initial design often brings up new questions, or a prototype reveals insights that didn't come up in an interview. When that happens, we explore further and keep refining our designs.

Research whenever you need it

For us, UX Research isn't just a fixed phase at the start of a project. Sometimes we kick off with it because there are still a lot of open questions. Other times, we already have a design and want to see how it works in practice. We also keep researching throughout the process. An initial design often brings up new questions, or a prototype reveals insights that didn't come up in an interview. When that happens, we explore further and keep refining our designs.

Eelco and Karen working on a project at Okapion

Looking beyond the user

A software issue isn't always a UX problem. For instance, a clunky step might actually be caused by an internal process, missing data, or two systems that don't talk to each other properly. Thatโ€™s why we don't just speak with end users. We also connect with product owners, subject matter experts, developers, and other key team members. We take a close look at the current product and how people use it for their work. This gives us a clear picture of what users truly need, as well as what's possible and necessary for your organization.

Looking beyond the user

A software issue isn't always a UX problem. For instance, a clunky step might actually be caused by an internal process, missing data, or two systems that don't talk to each other properly. Thatโ€™s why we don't just speak with end users. We also connect with product owners, subject matter experts, developers, and other key team members. We take a close look at the current product and how people use it for their work. This gives us a clear picture of what users truly need, as well as what's possible and necessary for your organization.

Looking beyond the user

A software issue isn't always a UX problem. For instance, a clunky step might actually be caused by an internal process, missing data, or two systems that don't talk to each other properly. Thatโ€™s why we don't just speak with end users. We also connect with product owners, subject matter experts, developers, and other key team members. We take a close look at the current product and how people use it for their work. This gives us a clear picture of what users truly need, as well as what's possible and necessary for your organization.

How do we conduct our research?

That depends on what you need. We can interview users or shadow them while they work. We also map out processes and information flows, evaluate existing software, or test a prototype with the people who will actually use it. We choose the research method that best helps us make the next design decisionโ€”never doing more research than necessary, but never designing based on guesswork either.

How do we conduct our research?

That depends on what you need. We can interview users or shadow them while they work. We also map out processes and information flows, evaluate existing software, or test a prototype with the people who will actually use it. We choose the research method that best helps us make the next design decisionโ€”never doing more research than necessary, but never designing based on guesswork either.

How do we conduct our research?

That depends on what you need. We can interview users or shadow them while they work. We also map out processes and information flows, evaluate existing software, or test a prototype with the people who will actually use it. We choose the research method that best helps us make the next design decisionโ€”never doing more research than necessary, but never designing based on guesswork either.

What are the benefits for you?

Good research doesn't end up as a thick report gathering dust in a drawer. It should simply help you make clear decisions.

Fewer assumptions about how the work actually gets done

Fewer assumptions about how the work actually gets done

Clear insights into where users actually get stuck

Clear insights into where users actually get stuck

A clear view of your business, process, and technical requirements

A clear view of your business, process, and technical requirements

Bringing different interests and dependencies out into the open

Bringing different interests and dependencies out into the open

Clearer reasoning behind design choices

Clearer reasoning behind design choices

We turn what we learn into practical tools as quickly as possible for the team taking it forward.

Eelco and Karen working on a project at Okapion
Eelco and Karen working on a project at Okapion
Eelco and Karen working on a project at Okapion

Looking at the same problem together

When it comes to complex digital products, everyone only sees part of the picture. Users know their daily routines. Developers know what's technically possible. And the business side has its own goals and requirements. Research helps bring all these perspectives together. Not to gloss over the differences, but to make them clear. That makes it much easier to make decisions together.

Looking at the same problem together

When it comes to complex digital products, everyone only sees part of the picture. Users know their daily routines. Developers know what's technically possible. And the business side has its own goals and requirements. Research helps bring all these perspectives together. Not to gloss over the differences, but to make them clear. That makes it much easier to make decisions together.

Looking at the same problem together

When it comes to complex digital products, everyone only sees part of the picture. Users know their daily routines. Developers know what's technically possible. And the business side has its own goals and requirements. Research helps bring all these perspectives together. Not to gloss over the differences, but to make them clear. That makes it much easier to make decisions together.

Research and design go hand in hand

We don't wait for all the research to wrap up before we start designing. As soon as we know enough, we bring ideas to life with a user flow, sketch, or prototype. This gives users and stakeholders something concrete to respond to. We then take what we learn and build it right back into the design. This way, researching, designing, and testing continuously feed into each other throughout the project.

Research and design go hand in hand

We don't wait for all the research to wrap up before we start designing. As soon as we know enough, we bring ideas to life with a user flow, sketch, or prototype. This gives users and stakeholders something concrete to respond to. We then take what we learn and build it right back into the design. This way, researching, designing, and testing continuously feed into each other throughout the project.

Research and design go hand in hand

We don't wait for all the research to wrap up before we start designing. As soon as we know enough, we bring ideas to life with a user flow, sketch, or prototype. This gives users and stakeholders something concrete to respond to. We then take what we learn and build it right back into the design. This way, researching, designing, and testing continuously feed into each other throughout the project.

Curious to learn more?

You can always call us or schedule a casual meeting with Eelco. We are happy to discuss what we can do for you!

Eelco de Vaal, director at Okapion

Curious to learn more?

You can always call us or schedule a casual meeting with Eelco. We are happy to discuss what we can do for you!

Eelco de Vaal, director at Okapion

Curious to learn more?

You can always call us or schedule a casual meeting with Eelco. We are happy to discuss what we can do for you!

Eelco de Vaal, director at Okapion
We work for, among others,
We work for, among others,
We work for, among others,

Frequently asked questions about UX research

What is UX research?

When do you use UX research?

Which UX research methods do you use?

Is UX research only focused on users?

What is the difference between UX research and usability testing?

Does UX research always have to happen before UX design?

What are the tangible benefits of UX research?

Frequently asked questions about UX research

What is UX research?

When do you use UX research?

Which UX research methods do you use?

Is UX research only focused on users?

What is the difference between UX research and usability testing?

Does UX research always have to happen before UX design?

What are the tangible benefits of UX research?

Frequently asked questions about UX research

What is UX research?

When do you use UX research?

Which UX research methods do you use?

Is UX research only focused on users?

What is the difference between UX research and usability testing?

Does UX research always have to happen before UX design?

What are the tangible benefits of UX research?