The people most likely to resist a new system are seated on the team that designs it, so the result carries their work and opposing it would mean disowning what they built.
An example
An auto parts plant was replacing its production scheduling system, and the plant manager knew the shift supervisors could sink it simply by working around it. Three months before rollout, the plant manager asked the four most influential supervisors, including the loudest critic of the project, to join the design team for twelve weeks. They wrote the changeover rules, chose the screen layouts for the floor terminals, and insisted on an override for rush orders that the vendor had called unnecessary. The override went in. Their names were on the launch notice, and each supervisor trained their own shift. In the first month a maintenance lead complained that the new schedule ignored machine downtime. The loudest critic answered at the shift meeting and pulled up the downtime screen the supervisors had designed.
Why it works
People who helped design a system see it as better, because it carries their safeguards and ideas, and supporting it earns them credit as its architects. Endorsing it gets easier, since they are backing their own work and need not feel they are giving in to leadership. Opposing it becomes costlier, because it would mean publicly disowning their contribution in front of peers who watched them shape it. It works when participation is substantive, when contributions visibly survive into the final design, when names and roles are public, and when the invitation comes early enough for real attachment to form.
The thinking behind it
Leon Festinger A Theory of Cognitive Dissonance (1957) describes the discomfort of holding cognitions that do not fit, and the common relief of changing a belief to match what one has already done. A supervisor who wrote the changeover rules and then opposed the system would hold two such cognitions. That is why the loudest critic defended the downtime screen at the shift meeting, and why overridden contributions turn the people involved back into opponents.
Robert B. Cialdini In Influence (1984), Cialdini argues that public, written positions create pressure to act in line with them. Names on the launch notice and supervisors training their own shifts make the commitment public. The principle also explains the counter: someone given a seat should keep a written record of where their contributions were overridden, so the public commitment does not extend to parts they did not shape.
When it fits
Rollouts that depend on adoption by people who can block them through non-use suit this: supervisors, clinicians, senior engineers, branch staff. You need a design process with real decisions still open, enough time before launch for attachment to form, and the willingness to accept changes you did not plan.
How to use it well
Invite the most influential likely resistors, including the loudest one, early enough to matter, usually months before launch.
- Give them real decisions with real scope, written into the team's charter.
- Keep their contributions in the final design, and when you cannot, explain why to them first.
- Publicize their roles and put their names on the launch.
- Let them teach the system to their own teams.
- Free up time from their regular duties so the design work does not become a second job.
Expect them to improve it. The changes they insist on are often the ones the system needed.
What it costs and where it backfires
Control over the design is partly given away, and some of their changes will cost money or time. Supervisors who see their work overridden become sharper opponents than before, with a new grievance: you pretended to listen. Some will treat the seat as a way to slow the project from inside. Participation has to be real. A committee convened to rubber-stamp a finished design is tokenism, and hollow participation arms the resistance.
When it is used on you
Given a seat, check whether your contributions survive into the final design, and say so in writing when they are overridden. You can accept the seat and keep your position, since an invitation commits you to nothing. Name hollow participation early.