Pressure-Testing Regulator and Stakeholder Support Before a Strategic Pivot

Start with the decision you actually need to make

Before any soundings, write down what you would change about the pivot if you learned a key regulator was lukewarm, hostile, or simply distracted. If the answer is nothing, you do not need intelligence, you need a communications plan. Most pivots fail this test. Leaders solicit views they have no intention of acting on, then mistake polite engagement for endorsement.

Good practice: define three or four specific positions the pivot depends on. For example, that the PRA will not require a capital add-on, that the FCA will treat the new product under existing permissions, that a key trade body will not lobby against it, that two anchor institutional clients will publicly tolerate the change. These are the propositions you are testing. Everything else is noise.

Sequence the soundings carefully

The order in which you talk to people determines what you learn. Get this wrong and you contaminate the well before you have drawn from it.

Start with the stakeholders whose views are most independent of each other and least likely to leak. That usually means former regulators, senior counsel with current supervisory dialogue, and one or two non executive directors at peer firms who have been through similar conversations. Avoid current supervisors until you have a clear hypothesis to test. Walking into a first supervisory meeting without one signals either weakness or fishing, both of which harden positions.

Move to industry bodies and peer firms next. They will tell you what the unspoken objections are, the ones regulators will not voice directly but will act on. Only then approach your lead supervisor, and do so with a specific, narrow question, not an open invitation to react.

Read what you hear properly

The single biggest error is treating absence of objection as support. Regulators rarely say no in early conversations. They ask questions, request more analysis, or note areas of interest. Each of these is a signal, and the signal is almost never positive.

What genuine support sounds like: specific engagement with implementation detail, willingness to name a supervisory contact, references to precedent that favours your case, and a tone that treats the pivot as a problem to be solved together. What lukewarm sounds like: repeated requests for more information, references to broader policy reviews underway, suggestions to revisit timing, and any version of we would want to understand more about governance.

Pay attention to who is in the room on their side. A step up in seniority or the addition of a policy lead usually means the matter has been escalated internally. That can be good or bad, but it is never neutral.

Test with a concrete proposition, not a concept

Vague soundings produce vague responses. If you want a real read, share a specific structure: the product, the perimeter, the timeline, the capital treatment you intend to apply, the consumer outcomes you expect. The more concrete you are, the harder it is for a stakeholder to give you a non answer. Some leaders resist this because they fear committing prematurely. The risk is the opposite: a vague sounding lets a regulator nod politely now and object substantively later, when you have already moved.

Build the disconfirming case deliberately

Assign someone senior, ideally outside the pivot team, to argue why each key stakeholder will quietly resist. Make them produce evidence: speeches, recent enforcement actions, supervisory letters to peers, public board priorities. If they cannot find any, that is a real datapoint. If they can, you have your agenda for the next round of soundings.

This is where internal teams routinely fall short. The people running the pivot are incentivised to hear support. You need someone whose job is to hear resistance.

Decide before you announce

By the time you brief the board for approval, you should be able to answer three questions in writing. Which stakeholders will actively support, which will tolerate, and which will resist. What you have changed about the pivot based on what you heard. What you will do in the first thirty days after announcement to lock in the support you have and contain the resistance you have not resolved.

If you cannot answer all three, you are not ready to commit resources. Go back and do another round.