Which Workflows Should You Point AI At First?

Why do the visible workflows get chosen first?

Three forces push in the same direction, and none of them are stupid.

The first is demonstrability. A workflow you can show on a screen in a ten-minute meeting will beat a workflow you would have to explain, every time, regardless of value. The second is ownership. The tasks that come up in a cross-functional session are the ones people are comfortable volunteering, which tends to mean tasks nobody is protective of and nobody is measured on. The third is risk. A pilot on a low-stakes workflow is easy to approve, because if it fails nothing happens, which is also the reason it does not matter much when it succeeds.

Underneath all three is a gap in who decides. Microsoft's 2024 Work Trend Index found that 60% of leaders worry their organization's leadership lacks a plan and vision for implementing AI. Direction, in the sense of choosing which work AI should touch and in what order, is a strategic decision that usually gets made by whoever was free on a Tuesday.

What separates a workflow worth starting from one that just demos well?

Whether AI can do the task is rarely the interesting question any more. For most tasks on most whiteboards, it can. The harder question is what happens to the time it gives back.

Four tests do most of the sorting. They take about fifteen minutes to run against a candidate workflow, and they can be run by the person who owns the work rather than by a consultant.

Test	What you are asking	A candidate that fails it
The owner test	Does the hour it saves land in one identifiable person's week?	"Everyone spends less time on first drafts"
The critical path test	Is this step what the next step is waiting for?	Faster deck formatting on a deck that then sits three days with legal
The destination test	Is there somewhere for the extra output to go?	Tripling content volume when review capacity is unchanged
The consequence test	Does something downstream have to change if this works?	A summary nobody has agreed to read or act on

A workflow that passes all four is usually less glamorous than the ones that came out of the session. It is often a workflow with a queue in front of it, a deadline behind it, and one named person in the middle.

The critical path test is the one that eliminates the most candidates, and it is the one people resist. Saving forty minutes on a task that was never holding anything up produces a genuinely better day for the person doing it, and no change at all to when the work reaches the customer. That is a real benefit. It is just not a benefit that reaches the P&L, and if the program was funded on a return, someone is going to ask.

What about the workflows that look bad on paper?

The best candidates often look unattractive at selection time, for structural reasons.

They tend to sit inside one function, so they do not surface in a cross-functional workshop. They are frequently owned by someone senior enough that their time is expensive and protected, which makes them awkward to volunteer. They often involve judgment rather than production, so the AI model's role is narrower and the demo is less impressive. And they usually require something to change downstream, which means the work does not end when the tool is switched on.

Consider a marketing organization where the true constraint is the approval cycle. Campaign concepts wait on input from stakeholders who never see the brief at the same time. Pointing AI at concept generation doubles the number of concepts entering a nine-day queue. Pointing it at preparing decision-ready briefs, with options, tradeoffs and a recommendation, so that a stakeholder can respond in one pass, shortens the cycle. The second one is harder to pilot, less fun to present, and worth considerably more.

That second option also requires the three stakeholders to agree to a new way of reviewing. This is the part that gets left out of AI roadmaps, and it is why the sequence matters more than the tool selection.

A useful habit when the list gets built: for each candidate, write one sentence describing what a person does differently on the Monday after it goes live, and who that person is. Candidates that cannot produce that sentence belong in a backlog rather than a roadmap, and the sentence usually takes under a minute to attempt. The resources library has more on how the chain gets diagnosed in practice.

Direction is the third link, and it is usually unowned

Average Robot describes the distance between what a leader expected AI to deliver and what it is delivering as the AI Profitability Gap™. The chain that explains it runs Investment, Usage, Direction, Skill, Reinvestment, Return.

Investment and Usage get measured, because finance tracks the spend and the vendor tracks the seats. Direction sits immediately after them and nobody measures it, because it is a decision rather than a number. Every organization has made that decision, whether or not anyone recognizes it as a decision. The list on the whiteboard was the decision.

AR's working order is people before process before platform, and Direction is where the process question lands. Before you can redesign a workflow, you have to have chosen the right one, and the right one is defined by where a saved hour converts into capacity, revenue, or a cost that leaves.

If you want to pressure-test the list you already have, the AI Profit Readiness Assessment will tell you whether Direction is where your return is stalling or whether the break is further along the chain. If the list needs rebuilding against evidence from your own workforce rather than a workshop, that is what the AI Profit Sprint is built to do, with the research, the prioritized plan, and the first quick wins. Either way, the useful move is to go back to the whiteboard list and run the four tests on it before the next tool gets approved.