
The tempting order is: pick a tool, then invent a use for it. That is how you end up with a chatbot nobody asked for and the same backlog on Monday.
The useful order is the other way round.
The sequence
Question the requirement. Is this job real? Who needs the output? What happens if you do it less often?
Delete. If it is not required, stop. Do not build a clever way to keep it.
Simplify. One owner. One list. Fewer steps. Fewer fields. The version a new starter could follow without a walkthrough from the person who “just knows.”
Speed it up. Same work, less waiting. Batch it. Answer it once. Cut the loop where three people touch a file to add one line.
Automate last. Only when the steps are worth keeping, and are boring enough that a tool will not make them worse.
If you skip to the end, you cement the junk. You also make it harder to delete later, because now it is “in the system.”
What automation is for
Automation is for the step you have already decided must happen, the same way, often enough that a person is wasted on it. Pulling last month’s figures into a one-page note. Turning a completed checklist into the email you always send. Drafting the first pass of a quote you will still read.
It is not for judgement you are not willing to stand over. It is not for a process you have not watched. It is not a way to avoid talking to the people who do the work.
How we use this in the room
In an Accendo Intelligence session we do not start with a product list. We start with your week. We ask, we watch, we cut. A tool appears only if it is the last move, not the first.
That is why the half-day workshop ends with a short, ordered list instead of a stack of logins. You should be able to see, in a month, whether the change saved time. If it did not, we drop it. No loyalty to a subscription.
If you have already been sold the tool, come anyway. The useful question is still the same: what should we have deleted before we automated it?


