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

Why can I build any screen, but not the flow that works?

You build what is handed to you, and you build it well. That is not nothing. But you call this a gap in skill, and that is a comfortable lie. The skill is there. What is missing is a question you have never been asked to ask. You were trained to execute. Hand you a screen, and you make it work. Nobody trained you to stand where the user stands and ask what they need next. That is not a flaw in you. It is simply a question you have not practiced. You will not learn it by reading more about design flow. You learn it by asking the question, on purpose, on the next real task in front of you — today, not after you feel ready.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
The reframe itself is short and simple; what takes work is building the habit of asking the new question, and only practice builds a habit.
How the two dials adapt to you →
What’s really going on

You are not missing a skill. You have only practiced one question — what was I told to build? Designing a flow asks another — what does this person need next? Stop reaching for your tools. Choose, today, to ask that question before you draw anything.

🔒 What you’ll build togetherUnlock by starting
A moveBefore opening any design tool, write down what the user is trying to accomplish — in their words, not the ticket's.
A moveTrace the flow backward from the user's goal to the first screen, instead of forward from the screen you were handed.
A moveWatch one real person attempt the task you're designing for. Do not explain anything. Just watch where they hesitate.
A moveTake a flow you already shipped and name the question it failed to ask. Write it down.
A moveAt the next decision point in your work, choose to ask 'what does the user already believe here?' before you design anything.

What changes unlock by starting

  • You build the habit of asking what the user needs next, before you touch a tool.
  • You can point to exactly where your current flow assumes knowledge the user doesn't have.
  • You ship one flow this month that starts from the user's goal, not the ticket.
  • You stop confusing 'I can build it' with 'I understand what they need.'
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.