Give the Skeptic a Seat. Only If You Can Still Change Something.

As far as I can tell, the advice is close to universal. You are replacing the AMS, or the finance system, or the CRM, and somebody tells you to get the skeptics in the room early. Give them a seat, let them poke holes, and the person who would have spent two years complaining becomes the person who owns the outcome. I believe this. I have watched it work. I have also watched it fail in a specific way that nobody warns you about.

The case for it is solid. Prosci's change-management research finds that the top reason employees resist is a lack of awareness about the purpose and reason for the change, listed ahead of fear of the unknown, and that much of the resistance it sees is avoidable. Jeffrey and Laurie Ford made the sharper version of the argument in Harvard Business Review back in 2009: treat resistance as feedback rather than as an obstacle, and one of their recommendations is literally to change the change, letting the resisters shape it. The skeptic is doing unpaid pre-mortem work on your project, and they are motivated to find the thing that breaks.

The condition the playbooks skip

Here is what goes wrong. The most direct test I know of is a 1990 lab study by Allan Lind, Ruth Kanfer and Christopher Earley. Male undergraduates were given a performance goal and got a say before the goal was set, a say after it was set, or no say at all. In the after condition, the experimenter told them the goal had already been decided and would not change regardless of what they said. Both kinds of voice were rated fairer than silence. But a say before the decision was rated fairer than a say after it. In that study, asking on a locked decision was the weaker of the two kinds of asking, like being invited to review a contract after it has been signed.

And it can go sour. The same paper summarises earlier studies by Robert Folger and colleagues on what researchers call the frustration effect: people react quite negatively to a procedure that looks like it gives them a voice when repeated bad outcomes, or what others tell them, point to biases that might cancel out that voice. My read is that the danger is not asking late. It is asking late while acting as if the door is still open. Once people spot that, the invitation itself becomes evidence against you.

Now put that in an association hallway. You invite the membership director who has been loudly against the migration onto the working group. Meeting two, she raises the renewal grace period, the thing she has handled by hand for nine years and the thing she is sure the new platform will get wrong. Everyone writes it down. Nobody tells her that the platform decision was signed in March and the grace-period logic is not configurable. She finds out in user acceptance testing, in front of her team.

You have not converted a resister. You have manufactured one, and you have handed her evidence. Her position is no longer "I do not like this system." It is "I told them in June and they knew." That version travels, it is true, and you cannot argue with it.

This matters more in our sector than in most, because a lot of association resistance sits in people you cannot manage around. A volunteer committee chair, a component or chapter leader, a twenty-year staffer who is the only person who understands how dues proration actually works. You cannot reassign them and you should not want to. Persuasion is the only lever available, which means the cost of burning it is higher.

The one page to write before the kickoff

So before you convene anybody, write one page with two columns on it.

On the left, the decisions that are genuinely still open. Field-level configuration. Which processes migrate as-is and which get rebuilt. Report definitions. Sequencing. Who trains whom, and when. On the right, the decisions that are locked, with the date each was made and the name of who made it. Platform. Budget. Go-live. Whatever else is already signed.

Then read the right-hand column out loud in the first meeting. Not in a deck, not in an appendix. Say it plainly: these four things are decided, here is when and by whom, and I am not going to pretend otherwise. It is an uncomfortable ninety seconds and it buys you the rest of the project, because every objection that lands in the locked column now gets an honest answer in the room instead of a polite note that dies in a spreadsheet.

The test is the left column. If you cannot name three things on it that a skeptic could actually change, do not dress the meeting up as a working group. Send the decision memo, say plainly what is locked and who locked it, name whatever input can still change something, and take the complaints. Being heard after the fact is weaker than being asked before, but in the lab it still beat silence. What turns it sour is pretending the door is open when it is not.

Pick the champion by the workaround, not the enthusiasm

The other half of the question is who else belongs in the room, and the default answer is wrong in a predictable way. Volunteers self-select, and my guess is that enthusiasm for a new system tracks having time to be enthusiastic, which tracks not being buried in the old one.

Pick instead by who owns the workaround. Somewhere in your organization there is a spreadsheet doing real work that the AMS was supposed to do. The consultancy Achurch names the symptom in its list of obstacles to AMS use: when people do not link the AMS to their workflows and tasks, teams revert to shadow spreadsheets and systems. Find those spreadsheets and you have found both your real process documentation and the people who wrote it. They are not always enthusiastic. They are always informed, and informed beats willing.

That search will pull you into departments that do not normally show up on an implementation roster. Finance, because dues reconciliation touches member records constantly and breaks loudly. Education, because credit and certification records have retention rules nobody else knows. Chapter and component staff, because they consume member data they do not control and have the longest list of things that silently do not work. None of these people own the system. All of them own an outcome that depends on it, and the same Achurch piece makes the related point that when everyone is responsible for the AMS, no one is.

The architecture side of this I have written about already, in why replacing the architecture beats migrating it and in what a composable member stack actually asks of you. This is the other half, the half that decides whether any of it survives contact with the people who have to use it. It needs no budget, no vendor, and no platform decision. It needs one page and an uncomfortable ninety seconds.

Quick takes

Log what the skeptic gives you as a decision, not as feedback. Feedback goes in a document nobody reopens. A decision has a date, an owner, and an answer, including "we considered this and chose not to." The difference costs nothing and it is the entire difference between the working group being real and being theater, because a person can check whether their item got answered.

The grace period problem is usually discovered, not prevented. I suspect much of what a long-tenured skeptic raises is a process the old system never actually supported either, held together by them personally. That is worth surfacing early even when you cannot fix it, because the alternative is finding it in the first renewal cycle after go-live, with no institutional memory left to explain it.

Watch the second meeting, not the first. People are polite in the first meeting. If the skeptic stops raising things by meeting three, do not read it as the objection being resolved. Read it as them concluding the exercise is decorative, which is close to what the frustration-effect studies describe: people reacting badly to a voice they suspect is being cancelled out.

Worth a read

Ford and Ford, Decoding Resistance to Change, Harvard Business Review, 2009. Seventeen years old and still the most useful framing available, mainly because it refuses to treat resistance as a personality defect to be managed.

Prosci on reframing resistance. Vendor-adjacent, and the underlying benchmarking data on why people actually resist is worth the click regardless of what you think of the methodology around it.

Achurch Consulting's seven obstacles to improving AMS use. No statistics in it, which I will not pretend is a strength, but the obstacles are practical, and the shadow-spreadsheet observation is the one I would act on first.

The question I would ask before the next kickoff is not whether the skeptics are in the room. It is whether anything they say in it could still change the plan, and whether you would be willing to say out loud which parts could not.

---

From the Mind of Ravi Rooprai is a weekly column on association tech, data, and AI. Read the perspectives for the longer arguments behind it.

Researched with AI assistance and fact-checked against primary sources. The analysis, judgment, and writing are mine. How this column is made →