Skip to main content

Product design

User research

We design digital products for people, so it is important to get to know those people. Which problems do they currently struggle with? What context are they using it in? What are their goals? We talk to your (potential) customers, sail through the analytics data and read your support logbooks. This way, we can help your team steer away from biases and into clear actions for the future.

In our experience: research, makes you money. Building the wrong digital product will cost more than doing decent research before jumping into the project.

Three steps

  1. Setting your goals

    It is easy to drown in information — humans are complex creatures after all. In order to gather the right information the first step is defining the research goals. This way we can ask the right questions, use suitable methods (whether qualitative or quantitative) and plan how we are going to gather the data. Preparing research will reduce the bias and bring more valuable user insights.

  2. Doing the research

    We begin our research mostly in chaos and uncertainty, bit by bit we unravel the mysteries of how and why people use your digital product. By the end of this phase we have a clear view on how to tackle your products challenges.

    Whether we are interviewing, interpreting analytics or conducting usability tests, we strive to remove biases in our way of working.

  3. Sharing our insights

    We think it's important that you and your team understand the information we have gathered. We recommend actions to take, so you don't get lost in the sea of insights.


Personas, scenarios & user journeys

These deliverables simplify the information we have about complex humans — very helpful as a reference during different phases of the project or in the future. They help everyone to understand, create empathy for the users and support in making solid decisions.

Clear documentation

In these reports, we will focus on the most important insights, considerations and recommended actions (of course we'll include the details as well if you are into that stuff). It serves as a point of reference throughout the project and as a guide to reassuringly proceed into the previously unknown future.

Hi, I'm Hannes

If you’re bobbing around in client requests, prioritisation and interface patterns, let us know. We’ll come and save your soul!

The ☀️ was in my eyes for the picture. Sorry for that.

Talk to me