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

We have the frameworks. Why do we still choose wrong?

You and your team have read the same books. You know the matrix, the pros-and-cons list, the test for what can be undone. And still, in the room, you stall. Or you argue about which tool fits, while the actual decision waits. This is not ignorance. You are not missing a framework. You are skipping the step that comes before any framework: naming, out loud, together, what kind of decision this is. The tool was never the hard part. Agreeing on what you are deciding — that is the hard part. Fix that first, and watch how much of the argument disappears.

◆ 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
They already hold the frameworks; what's missing is the practiced habit of sequencing — so this leans heavily toward coaching, not teaching.
How the two dials adapt to you →
What’s really going on

You do not lack a framework. You lack the discipline to name the decision before you reach for one. Stop grabbing a tool out of habit or comfort. Ask first: what kind of decision is this? Reversible or not. Fast or slow. Then the tool picks itself.

🔒 What you’ll build togetherUnlock by starting
A moveBefore any framework talk, say out loud as a group: reversible or not, fast or slow, mine or ours.
A moveAssign one person each meeting to ask 'what kind of decision is this' before anyone proposes a method.
A moveWhen the group fights over process, stop and check whether the real fight is about values, not tools.
A movePick one default framework for your most repeated decision type. Stop reinventing it every time.
A moveAfter each decision, write one line: what framework you used, and whether it actually fit.
PractiseName the Decision · a Pod of 4 · 30 min

What changes unlock by starting

  • Less time spent arguing about method, more time spent deciding.
  • A shared first step the whole team takes before any framework is chosen.
  • Fewer repeated fights that were really about values wearing the mask of process.
  • A short written record showing which frameworks actually serve your team's real decisions.
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.