When the Board and the Frontline Disagree on Change Appetite

The disagreement is data, not noise

When your board says customers, regulators or staff will accept a change, and your frontline says they won't, the instinct is to broker a compromise. Don't. The disagreement itself tells you something useful: two groups with different vantage points are reading the same stakeholders differently. Your job is to work out why, not to split the difference.

In financial services, this split shows up predictably: pricing changes, service model shifts, branch or adviser restructuring, technology migrations, conduct and culture programmes, ESG repositioning. The board sees the strategic case and a sanitised version of stakeholder sentiment. The frontline sees the daily friction. Both views are partial. Both are real.

Diagnose the source of the gap before you try to close it

There are usually four reasons board and frontline diverge on appetite:

1. Different stakeholders in mind. The board is thinking about institutional investors, the regulator and large clients. The frontline is thinking about specific customer segments, branch staff, or intermediaries. They are not disagreeing about the same people.
2. Different time horizons. Boards weigh appetite over 18 to 36 months. Frontline teams feel the first 90 days. A change that customers will tolerate by year two can still trigger attrition in quarter one.
3. Asymmetric information quality. Boards see survey aggregates, NPS trends and consultant decks. Frontline teams hear unfiltered complaints and see behavioural signals like quiet account closures or relationship manager pushback. Neither is the whole picture.
4. Incentive distortion. Frontline staff may overstate resistance to protect their book or workload. Boards may understate it because the strategy is already approved and capital is committed.

Name which of these is driving the disagreement in front of you. The intervention is different for each.

Get both sides looking at the same evidence

Most executive teams try to resolve these disputes through debate. That rewards the more confident speaker, not the more accurate one. A better approach:

• Define the specific stakeholder groups in scope. Not "customers" but "mass affluent clients aged 55+ in the South East with balances above £250k." Granularity forces both sides to talk about the same people.
• Separate appetite for the change from appetite for how it's delivered. Most frontline resistance is about execution, not principle. Most board confidence is about principle, not execution. Surfacing this distinction often dissolves half the disagreement.
• Triangulate with fresh, primary evidence. Commission a focused round of stakeholder conversations, structured interviews with 20 to 30 of the actual people in question, not another sentiment survey. Have both board representatives and frontline representatives review the raw transcripts, not the summary.

The judgement call: who carries more weight on which question

Frontline teams are usually right about: timing, sequencing, the specific objections customers will raise, which staff will leave, and the operational cost of poor communication. Take them seriously on these.

Boards are usually right about: whether the change is necessary, competitive direction, regulatory trajectory, and what the institution can absorb financially. Take them seriously on these.

The failure mode is letting either group rule on the wrong question. A frontline veto on strategic necessity is as dangerous as a board override on operational sequencing.

What good looks like

A defensible resolution has three features. First, the appetite question is decomposed: which stakeholders, for which element, over which horizon. Second, the evidence base is shared and primary, not filtered through layers. Third, the decision allocates authority by question type, with the board owning direction and the frontline owning pace and method, and both signing off on the integrated plan.

What goes wrong most often: executives treat this as a communication problem and run more town halls. It isn't a communication problem. It's an evidence and authority problem. More communication on top of unresolved disagreement just hardens positions.

Your next move

If you are sitting on a live disagreement of this kind, take 30 minutes this week to write down, for the specific change in question: which stakeholder groups each side is actually talking about, what evidence each side is drawing on, and which sub-questions you would assign to the board versus the frontline. If you cannot answer those three cleanly, you do not yet have a disagreement worth resolving. You have a conversation that hasn't been properly defined.