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

What do we do when the manual doesn't cover the failure?

You followed every step. Then the hardware broke in a way the guide never mentioned. Now your team stands there, looking at each other, waiting for someone to know the answer. Here is the truth: the guide was never the real skill. Reading steps is easy. Diagnosing the unknown is the work you were actually hired to do. A guide only covers what someone already knew to write down. When it fails to cover your problem, that is not bad luck. That is simply where your job begins. Your pod does not need a smarter guide. It needs a method for thinking together when no guide exists.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
This problem is less about missing facts and more about having a shared method and the nerve to use it, so coaching leads.
How the two dials adapt to you →
What’s really going on

You do not need a guide for every failure. You need a method for failures guides don't cover. Stop hunting for the missing page. State what you see. State what you expected. Find the gap between them. Do this aloud, together — the fix comes faster than any manual.

🔒 What you’ll build togetherUnlock by starting
A moveGather the pod and state only what you observe — the exact symptom, no guesses, no blame.
A moveSplit the hardware into testable parts. Choose one part each person will rule out, and test only that one.
A moveName one person to write down every test and result, so the team never repeats a dead end.
A moveBefore anyone searches online, make each person say one hypothesis out loud. Think first, search second.
A moveSet a 20-minute limit. When it ends, report what you've ruled out and choose the next move together — don't drift alone.
PractiseIsolate the Fault · a Pod of 4 · 30 min

What changes unlock by starting

  • Your pod stops waiting for one expert and starts reasoning together.
  • You build a method that works on the next undocumented failure too, not just this one.
  • You find the fault faster, because the search is organized, not frantic.
  • The team trusts its own judgment instead of hunting for a missing page.

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.