Sketch the flow, not the screen

When a product feels confusing, the instinct is to redesign the screen where people give up. I’ve learned to look one step wider first. The problem is often in the order of things, not in any single page.

So my first sketches are small. A row of rectangles on paper, each one a step, each with a few words about what happens there. No buttons, no type, no color. Just the sequence.

Order changes meaning

Moving a step can matter more than redesigning it. Asking for personal details before showing any value feels like a toll booth. Showing what someone gets first, then asking, feels like an exchange. The fields are identical, but the experience isn’t.

A flow sketch makes these swaps cheap. I can draw an arrow, cross out a box and try a new order in seconds. On screen, the same change would mean rebuilding several frames, so I’d be less willing to try it.

Count the decisions

One habit helps more than any other at this stage. For each box in the flow, I write down the decision the person has to make there. Pick a plan. Confirm an address. Choose whether to invite a colleague now or later.

Seen in a row, those decisions tell a story the screens can’t. Two hard choices back to back is a likely place for people to stall. A step with no decision at all can often be merged into its neighbor or dropped.

It also makes the conversation with engineers and product managers more concrete. We stop debating whether a page looks busy and start asking whether a decision belongs at that moment. That’s a question the whole team can answer.

When to move to screens

I stay on paper until the sequence survives a walkthrough with someone who hasn’t seen it. I talk them through each step and watch where they hesitate. If they ask why something comes before something else, the flow isn’t ready.

Once it holds up, the screens come quickly. Each one has a clear job, because the sketch already decided what it’s there for. The detail work is still hard, but at least it’s spent on the right pages.