When the Board and Compliance Disagree on Regulator Sentiment

Start by treating both signals as evidence, not noise

When your board says stakeholders are aligned and your compliance team is picking up unease in corridor conversations with regulators, the instinct is to pick a side. Resist it. Both signals are real. The board is likely responding to formal engagement: meetings with senior regulators, consultation responses, public statements. Compliance is picking up something different: the working-level view, the caveats that never make it into official correspondence, the concerns raised over coffee at industry events.

These two channels almost always diverge on complex products. The question is not who is right. The question is what each signal actually represents and how much weight it deserves.

Separate the three things people call regulator sentiment

Before you can validate anything, be precise about what you are measuring:

1. Formal position: what the regulator has said or written in official channels.
2. Institutional trajectory: where the regulator is heading based on policy direction, recent enforcement, and public speeches.
3. Working-level sentiment: what individual supervisors, policy leads, and technical specialists actually think.

Boards typically hear the first. Compliance typically hears the third. Both are true. Neither, on its own, tells you whether launch will succeed.

Run a structured validation, not a wider poll

Asking more people internally will not resolve the disagreement. It will amplify whichever view has more advocates. Instead, commission a small, disciplined external exercise. Three components:

Reconstruct the regulator's decision logic

Pull every relevant speech, consultation, Dear CEO letter, enforcement action, and policy statement from the last 24 months. Look for the specific concerns being raised about products like yours. Not general concerns, specific ones. If the regulator has flagged distribution risk, price fairness, or vulnerable customer exposure in adjacent products, assume those concerns apply to yours until proven otherwise.

Test the informal signals directly

Commission structured, attributable conversations with former regulators, senior industry counsel who have recently engaged the regulator on similar products, and trade body policy leads. You are not asking for gossip. You are asking three questions: what would the regulator's working level say about this product if asked privately, what conditions would they want attached, and what would make them escalate concerns formally.

Stress-test the board's confidence

Identify who told the board stakeholders are aligned. Was it a single relationship, a formal meeting, an inference from silence? Silence from a regulator is not endorsement. A supportive meeting with a senior figure does not bind the supervisory team who will actually review your launch.

What most people get wrong

The common failure is treating compliance's soft signals as a communication problem to be managed rather than intelligence to be tested. The second failure is the opposite: treating every corridor comment as a veto. Both are lazy.

Good looks like this: within four weeks you have a written assessment that distinguishes formal position, trajectory, and working-level sentiment; identifies the specific concerns most likely to surface; and gives the board a probability-weighted view of regulatory response, not a binary yes or no.

Sequence matters

Do the desk work first. Do not commission external conversations until you know what you are testing. Going into third-party interviews with vague questions produces vague answers and burns credibility with the people you are asking.

Once you have the assessment, bring it to the board with a clear recommendation: proceed, proceed with modifications, delay for further engagement, or stop. If the recommendation is to proceed with modifications, be specific about what changes and why. Boards accept nuance when it comes with a decision attached.

The decision point

Before the next board meeting, answer one question in writing: if the regulator's working-level view turns out to match what compliance is hearing, what is our exposure and what would we wish we had done differently. If you cannot answer that clearly, you are not ready to launch, regardless of what the formal channels are telling you.