The Decoded Method
A three-layer system for documenting how your business actually runs. Plain English, one page per process, built to be handed over instead of held in one person's head.
7-page PDF · no email required
Why most process documentation fails
Most businesses keep their processes in one place: someone's head. It works, right up until that person is on holiday, off sick, or leaves. Then the process leaves with them, and everyone else is guessing.
The usual fix is a giant quality manual. That fails for the opposite reason: it's too long to keep up to date, so it goes stale, and once it's stale nobody trusts it.
The Decoded Method is the middle path. ISO 9001 principles without the ISO overhead. A continuous improvement habit without the ceremony. Lean enough to actually keep alive.
Three layers, each with a job
Together they make a system you can hand to a new starter and trust them to follow. Here is how the three layers connect.
The Process Register
The spine. One row per process: what it's called, who owns it, and when it was last looked at. Often the first time a business has everything it does written down in one place.
- Ref — a short code, e.g. TB-PR-001
- Owner — one named person, never "the team"
- Category — Delivery, Sales, Admin, Finance, Marketing, or Tech
- Status — active, draft, review, or archived
- Last reviewed — the month it was last checked
The SOPs
The how-to layer. One page per process, a hard limit. If it needs more than a page, it's two processes, not one. Five sections, no more, no fewer.
- What this process does — one sentence: what it produces and why it exists
- Trigger — the specific event that starts it, never "when needed"
- Steps — numbered, plain English, actionable
- What good looks like — a measurable outcome, so you know it worked
- AI skills — which tools to reach for, and in what order
The Improvement Log
The Kaizen layer. When something breaks or gets better, you log it in three fields, nothing more. Every entry points back to the process it changed, so the register stays honest over time.
- What broke — what was failing, inconsistent, or slow
- What changed — what you actually altered
- Result — what improved, and how you know
The six principles
Plain English.
If the least experienced person can't follow it without asking, it's still a draft.
One page per process.
If it needs more than a page, split it.
Owner on everything.
One named person. Not a team.
Reviewed regularly.
Quarterly for most; at each milestone for active builds.
Delivery-linked.
Every system handed over ships with its process pack. Handover is never verbal-only.
ISO-ready, not ISO-burdened.
Maps to ISO 9001 principles, without the certification weight.
The register we run Decoded Ops on
Twelve processes, each owned, each with a status. The same artefact a Clarity engagement produces for a client, usually the first time they've seen their whole operation on one page.
| Ref | Process | Status |
|---|---|---|
| DO-PR-001 | Discovery Day Delivery | active |
| DO-PR-002 | Clarity Audit & Report | active |
| DO-PR-003 | New Client Onboarding | active |
| DO-PR-004 | Proposal Build & Sign-off | active |
| DO-PR-005 | App Requirements Capture | active |
| DO-PR-006 | ERP/eCommerce Integration Scoping | active |
| DO-PR-007 | Monthly Retained Review | active |
| DO-PR-008 | Invoice & Billing Cycle | active |
| DO-PR-009 | Client Handover & Sign-off | draft |
| DO-PR-010 | Process Pack Production | draft |
| DO-PR-011 | LinkedIn Content Publishing | review |
| DO-PR-012 | Sub-contractor Engagement | draft |
Get the whole playbook, free
Seven pages: the three layers with worked examples, the six principles, and a self-assessment scorecard to see where your operation stands right now. No email required.
Or book a call directlyWant it run across your own operation? A Clarity engagement builds your Process Register with you, mapping what you do, who owns it, and where the gaps are. Retained clients get the Method as a living hub I host and keep current, not a document that goes stale.