Planning theater: Where great strategies go to die

In boardrooms and project war rooms alike, the spotlight often falls on methodologies and people skills. Agile ceremonies, leadership models and culture change take center stage. These are vital — but they are not enough. In the shadows, the less glamorous but crucial players — constraints and dependencies — quietly determine whether the project succeeds or fails.

This isn’t just an agile story. The same physics apply to Waterfall programs, hybrid portfolios, construction, IT infrastructure and marketing transformations. The math — resources, timelines, budgets, sequencing, risk — defines the boundaries within which people and methods operate. Ignore it, and you’re staging a production without a script. Even worse, in today’s volatile political, operational and environmental climate, the script keeps changing as the play unfolds. Without the ability to see and re-solve the math in real time, even the best playbook becomes planning theater — polished decks, confident updates, disappointing outcomes.

I’m going to lay out a practical, cross-method view of the structural layer leaders must re-center: What constraints and dependencies really mean, why dynamic (not static) management is now a prerequisite, and how to embed this discipline into an operating model. I’ll ground it with a composite SAP S/4HANA case, then close with a C-suite checklist you can use Monday morning.

The universality of constraints and dependencies

Constraints are the hard boundaries of execution. PMI’s PMBOK highlights scope, schedule, cost, quality, resources and risk as core constraints; I add benefits as the strategic constraint that keeps outcomes tied to value. Constraints are not negative; they are design parameters. Fixed regulatory dates, a capacity ceiling for scarce skills, a funding envelope and an immovable site‑access window — all legitimate constraints that should inform strategy, not silently undermine it.

Dependencies are the connective tissue — the relationships that dictate order and coupling. Classic forms include finish-to-start (FS), start-to-start (SS), finish-to-finish (FF) and start-to-finish (SF). But in enterprise reality, I find five dependency families most useful:

1. Logical (one thing must precede another; design before build)
2. Resource-based (shared SMEs or equipment create queues)
3. Technical (interfaces, data models and integration points)
4. Decision/authority (approvals, funding, governance gates)
5. External (vendors, regulators, utilities, shipping lanes)

Across agile, waterfall and hybrid contexts, these mechanics don’t change. Sprints don’t nullify a cold‑start dependency on a third-party API; a Gantt chart doesn’t conjure a missing cybersecurity clearance. Methodologies describe how we work; constraints and dependencies define what is feasible and in what order.

Why you must manage the math in real time

In quieter eras, quarterly replans and annual budgets were tolerable. Today, they’re inadequate. Three forces make real-time management non-negotiable:

1. Political and regulatory volatility. Export controls, data‑sovereignty rules, sector-specific mandates — any of these can flip a “green” plan to “red” in a week. Being able to model the downstream impact on schedule, cost, sequencing and benefits is the difference between a controlled pivot and a nine-month delay.
2. Operational and supply uncertainty. Vendor bankruptcies, logistics shocks, skills shortages and strike actions quickly invalidate static plans. If your modeling horizon moves at the speed of your steering committee calendar, you are reacting with a lag.
3. Environmental events. Extreme weather, wildfires and grid outages increasingly affect site access, construction windows, data center cooling and shipping lanes. These are not theoretical risks; they are constraints you can quantify and plan against — if your system updates in near‑real time.

Real-time structural planning enables three decisive capabilities:

• Instant impact modeling. “If this supplier slips by two weeks, what happens to the cutover? To the marketing launch? To cash‑flow?” You need the answer in minutes, not at next month’s checkpoint.
• Pre-commit scenario testing. Before approving a scope change or budget shift, leaders should see the best‑feasible, most‑likely and worst-case structural outcomes side by side.
• Rolling re-optimization. As actuals replace assumptions, the plan should recompute the critical path, resource queues and milestone feasibility automatically. If finance can run rolling forecasts, transformation should too.

Bottom line: the math is not a one-time calculation — it’s a live system.

The math defined (without jargon)

To work the problem, align on terms:

