They assume that if you plan thoroughly enough, sequence tasks correctly, and manage dependencies properly, the initiative will unfold as designed. They treat obstacles as variables to be managed, not as hostile forces actively working against you.
This works fine for building a house. It fails catastrophically for organizational initiatives.
The Controlled Environment Fallacy
Traditional PM gives you frameworks for:
Defining scope (as if it won’t be challenged)
Sequencing work (as if dependencies stay stable)
Allocating resources (as if they won’t be pulled mid-flight)
Managing stakeholders (as if they’re neutral parties to be “engaged”)
Every parenthetical is where reality intrudes.
Scope doesn’t stay defined. The CFO adds requirements. Marketing discovers a “critical” feature. Legal raises concerns that reshape the design. These aren’t scope changes to be controlled through a change board. They’re political moves by actors with their own objectives.
Resources don’t stay allocated. Your best architect gets pulled to fight a production fire. The budget gets raided when another initiative goes over. Executive attention vanishes when a larger crisis erupts. You’re not managing resources. You’re defending them.
Stakeholders aren’t waiting to be engaged. Some want your initiative to fail because its success threatens their position. Others publicly support you while privately undermining you. A few genuinely want to help but lack the power to deliver on their promises.
The Gap
This is the gap between PM theory and PM reality: the gap between peacetime logistics and wartime operations.
Peacetime logistics assumes cooperation, stability, and shared goals. You’re moving supplies from Point A to Point B in a controlled environment.
Wartime operations assume the presence of opposition, uncertainty, and conflicting interests. You’re moving supplies while someone’s trying to stop you, conditions are changing, and your own side isn’t fully aligned.
Most methodologies are designed for peacetime. What if you’re operating in war?
They give you tools to manage timelines. They don’t teach you to read organizational politics. They give you frameworks for risk. They don’t teach you to identify who benefits from your failure. They provide you with governance. They don’t teach you when to bypass it.
Active Opposition
Every initiative faces internal politics: functions protecting territory, individuals protecting careers, leaders hedging commitments until winners emerge.
Every initiative faces environmental hostility: market shifts that invalidate assumptions, regulatory changes that force redesigns, and technological disruptions that make your approach obsolete mid-build.
Every initiative faces friction: complexity that compounds, misalignment that spreads, information that distorts as it moves through organizational layers.
These aren’t project management problems. They’re campaign challenges.
What Becomes Visible
Once you accept you’re in battle, the forces shaping your initiative become visible – and addressable.
You stop asking “How do we get back on plan?” and start asking “What’s actually happening, and how do we adapt?”
You stop treating politics as a dysfunction and start treating it as terrain to navigate.
You stop adding process and start concentrating effort where it matters.
The following posts examine these forces: misalignment, uncertainty, change, chaos, complexity, the human dimension, politics, market evolution, and the art of reading conditions that no status report reveals.
Name the forces. Lead accordingly.
Tomorrow Morning
Review your last status report and circle everything that reflects optics rather than reality.
Identify one dependency you are “managing” that is actually being defended politically.
Ask one direct question that your methodology avoids, but your initiative depends on.
















