The Assigned Skeptic: Institutionalising Challenge Before the Board Commits

Most UK boards say they welcome challenge. Fewer can point to the moment in the meeting when challenge was formally invited, recorded and answered. The gap matters because major decisions rarely fail for want of enthusiasm. They fail because a central assumption went untested, an alternative was never articulated, or a director with a relevant concern judged the moment unsuitable for dissent.

A red team protocol offers a practical remedy. It is not a permanent opposition, nor a substitute for executive accountability. It is a rotating, time-bound assignment that gives one or two directors a defined role in testing a proposal before the board commits. The purpose is not to slow decision-making but to improve its quality and to make the board's challenge function visible in its records.

Why informal challenge is not enough

Challenge that depends on confidence, hierarchy and timing is unevenly distributed. The director who has worked in a regulated industry may see a compliance risk that others miss. The director with recent operational experience may recognise an implementation problem. Yet neither may speak if the proposal has been socialised before the meeting and the board pack presents a single, polished route forward.

In these circumstances, minutes often record consensus rather than the questions that produced it. That is a governance weakness. The UK Corporate Governance Code places constructive challenge at the centre of effective board behaviour, but a principle needs a mechanism. A red team assignment supplies one without turning every agenda item into a debate.

Designing the rotating assignment

The chair should appoint the red team at the point a major decision is tabled, not after the paper has been circulated. For listed and private companies alike, the trigger can be defined by thresholds: acquisitions above a set value, material capital expenditure, entry into a new market, significant financing, major technology investment or a substantial change in operating model.

The appointees should not include the proposer or any director with a conflict of interest. Rotation is essential. If the same sceptic is always appointed, challenge becomes a personality rather than a process. A simple rota, reviewed annually, can ensure that different directors take the role and that the burden does not fall on one or two individuals.

The brief should be precise. The red team is asked to assume the proposal has failed and to identify the assumptions that would have to hold for success, the evidence that is missing, the alternatives that were not considered and the second-order consequences that the paper does not address. It is not asked to design the alternative strategy or to second-guess management's operational judgement. Its output is a short note or a structured set of questions, submitted to the chair and the proposer before the decision meeting.

A pre-mortem question set

A standard question set improves consistency and reduces the risk that the red team merely repeats the board's existing debate. Directors might ask:

• What must be true for this proposal to deliver its stated outcome?
• Which of those assumptions is least supported by evidence?
• What would a regulator, customer, competitor or lender see that we have not addressed?
• What would make us pause or reverse the decision within the first year?
• Which leading indicators would tell us the thesis is failing?
• What is the cost of delay, and what is the cost of being wrong?
• If we were starting from a blank page, would this still be the preferred option?

The chair should ensure the questions are answered in the meeting, not merely noted. Some may be resolved by management before the decision is taken. Others may need to be carried forward as conditions or monitoring points. The distinction matters: a red team exercise that produces no change to the paper or the decision should still produce a record of why the concerns were judged insufficient.

Minutes that do more than record consensus

The minute should record the appointment of the red team, the principal questions raised, the responses given and any unresolved concerns. It should also identify who is responsible for follow-up and when the board will revisit the assumptions.

There is a balance to strike. Minutes should not attribute every sceptical question to a named director if that discourages candour, but they should not be so anodyne that they obscure the challenge. A useful formulation is to record that the red team noted a specific risk, that management responded in a particular way, and that the board decided to proceed with named monitoring conditions. That gives future readers a clear account of what was tested and what was accepted.

For sensitive matters, the chair may agree that the red team's note is circulated to directors only and summarised in the minutes. The objective is not transparency for its own sake but a reliable record that challenge occurred before commitment.

Follow-up and closure

A red team protocol is incomplete without a follow-up loop. At the next meeting, or at a defined interval such as thirty or sixty days, the board should review whether the key assumptions are holding. If disconfirming evidence emerges, the chair should have an agreed route to escalate the matter back to the board rather than leaving it with management.

This follow-up need not be elaborate. A standing item on the agenda, linked to the board's risk register and decision log, is sufficient. The point is to close the loop between the challenge given before the decision and the evidence available afterwards.

Keeping dissent functional

A red team can become dysfunctional if it is treated as a permanent minority, a test of loyalty or a platform for personal opposition. The chair must set the tone: the red team is a temporary assignment, its questions are part of the decision process and the proposer has a right of reply. Time limits should be agreed so that challenge does not become filibuster.

Boards should also review the protocol annually. Did it improve the quality of papers? Did it surface risks earlier? Did directors report that challenge was easier to offer? The test is not whether the red team agreed with the final decision, but whether the board can demonstrate that it tested the decision before making it.

Constructive dissent is not an act of individual bravery. It is a governance routine. Giving it a job description, a rota and a minute is a modest change that can make a material difference to how UK boards reach consequential decisions.