The Adversarial Methodology

The Short Version

You cannot prove an M&A valuation or a market-entry thesis correct in advance. The future it depends on has not happened yet. What you can examine now is the evidence underneath it: how strong the proxies are, whether the reasoning was disciplined or worked backwards from a preferred answer, and which known decision biases are in play. Each of the three tools does that job at a different point in the governance cycle.

The intellectual case, and its grounding in Popper on falsification and Kahneman on decision hygiene, is set out in the methodology chapter of the white paper. This page covers what each tool involves, how long it takes, and what the board is handed at the end.

The Three Tools

The Red Team Protocol™ (continuous)

Cadence: continuous within a retainer, or four weeks as a standalone engagement. Addresses: absence of institutionalised challenge.

Applied to a strategic plan, a governance framework, or a decision heading for approval. The principal works from the board papers and the underlying analysis, identifies what the decision is actually resting on, and tests how well the evidence holds each assumption up.

It runs in three phases. The analytical work happens between meetings. Directors then commit their own view privately before they see any of it. Only then does the challenge material come back, alongside a map of where the board’s prior confidence and the findings agree and where they part company.

The standalone version, its deliverables and the four-week schedule are set out on the Red Team Review page.

The Risk Simulation Lab™ (periodic)

Cadence: quarterly or half-yearly within a retainer, or a bespoke 90-day build as a standalone engagement. Addresses: consensus dependency.

A live exercise in which the board and executive work a crisis scenario built for this organisation, using its real escalation routes, committee structure and reporting lines.

The scenarios are chosen to break the story the organisation tells about itself. The growth plan stalls, the load-bearing assumption turns out to be wrong, a regulator moves, or the reputational hit arrives from a direction nobody was watching.

What the principal is recording throughout is behaviour. Who escalated, how quickly, on what authority, and what the board was told at each stage. No document review produces that evidence.

The Pre-Mortem Diagnostic™ (event-driven)

Cadence: event-driven, a two to three week workshop, run before the commitment is made. Addresses: episodic engagement.

Booked ahead of a major capital commitment, a strategic shift, or a structural change. The session opens with the room being told the decision has already failed, twelve months from now, and asked to account for how.

Participants write their answers alone before anyone speaks, which is the point. The principal then aggregates the responses and looks for the clusters, the disagreements, and the failure modes that nobody named individually but that show up once the answers sit side by side.

The board receives a failure-mode map. It sets out the ways this decision could break, ranked by how many people arrived at each one independently and weighted for plausibility. The decision still belongs to the board, which now makes it knowing what it is carrying.

Two Rules That Govern All Three

The reading happens on our side. Assumption mapping, document review, scenario construction and the conversations with the second and third lines are the principal’s work, done between meetings. A non-executive with a day a month cannot absorb that volume, and asking them to is how challenge quietly becomes a formality. What reaches the board is short.

Directors commit before they read. Every structured output is preceded by an anonymous assessment in which each director records their own confidence and their own view of the material risks. It takes a few minutes and it changes what the material can do, because a position already written down is harder to abandon quietly than one still forming in the room.

Deployment Across the SGaaS Tiers

• Diagnostic SGaaS (T1). The Red Team Protocol is the primary instrument, used for the architecture assessment that defines the Diagnostic.
• Retained SGaaS (T2). All three tools deployed on continuous, periodic, and event-driven cadences respectively.
• Embedded SGaaS (T3). All three tools, with direct board application. The principal sits as Independent Board Observer or Mandated Advisor with contractual challenge authority.
• Pre-Exit SGaaS (T4). Diagnostic and Retained tooling, focused on exit readiness and the governance evidence base buyers will examine.

The tools can also be engaged standalone, and frequently serve as the entry point that demonstrates the value of a longer-term relationship.