Article
Here is a painful truth: if you automate too early, you do not get speed. You get a faster mess.
The most profitable word in ops is not yes. It is not yet.
The moment this shows up
This usually shows up when the team is tired, work feels sloppy, and everyone is a little sick of talking about the same problem.
Someone says, "We should automate this." And honestly, that can sound like relief.
But if the workflow is still changing every week, automation turns into a treadmill. You keep patching edge cases, adding exceptions, and wondering why the thing that was supposed to save time now needs babysitting.
A real example
Say a team wants to automate quote follow-up. The rule sounds simple enough: when a quote is sent, follow up twice.
Then you look at the real workflow. Half the quotes are missing a detail. Some need approval. Some go out from a personal email. Sometimes sales sends them. Sometimes ops does. Sometimes nobody is quite sure whose turn it is, which is always a promising start.
If you automate in that state, the tool will take the blame for a workflow that was never buttoned up in the first place.
The three prerequisites
Before you automate, check three things.
1. Stable inputs
The same key information needs to show up every time. If the inputs are random, the automation will be random too.
2. A clear finish line
You need to be able to say what done means in one sentence. Not in a workshop. Not across six comments. In one sentence.
3. One owner
One person owns done. Not the team. Not a channel. Not "we." One name.
If any of those are missing, the right answer is not yet. That is not hesitation. That is good judgment.
What to do instead
Not yet does not mean do nothing. It means make the workflow real first.
Usually that means one small move:
- make one intake form
- add one approval step
- define done in one sentence
- assign one owner
Nothing glamorous here. That is part of the point.
Once those pieces are in place, automation gets a lot easier. More importantly, it has a fair shot at working.
Why this matters
Building too early is expensive. Waiting until the workflow is clear saves money, saves rework, and gives the next build a chance to stay on the rails.
If you want help picking what is ready and what is not, book a discovery call.
What is the workflow you keep wanting to automate, but it still feels messy?