Automation
A rule that performs a task without a person doing it each time.
The computer does the repetitive step.
What It Is
You will find Automation in the Technology layer, alongside the rest of Integration. What it actually refers to is a rule that performs a task without a person doing it each time.
It is an idea you reason with rather than a deliverable you hand over, so two teams can both hold it correctly and still apply it differently. Once it is defined that clearly, arguments about it usually stop.
How It's Used
Most of the time Automation is used in build decisions, tooling and the plumbing behind a working system. It is usually discussed together with Integration, Email Automation and Workflow. The practical test is whether a decision changes because of it.
Why It Matters
Ignoring Automation rarely fails loudly — it fails slowly. When it is unclear, small technical debts compound into a rebuild. It is worth pinning down before anyone builds on top of it.
It is a way of thinking, not a thing you can hold. The computer does the repetitive step.
Termshift™
How the meaning shifts depending on who is using it, and where.
Practitioners use Automation as shorthand and expect no explanation — a rule that performs a task without a person doing it each time.
Outside the industry, most people would just say: the computer does the repetitive step.
The Bottom Line
If you only keep one thing about Automation: the computer does the repetitive step. Everything after that is detail.