Watch the work, write it down, then change it
Most process improvement fails because it starts with the process people describe rather than the process people perform. We reverse that order.
The four stages
Every engagement follows the same shape, regardless of which service you buy.
Observe
We sit with the people doing the work and record what actually happens, including the shortcuts. This usually takes two to three days spread over a fortnight.
Reconcile
We compare what we observed against what the team believes happens. The gap between the two is almost always the interesting part.
Document
We write the observed process honestly, then agree which parts should change. Documentation and improvement are separate steps on purpose.
Validate
Someone who has never done the task follows the document unaided. Every point where they get stuck becomes a revision.
Why this order matters
When you ask a team to describe their process, you get the version they believe they follow. It is rarely wrong on purpose — people genuinely do not notice the workarounds they have built up over years.
Documenting that described version produces a manual for a process nobody runs. Three months later it is in a folder nobody opens, and the real process is still in three people's heads.
Observing first costs a few extra days and saves the entire engagement.
What observation looks like in practice
- Two to three days on site or on calls, at different times of day
- Recording where information is looked up, and where it is guessed
- Noting every spreadsheet that exists only because a system does not
- Following one item end to end rather than sampling tasks
- Asking “what happens when this goes wrong” at each step
Principles we work to
Shorter is more likely to survive
A one-page SOP gets followed. A twelve-page one gets filed. We cut until it stops being usable, then add one line back.
Name the owner
Every document, register and review has one named person responsible. Shared ownership means no ownership.
Design for the busiest week
A process that only works on a quiet Tuesday is not a process. We test against peak conditions, not average ones.
Leave the reasoning visible
Every decision in a document says why. Without the reasoning, the next person cannot tell which parts are load-bearing.
Build with the team, not for them
Drafts are written alongside the people who will use them. Resistance usually means the document is wrong, not that the team is difficult.
Make revision cheap
Documents change. We build a revision cycle and a change log into every deliverable so keeping it current takes minutes, not a project.
What we need from you
- One decision-maker available for the diagnostic session
- Two hours of the delivery team's time in the first week
- Read access to whatever already exists, however messy
- Honesty about what has been tried and abandoned before
That is genuinely all. We do not need a project manager, a steering committee or a sponsor who never attends.
What you get from us
- A written scope with a fixed price before anything starts
- Working drafts during the engagement, not a reveal at the end
- Editable source files for everything produced
- One month of question-answering after handover
No slide decks unless you ask for one, and no recommendations we would not implement ourselves.
See how this looks for your team
The diagnostic session is where the approach meets your actual operation.