What's the difference between a complicated business and a complex one?

A complicated business has lots of moving parts, but they're designed: steps are clear and people know what happens next. A 25-step onboarding process with defined stages and owners can still feel calm. Complexity is different. It's the unnecessary variation and friction that crept in without anyone designing it: extra decisions, rework, and handoffs that lose context.

How do I know if my business is undesigned or just going through a rough patch?

A rough patch is temporary and tied to a specific event like a key hire leaving or a seasonal spike. Undesigned complexity is persistent. If the same friction keeps showing up regardless of what's happening externally, repeated questions, approval pile-ups, handoffs that lose context, that's a design problem, not a timing problem.

Should I automate first to save time?

No. Automation on top of confusion just makes the mess move faster and locks the complexity in place. Standardise first, then automate stable processes. If the workflow isn't clear to a human, it's not ready for a machine.

Where should I start if everything feels interconnected?

Pick the one journey that carries the most load or causes the most friction right now, lead to invoice, sales to delivery, onboarding, whatever stalls most. Map that single journey, find the stall point, define the handoffs and decision rights, and fix the inputs. That one improvement often loosens pressure across other areas too.

Won't standardising my delivery make it less bespoke for clients?

The opposite, actually. A clear base delivery architecture means you spend less time reinventing the basics and more time on the genuinely bespoke parts that clients actually value. Most service businesses reinvent from scratch not because their work is truly unique every time, but because they have no defined modules to build from. Create a standard structure with optional add-ons and clear criteria for genuine exceptions. You're not making it less personal. You're giving the bespoke parts a backbone so they can shine.

How long does this kind of business redesign take?

You can make a meaningful dent in one focused journey within a few weeks. You're not building a 40-page operations manual. You're defining a small set of agreements: decision rights, handoff criteria, tool roles, artefact standards. That's what lets work move without constant translation or you holding everything in your head. The first improvement usually creates enough relief to build momentum for the next one.

What if my team resists the changes?

Most resistance comes from uncertainty, not unwillingness. When people don't know what's expected or where to find things, they default to what's familiar, even if it's inefficient. Clear agreements, visible decision rights, and simple shared documents reduce that uncertainty. Expect a few small mistakes while the team learns. That's normal and healthy, not a sign the system is failing.

Your Business Isn’t Broken. It’s Underdesigned.

Your business works. Clients are paying. The team is trying. Revenue is coming in.

And yet. Everything feels harder than it should.

You answer the same questions. Projects stall for no obvious reason. Your calendar fills with “quick check-ins” that eat hours. Growth hasn’t created breathing room. It’s created drag.

If that sounds familiar, I want you to hear something clearly: your business is not broken.

It’s undesigned.

Not design as in fonts and logos.

Design as in how work flows through your business.

You don’t need to work harder, hire faster, or bolt on another tool. You need to step back and design the parts that grew by accident.

Let’s help you spot where undesigned complexity is hiding, and give you practical moves to start simplifying. No overhaul required.

Complicated is fine. Complexity is the problem.

People use “complicated” and “complex” like they mean the same thing. In operations, they’re not.

A complicated business has lots of moving parts, but they’re designed.

Steps are clear. People know what happens next.

A 25-step client onboarding process with defined stages, clear owners, and a standard toolkit?

That’s complicated.

It can still feel calm, if everyone knows their part.

Complexity is different.

Complexity is unnecessary variation and friction in how work flows through your business.

Extra decisions nobody needed to make. Rework that didn’t need to happen. Handoffs that lose context. “Work about work” that doesn’t improve a single outcome.

The goal isn’t to make your business simple.

Some businesses are genuinely complicated, and that’s fine. The goal is to remove the complexity that crept in without anyone designing the processes.

What an “undesigned business” actually looks like

Diagram showing where to find operational improvement opportunities in your business

An undesigned business isn’t sloppy. It’s a business that grew through accumulation.

Exceptions got added. Tools got added. Delivery got more bespoke. People built workarounds to cope.

Over time, “how we work here” became real, but implicit. Nobody wrote it down because it kept working.

Until it didn’t.

Here’s what undesigned areas usually have in common: Roles, decisions, and handoffs depend on specific people rather than clear, shared agreements Processes live in chat threads, email chains, and people’s heads instead of simple shared documents Tools were added to solve a moment, not designed into the end-to-end workflow, so you end up with fragmented data and duplicated sources of truth

This is why a business can look “fine” from the outside while feeling exhausting on the inside.

And it’s why the fix isn’t “try harder.”

The fix is to design processes to systemise what grew by accident.

The slow drain you can’t quite name

Quiet complexity rarely shows up as a single failure. It shows up as a pattern. → More messages. → More clarification threads. → More micro-decisions. → More context switching. → More rework. → More latent stress. → More of that background hum that makes you feel busy without feeling productive.

Research consistently shows that knowledge workers can spend a huge chunk of their time on coordination and “work about work” rather than skilled delivery.

If that sounds familiar, it’s not a people problem. It’s a design problem.

And the hardest part? When you’re in it, you normalise it. You start believing that’s just what running a business feels like.

Spoiler: It’s not.

Seven signs your business is undesigned

These are the patterns I see most often. For each one, I’ve included the likely cause and a practical first move.

