Our Approach
Discover. Improve. Execute. Sustain.
Our capabilities describe what we can do. This is the method behind them — the four stages every engagement runs through, and the principles that keep the work honest from the first conversation to the measurement that happens after we leave.
Four stages, one path
- Discover — find the real constraint
- Improve — redesign what the evidence supports
- Execute — deliver the change into the operation
- Sustain — measure after we leave
The method
One continuous path, not four separate phases.
The stages overlap and feed each other. Discovery keeps running while we improve. Execution starts while the design is still being proven. Sustainment is built into the work from the beginning, not added at the end.
- 01
Discover
Understand what is actually happening.
What happens
Business, process, people, data, and opportunity — read directly rather than inferred from a deck. We size the gap before proposing anything.
What you keep
- Operational and process assessment against real transaction data
- Interviews across leadership, management, and the frontline
- Constraint, waste, and variation analysis
- Quantified opportunity with the assumptions stated
- 02
Improve
Redesign the work, not the org chart.
What happens
Root causes solved, waste eliminated, processes redesigned around value and flow. The target state is specified precisely enough to be built.
What you keep
- Root cause analysis and solution design
- Future-state process and flow design
- Pilot, measure, iterate
- Business case tied to an agreed baseline
- 03
Execute
Turn the design into a delivered initiative.
What happens
Structured delivery using the right method for the work — predictive, agile, or hybrid — with governance, risk management, and executive visibility.
What you keep
- Initiative structure, plan, and cadence
- Predictive, agile, or hybrid delivery approach by workstream
- Risk, dependency, and decision management
- Implementation, cutover, and stabilization
- 04
Sustain
Make the gain permanent.
What happens
Ownership, metrics, governance, standard work, and adoption embedded so performance holds after the engagement closes.
What you keep
- Named owners and control plans
- Operating cadence and performance reviews
- Standard work and enablement
- Post-implementation measurement against baseline
What working with us looks like
From the first conversation to a validated result.
No fixed calendar. Each step ends when the work and the data say it does — and each one leaves you with something you keep.
The first conversation
You describe the outcome you need and what is standing in the way. We say what a realistic baseline and target look like — and whether this is work we should be doing together at all.
You keep: An honest read on whether the opportunity is real.
The data we ask for
Whatever already exists: volumes, cycle times, labor hours, defect and rework records, cost lines, service levels, system exports. We work from your operating data, not from a survey.
You keep: A defensible baseline your finance team recognizes.
Sizing the opportunity
The constraint is isolated and the gap is quantified with the assumptions written down. Nothing is presented as a range with no arithmetic behind it.
You keep: A prioritized opportunity set with the math shown.
Delivery, on the right rules
The predictive parts get sequence and dependency management. The adaptive parts get short cycles and fast feedback. One governance view over both, with the honest status.
You keep: Implemented change in the operation, not a recommendation.
Validation and handover
The measure is re-run against the agreed baseline, the control plan and ownership move to your team, and the check points are set by the process rather than a fixed calendar.
You keep: A validated result and the controls that hold it.
Deliverables
Exactly what you receive at each stage.
Every stage ends with named, documented artifacts you keep. This is not a summary deck handed over at closeout — it is the work product that lets your team hold the gain after we leave.
Discover
- Current-state process and value stream maps
- Constraint, waste, and variation analysis report
- Quantified opportunity sizing with stated assumptions
- Prioritized opportunity register
- Baseline performance snapshot
Improve
- Root cause analysis documentation
- Future-state process and flow design
- Business case tied to the agreed baseline
- Pilot results and measurement plan
- Target-state specification ready to build
Execute
- Initiative charter, plan, and delivery cadence
- Governance and decision-rights framework
- Risk and dependency register
- Implementation and cutover plan
- Executive status and measurement reporting
Sustain
- Named owners and control plans
- Operating cadence and performance review structure
- Standard work documentation
- Adoption and enablement materials
- Post-implementation measurement report against baseline
Operating principles
The rules that hold the method together.
The four stages describe the sequence. These are the principles that govern how each stage is run — the standard we hold ourselves to regardless of the scope or the industry.
Evidence before opinion
We read the operation directly — data, observation, frontline interviews — before we propose anything. The gap gets sized with the assumptions written down.
The method follows the work
Fixed sequence and hard dependencies run predictively. Evolving scope and new ways of working run adaptively. We do not force one rhythm onto both.
One continuous path
Discover, Improve, Execute, and Sustain are not separate phases with handoffs. The people who sized the opportunity are accountable for the result.
Sustain is designed at the start
Ownership, metrics, and control plans are built into the work from day one — not bolted on at closeout — so the gain survives the end of the project.
Delivery method
The method follows the work, not the other way around.
Inside Execute, the delivery approach is chosen per workstream — not imposed on the whole program. That is what keeps improvement work from being forced into a Gantt chart it does not fit, and keeps hard-deadline work from drifting under the label of "agile."
Predictive where sequence rules
Fixed dates, hard dependencies, regulatory or physical constraints. Plan it, hold it, manage the critical path.
Adaptive where learning rules
Process redesign, reporting, new ways of working. Short cycles, real feedback, value delivered before certainty arrives.
Hybrid, honestly governed
Both approaches in one program, each measured on its own terms rather than forced into a single status format.
Questions, by stage
The questions we get asked most.
Grouped by stage, because the concerns are different at each point in the work — what we measure against in Discover is not what worries a sponsor mid-Execute.
Discover
Improve
Execute
Sustain
Start the conversation
Bring us the outcome that isn't moving.
A short conversation about the outcome you need, the constraint in the way, and whether we are the right partner for it.