Skip to content

Two Views, One Decision

These are working methods developed through Wardcon’s own practice, not proprietary software or a licensed framework. What follows is a plain-English outline — the detail sits in how each is applied to a specific decision, not in the description below.

01 Mapping the consequences

Tracing what a decision sets in motion

The map runs on a simple chain: the decision, the direct change it causes, how dependencies respond, the effect across the enterprise, and the threshold or outcome that follows.

It is not a risk register. A risk register lists exposure. This traces propagation — the second-, third- and Nth-level effects that only show up once the first change interacts with the rest of the organisation.

Nth Consequence Thinking / the Wardcon Nth Consequence Review.

02

A plan and an owner are not evidence of capability

Wardcon tests whether the organisation can genuinely carry the decision: whether the people, attention, skills, governance, systems, supplier capacity, cash and operational headroom are actually available at the point they will be needed.

Where capability is missing, the answer is not automatically “do not proceed”. The task is to make the condition explicit: what must change, by when, and which evidence would justify proceeding.

03 What comes out of this

Specific enough to be enforced

01

Nth-level Impact Matrix

The business areas most exposed to cascading effects, named and ranked.

02

Friction Registry

The localised risks a standard tracking report overlooks.

03

Execution Blueprint

The exact specialist support the decision actually requires.

04

Operational Roadmap

The client-approved mandate for how and when support is deployed.

Conditions specific enough to be enforced, not a vague reassurance to “maintain close oversight”.