Long-standing complaints that a change genuinely fixes become the case for it, so supporting the change feels like vindication to the people who raised them and neutrality feels like tolerating the old problems.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
Six months after its Series B, a developer-tools startup hired a vice president of engineering whose priority was a move to a single code repository and a dedicated platform team. Few engineers cared about repositories. Plenty cared about the pager. She spent her first three weeks reading the on-call logs and the exit notes from the last year, and sat in on every team's retrospective. Two complaints came up everywhere: deploys that failed one time in five, and weekend pages for alerts nobody owned. Her proposal led with those two, quoted the engineers' own retrospective notes, and made dated commitments: deploy failures under one in twenty by the end of the second quarter, every alert owned by a named team by the third. It said plainly that the platform work would not fix the meeting load. The staff engineers who had resisted the repository move signed on within a month.
Why it works
Tying the plan to complaints people already hold raises the benefit of supporting it, because each grievance gets its own promised remedy. Supporting the change also becomes cheaper: it reads as vindication of positions people have held for years, so skeptics can switch without admitting they were wrong. Staying neutral looks worse, since it now means tolerating the problems people complained about. Four things have to be true: the grievances predate you and you did not cause them, the plan can actually address them, enough people hold them to matter, and you show restraint about promising fixes that results could later disprove.
The thinking behind it
Robert B. Cialdini Cialdini's Influence (1984) describes commitment and consistency: people who have taken a position feel pressure to act in line with it. Engineers who complained for years about failed deploys and weekend pages have committed, publicly, to wanting those things fixed. A plan that really fixes them lets them support it while staying consistent with their own record, and switching sides costs them no admission that they were wrong.
Erving Goffman Goffman's Frame Analysis (1974) argues that people make sense of events through frames that answer what is going on here. Presenting a platform migration as the remedy for the pager and the deploys reframes a technical project as the answer to a shared complaint. The frame holds only while the remedy is real; a promised fix that never arrives turns the frame into what Goffman called a fabrication.
When it fits
This fits when real, long-standing complaints exist and your plan fixes some of them as a matter of fact. It suits a leader who arrived after the grievances formed and is not tied to whoever caused them. Timing matters: too early and the complaints have not settled into shared language; too late and a rival program has already claimed them.
How to use it well
Start by listening for what people already say, in their own words.
- Collect the grievances from sources people trust: on-call logs, ticket queues, exit notes, team retrospectives, skip-level conversations.
- Sort them against your plan: what it fixes, what it partly fixes, what it does not touch.
- Make dated, measurable commitments only on the ones it fixes, and say plainly which ones it leaves alone.
- Credit the people who raised each problem first, and use their language when you describe it.
- Report progress against each commitment on a schedule, including misses.
What it costs and where it backfires
Borrowed grievances come with a bill: the people who hold them expect redress, and a remedy that does not arrive costs more trust than never mentioning the complaint. Leaving out grievances that touch your allies will be noticed and read as a sign of whose side you are on. Promising fixes you do not intend, or stirring up resentment that was not there, is manufactured outrage, and people find out.
When it is used on you
Suspect it when change messaging suddenly uses the vocabulary of old complaints it never addressed before. List every grievance the change claims to fix and ask for a specific, dated commitment on each. Look at which complaints the plan leaves out, which often shows whose interests it protects, and check later results against the promises.