Testing Implementation Feasibility After Board Approval: A Practical Guide

The problem you actually have

The board said yes. Now the people who have to deliver are sending mixed signals: enthusiastic in the steering committee, cautious in one-to-ones, silent on the harder questions. You suspect the strategy was approved on a version of reality that several key decision-makers privately do not believe in.

This is not a communication problem. It is a commitment problem, and treating it as the former will cost you twelve months.

What conflicting signals usually mean

Three patterns turn up repeatedly in regulated firms.

First, conditional assent: senior people supported the strategy because the conditions they need (budget, headcount, regulatory tolerance, vendor capability) were assumed rather than confirmed. They are not against it. They are waiting to see if the conditions hold.

Second, scope drift between rooms: the strategy approved at board level is subtly different from the one being discussed in the second line, in technology, or in the business units. Each group thinks they agreed to something slightly different. No one has noticed yet.

Third, professional hedging: decision-makers who will be personally accountable for delivery are protecting themselves. Their hedging is not disloyalty. It is information about risks the board paper did not surface.

Most executives misread the third as the first. They escalate, push for visible commitment, and lose the intelligence the hedging contained.

How we approach validation

Our work in these situations follows a clear logic. We are not auditing the strategy. We are testing whether the commitment underneath it is real, durable, and consistent across the people who have to deliver it.

Map the decision-makers who actually matter

Not the RACI. The real list: the eight to fifteen people whose private view will determine whether implementation succeeds. This usually includes two or three who were not in the board room and whose objections, once surfaced, will reset the timeline.

Conduct structured, confidential conversations

We interview these individuals on your behalf, under conditions that allow them to say what they would not say to you directly. The questions are designed to separate three things: their view of the strategy's logic, their view of its feasibility in their domain, and the specific conditions they are assuming will hold.

The last category is where most strategies fail. People rarely volunteer their assumptions. They have to be asked.

Triangulate against external signals

Where implementation depends on regulator tolerance, vendor delivery, or market conditions, we test those assumptions directly with the relevant external parties. A decision-maker hedging on regulatory risk is often right, and the only way to know is to ask the regulator a properly framed question.

Produce a commitment map, not a report

The output is a clear picture: where commitment is real, where it is conditional, where it is absent, and what specifically would have to be true to convert the conditional commitments into firm ones.

What good looks like

A useful validation exercise produces three things you did not have before.

One, a specific list of assumptions the strategy depends on that were not explicit in the board paper. Two, a named view of which decision-makers will actively drive delivery, which will comply, and which will quietly resist. Three, a small number of decisions, usually three to six, that the executive team now needs to take to make the strategy deliverable.

If the output is a heatmap and a set of platitudes about alignment, the work was not done properly.

What most people get wrong

They run the validation through their own org structure. The people being asked whether they support the strategy are being asked by the person who championed it. The answers are useless.

They also confuse pace with progress. Pushing harder on implementation while the underlying commitment is conditional produces the appearance of momentum and the reality of accumulating risk. By month nine, the hedges become formal objections, and the strategy is reopened under worse conditions.

Your next decision

Before the next steering committee, write down the five decision-makers whose private view you are least certain about. If you cannot confidently predict what each of them would say in a confidential conversation about implementation feasibility, you do not yet have the commitment the board thinks it approved.

That is the point at which independent validation pays for itself many times over. The question is not whether to test commitment. It is whether to test it now, while the strategy can still be adjusted, or later, when it cannot.