Business Process Block
Document business processes with sequential steps, actors, systems, inputs/outputs, KPIs, and SLA targets.
The Business Process block documents end-to-end business processes. It captures the sequence of activities, responsible actors, systems involved, required inputs, expected outputs, and performance metrics for process monitoring and improvement.
When to Use
Block Properties
| Property | Required | Description |
|---|---|---|
| Process ID | No | Unique identifier (e.g., BP-001) |
| Process Name | Yes | Descriptive title |
| Description | No | Purpose and business value |
| Process Owner | No | Person or role responsible |
| Category | No | Core Business, Support, Management, Operational |
| Trigger Event | No | What initiates the process |
| Process Steps | No | Ordered activities with actor and system tags |
| Inputs | No | Required inputs to the process |
| Outputs | No | Expected deliverables |
| Systems | No | Technology systems involved |
| KPIs | No | Key performance indicators |
| SLA | No | Service level target |
| Status | No | Active, Draft, Under Review, Deprecated, Optimising |
| Notes | No | Additional context or improvement opportunities |
Process Categories
Process Status
Example: Order Fulfilment Process
A core business process for e-commerce order handling.
Example: Employee Onboarding Process
A support process for HR operations.
Example: Change Management Process
A management process for controlled changes.
Best Practices
| Practice | Description |
|---|---|
| Clear Triggers | Define clear triggers for when the process starts |
| Specific Actors | Identify specific actors for each step |
| System Mapping | Map systems to steps for automation opportunities |
| Output Documentation | Document expected outputs from each activity |
| Business-Aligned KPIs | Set measurable KPIs aligned with business goals |
| Realistic SLAs | Define realistic SLAs based on historical performance |
| Regular Review | Review and update processes regularly |
| Exception Handling | Include exception handling and escalation paths |
| Consistent Naming | Use consistent naming across related processes |