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

I can follow the audit steps — so why don't I know what to test?

You and your pod can walk the program line by line without missing a step. You tick every box. And still the work feels hollow, because the program was written by someone else, for a case that was not yours. The steps point at something. They were built by people who once asked, for this exact spot, what could go wrong. You are following their answer without asking their question. That is the gap — not a knowledge gap, a courage gap. Asking "what could fail here" means admitting you might find something. You will not close this gap alone, and you should not try to. A pod exists so that one person's blind spot is another's obvious question. Bring your doubts to the table instead of hiding them behind a finished checklist.

◆ 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
The concept of risk-based testing is simple to state, so the real work is practicing the judgment through repeated, guided attempts with others.
How the two dials adapt to you →
What’s really going on

You test what can fail and cost someone something. The program tells you where to stand; it cannot tell you what you're looking for. Stop asking what the checklist wants. Ask what could go wrong here, and who pays if it does. That question, not the list, is the audit.

🔒 What you’ll build togetherUnlock by starting
A moveBefore opening the program, write down in one sentence how this business makes its money — then ask what could stop that.
A moveFor each line item, say out loud: 'what would someone have to do, or fail to do, for this number to be wrong?'
A moveWith your pod, name three risks each, then argue down to the three you actually believe matter.
A moveChoose the test that would embarrass you most if you skipped it — not the easiest one on the list.
A moveAfter every audit, write down one risk the program never mentioned. That list is yours now, not theirs.
PractiseName the Failure · a Pod of 4 · 30 min

What changes unlock by starting

  • You stop treating the program as the answer and start treating it as a starting point.
  • Your pod catches risks no single member would have found alone.
  • You can explain, in plain words, why you tested what you tested.
  • You build your own growing list of risks the standard program misses.
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.