When a client shelves a recommendation you know is right, the instinct is to check the analysis again. Usually the analysis was fine. What's missing is the person who has to act on it — either they weren't part of building the recommendation, or acting on it costs them something they weren't willing to spend.
The analysis is rarely the problem
A recommendation can be well-researched, correctly reasoned, and clearly written, and still go nowhere. That's a hard thing for consultants to accept, because it means the slide isn't the lever. The two things that actually kill a good recommendation happen away from the deck entirely.
Reason one: the person who has to act wasn't in the room
If a recommendation shows up for the first time in a final readout, the person who has to implement it is meeting it cold — at the exact moment they're also being asked to approve it. People rarely commit to something they're seeing for the first time in front of their own boss. Preview the direction with them earlier, even informally, and the final readout becomes a confirmation of something they already helped shape, not a surprise they have to react to publicly.
Reason two: it threatens something they won't say out loud
Some recommendations are ignored because they're politically expensive, not because they're wrong. Consolidating two teams threatens someone's headcount. Cutting a channel threatens the person who championed it. Reassigning a project threatens someone's visibility with their own leadership. Nobody says "I'm blocking this because it shrinks my budget" in a meeting — it just quietly doesn't get actioned. If you know that cost exists before you present, you can address it directly or route around it. If you find out after, you're stuck re-litigating a decision that already happened in someone's head weeks earlier.
This is a stakeholder mapping problem, not a presentation problem
Both failure modes trace back to the same gap: not knowing, early enough, who has the power to slow-walk your recommendation and what they stand to lose from it. A stakeholder map built at kickoff and never revisited only tells you who mattered in week one. The people whose turf gets threatened by a specific recommendation often don't reveal themselves until the recommendation exists — which means the map needs another pass once you know what you're actually going to propose, not just once at the start of the engagement.
Worked example
The recommendation: Consolidate two regional sales ops teams into one, reporting to a single director.
Who has to say yes: The VP of Sales (budget owner) and the director of the smaller team, who loses their standalone reporting line under the new structure.
What went wrong the first time: The recommendation was presented cold in the final readout. The smaller-team director pushed back in the room, the VP sided with caution rather than override their own director in front of the client, and the recommendation stalled.
What changes with earlier buy-in:A 15-minute preview with the smaller-team director a week before the readout, framed around what their new scope looks like post-merge — not just what they lose. By the time the recommendation is presented formally, they've already raised their concerns privately and had them addressed, so the readout confirms a decision instead of triggering one.
None of that requires a better slide — it requires knowing, before you finalize the recommendation, who's going to feel it and bringing them in while it's still forming. The free Stakeholder Mapping Tool gives you a place to track that as the engagement moves, not just as a one-time exercise from kickoff.