Design process

1. Problem definition

All projects start with a need; an internal business problem, a customer issue, an improvement to an already existing piece of the system. First step is always to look for insights, seek the source of the problem, and do some initial research around it.


2. Discovery

On top of the desk and user research, during the discovery phase of my projects I invite people from other parts of the business to collaborate with and bring their expertise to the table. We also sync later, on the project's progress; it's a great opportunity to ask for their opinion and introduce further fixes into the design.


3. Design exploration

Next step is trying to solve the problem. As a designer I don't settle, and explore several different ideas. I collaborate with team members to workshop various options with me, or I propose a few rough solutions. We assess what works best, what’s technologically possible, and what could fit into the time frame we have.


4. Prototyping and user testing

I develop our idea through a series of user flows, wireframes and low fidelity mockups. During many internal reviews as well as tests with users, we talk about the proposed solutions, how they work, and what could be improved. We iterate a few times, until we arrive at a well working prototype we’re all satisfied with.


5. Final designs

I focus on delivering high fidelity designs as a base for the development team to start their work. We communicate mainly using Figma and of course – verbally. We discuss the designs and how can we build code for them, and solve any issues as they appear.


6. Release and learning

After that, in the simplest version of the process, we release our work.

Recenlty, I've been working on many experiments; based on the numbers, and previous insights from user interviews, we can gauge whether the feature is working the way we intended or not. This allows us to make better informed decisions and iterate much faster.

Back to top Arrow