Process Analysis and Improvement
This domain tests as-is and to-be analysis, value-added classification and root-cause techniques used to improve a process with evidence rather than opinion.
As-is and to-be
Process analysis evaluates the current (as-is) process to establish a baseline and identify improvement opportunities. As-is models must be validated with participants and data; a workshop-only model may be fiction. To-be design describes the future process with measurable targets. Value-added analysis classifies steps as value-adding (the customer values it), business-value-adding (required by regulation or risk) and non-value-adding (waste). Root-cause analysis moves from symptom to cause using 5 Whys, Ishikawa diagrams and Pareto analysis. Process mining can reconstruct actual flows from event logs.
Worked example
Invoice approval takes ten days. Value analysis shows approval by three managers is business-value-adding but sequential; rework from missing purchase orders is non-value-adding. A 5 Whys trace finds the root cause is that purchase orders are optional in the requisition form. To-be design makes a purchase order mandatory and delegates approval below a threshold. Target cycle time: two days.
Traps
Do not treat all non-value-adding steps as removable; some are compliance-required. Do not accept the first symptom as root cause. Do not redesign before validating the as-is. Avoid measuring only activity time and ignoring waiting time, which often dominates cycle time.