Strategy gets lost before it reaches the project

You get handed a project that sounded perfectly clear upstairs and makes no sense down here. Nobody lied and nobody got a single step wrong. What happened is that the strategy came apart on its way down, and that has a recognizable shape.

Strategy does not fail all at once

On 7 October 2026 PMI published a post by Denise Jarvie that puts it plainly. What executives read as an execution problem is usually an organizational capability problem, because strategy loses coherence as it travels.

The sentence that organizes everything else is that the breakdown happens in four predictable places. Not a different one each time, but the same four.

The four breakdown points come from the post PMI published on 7 October 2026.

Purpose does not travel with the strategy. The plan leaves with clear intent and the why stays behind. Each function reads the message its own way, priorities multiply and local objectives compete with enterprise ones. Teams end up watching activities and deliverables instead of the outcome the strategy was after. The brutal part is that nobody decides badly, because everyone makes reasonable calls with their own context and the sum pulls in different directions.

Those closest to the work decide least. Critical decisions sit far from the front line, exactly where the problems get noticed first. Teams have to respond to changing conditions while waiting for an approval or a governance review. Learning slows, opportunities pass and risks grow unwatched until fixing them gets expensive.

The operating model works against it. Growth strategies get designed on structures built for stability. Budgets reward annual planning even when priorities change quarterly, and each function optimizes its own. So leaders believe people are resisting, when people are constrained by a system built for a different reality.

People do not say what they know. Adapting depends on learning, and learning depends on somebody daring to say what they see. If delivering bad news is costly, assumptions go unchallenged and leadership receives a filtered version of reality instead of reality.

The figure PMI puts on top of it

Inside the first point there is a number worth keeping. According to PMI research, net project success scores swing from minus 18 with no clear vision to plus 41 when the vision is well defined.

The post attributes those two figures to PMI research without naming the report, so they are quoted the same way here, with no year or sample they do not have. What it does name is the study behind the general thesis, Closing the Change-Readiness Gap.

Where this shows up in the exam

None of the above is in your hands as a project manager, and yet the outline asks you to do something about it.

In the July 2026 outline, the Business Environment domain weighs 26 per cent, a move we covered in full in the Business Environment post. Its seventh task is called support organizational change and it has only two enablers. Assess organizational culture, and evaluate the impact of organizational change on the project and determine required actions.

Two enablers for a subject this size looks like very little, and that disproportion says exactly what you need to understand. The outline is not asking you to fix the operating model or redistribute decision authority. It is asking you to read the culture and translate the change into project actions.

What is yours and what is not

That is the distinction between a correct answer and a heroic one. Redesigning the company’s governance is not yours, and an option that has you doing it is almost always out of scope.

What is yours is the first enabler read seriously. Assessing the culture means knowing whether bad news can be spoken here, how long a decision takes and how far your team can move without asking permission. And the second means that once you know, you change something in the project, the engagement plan, the reporting cadence, the agreed escalation path.

That is where it joins up with the three stakeholder tasks, because the purpose that got lost along the way comes back in concrete conversations with concrete people, not in an announcement.

What it looks like in a question

The scenario describes a reorganization under way, a team receiving contradictory priorities from two functions and a sponsor insisting on the date. The options offer escalating, replanning, asking leadership to clarify the priorities, or evaluating how the change affects your project and adjusting accordingly.

The last one is what matches the outline, and the other three feel more decisive. Asking leadership to clarify is not wrong in real life, but in the exam it is handing the problem back. Evaluate and adjust is the verb the enabler uses.

PMBOK 7 looks at the same thing through outcomes rather than tasks, and that is in the eight performance domains.

The four breakdowns are not four problems, they are one seen from four sides, which is that the organization cannot hold itself together while it moves. Your project is the last place that shows and the first place it gets paid for.

Join the waitlist

At The PM Architect we write the PMBOK study guides in five languages, with real classroom cases and exercises that come with an explanation. They will be free. Leave your email on the home page and we’ll let you know the moment they’re ready.