• Schedule constraint: immovable window (regulatory date; holiday blackout). Use tolerances where possible.
• Capacity constraint: practical throughput of key roles, plants or platforms. Look at effective capacity, not headcount.
• Budget constraint: funding envelope and phasing (cash timing matters as much as totals).
• Scope constraint: the non‑negotiable outcomes; keep a list of deferrable items.
• Quality constraint: acceptance standards and compliance thresholds that can’t be traded away.
• Risk constraint: how much uncertainty we will accept; binds scenario choices.
• Benefits constraint: the floor for value; if eroded below tolerance, stop or pivot.
• Dependency set: the graph linking work, decisions and externalities; measured not just in count, but in criticality and coupling.

Leaders should see these on one page, refreshed weekly: where we are breaching tolerance, which dependencies have become critical, and which mitigation buys the largest benefit per dollar or day.

Composite case: The S/4HANA domino effect

GlobalCo (a composite of real programs) is a diversified manufacturer/retailer. The board funds a three‑year portfolio with four streams:

1. SAP S/4HANA is replacing ECC across finance, procurement and manufacturing
2. Marketing transformation: global rebrand and e-commerce refresh
3. Operations: plant digitalization and predictive maintenance rollout
4. IT foundation: cloud landing zones, identity modernization, zero trust

Planning posture. The PMO builds a meticulous integrated plan. Workstreams choose methods: Agile for digital products, stage‑gate for ERP core and hybrid for plants. Dependencies are captured in worksheets and a shared Confluence. The plan looks airtight.

What was missed? The dependency map was static and under‑weighted in governance. Four realities converge:

• Master data dependency. The rebrand and e-commerce refresh require stable product and pricing data. S/4 pricing condition records won’t be stable until data cleansing is complete. Cleansing is six weeks late because the data team is also supporting a statutory reporting change.
• Architect capacity bottleneck. The same three integration architects are critical for S/4 interfaces and identity modernization. Their calendars look fine on paper until two go on unplanned leave. Queue times double; the critical path shifts unnoticed.
• External dependency shock. A third-party tax engine vendor faces a certification delay in one region, blocking integration tests for invoicing. The knock-on effect: Finance cannot enter a parallel run as scheduled, which blocks plant cutover approvals.
• Regulatory constraint. A new sustainability reporting rule brings forward the deadline for Scope 3 data capture, diverting analytics engineers and pushing the data lake sprint that feeds S/4 analytics off the rails.

The symptoms. Agile teams report strong velocity. Stage‑gates show green until the week they don’t. Leadership wonders why “everything was on track” right up to the slip. Morale sags. Vendors ask for change orders. Two markets delay the rebrand because price files are unreliable. A plant postpones its cutover window because testing is incomplete.

The cost. Nine months of delay across the portfolio; 22% budget overrun; lost seasonal revenue in two markets; and opportunity cost as other initiatives queue behind the ERP cutover.

The pivot. The COO sponsors a “control tower” for structural planning with three mandates:

1. Live dependency graph. Replace static sheets with a single model ingesting Jira, MS Project and SAP test data. Each dependency gets an owner, SLA, criticality score and visual heat.
2. Weekly scenario cadence. Every Thursday, the tower runs three simulations: “slip vendor tax engine by two weeks,” “lose one architect for ten days,” and “bring forward sustainability reporting again.” For each, the model recomputes the critical path, capacity queues and cost/benefit of mitigations.
3. Funding flexibility. Finance agrees to a modest “adaptive envelope” that can be tapped to accelerate mitigations (backfill a scarce architect; extend parallel run capacity; bring in a data‑cleansing surge team) if the model shows the move pays back within the quarter. 

The results. Within six weeks:

• The team decouples the brand launch in two markets by standing up a temporary pricing service that reads from the old ERP while S/4 cleanses catch-up; risk accepted, value realized.
• A contractor pod absorbs lower-value integration work, protecting critical architect time for the identity cutover and S/4 interfaces. Queue times drop 35% in three sprints.
• Finance re-phases parallel run: one region enters early to de-risk, while another slips to align with the tax‑engine certification. The model shows a net positive cash‑flow effect despite deferral.
• Plant A keeps its cutover window by borrowing automation testers from the digital stream for ten days, paid back by pausing a noncritical feature.

The portfolio is still three months late, not nine. Overrun lands at 8%, not 22%. Crucially, leadership regains confidence because the plan stops pretending and starts computing.

