Skip to main content

Validating Your Decision-Maker Map Before a Regulatory Shift

This guide sets out how senior executives can pressure-test their map of decision-makers and veto players ahead of a material regulatory change. After reading, you will know where the typical blind spots sit, how to confirm real influence rather than nominal authority, and what to do when your map and reality diverge.

Start with the assumption that your map is wrong

Most executive teams walk into a regulatory shift with a stakeholder map built for the last decision, not the next one. The names are familiar, the org chart is current, and the relationships feel solid. That is exactly the problem. Regulatory change reshuffles who actually carries weight: a technical specialist three layers down can become the binding constraint, a politically exposed division head can quietly withdraw cover, and a regulator's policy lead can be overtaken by their supervision counterpart without anyone telling you.

Validation is not about producing a more detailed map. It is about testing whether the map you have predicts behaviour under the new conditions.

Separate formal authority from real influence

List every party with a formal role in the decision: sign-off rights, statutory consultation status, board reserved matters, regulatory approval thresholds. That is your floor, not your answer.

Then ask three diagnostic questions for each name:

  • When did this person last block or materially reshape a decision in this area? If the answer is never, treat their veto as theoretical until proven otherwise.
  • Who do they call before they form a view? That person is often the real decision-maker.
  • What would have to be true for them to spend political capital opposing this? If you cannot answer specifically, you do not understand their position.

The people who fail this test are usually the ones executives have overweighted. The people who pass it but are missing from your map are the ones you need to find.

Hunt for the hidden veto players

Three categories get missed repeatedly.

Technical gatekeepers. Heads of model risk, financial crime MLROs, chief actuaries, data protection officers. Under regulatory change, their sign-off often becomes load-bearing in ways the executive committee does not see until a paper is delayed.

Second-order regulators. You know your lead supervisor. Do you know which other authorities will be consulted, which have memoranda of understanding that trigger automatic involvement, and which have informal influence through joint committees? In cross-border cases, a junior official in a secondary jurisdiction can hold up a decision for months.

Internal coalition holders. The non-executive who chairs the risk committee, the group GC, the regional CEO whose P&L is affected. They rarely appear in process maps but they shape what the board will accept.

Triangulate before you trust

A single source on stakeholder positioning is almost always misleading. Use at least three independent reads:

  1. Direct conversation with the stakeholder or their team.
  2. Observation of recent behaviour on adjacent decisions.
  3. A third party who deals with them in a different context.

If the three reads do not agree, you have not finished the work. The most expensive errors come from accepting the first plausible answer because it confirms what the team already believed.

Test the map against a live scenario

Take the actual regulatory change and walk it through. Who has to say yes, in what order, by when? Where are the points at which a single party can stop or slow the process? Now stress it: what happens if the supervisor changes mid-process, if a political principal intervenes, if an industry body takes a position against you?

If your map cannot answer these questions specifically, with named individuals and predicted positions, it is not yet validated. Generic answers ("the regulator will want comfort on conduct") are a signal that the work is incomplete.

What good looks like

A validated map is short, specific, and uncomfortable. It names people your team would rather not have to manage. It identifies at least one veto player you did not previously take seriously. It predicts, in writing, how each key party will respond to the change, and it commits to revisiting those predictions on a defined cadence.

If your current map is long, comprehensive, and reassuring, it is almost certainly wrong.

Your next move

Before the next executive discussion on this regulatory change, take your current stakeholder map and mark every name where you cannot answer the three diagnostic questions with evidence. That subset is your validation workload. Everything else is decoration.

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

Book a conversation