Use the estimate as a planning range, not a fixed promise.
Per process, phases total about 16–23 weeks if run back to back. The upper range of discovery allows for December absences; phases may overlap where dependencies allow, but approval gates stay explicit.
Dark bar = lower estimate; light extension = upper estimate (e.g. December absences, data readiness).
Discover & map
Confirm scope, interview teams, map current process, validate systems and pain points. Upper range allows for December absences.
RACI & owners
Validate decision roles, handoffs, process owner and escalation path.
DMAIC improvement
Baseline, analyze causes, test change options and agree control design.
SOPs, KPIs & sign-off
Approve documentation, metric dictionary and ERP-ready requirements.
- December absences, stakeholder availability, data readiness and system integration may extend duration.
- Technical review by Mohammad and process selection confirmation by Hanan are prerequisites to committing dates.
- Run the interim M&E reporting cycle in parallel; do not wait for the end of process mapping.
- Plan a later wave only after Wave 1 capacity and lessons are reviewed.
Planning gates
Gate 1 · Scope
CEO confirms initial processes, sponsor, process owner and expected deliverables.
Gate 2 · Design
Department heads validate AS-IS, RACI, TO-BE, controls and KPI definitions.
Gate 3 · Digitalize
IT confirms feasibility, security and data access; pilot users test ERP workflows and automated reports.