Separating Real Implementation Risk from Change Resistance

Start by accepting both can be true at once

When the board has signed off but the signals from below and around you are mixed, the instinct is to pick a side: either the strategy is flawed and needs revisiting, or people are dragging their feet and need pushing. In practice, both are almost always present. Your job is not to choose between them. It is to separate the two cleanly enough to act on the real risks without capitulating to the noise.

Get this wrong and you either bulldoze through legitimate operational problems that will surface six months later as cost overruns and regulatory findings, or you let well-organised resistance disguise itself as prudence and stall a strategy the board has already backed.

Sort the signals before you analyse them

Before engaging with any concern on its merits, classify it on three dimensions:

Source proximity. Is the person raising it accountable for delivering part of the plan, or commenting from the sidelines? Concerns from accountable owners deserve more weight, but also carry more incentive to inflate risk.

Specificity. Real feasibility concerns name systems, dependencies, regulatory clauses, capacity constraints, or sequencing problems. Resistance tends to stay abstract: "the timeline is aggressive," "the business isn't ready," "clients won't accept it."

Falsifiability. Can the concern be tested? "Our core platform cannot handle the volume increase by Q3" is testable. "The culture won't support this" is not, at least not directly.

Concerns that are specific, falsifiable, and raised by accountable owners go to the top of the pile. Everything else gets a different treatment.

Pressure-test the substantive concerns properly

For concerns that pass the triage, do not ask the person raising them to prove their case. They will, and you will end up with a defensive memo. Instead, commission a small, time-boxed feasibility assessment with a named owner who is not the person who raised the concern and not the person championing the strategy. Two weeks, written output, specific question.

The most common failure here is asking the wrong question. "Can we do this by Q3?" produces a yes or no. "What would have to be true for us to deliver this by Q3, and which of those conditions are currently not met?" produces something you can act on.

Where concerns touch regulated activities, get the second line in the room early. Risk and compliance teams sitting outside the testing process and then objecting at gate reviews is one of the most expensive patterns in financial services execution.

Read the resistance, do not dismiss it

Concerns that fail the triage test, vague, untestable, raised by people not accountable for delivery, are still telling you something. They usually point to one of three things: the strategy's rationale has not been communicated in terms that connect to the objector's world; the objector expects to lose something (headcount, status, P&L control) and has not said so directly; or there is a history of failed change that has trained people to wait it out.

None of these are reasons to revisit the strategy. All of them are reasons to adjust how you implement it. Name what people are actually worried about. If headcount is moving, say so. If a business line is being de-emphasised, do not pretend otherwise. Manufactured ambiguity feeds resistance more than hard news does.

Decide what would change your mind, before you hear the answers

Before the feasibility assessments come back, write down what findings would cause you to adjust scope, sequencing, or timeline, and what findings would not. Share this with your executive team. This is the single discipline that most separates leaders who execute approved strategies from those who relitigate them.

Without it, every new piece of information becomes ammunition in an ongoing argument. With it, you have a clear test: does this concern, if true, hit the threshold we set?

What to do this week

List the five loudest concerns you are currently hearing. Score each on source, specificity, and falsifiability. Pick the two that score highest and commission written feasibility assessments with two-week deadlines and named owners outside the original debate. For the rest, decide whether they need a communication response, a personnel conversation, or nothing at all. Do this before your next steering committee, not after it.