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

Why do I freeze on a bug no one has shown me?

You and your team hit a failure no one has seen before. Everyone waits. Someone hopes a braver or smarter person will speak first. This is not a skill gap. It is a habit of waiting for permission to think. A known bug is recognition — you have seen its shape before. An unknown one is not recognized, it is built, step by step. You narrow the space. You test one thing. You write down what you learn, so your pod does not repeat your steps. This is a craft, not a gift. Anyone can learn it, including you, including this team. But only if you stop treating confusion as proof you are unfit, and start treating it as the first fact to work with.

◆ How this problem reads on the two dials
GuidanceKnowledge
Coaching
More to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
There is a real, teachable method for narrowing unknown failures, but the harder work is coaching people past the freeze and into shared practice.
How the two dials adapt to you →
What’s really going on

You do not lack skill. You lack a method for the unknown. A pointed-to bug only needs memory. An unknown failure needs a process: narrow it, test one guess, record what you learn. Stop waiting to recognize the problem. Choose the first question you can answer, and ask it now.

🔒 What you’ll build togetherUnlock by starting
A moveBefore touching anything, write down what you expected and what actually happened.
A moveCut the system in half. Find out which half still contains the failure.
A moveSay your current guess out loud to your pod before you test it.
A moveChange one thing at a time. Note the result before changing the next.
A moveOnce you find the cause, write the three steps that led you there, for whoever hits this next.
PractiseNarrow the Unknown · a Pod of 4 · 30 min

What changes unlock by starting

  • You have a first concrete move within a minute of an unfamiliar failure.
  • Your pod narrows problems together, instead of stalling for an expert.
  • You stop treating 'I don't recognize this' as 'I can't do this.'
  • Your team builds a shared record of failures and the paths that solved them.

Related problems

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.