Surface Honest Resistance

Surface the real objection that is quietly blocking a change.

Surface Honest Resistance

What this fixes

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.

How this works

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.

Time required

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.

When to use

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:

  • a change has stalled and the stated reasons don’t fully explain it
  • people nod in the meeting, then quietly don’t adopt
  • you’re about to roll something out that you know will meet resistance
  • the same objection keeps returning, even after you’ve answered it

What you get

  • The real objections, surfaced - not the stated reasons
  • The hidden pattern behind them
  • One concrete change to the rollout, with an owner

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.”

What you’ll notice

  • An objection surfaces that no one had said out loud
  • The room goes quiet when the real one goes up
  • The resistance turns out to be a pattern, not one difficult person

Why this works

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.

What you need

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.

Steps

  1. Name the change (4–5 min). Team: appoint a facilitator first. Write one real change everyone in the room has experienced.
  2. Surface, privately (9–11 min). Everyone completes the honest-response prompts on cards - anonymously, one response per card. Write what you’d say if it were safe. One concern per card. Don’t discuss while writing.
  3. Read aloud, neutrally (11–13 min). Do not discuss individual cards.. The facilitator collects every response, shuffles the cards, then reads every card aloud and posts it - no defending, no reacting, no guessing who wrote it.
  4. Cluster by what’s protected (12–14 min). Ask: “What is this person trying to avoid losing?” Place the card in the category that best answers that question - status, competence, workload, control, habit/routine. The fullest zones are the real blockers. If two clusters are equally large, choose the one that is most likely to block adoption if left unaddressed. Don’t solve or debate objections while clustering. First, understand the pattern. Solutions come only in Step 5.
  5. Redesign and commit (12–14 min). Take the largest cluster and change the rollout to address what it protects - not just re-explain the change. If the biggest cluster is still left unaddressed, the rollout hasn’t changed. Commit one change, with an owner.

Output / Takeaways

You leave with:

  • The real objections, in the team’s own words
  • What each cluster protects - the named pattern
  • One rollout change this week, with an owner

Important rules

  • Capture is anonymous - identical pens, shuffled, read by others
  • Cluster by what’s protected, never by who said it
  • The facilitator reads neutrally and never argues an objection
  • End with a rollout change, not just a fresh understanding

Planning to facilitate this activity? Access the resources below to get started.

MIndn
Execution must be smooth. Not chaotic or stressful.
Built by Witmer.