Skip to main content

Surfacing False Assumptions Before a Strategic Shift Goes Public

A practical method for senior leaders to quickly test where their assumptions about blocking stakeholders are wrong, before a strategic shift is announced. After reading, you will know how to design and run a compressed external testing exercise that produces decision-grade intelligence in two to four weeks.

Start by accepting what you don't know

If you are reading this, the strategy is largely set and the announcement window is approaching. The risk is not that you have missed obvious stakeholders. It is that you have a confident, internally consistent view of what regulators, large shareholders, ratings agencies, key clients, distribution partners, or politically active critics will tolerate, and parts of that view are wrong in ways your team cannot see.

The goal of the exercise below is not consensus or comfort. It is to find the two or three assumptions that, if wrong, would force a redesign, and to find them before they surface in a supervisory letter, a proxy advisor note, or a front page.

Write down the assumptions before you test them

Before any external conversation, force the executive team to commit assumptions to paper. For each blocking stakeholder, write a single sentence: what we believe they think, what we believe they will do, and what we are relying on them not doing. Then mark each one: high confidence, working assumption, or guess dressed as fact.

Most teams discover that 30 to 50 percent of what they treated as known is actually inference from old conversations, second hand readouts, or pattern matching from a different deal. That is the testing list.

Identify the genuine blockers, not the noisy ones

A blocker is someone who can stop, materially delay, or force expensive redesign of the shift. Not someone who will complain. Sort your stakeholder list into three groups:

  • Hard blockers: regulators, large shareholders above disclosure thresholds, JV partners with consent rights, ratings agencies whose downgrade would breach covenants.
  • Soft blockers: trade bodies, influential sell side analysts, consumer groups, political figures with platform but no formal power.
  • Amplifiers: media, social commentators, former insiders.

Spend 80 percent of testing effort on hard blockers. Soft blockers matter for sequencing and narrative, not for go or no go.

Choose the right channel for each test

Direct approach is rarely the right first move. It signals intent, creates a record, and invites a defensive response. Better options, in order of preference:

  1. Proxy conversations: former officials, ex-board members, advisers who recently left the stakeholder organisation. They will tell you what current incumbents will not say out loud.
  2. Analogous case probing: ask about a recent comparable transaction or shift. Listen for the words they use, what they flagged as problematic, what they accepted.
  3. Hypothetical framing through trusted intermediaries: a lawyer, banker, or consultant who can table a scenario without attribution.
  4. Direct conversation, only when the assumption cannot be tested any other way, and only after you have decided what you will do if the answer is bad.

The sequencing matters. Direct conversations early lock in positions you may not want locked in.

Listen for the things that contradict your model

The instinct in these conversations is to seek confirmation. Train your interviewers to actively hunt for disconfirming signals: hesitations, qualifiers, references to other parties you had not considered, concerns that sit outside your framing. A regulator saying "we'd want to understand the operational resilience implications" when you expected a conduct question is the signal. Do not smooth it over in the readout.

What good looks like: a one page output per stakeholder that explicitly states which prior assumptions held, which were wrong, and which remain untested. Not a narrative summary.

What most teams get wrong

Three recurring failures:

  • Testing through advocates. The relationship partner who has known the regulator for ten years cannot run this. They are too invested in the existing reading.
  • Treating silence as assent. If a stakeholder did not object in a past meeting, that is not a data point about this shift.
  • Compressing the synthesis. Teams spend three weeks gathering input and one afternoon making sense of it. Reverse the ratio on the high stakes assumptions.

The decision point

At the end of the exercise you should be able to answer one question in front of the board: which of our pre-existing assumptions, if any, no longer hold, and does the shift still work under the revised view? If you cannot answer that cleanly, you are not ready to announce. If you can, you have bought yourself the right to move fast with the parts that survived testing.

The next action is the assumption list. Put it on paper this week.

Polar Insight helps senior leaders in financial services understand what their key stakeholders actually think before significant decisions are made.

Book a conversation