Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why can I build any screen but not design the flow?

You can take a finished plan and build it well. Hand you a blank page and ask you to invent the flow, and you stall. That is not a flaw in your talent. Someone else has been doing the thinking for you. You were handed the decisions already made, and asked only to execute them. Of course you never practiced making those decisions yourself. Nobody gave you the chance. This is not fixed alone, at a desk, by staring harder. It is fixed by changing the question your team asks out loud, every time, before a screen gets drawn.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
A little to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The person needs a small amount of teaching (what 'flow thinking' actually means) but mostly needs repeated practice and team habits to build the muscle.
How the two dials adapt to you →
What’s really going on

You are not missing a design skill. You are missing a habit: asking what the person needs next, before you draw anything. Stop starting with the screen. Start with the next decision the user must make. Ask it out loud, with your team, first.

🔒 What you’ll build togetherUnlock by starting
A moveBefore anyone opens a design tool, say out loud as a team: 'After this step, the user needs ___.' Fill the blank first.
A moveList the decisions a person must make, not the screens you must build. Decisions come first.
A movePick one teammate to play the confused user. Walk them through the flow in silence. Watch where they stop.
A moveCut any screen that answers a question nobody has asked yet. If it informs no decision, remove it.
A moveEnd every flow review with one question: 'What does the next person need?' Not 'Does this look good?'
PractiseDecision Before Screen · a Pod of 4 · 30 min

What changes unlock by starting

  • Your team can draft a flow from a blank page, not just a spec.
  • Meetings shift from arguing about looks to arguing about what the user needs next.
  • You catch and cut unnecessary screens before they get built.
  • You stop waiting for someone else to hand you the thinking.
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.