Current-state workflow map
- Triggers and end states
- roles and handoffs
- systems and exceptions
Workflow and process diagnostic
Map the work. Choose the right change.
We work with your team to understand how a business process runs today, where it loses time or control, and which changes are worth making. The answer may be a simpler process, clearer ownership, better-connected tools, rules-based automation or AI.
The diagnostic
Start with the process, not the product.
A documented process rarely tells the whole story. Real work includes exceptions, informal checks, duplicated data, delayed approvals and workarounds that have become normal.
The Workflow Opportunity Map follows one bounded process from its trigger to its outcome. We look at the people, decisions, information, systems and controls involved. This creates a shared view of the work before anyone commits to a platform, automation programme or AI build.
The purpose is to make a sound change decision. The map is useful whether that decision leads to technology, an operating change or no further investment.
What the map examines
We concentrate on the parts of the process that determine whether a change will work in practice.
- 01
Purpose and boundary
The trigger, end state, business or user outcome, process owner and the question the work needs to answer.
- 02
Work and handoffs
Roles, queues, approvals, exceptions, rework and the points where responsibility changes hands.
- 03
Information and tools
Where information enters, how it changes, where it is duplicated and which systems people rely on.
- 04
Controls and constraints
Permissions, policy, audit needs, failure paths, regulation and the decisions that need human judgement.
- 05
Performance evidence
Available information about volume, elapsed time, service quality, errors, cost and demand. Missing evidence is recorded rather than replaced with assumptions.
A short route from uncertainty to a decision.
The method is scoped around one process and one decision. It does not assume that implementation follows.
- 01
Frame
Agree the process boundary, the outcome that matters and the decision the map must support.
- 02
Observe and map
Work with the people involved to trace the current process, including exceptions, tools, information and controls.
- 03
Examine the options
Compare process, ownership, tooling, integration, automation and AI changes against value, feasibility, risk and adoption.
- 04
Recommend and sequence
Set out what should change first, who needs to own it, what evidence is missing and whether to prove, implement, defer or stop.
What you leave with
The detail depends on the process, but the output must be clear enough for the team responsible for the next decision.
Opportunity and constraint register
- Delays and rework
- data and control constraints
- dependencies and owners
Options assessment
- Process changes
- tooling and integration choices
- automation and AI fit
Recommended next step
- Priorities and owners
- measures and risks
- proof scope or stop decision
Decision principles
AI has to earn its place.
AI may be useful when the work depends on variable or unstructured information, complex patterns, search, prediction or generation. It still needs suitable data, clear ownership, proportionate controls and a way to assess whether it is performing well enough.
It is usually the wrong starting point for stable steps that ordinary software, rules or a process change can handle more predictably. We therefore consider the options in a practical order:
- Remove work that does not need to happen.
- Simplify the process and clarify ownership.
- Improve information quality or connect existing systems.
- Automate stable, repeatable steps.
- Use AI where it offers a meaningful advantage and can be controlled.
Suitable when
A process crosses teams or systems and nobody has a reliable end-to-end view; delays, rework or unclear ownership keep recurring; a significant technology decision is being considered; or the team needs to compare options before funding a proof.
The work also needs an accountable process owner and access to people who perform or govern the process.
Not suitable when
The required change is already known and only needs straightforward delivery; the people who do the work cannot take part; the aim is to justify a predetermined AI purchase; or the expected benefit cannot be defined well enough to guide a decision.
What a useful outcome looks like
Your team should be able to explain what is actually happening, which problem is worth addressing, what should change first, which decisions must remain under human control, how improvement will be assessed and whether AI is justified.
Questions
Workflow Opportunity Map FAQs
What is a Workflow Opportunity Map?
It is a structured view of a business process and the opportunities to improve it. It records the current work, handoffs, systems, information, controls and constraints, then compares the available changes and recommends a next step.
Is this an AI assessment?
Not primarily. It is a workflow and process diagnostic. AI is one option alongside process redesign, clearer ownership, integration, existing software and rules-based automation.
Which workflows can be mapped?
The strongest candidates are recurring processes with a clear trigger and outcome, several participants or systems, and a problem worth resolving. We agree the boundary before the work begins rather than attempting to map the whole organisation at once.
Who needs to take part?
Usually the process owner and people who perform the work. Depending on the process, that may also include downstream users and colleagues responsible for technology, data, risk, security or compliance.
What evidence do you need?
Existing process notes, sample inputs and outputs, a view of the systems involved and access to the people doing the work are useful. Perfect documentation or performance data is not required. Missing evidence becomes part of the finding.
What happens after the map?
The recommendation may be a change the team can make itself, a tooling or integration change, a focused proof, a larger implementation, or a decision to defer or stop. Any follow-on work is agreed separately.
Bring us one process that needs a better answer.
Tell us where the work gets stuck, which teams and tools are involved, and what needs to improve. We will use the brief to decide whether a Workflow Opportunity Map is the right next step.