Article silo
Automation
Automation is the work of separating repeatable handling from decisions that still need judgement.
Primary question
What can the system do reliably before a human needs to decide?
Focus
Follow-up, reminders, status visibility, context assembly, and exception routing.
Best for
Teams where small repeated tasks quietly consume capacity every week.
Guide count
16 published pieces in this silo
Topic cluster
Supporting articles
Essential
Reference / 4 min
What Is Workflow Automation in Practice?
Workflow automation removes repeated human handling from rule-based work. Not robots. Not AI. Removing the person from steps that always happen the same way.
Article / 5 min
What Manual Follow-Up Costs Each Week
Manual follow-up feels small because each message is small. Across a team, it becomes lost capacity, slower service, and work that should have been a system.
Article / 6 min
Why Follow-Up Automation Fails Before It Goes Live
Most follow-up automation is turned off within three months. The failure rarely starts with the workflow tool. It starts upstream, before the first message.
Article / 6 min
When Not to Automate a Workflow Yet
The instinct to automate everything is understandable. It is also frequently wrong. The situations where automation makes operations worse, not better.
Reference / 4 min
What Is an Automation Trigger in Practice?
An automation trigger is the defined condition that fires a workflow. Not a feeling about when something should happen, a rule you can write down and test.
Reference / 5 min
What Is Human-in-the-Loop Automation?
Human-in-the-loop automation keeps a person at the decision points a rule cannot cover: the machine handles, the human makes the judgement calls.
Article / 7 min
The Human/System Boundary in Operational Design
The useful boundary is not human versus automation. It is repeated handling versus the judgement, context, and accountability that still need a person.
In Practice
Article / 6 min
Building Follow-Up That Survives a Handoff
Follow-up that works for one person usually breaks the moment a second person joins. The reason is structural, not personal. How to fix it at the system level.
Article / 5 min
Automation or Custom System for the Workflow?
Not every workflow needs automation, and not every automation needs a custom build. Use the problem shape to choose.
Article / 6 min
How to Calculate Your Automation ROI
Before building, calculate whether it is worth it. A simple model for the return on an automation investment, without spreadsheet theatre or invented numbers.
Case study / 8 min
Inside Inbox Intelligence
How a shared inbox diagnostic turns follow-up activity into operational signal, and what a production version would need before a team could run it daily.
Article / 7 min
Debounce vs throttle
A living-example teardown of debounce vs throttle: when to wait for a burst to settle, when to cap the rate, and how it rate-limits an automation trigger.
Article / 7 min
A scheduled inbox triage automaton
A living-example teardown of a scheduled automaton that files your unread mail each morning by plain-language rules, only labelling and leaving a digest.
Field notes
Reference / 5 min
Automate or Hire for Repeated Work?
Usually framed as a cost comparison. That is the wrong frame. The real question is what kind of work this is, and whether it belongs in a system or a person.
Reference / 4 min
What Is a Follow-Up Sequence in Sales?
A follow-up sequence is a structured series of timed actions triggered by a single event. The difference between follow-up in a system and in someone's head.
Other silos