Automation & operations · 2026-09-24

The Difference Between a Process and a Habit

If the work would change shape without one specific person doing it, that's a habit, not a process. Here's why the difference matters more than it sounds.

Most businesses believe they have processes. What they usually have is habits: things that get done the same way most of the time, by the people who happen to remember how, until one of them doesn’t.

A habit lives in a person. A process lives on paper

The test is simple. If the person who usually handles a task went on leave tomorrow, would the work still get done the same way? If the honest answer is “probably not exactly,” that task is a habit, not a process, regardless of how reliably it happens when that person is around.

A real process survives the absence of any one person. It doesn’t rely on memory, and it doesn’t quietly change shape depending on who’s doing it that week.

Why the distinction actually matters

Habits can’t be improved on purpose, because there’s no fixed version of them to compare against. They can’t be delegated cleanly, because handing one off means describing something that was never actually written down. And they can’t be priced accurately, because nobody really knows how long the task takes when it includes all the small variations that happen depending on who’s doing it.

None of that is a character flaw. It’s just what happens by default when a business grows past the point where one person can hold every task in their head.

Turning a habit into a process

The first step isn’t automation. It’s writing down how the work actually happens today, including the workarounds nobody mentions in a meeting. That single step usually reveals more than expected: two people doing the same task differently, a step that only exists because of a one-time exception that became permanent, or a handoff that depends on someone remembering to mention it.

Once the real sequence is visible, deciding what to automate becomes much easier, because you’re automating a known process instead of guessing at an assumed one.

Three habits worth checking first

  • Quoting or proposals: does the same request produce the same document regardless of who writes it?
  • Onboarding: does a new client get the same start whoever signed them and whatever week it is?
  • Reporting: does it happen on a schedule, or does it happen when someone finds a free afternoon?

These three repeat the most and touch every client the same way, which makes them the fastest place to see the return on turning a habit into something that runs the same way every time.

Keep reading

Tell us which task your team repeats most.

One call, no deck. We’ll tell you what we’d build first and what it would take.

info@minchin.io