top of page
The Strategy eXecution Forum logo

🔮 Dependency Readings 🔮 - Dependency Management

Writer: Ben Chamberlain
Ben Chamberlain
5 days ago
2 min read

Nobody documented the dependencies. So we hired a psychic.


Every organization has one.


The person everyone goes to when they want to know whether their initiative depends on anything. They close their eyes, sense that one team needs something from another, and nod knowingly. They know because they happened to be in the right hallway conversation a few months ago. Nobody wrote it down.


Cartoon of a psychic in a turban and starry cloak reading a crystal ball full of linked boxes at a Dependency Readings table while worried colleagues with binders line up and an empty binder lies open

That is how dependencies are managed in many organizations. Initiatives are approved in isolation, each with its own plan, and the connections between them live in people's heads, in side conversations and in assumptions nobody said out loud. You have to be a mind reader to find them, and what can't be found can't be accounted for or tracked.


So the conflicts surface at execution, when the cost is already unavoidable. Two initiatives need the same people, the same systems, the same moment of the business's attention. One quietly waits on another that nobody knew it was waiting for. The portfolio overcommits, gridlock builds in the background, and the psychic gets another line of worried visitors.


This is where Principles 5, 6 and 9 work together.


  • Principle 5, Capture & Qualify All Demand, captures dependencies first, when a request enters the pipeline and is assessed.

  • Principle 6, Continuously Optimize the Strategic Roadmap, surfaces the critical ones on a living, multi-year, rolling roadmap, visible across initiatives, teams and the operating fabric of the business before they become execution conflicts, and weighs interdependency alongside alignment, return and risk whenever investment is rebalanced.

  • Principle 9, Empower Execution & Drive Change, then tracks them throughout delivery, so a dependency that shifts is seen early and not discovered by surprise.


Retiring the crystal ball does not mean documenting every task level link. It means making the critical dependencies visible, shared and tracked, so they are managed on purpose and not by luck.


The 10 Key Principles aren’t something we came up with on our own. They’re being defined in the open by the StrategyXF community, multi-disciplinary leaders and practitioners across Strategy, Operations, Finance, HR, Architecture, Transformation, PMO, Delivery, and Change Management, naming the real challenges holding organizations back and sharing what’s actually worked.


Be honest. Does your organization have a dependency register everyone can see, or a person everyone calls?👇



StrategyXF Painfully Accurate Series (Sad, but True!)

This cartoon is part of Painfully Accurate, a StrategyXF series built from real Strategy Execution challenges our members have actually lived through, laughed about, and found a way past.

StrategyXF Painfully Accurate Series (Sad, but True!)

This cartoon is part of Painfully Accurate, a StrategyXF series built from real Strategy Execution challenges our members have actually lived through, laughed about, and found a way past.


Every scene started as something a leader or practitioner described, not a hypothetical, an actual moment somebody in this community said out loud and everyone else in the room recognized instantly. Sad but true, every one of them, and every one of them survivable.


If any of this feels a little too familiar, you're exactly who this community was built for. Join StrategyXF and help us turn these shared war stories into the practical, personalized strategies that finally put them behind us.


bottom of page