Talk it through with Aurelius
How do I delegate without it coming back wrong?
You hand something over and it comes back not quite right, or it comes back to you entirely. So you start keeping the things that matter, and your week fills up again.
◆ How this problem reads on the two dials
GuidanceKnowledge
1:1 with AureliusWith others (a Pod)
CRAFT, strongly. Five levels of authority and a checkpoint rule. The common failure is ambiguity about how much rope was handed over, which no amount of self-knowledge resolves.
How the two dials adapt to you →What’s really going on
Work comes back wrong far more often because the authority was never stated than because the person could not do it. Name the level out loud and most of the rework disappears.
🔒 What you’ll build togetherUnlock by starting
KnowledgeName the level of authority you are handing over
KnowledgeThe check-in that is not a takeover
A moveAsk whether you are keeping the work because it is risky or because you are good at it. Only one of those is a reason.
What changes unlock by starting
- You state the level of authority when you hand work over.
- You set the checkpoint at hand-off rather than when you get anxious.
- You can intervene without quietly reclaiming the work.
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.