Everyone says they support the change. Adoption still doesn’t happen. The team keeps arguing about the stated objections - “no time”, “it won’t scale” - while the real objection is the one nobody will say out loud. This activity surfaces what people are actually protecting, without exposing who said it, so you can redesign the rollout around it.
Your company rolls out an AI coding assistant. Every meeting ends with sensible objections: “it’s not secure enough”, “our current process works”, “we don’t have time to learn it”. Months later, adoption is still poor.
When the team runs Surface Honest Resistance, the biggest pattern isn’t security - it’s the fear of looking less capable than colleagues. The rollout changes from more technical training to protected practice sessions where people can learn without being judged. Adoption begins to move because the rollout now addresses the real concern.
Everyone responds privately to a few prompts that bring out the unsaid thing - what they’d quietly be relieved to lose, what they hope leadership hasn’t noticed. The responses are anonymous, shuffled and read aloud by others, so no one is identified. Then the team clusters them by what each one protects - status, competence, workload, control, habit/routine - and the real blocker becomes visible as a pattern.
Team: one person acts as the facilitator - they run the activity using the Facilitator Guide while everyone else takes part. The facilitator never identifies who wrote what.
Team ✓ · About 45–60 minutes, with a facilitator.
The time required is indicative and will depend on the nature of the problem and the size of the team.
The facilitator must read the short facilitation guide first - about 8–10 minutes. It is a downloadable PDF on this page.
Bring one real change that’s being resisted - a process change, a reorg, a tool migration, a new way of working. Best with the people who’ll actually live with it.
Use it whenever:
You’ve done it well when: the team can point to the largest cluster and say “this - not the reason we kept arguing about - is what’s actually stopping it.”
Most people won’t openly admit what they’re worried about if it could make them look weak, resistant or selfish. Anonymous responses make it safe to say the real objection. When similar concerns are grouped together, the team stops seeing “difficult people” and starts seeing a common pattern it can address.
You don’t solve resistance by answering louder. You solve it by discovering what the objection is protecting.
One change that’s being resisted. A real, current change - or a starter-change card if the group has none of its own.
One facilitator. They run the flow, read every response aloud neutrally, and hold the anonymity line. They never argue an objection or guess who wrote it.
The Honest Response Cards. Write-on cards with prompts that bring out the unsaid thing indirectly (‘the part I’d be relieved if someone cancelled is…’, ‘what I hope leadership hasn’t noticed is…’). One response per card, anonymous.
The protect-categories board. Five zones - status, competence, workload, control, habit / routine - to cluster the responses by what each protects.
Plain identical pens. So no handwriting can be traced. Anonymity is the whole mechanism.
Output / Takeaways
You leave with:
Important rules
Planning to facilitate this activity? Access the resources below to get started.