Workflow prioritiser: how to use the results
The prioritiser compares candidate tasks on how often they recur, how long each run takes, how structured the inputs already are, and what a wrong output would cost. It produces an order, so the first project is the one most likely to work rather than the one that sounds most impressive.
( The Detail )
What this tool tells you
A high ranking means a task is a reasonable candidate, not that it is guaranteed to succeed. It does not estimate build effort, judge whether your team will adopt it, or account for a supplier or system that will not cooperate. Those constraints come from whoever knows the operation.
Using it well
Treat the output as a shortlist of conversations rather than a verdict. The most useful thing it produces is usually the question you had not thought to ask, or the gap between what two people in the business assumed was already being tracked.
Take the single highest-ranked item and test whether the business can describe what a good outcome would look like and who would own it. If it cannot, the honest next step is to map that workflow properly before committing to build anything.
How to approach it
Begin with the decision rather than the tool. Name the recurring judgement this affects, the information it depends on, and the person accountable for acting on the result. That framing keeps the first build small enough to inspect and useful enough to matter.
Keep a human review point in the loop until the quality and the failure modes are understood. A system that shows its working - what it drew on, where it is uncertain, and what it deliberately left alone - is one a business can keep running after the initial build.
( Next Step )
Start small enough to review, but on a workflow important enough to show whether a better system is worth building.