DEV Community

Hive80-lab
Hive80-lab

Posted on Originally published at hive80-lab.github.io

What to Automate First: the 4-Question Filter for Small Teams

What to Automate First: the 4-Question Filter for Small Teams

The first automation a small team builds is usually the wrong one — the exciting one, not the valuable one. A chatbot nobody asked for beats an invoice reminder nobody has to send, in excitement. In value, it's not close. This page is the 20-minute filter that decides for you, before you spend a weekend building the wrong thing.

The 4 questions (in order)

  1. Does this happen at least weekly?
    Automation pays back through repetition. A once-a-quarter task that takes 10 minutes isn't worth the build, however fun the build is.

  2. Is the task's rule writable in one sentence?
    "Every completed order gets a confirmation email" — writable. "Review whether this lead looks promising" — not yet. If you can't state the rule in one sentence, you don't understand the task well enough to delegate it to a machine.

  3. Is failure visible within a day?
    Good candidates fail loudly or observably (email didn't send, invoice missing). Bad candidates fail silently for weeks (data enrichment — wrong output looks like right output).

  4. Can a human check the output in under a minute?
    If verification is expensive, you've automated the task and manualized the review — the worst trade in automation.

Scoring

Four yeses = automate next sprint. Two or fewer = leave it alone for now. Three = fix the weak answer first — usually #2: write the rule sentence until it's actually true.

The 3 red flags (any one means don't automate yet)

  • The process changed in the last month.
    You'd be automating a snapshot of a moving process. Stabilize first.

  • Nobody currently does the task end-to-end.
    Automation needs a reference human; without one there's no ground truth to check against.

  • The task exists to catch rare, expensive errors.
    Human review IS the control here. Automate the logging of those errors, never the judgment.

Worked examples

Candidate Weekly? Rule? Fails loudly? <1min check? Verdict
Invoice overdue reminders Y Y Y (email log) Y Automate
Backup verification alert Y Y Y Y Automate
Lead scoring Y N N (silent) N Leave alone
Refund approvals N N N N Leave alone — judgment is the control

What stays human, always

Anything involving judgment about people — hiring, pricing decisions, escalating an angry customer. Automate the paperwork around those, never the decision. And once a winner is picked, the boring part is the part that matters: run it in shadow mode for a week, give it a kill switch, and put a monthly review on the calendar. Automations don't die loudly; they rot quietly until someone notices the wrong invoices went out in March.

Automation starter pack for small teams: HIVE20 | Incident-response kit: HIVE20

Top comments (0)