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

The manual ran out. Now what do I do?

You know the manual well. That is not in question. What you have just found is its edge — the place where the book stops talking and the system keeps acting. This is not a gap in your training. It is the gap that exists in every manual, because no one can write rules for every failure. Here is what you are really telling yourself: "I need the right answer before I can act." That is false comfort. You do not need the right answer. You need to look at what is in front of you, test what you can control, and move. The person who wrote the manual was not smarter than you. They just saw this failure first. You have reasoned before, without a manual, many times — you just didn't call it that. You have fixed a broken plan, settled a dispute with no clear rule, decided something on the spot with no one to ask. That is the same muscle. It has not atrophied. You are simply afraid to use it without permission.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
A little to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
The person already has technical knowledge; what's missing is a method and the nerve to use it, so coaching dominates over teaching.
How the two dials adapt to you →
What’s really going on

You are not stuck because you lack a skill. You are stuck because you were trained to match problems to answers, not to think. When the manual ends, your job starts. Stop searching for the missing page. Look at what the system is actually doing, not what it's supposed to do, and reason from there.

🔒 What you’ll build togetherUnlock by starting
A moveWrite down exactly what the system is doing right now, with no interpretation — only what you can observe.
A moveList what you actually control in this moment, and cross out everything you don't. Act only inside that list.
A movePick the smallest safe test you can run to learn something new about the failure, and run it before you theorize further.
A moveState out loud what you would tell a junior colleague to do here — then do that, instead of waiting for someone senior to confirm it.
A moveAfter you act, write one line on what the manual should have said. This is how you build the judgment the next version of you will need.

What changes unlock by starting

  • You can act on an undocumented failure without waiting for permission or a perfect answer.
  • You trust your own observations over your anxiety about not knowing the 'official' answer.
  • You build a habit of testing small instead of theorizing big.
  • You stop treating 'the manual doesn't cover this' as a stopping point, and start treating it as your actual job.

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.