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

Which of our efforts actually caused the result?

You did the work. The result came in. Now you sit together, picking through what you did, trying to find which piece mattered. One person says it was the outreach. Another says it was the timing. No one agrees, because no one wrote down what they expected before it happened. This is not a result problem. You got a result — that part is done. The real problem is that your team never named the bet. You never wrote, before you acted, what you believed would work and why. Without that, every win looks like luck, and every loss looks random. What is in your power now is simple. You cannot go back and fix the last project. You can choose, together, to never run an effort again without naming your bets first.

◆ 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 mostly behavior change — teams need less teaching about why and more practice naming bets together before they act.
How the two dials adapt to you →
What’s really going on

You cannot find the cause after the result arrives — by then you will only invent one. Before your next effort, gather your people and write down what each of you believes will drive it. Name the bet before you place it. Then you will have something to test, not a story to believe.

🔒 What you’ll build togetherUnlock by starting
A moveBefore your next project begins, have each person write down what they believe will drive the result.
A moveRank those beliefs — which factor matters most, which matters least.
A moveStore the list where everyone can see it, not in one person's head.
A moveAfter the result comes in, compare it to the list before you discuss anything else.
A moveName what matched and what missed — out loud, as a group.
PractiseThe Reckoning · a Pod of 4 · 30 min

What changes unlock by starting

  • You will know, within one cycle, whether your guesses were right.
  • Wins will teach your team something, not just feel good.
  • Losses will show a cause, not just leave a sting.
  • Your team will argue about evidence, not opinions.
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.