How do we catch trouble before it breaks, not after?

You are good in a crisis. Something breaks, you find it, you fix it. That is real skill. But it is not the same skill as seeing the break coming. Right now your team watches outcomes — the thing that already failed. By the time you see it, the cause did its work days or weeks ago. You are not slow. You are looking in the wrong place. This is not a puzzle to solve alone at your desk. Your team sees different pieces of the same machine. Sit down together and agree on what to watch before it breaks — not after.

◆ 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

This calls less for new information and more for the shared habit of watching causes together, so guidance leads.

How the two dials adapt to you →

What’s really going on

You already fix what breaks — that isn't the problem. The problem is you watch results, not the causes behind them. Choose three early signals your team checks every week, before an outcome arrives. Smoke spotted early costs an hour. Flame spotted late costs the house.

🔒 What you’ll build togetherUnlock by starting

A moveList the last five fires your team put out. For each one, name what was true a week before — the thing nobody was watching.

A moveAgree together on three leading signals — numbers or signs you can check before failure, not after.

A moveAssign one person to each signal. They report weekly, without being asked.

A moveSet a clear threshold for each signal — the point where you act, before the break.

A moveMeet monthly and ask: did the signal warn us in time? Adjust what you watch.

PractiseSmoke Before Fire · a Pod of 4 · 30 min

What changes unlock by starting

Your team names causes, not just symptoms.
You catch problems weeks before they break, not after.
Everyone shares the same early-warning signals — no more guessing.
Less time firefighting, more time building.

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.