The most interesting automation is not always the one that does the most. Sometimes it is the one that quietly prepares the information a person needs to make a better decision.
That is where we like to start: with a repeatable handover, an understandable boundary, and a human owner.
Find the repeatable part
Look at a process that happens often. A request arrives. Someone copies a few fields. Another person looks for a document. A third person asks whether the details are complete.
There may be a useful opportunity to organize that handover. There may also be exceptions that should stay with a person. Both observations belong in the design.
Make the boundary explicit
A workflow should have a clear answer to “what is this allowed to do?” Preparing a draft and sending it to a customer are different actions. Suggesting a category and changing a financial record are different responsibilities.
Start with the narrowest useful permission. The system should not need access to everything simply because one part of the process could benefit from automation.
Expect incomplete information
Real requests are not always tidy. A field may be missing, an external service may be unavailable, or the same request may arrive twice. The workflow needs a way to handle those situations without pretending the work succeeded.
A practical review conversation includes:
- Which inputs must be present?
- What counts as a duplicate?
- Who reviews uncertain suggestions?
- How can the workflow be paused?
- What record explains the action afterward?
These questions make the automation easier to supervise and easier to improve.
Keep a person’s next step visible
The best output may be a well-organized review queue, not an unattended final decision. When a person can see the context, the suggestion, and the reason for escalation, the tool becomes a useful collaborator.
We treat automation as a product-design problem as much as a technical one. It should fit the way people work, not ask them to work around it.
Thoughts worth sharing.
Comments are reviewed before publication. Your email is never displayed.
