Explore Ops

Article

Still doing the same ops by hand every week?

The search is not “how to purge a CDN.” It is the Friday ritual you still click through — leads, reminders, the same eight steps — and how to put that path on rails.

Direct answer. If the same trigger always gets the same eight clicks, that is a candidate for ops automation: name the trigger, name the owner, run the path without a hero — then keep it alive with care, not another spreadsheet.

Desk illustration of a repeating weekly checklist turning into one automated ops path

The useful search is not “how do I purge Cloudflare.” It is why am I still the person who has to remember this. A cache purge after a site deploy is one boring example of a class: a known trigger, the same clicks, and a quiet failure if anyone skips a step. US small businesses run that class all week — inbound leads, reminders, missed calls — and it does not show up as a developer ticket. It shows up as “we’ll get it Monday.”

What is a repeatable ops task?

A repeatable ops task is work that fires from the same trigger and should always produce the same next steps. Form submitted. Appointment booked. Call missed. Site shipped. If a competent person would do the same eight things every time, you do not need a hero. You need a path.

Asana’s Anatomy of Work research (knowledge workers, not a census of US trades) still names the pattern honestly: a large share of the week is work about work — coordinating, re-entering, chasing — rather than the skilled job you hired for. Their 2023 index also reported that people estimated better processes could return on the order of several hours per week. Treat that as a signal, not a promise for your shop. The earlier Anatomy of Work PDF describes the same class of duplicated manual steps.

You do not automate judgment. You automate the stairs to the judgment.

Why do “quick” manual steps keep winning?

Because each one looks cheap. Typical failure modes:

  • The same lead is typed into a form, then a sheet, then a phone
  • Reminders go out only when someone remembers Friday
  • After-hours inquiries sit until the inbox owner is back
  • A website change is live, but a leftover click (purge, republish, “did you hit save?”) is still a person

None of those need a science project. They need an owner and a trigger. If two people might do it — or zero people might — you have a ritual, not operations.

What does the path look like instead of eight clicks?

Name four things. If you cannot, stop buying tools.

01 Trigger Same event 02 One record Pipeline / sheet 03 Notify Named owner 04 Fallback

  1. Trigger — the event (form, booking, missed call, deploy)
  2. Record — one pipeline or sheet of truth
  3. Notify — a human who can act, with context
  4. Fallback — what happens if nobody claims it

On our own site, the “purge after publish” step is that pattern in miniature: the trigger is a real deploy, the action is mechanical, and skipping it leaves visitors on stale pages. Your Friday list is the same shape. The product names change; the gap does not.

For inbound work, that is Lead Intake Ops — capture, route, alert, follow-up — not a bigger ad budget. Reminder and missed-call loops are the same idea on Appointment Ops and Home Service Ops. Tooling can sit on apps you already pay for or a hosted layer — On your tools vs We host it.

What does “good” look like without fake ROI?

You should answer, in one screen:

  • What fired, from where, and when
  • Who was supposed to act
  • Whether the path ran without a hero

If you cannot, automation will copy the mess faster. Clarity first. Then put the boring stairs on rails and keep them with monthly care.

Next step

If the pain is unanswered hand-raises, start with Lead Intake Ops. If the pain is no-shows, use Appointment Ops. Missed calls: Home Service Ops. When the leftover clicks live on the website itself, that is Site Care.

FAQ

Which tasks should a small business automate first?

Start with work that is frequent, the same every time, and painful when it is skipped — inbound leads sitting unanswered, appointment reminders, missed-call follow-up. Skip one-off judgment calls until the boring path is reliable.

Is this the same as buying more software?

No. Extra apps without an owner still leave a manual gap. You need one place of record, a named next step, and an alert if nobody acts. Tools are the plumbing.

We already have Zapier or Make. Are we done?

A connector is not a process. If someone still copy-pastes between tabs after the zap runs, you automated a fragment. Kickoff is for drawing the whole path.

Will automation replace my front desk?

No. It stops the silent gaps — the lead at 9pm, the reminder nobody sent — so humans spend time on conversations, not re-typing.

Sources & citations

External references that support claims in this article. We cite research and primary docs — not invented statistics.

  1. — Asana () Knowledge workers reported most of the day still goes to “work about work,” not skilled work; respondents estimated process improvements could save about 4.9 hours per week.
  2. — Asana Earlier Anatomy of Work findings on time lost to duplicated, low-value manual steps (knowledge-worker survey; not a US-trades census).