The most failure-prone parts of a change program are routed to the departments that opposed it, and the misses that follow discredit those critics and every objection they raise afterward.
An example
For six months the head of estimating at a commercial construction firm had argued against a new project-controls platform, citing its weak handling of change orders. Once the executive committee approved it anyway, the chief operating officer announced that estimating would lead the hardest part of the migration, converting eleven years of historical bid data, "since they know the data best." The two workstreams with clean data went to teams that had backed the platform. Estimating's conversion ran four months late and lost cost codes on forty projects. At the next executive meeting, when the head of estimating raised a concern about the platform's change-order module, the chief operating officer noted that estimating had yet to finish its own piece of the rollout. Nobody else at the table took up the concern, which turned out to be correct the following spring.
Why it works
Routing the most failure-prone work to the people who opposed a program builds a visible record of their struggles, and decision-makers weigh that record against every objection they raise later. Their analytical credibility, often the main thing they brought to the debate, drains away, so their side looks worse. Siding with them gets more expensive for anyone else, and the critics spend their time firefighting the work they were handed, with little left for organized opposition. The sponsor has to control how work is allocated and have a plausible reason for the routing, such as expertise, a request for ownership, or a wish to be inclusive.
The thinking behind it
Lee Ross In Social Roles, Social Control, and Biases in Social-Perception Processes (1977), Ross, Amabile, and Steinmetz found that quiz players randomly assigned to write the questions were judged more knowledgeable than those assigned to answer them, though the roles alone made the difference. Assignments shape how competence is judged. A sponsor who hands critics the hardest workstreams and supporters the clean ones creates a gap in apparent competence. Showing the allocation beside each team's stance makes the roles visible.
Jonathan Baron Baron and Hershey's Outcome Bias in Decision Evaluation (1988) found that decision-makers are judged more competent when outcomes happen to be good, even with identical information. Critics who own the most failure-prone work will produce worse outcomes, and those outcomes will be read as evidence about their judgment, including their judgment of the program. Presenting a failure as a design problem, with the data and timeline limits on record, separates the outcome from the critic.
Warning signs
Known critics of a program own all of its highest-variance workstreams, assigned with explanations like "they have the domain expertise," "they asked for ownership," or "we wanted to be inclusive." Supporters get the clean, predictable pieces. Later, the critics' objections are answered by pointing at their delivery problems. The allocation was settled early, often in the same meeting that approved the program.
How to defend yourself
Read every high-visibility, high-variance assignment as a political document as well as an operational one, because the attack is made when the work is handed out, well before anything fails.
- Ask who else was offered the work and how the pieces were allocated across teams.
- If the routing is lopsided, show stakeholders the allocation side by side with each team's stance on the program.
- Accept only on shared accountability terms written down: joint ownership with the sponsor's team, a stated risk rating, and success criteria that reflect the difficulty.
- Or decline in writing, with your reasons.
If the work fails anyway, present the failure as a design problem, with evidence: the data quality, the timeline, the platform limits you flagged at the start.
How a leader shuts it down
Allocate the riskiest work by capability and capacity, and publish the reasoning. Compare a program's allocation table with who supported and who opposed it; a close match deserves a question. Keep critics' objections on the agenda and judge them on their merits, separately from their delivery record.