Your team keeps asking the same questions Cause: Decision rights and information locations are implicit. People ask because they genuinely don’t know where to look or who decides.

First move: Create a simple “source of truth”, then make it searchable. Start by defining where each key item lives (client details, briefs, assets, decisions). Then put those documents into one searchable knowledge hub your team can query instead of asking you. If you are in Google Workspace, NotebookLM can work well for this. If you are not, a lightweight knowledge base in Notion or Obsidian can do the same job. The goal is not the tool. The goal is one place to look, and a fast way to find answers.
Work only moves when you touch it Cause: No clear handoff criteria or next-step triggers. Dependencies are invisible, so everything waits for you.

First move: Define “definition of done” for each stage of your core workflow. Make entry and exit rules visible on a simple board. When people can see what “ready for the next step” looks like, they stop waiting for permission.
Too many tools, not enough clarity Cause: Tools were adopted without redesigning the workflow they sit inside. They became personal coping mechanisms instead of shared systems.

First move: Map the core workflow first. Then assign clear tool roles: system of record, task management, communication, assets. Remove the duplicates. If you can’t answer “where is the latest truth about this client?” without checking three tools, that’s your starting point.
Every client engagement feels “unique” Cause: No default delivery architecture. Standardisation feels like it would reduce value, so every engagement gets reinvented from scratch. First move: Define a base delivery structure with standard modules, optional add-ons, and clear criteria for genuine exceptions. You’re not making it less bespoke. You’re giving bespoke a backbone.
Sales-to-delivery handoffs keep breaking Cause: Undefined intake standards. What sales captures doesn’t match what delivery needs.

First move: Create one intake artefact (a brief) with mandatory fields. Add a handover checklist. Only add a handover meeting when complexity actually warrants it. Most of the time, a solid brief is enough.
You’re the approval bottleneck Cause: Unclear delegated authority and no escalation rules. The team defaults to checking with you because nobody’s defined what’s safe for them to decide alone.

First move: List your recurring decisions. Set “safe to decide” ranges. Define when escalation is required and what happens if a decision isn’t made within a set time. Expect a few small mistakes while the team learns. That’s normal. The point of safe ranges is to keep those mistakes low risk, so learning happens without expensive consequences. You’re not giving up control. You’re designing it.
Rework loops and repeat defects Cause: Unclear standards, vague requirements, and missing checklists. Work starts before the brief is actually ready.

First move: Define acceptance criteria for the work that matters most. Standardise your templates. Track your top five repeat defects for a few weeks so you can fix root causes instead of symptoms.

Quick diagnostic: where’s your biggest opportunity for improvement?

If a key person was away for three weeks, do you know exactly what would break first, or is it still undocumented?
Are a large share of your daily messages status requests rather than value-creating decisions?
Can you answer “what’s the latest truth?” about a client or project without checking multiple tools?
Do projects get sent back because the brief or intake was missing key information?
Do team members ask for your approval on small decisions, mostly out of habit?
Are proposals built from scratch instead of assembled from defined modules?
Do status meetings exist mainly to reconstruct reality that should already be visible in the system?
Did you adopt your last few tools before mapping the workflow they were meant to improve?

If you relate to 3 or more, you’ve got undesigned areas creating quiet drag on your business.

The good news is you don’t have to fix everything at once.

Start where work stalls most often, and improve that process.

Where to start (without a full overhaul)

Here’s the thing about operational redesign. It’s not about adding more process. It’s about removing friction.

Fewer decisions, fewer pathways, clearer defaults, simpler handoffs. If you’re feeling the drag, here’s a calm order of operations.

Step 1: Pick one process journey that really matters Not everything. One journey. Lead to invoice. Sales to delivery. Client request intake. Onboarding. Content production. Pick the one that’s causing the most friction right now.

Step 2: Find the stall point Ask yourself: “Where does work most often stall, and what decision or approval is it waiting on?” That’s your entry point.

Step 3: Define the minimum agreements Operational clarity isn’t a 40-page manual. It’s a small set of agreements that let work move cleanly. Decision rights. Role boundaries. Workflow steps. Artefact standards. Handoff criteria. Tool ownership. Write them down. Make them findable. That’s it.

Step 4: Fix the inputs and handoffs This is where complexity hides. Use “definition of ready” (what must be true before work enters a stage) and “definition of done” (what must be true before it leaves). When work doesn’t enter stages half-formed, rework drops dramatically.

Step 5: Then, and only then, decide what to automate Automation on top of confusion locks complexity in place. It just makes the mess move faster.

Standardise first, then automate stable processes. Not the other way around.

Final tip before you go

When your business is undesigned, capable people compensate with effort. They use DMs to bridge gaps. They build private spreadsheets. They ask “quick questions” to avoid mistakes.

It works.

Until it doesn’t.

Designing your business gives you something different. It gives you a business that can be complicated and still calm, because work can move without constant translation, heroics, or you holding everything in your head.

You don’t need a transformation. You need a few well-placed design decisions.

Pick the symptom you feel most often. Map one journey. Define the interfaces. Standardise the inputs. Make the handoffs explicit.

That’s smart business design.

Calm systems are the foundation under everything new visibility brings. Related reading: