Understand first. Change with purpose.

Five stages guide the work. We agree on the scope, outputs and starting point with your team.

Understand

Understand the goals, constraints and work as it happens.

Shared problem statement

A short written description of the problem, who it affects and what a good outcome would look like, agreed on by the people involved before solutions are discussed.
Map of how work happens now

A step-by-step picture of how requests and information move today, including where work waits, repeats or is retyped.
Agreed starting point

The current measures, such as volumes, waiting times or error counts, recorded before anything changes so later results can be compared.

For example A one-page map of where requests wait, who handles them and where information is retyped.

Design

Agree on how the work should change: the process, responsibilities, measures and the role of technology.

Proposed workflow

The redesigned sequence of steps, who does each one and what information passes between them, reviewed with the people who will use it.
Responsibility and decision map

For each step: who owns the work, who makes the decision, who is consulted and where issues are escalated.
Measure definitions

For each measure: what it counts, where the data comes from, how often it is updated and which decision it supports.

For example A map of the owner, decision-maker and escalation path for each step.

Build

Create or configure the agreed solution, test it and document how it works.

Configured or built solution

The agreed workflow put into a tool: an existing product configured to fit, or a custom application where nothing suitable exists.
Test scenarios

Realistic cases, including exceptions, worked through before launch to check that the solution handles the work as agreed.
System documentation

How the solution works, its rules and settings, and who maintains it, written so someone other than the builder can support it.

For example A short guide to the workflow, routing rules and maintenance responsibilities.

Adopt

Pilot with the people who will use the change. Train, support and adjust.

Pilot plan

Who tries the change first, what support they receive and what will be reviewed before a wider rollout.
Role-specific guidance

Short instructions for each role, covering only the steps and decisions that person handles.
Record of changes

A log of what was adjusted during the pilot and why, so later decisions can be traced.

For example A pilot summary of what confused people, what changed and what needs attention.

Evaluate

Review results, use and quality against the starting point, alongside the experience of the people doing the work.

Evaluation summary

What changed, what worked, what did not, and what the people doing the work reported.
Comparison with the starting point

The agreed measures compared with the starting point recorded at the beginning, with any limits of the comparison stated plainly.
Recommended next steps

What to keep, adjust or stop, and what to look at next, in priority order.

For example A before-and-after review of agreed measures, alongside feedback from the people doing the work.

Conceptual close-up of limestone, olive ceramic and walnut curves meeting at a brushed brass junction.

Informed by industrial-organizational psychology.

Industrial-organizational psychology studies people at work, including decisions, communication and collaboration. That perspective informs how we understand the problem, involve people and evaluate change. These five stages are a practical way of working, not a validated proprietary method.

What to expect.

Collaboration: Working sessions with the people doing the work, as well as leadership.
Your participation: A named contact and access to the people, information and decisions the work needs.
Data handling: Share only what the work requires. Agree on access, storage and confidentiality before sharing it.
AI use: Agree on approved tools, data limits, human review and accountability before AI is used with your information.
Scope: A written scope defining the problem, included stages, exclusions and review points.
Ownership: Ownership of deliverables, code, data, accounts and subscriptions is agreed on before anything is built.
After launch: Documentation, training, support and maintenance are agreed on during scoping.

Talk through the work.

Start a conversation