"Automation" and "automated system" get used constantly, often without much clarity about what's actually meant. This article is a short introduction to thinking about automation properly before diving into building anything in Zoho.
Define it properly first: Trigger, Action, Outcome
Before building any automation, it helps to break your requirement down into three plain parts:
- Trigger: The thing that starts the automation. For example, a new lead being created, or a deal moving into a particular stage.
- Action: What should actually happen as a result. For example, sending an email, updating a field, or creating a task.
- Outcome: The end result you actually want to achieve. For example, faster follow-up on new leads, or fewer manual data entry errors.
If you can't describe your automation idea in these three parts, that's usually a sign it needs more thought before building it, not a reason to build it anyway and hope it works out.
Two broad types
Fully automatic (workflow)
This runs entirely on its own once set up: if this happens, then that happens, with no human involved. It's consistent and fast, but it also runs exactly as configured every time, mistakes and all, so it needs to be well thought through before it's switched on.
Semi-automatic (macros)
This still requires a person to trigger it, but then handles a series of steps automatically once started. It's a useful middle ground when you want to save time on repetitive tasks without removing human judgement from the process entirely.
Pros and cons worth weighing up
- Automation saves time on repetitive work, but building and maintaining it well takes time and budget too, it's not simply a switch that gets turned on for free.
- Just because something can be automated doesn't mean it should be. It's worth asking whether the benefit genuinely outweighs the cost and complexity of building and maintaining it.
- The more automations you build, the more moving parts there are to keep track of, and to fix, if something changes elsewhere in your setup.
Note: A good rule of thumb: if you can't clearly state the trigger, the action, and the outcome you're expecting, it's worth pausing to define the requirement properly before building anything.
Need help? If you're thinking about automating a process in Zoho and want help defining or building it, our team can talk it through with you.
Book a discovery call with 1 Cloud Consultants.