Simple by Design

What if the most sophisticated thing you could do for your business was to make it simpler?

Not smaller. Not less capable. Not stripped of what makes it work. Just clearer. Easier to navigate for the person who has to run it every day. Built for the business you actually have, not the one you are dreaming or manifesting.

That is what simplicity means as a design principle. And it is harder to choose than it sounds, because we are surrounded by a completely different operating system.

The default assumption in most business advice is that more is better. More automation, more tools, more systems, more capacity. All built for growth. Complexity gets dressed up as sophistication. A sprawling tech stack becomes evidence of a serious business. The question is almost never: Does this actually make things clearer? It is almost always: how do we do more?

Simplicity asks a different question entirely. Not: what else could we add? But: what is the clearest path from here to there, for the person who actually has to walk it?

Sometimes the answer involves automation. Sometimes it deliberately does not. Simplicity is not a bias toward technology or away from it. It is a commitment to not making things more complex than the work requires.

The ritual that didn't need automating

A client came to me wanting to automate a specific step in their process. After their events, they collected the names of attendees who had consented to join their newsletter and manually imported them into their email platform from a spreadsheet. It worked. But it felt like a task, and she wanted it off her plate.

We looked at what automation would actually require. To remove that one manual step, they would have had to move away from the software they loved, the one that made the rest of their process feel easy, and add two or three additional tools to essentially replicate what they were already doing. The automation would have been real. But so would the cost: more tools to maintain, more connections to troubleshoot, a base platform replaced by something less suited to how they worked.

And their attendance volume wasn't there yet to justify any of it.

So I asked them: what if this step wasn't a problem to be solved?

The volume was small enough that the time it actually took was minimal. A few minutes, a handful of names. The friction they were feeling wasn't really about the time at all. It was about the story that manual work tells us: if it isn't automated, it isn't professional, it isn't scalable, it isn't serious.

My suggestion was a reframe. What if, instead of automating it away, you turned it into a small ritual? A few minutes after each event, you open the spreadsheet, you move the names across, and you let yourself feel a moment of gratitude for the people who showed up and wanted to stay in touch.

The manual step stayed. Not as a compromise, but as a choice. A small, intentional rhythm that kept their process simple and kept them connected to the people at the center of it. When events grow beyond what they can handle alone, it will be time to reevaluate. Maybe automation, or maybe it will be time to delegate.

The system built for a business that didn't exist yet

The second story moves in the opposite direction, but arrives at the same place.

I worked with a business that had been designed at scale before it had the volume to need it. The owner had a big vision, which is not a problem in itself. But they had hired someone to build out a fully operational system early on, with layers of automation, multiple tools deeply integrated with each other, and a level of complexity that made sense for a business managing hundreds of students across multiple courses at a time.

They were not managing hundreds of students. They were managing a handful at a time.

By the time I came in, neither they nor their assistant fully understood how the system worked or how the pieces were connected. Every time they ran a course, everything had to be replicated for the new course. Things broke in ways nobody could trace. And they were paying for tools they didn't need and with duplicate capabilities, at a scale they hadn't reached, for a version of their business that existed only in the original vision.

The sophistication of the system had become its own kind of burden.

We simplified. Not because growth wasn't the goal, but because the system needed to serve the business they were running now, with room to grow into something more, only when the volume actually called for it. Complexity introduced before it is needed doesn't prepare you for growth. It just makes the present harder and more expensive.

What simplicity is actually asking

Both of these stories are about the same thing: the pull to build for a future self rather than design for a present one.

It is an understandable pull. We want to be ready. We want to look serious. We want to stop doing things manually because manual feels unscalable and unscalable feels like a problem.

But a system that is too complex for the person managing it is not a sophisticated system. It is an extractive one. It takes time, attention, and energy that could be going toward the actual work.

Simple by design means asking: Does this process suit the business I have right now? Does it work with how my brain actually operates? Can I understand it, sustain it, and feel at home inside it?

And sometimes it means recognizing that a manual step is not a gap in your operations. It is a feature of them.

In the next post, I'll close the series with the third principle: what sustainability actually requires when we take seriously the idea that the person running the business is also a resource worth protecting.

But for now, where in your business are you carrying complexity that was built for a version of yourself that doesn't exist yet? What would it take to put it down?

Here's to imagining what's possible...

Have a thought, a question, or a moment of recognition while reading this? I'd love to hear from you. Connect with me here.

Want to stay in the conversation? Sign up for Regeneration in Practice, Slow, honest notes on building a business that sustains you.