Product Design

Good products get out of their own way.

I design digital tools and apps around how people actually use them. Not around what looks good in a demo.

Most digital products fail not because the idea was wrong but because the experience of using them is. Features that are hard to find, flows that require too many steps, interfaces that made sense to the team building them but nobody else. Good product design removes that friction before it gets built in.

I work from the user backwards. What does this person need to accomplish, what is the fastest way to get them there, and what gets in the way. Every feature, every screen, every interaction is measured against that.

Process

How I work.

Discovery

We start with your users, not your feature list. Who are they, what are they trying to do, and where does the current experience break down.

User Flows

Before any screens are designed I map out the core flows. The paths a user takes to complete their main tasks. This is where most product problems are caught and fixed cheaply.

Wireframes & Design

Low-fidelity first, then high-fidelity in Figma. Structure and logic before visual design, every decision justified by user need rather than visual preference.

Prototype

A clickable prototype so the product can be experienced before anything is built. You can walk through it, share it with stakeholders, and request changes while they are still cheap.

Build

My developer partner Matija handles development. I stay involved throughout so nothing gets lost between the design file and the code.

Testing & Launch

Before going live we test the product against real user behaviour. Small things get caught here that save bigger problems later. Then we launch.