Find the constraint. Fix the system.
A controlled sequence: diagnose the binding constraint with evidence, plan the deliverables, owners and rollback before anything ships, implement through staging and change control, and measure the result against the baseline.
Diagnose
Define the problem, the measures, the sources and their limitations — then separate facts from assumptions and isolate the primary constraint.
Plan
Deliverables, owners, dependencies, acceptance criteria and rollback.
Implement
Ship approved work through staging, testing and change control.
Measure
Record the result against the baseline and choose the next constraint.
Diagnose
Diagnose before prescribing
The diagnosis distinguishes the binding constraint from visible symptoms. Facts, client statements, assumptions and estimates are kept separate, and missing or unreliable data is treated as a finding — not papered over.
Every material finding carries evidence, a confidence level and a business consequence. A finding without all three is an opinion, and we label it as one.
Opportunities are ranked by impact, evidence confidence, urgency and feasibility — so the order of work is a conclusion rather than a preference.
Migration is never the default recommendation. Platform economics are compared first, because a migration relocates a constraint more often than it removes one.
Diagnose artifacts
Findings register
Each finding with its evidence, confidence level and business consequence.
Ranked opportunity list
Impact, confidence, urgency and feasibility, scored and ordered.
Plan
Plan before you commit resources
A named constraint is not yet a scoped project. Before anything ships, the finding becomes a written plan: what changes, who owns each piece, what it depends on, how the work will be accepted, and how to undo it if something breaks.
Each deliverable has a name, an owner and a due date before work starts — not assigned informally once the clock is already running.
What blocks what, and who has to sign off before the next step can begin, is written down rather than discovered mid-implementation.
Done is defined before work starts, in terms specific enough to verify — and the rollback path is agreed before the change ships, not improvised after something breaks.
Plan artifacts
Scope document
Deliverables, owners and dependencies, agreed in writing before implementation starts.
Acceptance criteria
The specific, verifiable definition of done for the approved change.
Implement
Implement with production safety first
Production safety outranks schedule pressure. No work starts without an approved scope and acceptance criteria, and no scope change proceeds without its impact on fee, timeline and risk documented in writing.
Staging, verified backups, rollback triggers and least-privilege access on every material change. The way back is tested before the way forward is taken.
One accountable owner per decision, deliverable, metric and commitment. Shared ownership is how work quietly stops being anyone’s.
Weekly status reports describe outcome risk — not activity volume. A busy week that moved nothing is reported as a week that moved nothing.
Implement artifacts
Approved scope
Deliverables and acceptance criteria, agreed in writing before work starts.
Rollback plan
Backup, trigger conditions and the tested route back to the previous state.
Measure
Measure what the constraint actually affects
Only outcomes connected to the active constraint are measured: operating cost removed, manual hours eliminated, launch lead time, error rates, conversion or retention where those are the binding issue. Estimates are labelled as estimates.
A documented baseline before implementation, with its sources and its limitations written down at the same time — not reconstructed afterwards.
Immediate implementation outputs are separated from lagging commercial results, because conflating the two is how agencies claim credit they have not earned.
Results are reported with context, never converted into claims the evidence cannot support. Where the data is thin, we say so instead of rounding up.
Measure artifacts
Baseline document
The measures, their sources and their stated limitations.
Outcome report
Result against baseline, with every estimate labelled as an estimate.
Find my constraint
This sequence runs behind every engagement. Start it with a free fit check — we say honestly whether the paid step is warranted.