Automation concepts
Workflow automation is software that moves information between systems and carries out steps according to rules you define. Every automation has the same skeleton: a trigger (the event that starts it) followed by one or more actions (what happens next). “When a new row is added to the new-hires spreadsheet, send a welcome email” is a trigger and an action.
No-code tools let you assemble these from menus instead of writing software. Zapier is one; Microsoft Power Automate, Make and n8n are others. The concepts in this module apply to all of them.
Three levels of automation
| Level | How it behaves | Strength | Weakness |
|---|---|---|---|
| Rule-based automation | Follows fixed rules: if this, then that. | Predictable; does the same thing every time. | Cannot handle unstructured input or situations nobody anticipated. |
| Automation with an AI step | A fixed workflow in which one step uses a language model to read, classify, extract or draft. | Handles free text, such as an email to the HR inbox. | The AI step can be wrong, so its output needs a check before anything important happens. |
| AI agent | Given a goal and tools, the AI decides which steps to take. | Flexible. | Least predictable. Needs the tightest limits and oversight. |
Begin with rule-based automation. Add an AI step only where the input is unstructured, and put a human checkpoint after it.
What makes a good automation candidate
| Criterion | Question |
|---|---|
| Frequent | Does it happen at least weekly? |
| Rule-based | Can you write the rules down without “it depends”? |
| Digital | Do the inputs already exist in a system, form or spreadsheet? |
| Stable | Has the process stopped changing? |
| Low exception rate | Do most cases follow the standard path? |
| Low harm if wrong | Would an error be noticed and fixed easily? |
| Owned | Is there a named person who will maintain it? |
Common HR candidates
| Good candidates | Keep a person in control |
|---|---|
| Kicking off onboarding tasks when an offer is accepted Reminders for incomplete forms, training or reviews Interview scheduling confirmations Routing leave or expense requests to the right approver Filing documents and updating trackers Sending survey invitations and reminders Sorting the HR inbox into categories for a person to act on Distributing regular reports | Any message that communicates a decision about a person (offer, rejection, discipline, termination) Anything based on an AI score or prediction about an individual Changes to pay or employment status Responses to complaints or sensitive disclosures Anything that cannot be undone |
Map the current steps first. You will usually find steps nobody needs, handoffs that cause delay, and rules that exist only in someone’s head. Remove and clarify those, then automate what remains. Automating a confusing process produces confusion more quickly.
Estimate the time you will save Minutes per occurrence × occurrences per month × 12, less the time to build and maintain. Example: the new-hire kickoff takes HR 25 minutes of copying and emailing per hire; Brightwater hires about 120 people a year. That is 50 hours a year. If the automation reduces HR’s part to a 3-minute review, the saving is about 44 hours a year, against perhaps 6 hours to build and test and an hour a month to maintain.
Jot down key ideas in your own words. Saves automatically.