Automate Less. Design More.

Every firm that buys an automation tool expects the same thing: relief. What most of them get is the same chaos as before, now moving too fast to catch.

Automation is an amplifier. Point it at a clean, designed process and it gives you leverage — the right thing happens, every time, without anyone remembering to do it. Point it at a broken one and it gives you the exact same broken outcome, faster, more often, and with the false confidence that comes from a green checkmark. The tool did its job. The job was wrong.

That’s why our first answer to “what should we automate?” is almost always “less than you think — and not yet.” Design comes first. Automation is the last layer, not the first move.

Automating a broken process just helps you break things at scale.

Law Firm Architects · Operating Philosophy

01Speed is not the same as design

A Zap that fires the wrong intake email at the wrong moment isn’t a small problem — it’s the old problem with a multiplier on it. When the process lived in someone’s head, mistakes were occasional and human. When you automate that same undefined process, the mistakes become systematic and invisible. Nobody is watching, because the machine is “handling it.”

Speed feels like progress. But speed applied to a path nobody designed just gets you to the wrong place sooner. The firms that win with technology aren’t the ones with the most automations. They’re the ones who designed the work so well that the automations have something solid to stand on.

02Design the path, then automate the beats

The order matters more than the tools. Before any tool touches the work, the path has to be explicit: the lanes a matter travels (tracks), the sequence it moves through (stages), and the individual actions inside each phase (beats). Automation lives at the beat level — and only after the layers above it are designed.

• Map the stage: what pulls work in, who owns it, what “done” means, what hands it off.
• Name the beats: the specific actions inside the stage that actually repeat.
• Stabilize it manually: run the designed path by hand until it’s boring and predictable.
• Then automate the boring parts: the triggers, the reminders, the data moves.

03What to automate — and what not to

Once the path is designed, the right targets become obvious. Automate the things that are repetitive, rule-based, and low-judgment: the status update, the calendar entry, the document assembly, the “where is my case” email. Leave the judgment calls to people. The goal isn’t a firm with no humans in the loop — it’s a firm where humans only touch the parts that need a human.

04Where to start this week

Don’t open your automation tool. Open a blank page. Take the process you most want to automate and design it by hand first — the stages, the owners, the beats. Run it manually until it’s predictable and dull. Only then ask which of those dull, repeatable beats a machine should carry.

When you automate a designed path, technology finally does what you hoped it would: it disappears into the background and the firm just runs. That’s the whole point. Automate less. Design more.