The objection is evidence about the rollout first
Resistance is the cheapest diagnostic information a rollout produces, and the reflex to overcome it destroys the data. A team saying "this is process for its own sake" is making a claim that can be true or false, and it is answerable: which ceremony, what does it cost us in hours, what decision does it produce, and what would we lose if we stopped attending. That is four questions, and asking them changes the conversation from a negotiation about compliance into a joint investigation.
Go and get specifics before you form a view. In practice the sentence covers at least four different complaints, and they need different responses.
| What they say | What is often underneath | What it is evidence of |
|---|
| "The planning event is two days of theatre" | Their work is unplannable at a quarter's horizon — support, platform, incident-driven | A real mismatch between the framework's batch and this team's work |
| "We already do this, with different words" | Mature practice being asked to relabel | Rollout designed for the median team, applied uniformly |
| "Nothing we raise ever changes" | Two rounds of feedback absorbed with no visible change | The programme is not running the inspect-and-adapt loop it prescribes |
| "This is surveillance" | Estimates aggregated upward and used to compare teams | A measurement design defect, and the most legitimate objection of the four |
| "We do not want to be told how to work" | Sometimes exactly what it says | Genuine change aversion, and it still has to be engaged with |
Only the last row is the thing the sponsor assumes the whole conversation is about. Reaching for that explanation first, before the other four have been eliminated, is the commonest failure in this situation and it is visible to the team within a minute.
A test that separates signal from aversion
Two questions do most of the work. The first: what would have to be different for this to be worth your time? A team with a legitimate objection answers concretely — drop the second planning day, let us bring a forecast instead of a commitment, stop aggregating our points. A team that is simply resisting change tends to answer with a restatement of the objection, and that difference is diagnostic without being accusatory.
The second question is about a cost they are already paying: what is going wrong now that this is supposed to fix? A team that can name the integration surprise, the late dependency, the quarter where two teams built the same thing, is arguing about the mechanism rather than about the problem, and there is a deal available. A team that says nothing is going wrong is either right — in which case they should probably be exempt — or has not looked, and that is the conversation to have instead of the one about attendance.
Here is roughly how the useful version of that conversation goes, including the part most people skip.
COACH You said the planning event is process for its own sake. Which
part - the two days, the room, the commitment at the end?
DEV The commitment. We plan ten weeks of work and by week three
we're doing something else because prod is on fire. Then we
get asked why we're off plan.
COACH How much of the last quarter went to unplanned work?
DEV Most of it. Maybe two thirds. It's always two thirds.
COACH Then I think you're right and the plan is wrong, not you.
[naming it, before defending anything]
What I need from you in that room is different from what the
others give. Would you bring a forecast - a range, with the
two thirds priced in - instead of a commitment?
DEV They'll say we're not committing.
COACH They will, and I'll take that. What I am not going to do is
get you an exemption from the room, and I want to say why
rather than pretend it's the framework's rule. Four teams
depend on you. If you're not there, they plan against
assumptions about you that nobody checked, and you spend
the quarter being interrupted by the consequences.
DEV That's fair. The two-day thing is still ridiculous for us.
COACH Then come for the half day where the dependencies get
argued. I'll tell the RTE that's the deal and why.
If it goes badly, that's mine to own, not yours.
Three properties make that exchange work. The coach concedes the accurate part before asking for anything, which is what buys the rest. The non-negotiable is justified by a consequence to other people rather than by the framework prescribing it, because "the framework says" is an argument that loses this audience permanently. And the coach takes the risk upward instead of asking the team to absorb it, which is the actual difference between coaching a team and administering a rollout.
When they are right, change the rollout
If the objection is legitimate, the deliverable is not a better explanation. It is an amendment, made visible to every other team, because a concession granted quietly to the loud team teaches everyone that objecting privately is the way to get things changed.
That means going to whoever owns the programme with a specific, small, defensible ask: this team brings a forecast rather than a commitment; this team's numbers are not aggregated into a comparison; this ceremony drops from weekly to fortnightly for everyone and we look again in two months. Frame it as the programme doing what it tells teams to do — inspect the process and adapt it — which is both true and the only framing that does not require the sponsor to admit a mistake.
Two things make the ask land. Bring the cost in hours: eleven people, two days, is a number a sponsor can weigh, and it is usually the first time anyone has put one on a ceremony. And bring the alternative rather than the removal, because "we will stop attending" is a request the programme must refuse and "we will bring a written forecast and be present for the dependency session" is one it can accept.
The label that ends the conversation
The specific thing to refuse is the word disengaged, or its cousins — not on board, change-resistant, a culture problem. Once a team carries that label, every subsequent piece of feedback from them is discounted as attitude, the programme stops receiving information from its most attentive critics, and the team learns that saying nothing is cheaper. That is how a rollout arrives at full compliance and no improvement: the ceremonies are attended, the objections have gone quiet, and the delivery numbers have not moved.
The failure sits at the coach's feet rather than the team's, and it usually comes from a role conflict nobody has named out loud. A coach paid by the transformation programme, measured on adoption, is structurally incentivised to read resistance as aversion. Saying that plainly in an interview — that you would want to know what you personally are measured on before answering, because it determines which explanation you will find attractive — is a considerably stronger answer than any technique.
The last thing worth saying is that some resistance survives every good-faith move, and the answer then is not force. A team held to a ceremony it has argued against, with reasons that were heard and answered, will comply and give it nothing; the honest position is to name the disagreement, agree what evidence would settle it, and set a date to look. That is slower than an escalation and it is the only version that leaves you able to coach the team afterwards.
The resistance is the only unfiltered feedback the rollout will ever get, and a programme that converts it into a label about the team has arranged not to hear anything again.
© 2026 Preptima. Originally published at preptima.com (opens in a new tab).