Automation Starts Before the Automation
A workflow can fail before the automation even starts.
Example:
A maintenance request enters the system:
“Water leaking.”
The temptation is to immediately automate:
→ classify it
→ route it
→ notify a vendor
→ update the tenant
But there’s a problem.
Where is the leak?
How severe is it?
When did it start?
Are there photos?
Can someone access the property?
Has the same issue happened before?
If the input is incomplete, the workflow creates more back-and-forth downstream.
So I'm testing a slightly different way of thinking about automation:
1. Capture the request
2. Check whether the information is complete
3. Collect what's missing
4. Then trigger the operational workflow
The interesting part isn't always replacing a manual task.
Sometimes the biggest opportunity is preventing unnecessary work from being created in the first place.
For anyone building automations: how often do you check input quality before designing the workflow?
