Talk it through with Aurelius
Why do complex, cross-team processes still defeat me?
You can map steps, cut waste, assign owners — when the work is yours to command. That skill is real. No one should tell you otherwise. But a process crossing teams is not a design problem. It is a power problem. Each team has its own boss, its own targets, its own idea of finished. Your diagram cannot govern what your authority does not reach. The defeat you feel is not proof you lack skill. It is proof you are trying to solve with a pen what only agreement can solve.
◆ How this problem reads on the two dials
GuidanceKnowledge
1:1 with AureliusWith others (a Pod)
The core insight — design versus authority — needs stating once clearly; everything after that is action, not more theory.
How the two dials adapt to you →What’s really going on
The problem isn't skill. A simple process has one owner: you. A cross-team process has many owners, many incentives, and no one in charge of the whole. No diagram fixes that. You fix it by naming who decides what, before you design anything else.
🔒 What you’ll build togetherUnlock by starting
A moveBefore you draw one box, list every team touched and name who can actually say yes or no for each.
A moveCall a short meeting with one decision-maker per team, not their delegates. Get agreement on the outcome before you argue about steps.
A moveMark every point where the process crosses from one team to another. Assign one named owner to each crossing, not each task.
A moveWhen you meet resistance, ask what that team is measured on. Change the handoff to serve their measure too, not only yours.
A moveSet a review date now. A cross-team process is never right on the first draft. Choose to revisit it, not to perfect it upfront.
PractiseMap the Handoffs · a Pod of 4 · 30 min
What changes unlock by starting
- Within a week you'll know if the block is design or authority, and stop wasting effort on the wrong one.
- Every handoff will have one named owner instead of a vague 'the team.'
- You'll get agreement from decision-makers before spending more hours drawing the process.
- You'll expect friction at each crossing instead of being surprised by it.
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.