What it looks like inside the business
Three pilots are running and nobody remembers who approved the second one. The first build went to the team with the most vocal sponsor, and it automated a task that happens twice a month. A software vendor has proposed an AI feature that solves the vendor's roadmap, and the renewal is due. Meanwhile the workflow that burns twenty hours a week sits untouched, because it belongs to a quiet department.
Why it happens
Selection by enthusiasm. Workflows get chosen because someone is excited, a demo was impressive, or a competitor announced something. The questions that should drive selection are less exciting: how often does this work happen, what does an error cost, is the data ready, can this team absorb a change right now. Those questions are rarely asked first.
The end state
A scored shortlist. Every candidate workflow ranked on the same five measures: value, frequency, feasibility, risk and readiness. Leaders can see why the top workflow is on top, defend the choice to a board, and point to the evidence when someone lobbies for their pet project. The first build starts with the organisation already agreed on why.
How the work gets there
Momentum Diagnostic, stages 01–02 of the Momentum Cycle. Assess reviews systems, data, workflows and people. Prioritise scores the candidates. The output is the shortlist, the risks to avoid, and the evidence behind the recommendation.
| Workflow | Value | Frequency | Feasibility | Risk | Readiness | Total |
|---|---|---|---|---|---|---|
| 01Invoice matching | 5 | 5 | 4 | 4 | 4 | 22 |
| 02Enquiry triage | 4 | 5 | 4 | 3 | 3 | 19 |
| 03Job scheduling | 4 | 4 | 3 | 3 | 3 | 17 |
| 04Report assembly | 3 | 4 | 4 | 3 | 2 | 16 |
| 05Onboarding pack | 3 | 2 | 4 | 4 | 3 | 16 |
The evidence chooses the workflow.