Talk it through with Aurelius
How do I run a meeting that actually decides something?
The meeting happens, everyone talks, it ends on time and nothing is settled. Two weeks later you are having it again with the same people.
◆ How this problem reads on the two dials
GuidanceKnowledge
1:1 with AureliusWith others (a Pod)
CRAFT. Decision-shaped invite, a named decider, and a closing ritual. All knowable form. A self-aware manager who has never seen it done will still hold a discussion that reconvenes.
How the two dials adapt to you →What’s really going on
A meeting that decides is built differently from one that discusses, and almost all of the difference is in the invite and the last two minutes.
🔒 What you’ll build togetherUnlock by starting
KnowledgeA meeting has a decision or it has no reason to exist
KnowledgeEnding it so the decision survives contact
A moveAsk whether the meeting exists to decide or to spread the risk of deciding. Both happen; only one is fixable with structure.
What changes unlock by starting
- Your invites name the decision and the decider.
- You close by reading back the decision, the owner and what was not decided.
- Meetings with no decision get cancelled rather than held.
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.