
Business context immersion, value stream mapping, a quantified baseline, root-cause design, configuration, control. What actually happens in each phase of a pre-ERP Lean Six Sigma engagement, and what it leaves behind.
Summarised from the Go2Cab business insight series
An ERP programme is not a software project that happens to touch the business. It is a business decision that happens to end in software. The difference is the order of work, and the order is the method.
The six phases below run in sequence, and the sequence is not negotiable. Configuration sits at phase five, not phase one, because a system built before the process is understood simply automates whatever variation was already there. Microsoft Dynamics 365 and Business Central* are excellent at locking in a process; they cannot tell you whether the process was worth locking in.
Each phase has a purpose, a set of Lean Six Sigma tools, a Microsoft platform application, an AI and analytics role, and a headline output. Those are set out in full below.
Before any ERP discussion, we conduct deep operational immersion: interviewing stakeholders, shadowing processes, and documenting your business dynamics, workflows and constraints as they actually run.
Headline output: 100% bespoke to your operations. Nothing enters scoping that nobody observed.
Every value stream is mapped end to end, identifying all value-added and non-value-added steps. Every process touchpoint is documented, measured and stress-tested against your business objectives.
Headline output: VSM — every process mapped, with the waste visible and quantified.
Statistical process capability is measured across all key workflows. We establish a quantified baseline — cycle times, defect rates, throughput — so every future improvement is objectively verifiable rather than merely claimed.
Headline output: to a 3.4 defects per million target, measured on your own data rather than a benchmark.
Root causes of inefficiency, variation and waste are identified and quantified. We then redesign the process to its optimal state before a single line of configuration is written.
Headline output: a process capable of six sigma or better, designed on evidence.
Only now is Dynamics 365 or Business Central configured — built precisely around your redesigned, optimised processes. Every module, workflow and automation reflects your operational context rather than a vendor template.
Headline output: an average 42% waste eliminated by the time the system goes live.
Statistical process controls are embedded into the live environment. Real-time dashboards, alerts and control plans ensure improvements are sustained and continuously refined after go-live.
Headline output: a continuous improvement cycle that outlives the engagement.
Each phase leaves its result in one of the four layers of our process-first business architecture: process, information, control and operating. The layers are set out in The Four-Layer Business Architecture, alongside what each one delivers, how it is proven, and how the two commissioning tracks differ.
*All product names, logos, brands, and AI models mentioned in this article are the property of their respective owners and are used for identification purposes only, without implying endorsement or affiliation with Go2Cab.
The takeaway
Six phases, run in order: understand the operation, map the flow, measure the baseline, root-cause the constraint, configure the platform, then control the gain. Skip one and the software locks in the old process.