See where work waits between departments, act on it and measure what changes
Investigate where recorded work waits, agree an improvement action with a responsible owner and measure whether the delay falls.
Where included
- Field Sales (iField)Controlled beta
Does this sound familiar?
An order passes from sales to finance to operations to delivery. Each department reports its own figures, delays are explained with opinions, and improvement actions are agreed in meetings without anyone measuring whether they worked.
Who is involved
- Operations or process manager
- Department heads
- Executive who reviews performance
- Owner of each improvement action
From trigger to outcome
Follow the work from the first trigger. Each arrow names what passes along it and carries its evidence status in words, so a planned step never looks like a working one.
How to read the lines
- Solid line: Demonstrated in testing
- Dashed line: Planned
| From | To | What passes | Evidence |
|---|---|---|---|
| From:iKPI | To:iSight | What passes:Pinned performance summary | Demonstrated in testing |
| From:iFlow | To:iKPI | What passes:Workflow timings for measurement | Planned |
| From:iKPI | To:iFlow | What passes:Approved improvement action | Planned |
| From:iField (Where included) | To:iKPI | What passes:Visit records for performance measures | Demonstrated in testing |
Who acts at each hand-off
The people involved, in the order the work passes between them.
Process manager
Compares recorded stages, waiting time and targets for the process
Result: The stage where work waits, from recorded data
Next owner: Department head
Department head
Investigates the delay and agrees an improvement action with an owner
Result: A responsible improvement action
Next owner: Action owner
Action owner
Carries out the agreed action and reports back
Result: A change the next comparison can measure
Next owner: Process manager
Executive
Reviews a pinned performance summary
Result: Priorities decided from recorded figures
Next owner: Process manager
What each product contributes
Each product's part in this workflow, with its current status.
- iKPIRoadmap
Is designed to compare recorded stages, waiting time and targets, telling missing timestamps apart from zero waiting time.
- iSightRoadmap
Is designed to give managers a pinned summary of approved performance figures.
- iFlowRoadmap
Is designed to carry approved actions and approvals as workflows. Connecting it to performance measurement is planned.
- iFieldControlled betaWhere included
Where included, is designed to supply visit records as a source for performance measures.
What your business gains
- Investigation starts from recorded stages, not opinions
- Each improvement action has a responsible owner
- The next comparison shows whether the delay fell
See where to investigate delay, assign a responsible improvement action and measure the result.
A useful measure for a pilot
Waiting time at the slowest stage of one chosen process, compared before and after the improvement action.
What this requires
This workflow is on the roadmap. As designed, it needs these in place:
- Recorded events from the chosen process, from validated event files or an approved API connection.
- The process configured with you: its stages, the owner of each stage and the business calendar.
- Metric definitions and targets approved by your managers.
- Approved real figures before any summary is shared: testing so far uses synthetic data.
Evidence and scope
The pinned performance summary is demonstrated in testing on synthetic data, on code not yet released to customers; so are visit records as a source, where field visits are included. Workflow timings feeding measurement, and approved actions becoming workflows, are planned.
- Demonstrated in testingthe connection passes automated tests in test environments, on code not yet released to customers.
- Plannedit is not built yet. It is shown so you can see the intended workflow.
Each product shows its own status, and none is described as released for general use. Your demo confirms what applies to your deployment.
A suitable starting option
Performance and reporting
Compare what this starting option includes, what it requires and what can be added. Packaging is agreed per deployment.
Questions about this workflow
Do improvement actions turn into workflows by themselves?
No. Passing workflow timings into measurement and turning an approved action into a workflow are both planned connections. Managers record and follow up actions themselves.
Does the department map mean four connected systems?
No. The departments are a map of your process. Measurement works from the events your process records, from files or an approved connection.
Bring one process that keeps waiting
Choose a process where work waits between teams. We walk through how its stages would be measured and how an action would be followed up.
Request a tailored demo of this workflow