Why does coordinating with other teams overwhelm me?

You built your piece. It works. Then another team is late, or silent, or breaks a promise — and suddenly you are not building. You are chasing people, guessing dates, absorbing shocks that were never yours. This is not a personal failing. No one taught you to expect this. You were never given a method for tracking work you do not control. So each dependency arrives as a surprise, and you react like you are under attack. You were not attacked. You were unprepared for something predictable. Here is what is true. You cannot make another team move faster. You can only choose whether you see the delay coming, and whether you have a plan when it does. That is the whole of your work now.

◆ How this problem reads on the two dials

GuidanceKnowledge

More coaching

Some to learn

1:1 with AureliusWith others (a Pod)

Mostly you & the coach

A little with peers

There is a concrete system to teach here, but the deeper block is treating dependencies as attacks instead of information, so guidance carries the weight.

How the two dials adapt to you →

What’s really going on

You have no system for other people's work — that is the whole problem. Build one now. List every dependency you rely on. Name who owns each. Set a date you need it by, not the date promised. Check the list weekly. You do not control their work. You choose whether you see it coming.

🔒 What you’ll build togetherUnlock by starting

A moveList every dependency you have right now — every piece of work you need from someone else to finish yours.

A moveWrite down who owns each dependency and the date you need it, not the date they promised.

A moveSet a fixed day each week to check that list, not just when panic forces you to.

A moveWhen a dependency slips, ask what you will do next, not who is to blame.

A moveSeparate what you can push — a reminder, a deadline, an escalation — from what you cannot: their priorities, their pace.

What changes unlock by starting

A written list of every dependency, so nothing arrives as a surprise.
A weekly check-in habit that catches delays before they become crises.
Less time spent reacting to other teams, more spent on your own work.
A steadier response when something slips, because you already have a next step.

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.