The Pegasus method

From exposure to evidence.

A visible five-stage method that makes decisions, ownership and verification explicit.

Request a scoping call

Who this helps

Built around a buying situation.

Decision makers comparing consultancy approaches
Project and assurance leaders
Buyers who need clear ownership and outputs

Useful when

The trigger is already visible.

Previous consultancy produced reports without closure
Several workstreams need a common decision process
Scope, evidence and professional boundaries must be explicit

The position

A method built around the decision.

Pegasus begins with the exposure, authority and evidence rather than a predetermined package. Each stage creates a visible decision: what matters, what control is proportionate, who will operate it, what evidence demonstrates effectiveness and what must improve next.

A defined scope and accountable decision owners

Controls matched to the real operating context

Evidence that can be reviewed, tested and improved

Scope

What the work includes.

Every engagement is scoped around authority, operating context, available evidence and the decision that must be made.

Context before prescription

Define context, consequence, evidence quality, decision rights, constraints and the smallest valuable scope.

Practical implementation

Translate findings into practical controls, workflows, responsibilities, hold points and usable outputs.

Verification and improvement

Test implementation, record limitations and residual risk, verify actions and create a controlled improvement route.

Method

A controlled route from exposure to evidence.

Decision points, responsibilities and verification stay visible from the start.

Discover

Define the exposure, context, evidence, owners and decision that matters.

Design

Select proportionate controls and make responsibilities and hold points visible.

Implement

Embed the agreed system into the real operating workflow.

Verify

Test whether controls work and whether the evidence supports the conclusion.

Improve

Close actions, learn from exceptions and strengthen the system over time.

Outputs

Evidence designed for use.

Scope and evidence map

Prioritised findings and action ownership

Practical control or implementation pack

Verification record and next-step roadmap

Questions answered

Before you scope the work.

Does every engagement use all five stages?

The logic remains consistent, but depth varies. A focused review may stop after discovery and design; an implementation programme may continue through verification and improvement.

How are limitations handled?

Scope limits, unavailable evidence, assumptions, dependencies and professional boundaries are recorded so a decision maker can understand what the work does and does not support.

Start the conversation

Bring the exposure. Leave with a controlled route forward.

A first conversation is used to understand context, authority and the decision required—not to force a predetermined package.