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

We can design it. Why can't we build something people can click?

Your mockup is done. It looks right. Every screen sits in place. But nothing moves when someone touches it. Your pod has quietly agreed that's someone else's job. That agreement feels comfortable. It lets you stay on the side marked 'designer' and call the rest 'engineering.' But the line is fiction. You have not built something interactive because you never needed to — not because you cannot. Working with others makes this easier to hide. Someone in your pod waits for someone else to cross first. Choose to be the one who crosses — today, on one screen, not the whole product.

◆ 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
This is less about missing facts than about crossing a line you've drawn yourself, so coaching toward action carries more weight than teaching.
How the two dials adapt to you →
What’s really going on

The line between designer and builder is one you drew — not one that exists. You never needed the tools, so you never picked them up. Choose one small piece of your mockup. Make only that piece click. The gap does not close by deciding; it closes by doing.

🔒 What you’ll build togetherUnlock by starting
A moveChoose one screen from your mockup. Make one button on it do one real thing.
A moveName one person in your pod who owns this — not the whole build, just this piece.
A moveSet a two-hour limit. If it takes longer, you chose the wrong tool.
A moveShow the rough, unfinished version to someone outside your pod before you polish it.
A moveSay the tool's name out loud in your next meeting. Stop calling it 'something interactive.'
PractiseThe One-Screen Build · a Pod of 4 · 30 min

What changes unlock by starting

  • One flow from your mockup that a stranger can actually click through.
  • A named owner for the next interactive piece, not a vague plan.
  • A specific tool chosen, replacing the dread of 'figuring it out.'
  • Real feedback from someone outside the pod, before the whole thing is built.
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.