Current process
Read and copy the request
- Owner
- Operations
- System
- Email and spreadsheet
- Control
- Visual check
- Risk
- Missing fields or conflicting versions
Process comparison
How a process can change when redesigned.
Explore three examples of a current operation and a target workflow. Each step shows who acts, which system they use, how it is controlled and what risk remains. These are illustrative scenarios, not guaranteed outcomes.
Illustrative example · 01
Repetitive manual process
Example: handling a request received by email that needs approval before execution.
Current process
Target workflow
Target workflow
Submit the request in a form
- Owner
- Requester
- System
- Form and shared record
- Control
- Field validation
- Risk
- Incomplete source data
Current process
Ask for approval by email
- Owner
- Manager
- System
- Inbox
- Control
- Manual follow-up
- Risk
- Waiting without a visible status
Target workflow
Route for approval using rules
- Owner
- Manager
- System
- Workflow
- Control
- Recorded status and decision
- Risk
- Outdated rules
Current process
Execute and report closure
- Owner
- Operations
- System
- Work tool and email
- Control
- Later review
- Risk
- Closure without shared evidence
Target workflow
Execute with review and traceability
- Owner
- Operations
- System
- Integrated work tool
- Control
- Human validation and closure log
- Risk
- Exceptions need manual handling
See the example’s conditions and limits
Feasibility conditions
Improvement depends on data quality, a process owner, an available integration and human validation. The actual workflow is defined after reviewing your context.
Illustrative example · 02
Point-to-point integration
Example: passing an order status from one tool to another.
Current process
Target workflow
Current process
Export a file
- Owner
- Operations
- System
- Source system
- Control
- Export review
- Risk
- Incomplete file
Target workflow
Emit the status change
- Owner
- Source system
- System
- Integration interface
- Control
- Data contract and validation
- Risk
- Source unavailable
Current process
Adapt and import the data
- Owner
- Technical team
- System
- File and destination system
- Control
- Manual field comparison
- Risk
- Incorrect mapping or format
Target workflow
Transform and deliver the data
- Owner
- Integration service
- System
- Connector between systems
- Control
- Logging, retry and idempotency
- Risk
- Schema change
Current process
Resolve errors once found
- Owner
- Operations
- System
- Email and separate systems
- Control
- Reactive review
- Risk
- Divergent states
Target workflow
Reconcile and review exceptions
- Owner
- Operations
- System
- Monitoring view
- Control
- Alert and human reconciliation
- Risk
- Unresolved incidents
See the example’s conditions and limits
Feasibility conditions
Improvement depends on data quality, a process owner, an available integration and human validation. The actual workflow is defined after reviewing your context.
Illustrative example · 03
Incident management
Example: handling a service incident reported by a customer.
Current process
Target workflow
Current process
Receive and forward the report
- Owner
- Support
- System
- Control
- Inbox review
- Risk
- Report without an owner
Target workflow
Record and classify the report
- Owner
- Support
- System
- Incident register
- Control
- Required fields and review
- Risk
- Wrong initial classification
Current process
Find context and assign
- Owner
- Coordinator
- System
- Messages and separate tools
- Control
- Manual lookup
- Risk
- Inconsistent priority
Target workflow
Assign with context and priority
- Owner
- Coordinator
- System
- Shared queue
- Control
- Visible rules and human adjustment
- Risk
- Limited team capacity
Current process
Resolve and inform
- Owner
- Specialist
- System
- Work tool and email
- Control
- Manual confirmation
- Risk
- Customer without an updated status
Target workflow
Resolve, validate and communicate
- Owner
- Specialist
- System
- Register and communication channel
- Control
- Closure validation and history
- Risk
- Reopened if the issue persists
See the example’s conditions and limits
Feasibility conditions
Improvement depends on data quality, a process owner, an available integration and human validation. The actual workflow is defined after reviewing your context.