There’s a decision at the C-level that nobody wants to own, so a consultancy gets hired. The consultants recommend, collect their fee, and leave. If the decision later falls apart, it has a convenient home: “That was the consultancy’s recommendation.” Each step in this chain is individually rational. Nobody designed the mechanism. But the steps add up to a structure in which ownership quietly disappears, and product managers are the ones who live with the consequences.
Picture the moment it arrives. A strategy deck lands in your inbox. Forty slides, six weeks of stakeholder interviews, a target operating model, a prioritized initiative list. Everyone involved acted reasonably: leadership wanted rigor, the consultants delivered what was asked. But nobody who built the deck will be in the company three months from now. And it’s now your roadmap.
This isn’t a story about bad executives. It’s a repeatable organizational mechanism. I call it accountability laundering: the process of routing a decision through a third party so that ownership becomes untraceable.
The pattern has three stages:
- Outsource the decision. The engagement is framed as “bringing in expertise,” but it transfers decision authority to people who won’t be present when the decision plays out.
- Accept the recommendation. Leadership adopts the output, often without meaningful internal challenge. Formally, an executive always signs off. But a signature under someone else’s recommendation is ratification, not ownership.
- Disclaim the outcome. When the decision produces problems, no executive owns it. The consultancy is gone. The internal team inherits a strategy they didn’t choose and can’t easily reverse.
The result is a decision that has no accountable owner inside the organization. Not because no one made it, but because the accountability was passed through a structure that makes it disappear. Whether anyone intended that outcome is beside the point. The structure delivers it either way.
Why this matters to product managers
If you’re a PM working inside this pattern, you already know the symptoms. You just might not have named the cause.
Your roadmap isn’t yours. A consulting-driven strategy lands on your desk as a set of priorities you didn’t shape and weren’t consulted on. Discovery becomes decorative. You’re executing someone else’s thesis about your product, built by people who interviewed a few stakeholders for six weeks and left.
Decision authority gets temporarily exported, then permanently lost. While the consultancy is engaged, internal teams defer. “Let’s wait for the recommendation.” After the consultancy leaves, the recommendation hardens into doctrine. Challenging it means challenging the investment that leadership already made, which reads as disloyalty rather than product judgment.
You escalate against a document, not a person. When the recommendation conflicts with technical constraints, compliance requirements, or customer realities that only your team understands, there is no one to have the trade-off conversation with. The people who made the decision aren’t in the room anymore. You end up arguing with a slide deck, and slide decks don’t negotiate.
Team morale erodes quietly. Engineers and designers who watched a consulting team override months of internal discovery learn the lesson fast. Their work doesn’t carry weight. The next time you try to run genuine discovery, the engagement will be lower. Why invest in building conviction internally if an outside firm can overwrite it?
How to recognize the pattern early
Not every consulting engagement is accountability laundering. External expertise is sometimes genuinely needed: regulatory shifts, market entry into unfamiliar territory, capability gaps that don’t exist internally. The question is whether the engagement is structured to build internal capability or to replace internal judgment.
Three signals that an engagement is being used as an accountability shield:
The scope is decision-shaped, not knowledge-shaped. If the consultancy is hired to recommend what to do rather than to help the organization understand something it can’t understand alone, the engagement is structured to produce a decision that leadership can adopt without owning.
No internal decision-maker is named. A legitimate engagement has a named executive who will own the final call and the outcome. If the engagement ends with “the consultancy recommends X” and no one internally says “I am choosing X and here’s why,” you’re watching ownership evaporate in real time.
The recommendation bypasses existing product evidence. If your team has discovery outputs, customer data, or domain expertise that contradicts the consultancy’s direction, and no one asks you to present it alongside their recommendation, the engagement isn’t seeking the best answer. It’s seeking a defensible one.
What you can do inside the pattern
You probably can’t stop the engagement. You can make it structurally harder for accountability to disappear.
Document your position before the decision lands
If you have a perspective on the strategic direction, write it down before the consultancy delivers. Date it. Share it with your lead. This isn’t about being right. It’s about having a traceable record that internal product judgment existed and was either considered or ignored. When the consulting-driven decision fails in a year or two, the question will be “why didn’t anyone see this?” Your document is the answer, the same mechanism I describe in Make Blockers Impossible to Ignore.
Insist on named ownership at the handoff
When the consultancy presents its recommendation, ask one question in the room: “Who owns this decision going forward?” Not who sponsors the project. Not who manages the rollout. Who is accountable for the outcome. If no one answers, you’ve surfaced the accountability gap in front of witnesses. If someone answers, you’ve created a commitment.
Be clear about what this costs. Asking it in front of leadership marks you as someone who notices. That is exactly why it works, and why you should decide beforehand whether you can afford it.
Map the recommendation against your existing evidence
Take the consultancy’s output and formally map it against your discovery findings, customer data, and known constraints. Document where it aligns and where it conflicts. Present this mapping to your stakeholders. You’re not fighting the recommendation. You’re making the trade-offs visible. If leadership proceeds anyway, they’ve done so with full information, and that’s documented too.
Protect your team’s decision space
Consulting recommendations tend to be broad. They describe strategy. They rarely describe implementation. Claim the implementation space explicitly. “We’ll execute within this strategic direction, and we’ll own the sequencing, scoping, and trade-off decisions within it.” This preserves real product authority where it matters most: in the details that determine whether the strategy actually works.
The real cost is invisible
The financial cost of consulting engagements is visible on a balance sheet. The accountability cost is not.
Every time a decision gets laundered through an external party, the organization loses a learning cycle. When an internally owned decision fails, the team learns: what assumptions were wrong, what signals were missed, what should change next time. When a consulting-driven decision fails, the organization learns nothing. The consultancy isn’t there to do the retrospective. The executives who adopted the recommendation have no incentive to examine why. The failure becomes an orphan.
Over time, this creates organizations that repeat the same strategic mistakes, each time with a different consultancy’s logo on the slide deck. The pattern isn’t that consultants give bad advice. It’s that the structure prevents the organization from learning from any advice, good or bad, because no one is positioned to own the feedback loop.
The uncomfortable question
If your leadership team consistently hires consultancies to make decisions that executives should own, the problem isn’t the consultants. It’s the accountability culture. Consultants are a symptom.
The question for you as a PM is whether you’re operating inside a fixable pattern or a permanent one. If leadership occasionally uses external support and you can create the documentation and ownership structures described above, you can navigate it. If every major decision gets routed through an external party specifically so that no one internal has to commit, you’re not in a consulting problem. You’re in a leadership problem.
And leadership problems don’t get solved by better documentation.
They get solved by recognizing when accountability has left the building and deciding how long you’re willing to work in the space it left behind.