Ask someone how they use AI and you'll hear a version of the same thing: they open a chat, ask a question, read the answer, and close the tab. Maybe they paste the answer into an email. Then, later, they open a new chat and do it again.
That's the smallest possible version of the tool. The step most people never take is the one where the answer stops being the destination and becomes the input to the next thing. That's a workflow, and once you see it you start noticing how many of your repeatable tasks have the same shape.
A workflow is steps, where each output is the next input
That's the whole definition. Take something from over here, do something to it, and what comes out goes into the next step. Repeat until you have the thing you actually wanted.
It sounds too simple to be worth a name. It's worth a name because of the contrast:
In the top row, you're the wiring. You ask, you read, you copy the answer somewhere, you decide what to ask next. Every join between two steps is a person doing a small act of clerical work. Four steps means four questions and three copy-pastes.
In the bottom row, the joins are automatic. You describe the chain once, and each step's output lands in the next without you carrying it. Four steps means one instruction and one thing to check at the end.
Same model. Same intelligence. The difference is who does the joining.
Parts of your job are already workflows
Not the job. The judgement calls, the client relationships, the work where the point is that you did it. None of those are chains, and they won't become them. But most weeks contain a handful of repeatable tasks that already have this shape, and nobody has written them down.
Think about one that took an hour last week. Chasing an unpaid invoice, say.
- 01Open the accounting system, find invoices more than 30 days old.Transport
- 02For each one, check whether it has been chased, and when.Transport
- 03Look up the contact for that account.Transport
- 04Write an email that matches how you talk to that customer.Judgement
- 05Read it, send it, note that you did.You approve
Look at the tags. Three of those steps are transport: fetching something from one place and putting it somewhere else. One needs your judgement about this customer, and the last one is you, reading it before it goes. Inside a repeatable task like that one, most of the hour goes on the carrying, not the deciding.
Write a task down as steps and you can see which parts are which. That's the map of what you can hand over, and what stays yours.
Why the chained version isn't just faster
The obvious benefit is speed, and it's real: what took an hour takes four minutes. Three things matter more.
It's repeatable. A chat is a one-off conversation. A workflow is a description of how the job gets done, so it happens the same way on a Tuesday when you're busy as on a Friday when you're not. Consistency is the actual product.
It gets better instead of drifting. When a workflow produces something wrong, you can point at the step that did it and fix that step. In a chat you try again with different words and see what comes back. Fixed steps are debuggable; re-prompting is not.
It scales sideways. Ten invoices takes the same effort to set up as one. That's not true of doing it by hand, and it's not true of chatting.
Where the human stays
Every workflow I build for a client keeps an approval step, and it's not a formality. The last step before anything reaches a customer is a person looking at it and saying yes.
Chained steps mean a mistake early on gets carried to the end and arrives looking confident. A person at the end catches that. That is the trade this whole idea rests on: you hand over the clerical work and keep the judgement, and you get the hour back.
The rule I use: AI does the transport, humans do the deciding. If a step is a decision that would embarrass you if it went wrong, that step has a person in it.
How to find your first one
You don't need a platform to start. You need a candidate: a task that is repeatable, boring, mostly transport, and already connected.
Start with one. Write down the steps by hand, in plain English, the way you'd explain it to a new hire. That document is most of the work; the automation is the easy part afterwards.
If you want a hand finding the first one worth doing, that's precisely the thing I do.