Understand
A proposed before-and-after workflow
Department leaders maintain separate lists of problems and propose unrelated technology purchases.
Process owners use a shared current-state map, score opportunities against value, effort, risk, readiness, and adoption, then sponsor a bounded first project with defined evidence.
The future state remains a design until it is tested with the people, data, systems, and exceptions in scope.
Deliver
Data and decisions needed
Access is limited to what the agreed work needs. Client owners approve source authority, operational rules, and acceptance criteria.
| Reference | Input or decision to establish |
|---|---|
| 01 | Representative process records and reports |
| 02 | System and interface inventory |
| 03 | Known constraints, incidents, and planned changes |
| 04 | Stakeholder availability and decision rights |
Deliver
Delivery sequence
A bounded sequence protects continuity and makes learning visible before wider rollout.
- 01Frame business outcomes and exclusionsDefine evidence and the exception path
- 02Observe representative workflowsDefine evidence and the exception path
- 03Map data, systems, handoffs, and failure pointsDefine evidence and the exception path
- 04Score opportunities and dependenciesDefine evidence and the exception path
- 05Define a pilot and governance cadenceDefine evidence and the exception path
- 06Present roadmap options and decision recordConfirm ownership and handover
Govern
How it fits existing systems
Existing systems are mapped by business responsibility, supported interface, data authority, update timing, and failure behavior. The design may integrate, configure, retain, or replace a component; no universal compatibility is assumed.
Govern
When a different approach may be better
If one well-defined workflow is already causing an urgent and measurable problem, a focused discovery and pilot may be more useful than an enterprise-wide strategy exercise.