What mattered most: not a different methodology, but a different relationship to the math — from static documentation to live, decision-grade modeling.

Cross‑domain snapshots (same math, different costumes)

• Construction. You cannot pour before inspection. Weather is a schedule constraint; concrete is a supply constraint; crane time is a resource constraint. A single deferred permit can ripple through twenty subcontractors unless dependencies are mapped and alternative sequences pre-approved.
• IT cutover. Go‑live windows are real; rollback plans are constraints. Identity and networking are technical dependencies with zero tolerance for surprises. A single firewall change control can stall five teams unless authority-based dependencies are visible and time-boxed.
• Marketing transformation. Campaign timing depends on product availability, legal review and channel inventory. Without a live dependency map, spend lands in periods when supply is constrained or pricing is unstable — burning budget with no benefit.

From planning theater to structural mastery: the playbook

1) Establish a control tower (small, ruthless, data‑literate)

Mandate: keep constraints and dependencies live, accurate and visual; run scenarios; recommend mitigations with ROI. This is not bureaucracy; it’s an air‑traffic function.

2) Build the single structural model

Unify data from PPM/PMO, Agile boards, ERP, HRIS, vendor portals and testing tools. Track not just dates, but queues and throughput for scarce roles. Show slack and coupling explicitly.

3) Institutionalize scenario cycles

Weekly fifteen-minute “what‑if” reviews: top three plausible shocks; their computed impact; the cheapest effective mitigations. Decide. Move. Include the executives/owners.

4) Make funding adaptive

Create a modest, pre-approved mitigation fund. Tie releases to modeled payback (e.g., “$180k for a surge data‑cleansing squad avoids $1.2M seasonal loss”). Finance will support agility when the math is transparent.

5) Design for decoupling

Organize around value streams, invest in modular architecture and create temporary shims where full decoupling isn’t yet possible. Every dependency you remove multiplies speed.

6) Elevate structural literacy

Teach leaders to read the dependency graph like a P&L: understand critical path, coupling and queueing effects. Reward teams for surfacing hard constraints early.

7) Measure structural health

Add metrics: dependency lead time, constraint breach count and burn‑down, effective capacity vs. plan, scenario coverage, and time‑to‑pivot. Celebrate reductions the way you celebrate cycle time.

Executive readiness checklist (10 questions)

1. Do we maintain a single, live constraint and dependency model across all major initiatives?
2. Can we simulate the impact of a vendor slip, a funding cut or a regulatory change within hours?
3. Do funding and staffing decisions reference modeled payback, not anecdotes?
4. Are authority-based dependencies (approvals, design reviews) visible with SLAs?
5. Do we track effective capacity (after meetings, PTO, context switching), not just headcount?
6. Are external dependencies (vendors, regulators, utilities) owned with escalation paths?
7. Do we run a weekly scenario cadence with decisions recorded and acted upon?
8. Is there a mitigation envelope we can deploy rapidly when the model justifies it?
9. Do leaders routinely challenge coupling and reward decoupling work?
10. Do we measure structural health alongside delivery velocity and financials?

If you answered “no” to more than three, you likely have pockets of planning theater.

Conclusion: Lead beyond the frameworks

Frameworks and leadership give you speed and alignment. Structural clarity gives you feasibility. In unsettled times, leaders who can see, simulate and steer based on constraints and dependencies will outperform — because they’re making decisions in the world as it is, not as the slideware imagined.

This is not an argument against Agile or a plea for more bureaucracy. It’s a call to put the math on the table, in real time, for every major effort — ERP, construction, IT, marketing, operations. When you do, meetings get shorter, choices get clearer and outcomes get measurably better. That is how you retire planning theater and deliver durable transformation.

Sources and further reading

• PMI — PMBOK® Guide, Seventh Edition: foundational definitions of constraints, risk and dependency types.
• McKinsey — research on organizational agility, scenario planning and resilience in volatile contexts.
• Bain & Company — scenario-based planning and funding agility; linking structural discipline to EBIT improvement.
• Boston Consulting Group — dependency management, modularity and the agility‑profitability nexus across large programs.

This article is published as part of the Foundry Expert Contributor Network.
Want to join?