**89. Systems Thinking: The Secret to Escaping the Bottleneck — Transcript & Summary | SozAI**
Source: https://sozai.app/transcript/systems-thinking-escaping-bottleneck/

Justin, a techie lawyer, explains systems thinking as the key to escaping the solo-founder bottleneck: documenting repeatable processes so tools, delegation, and automation actually work.

## Key Takeaways

- Systems thinking means seeing work as repeatable processes, which is the foundation that makes tools, hires, and automation effective.
- Most automation fails because the underlying process was never clearly defined.
- Delegation works only when the process is documented; otherwise it becomes abdication.
- Writing down a process once pays back every time it runs without the owner.
- Start by mapping the most time-consuming recurring processes, even roughly, this week.

## What the video covers

- Opens with the solo founder's reality: doing everything, working late, and being the bottleneck of their own business.
- Argues the bottleneck is structural: work processes exist only in the owner's head, creating tribal knowledge that cannot be transferred.
- Defines systems thinking as seeing work as repeating processes with inputs, steps, and outputs, not a specific tool or software.
- Illustrates systems with everyday examples: traffic lights, recipes, and airport boarding processes.
- Explains that a process needs clear triggers, steps, and definitions of done before automation or delegation can succeed.
- Distinguishes true delegation (handing over a documented, runnable process) from abdication (handing off a task without context).
- Introduces the idea of documenting explicit rules so others can handle exceptions without escalating back to the owner.
- Notes that automation is execution, not intelligence, so unclear processes automated will simply fail faster.
- Recommends an audit: list recurring tasks, pick the most time-consuming ones, and map them with triggers, steps, and rules.
- Encourages starting small with rough, imperfect documentation and no budget or technical background required.

## Chapters

1. 00:00 The solo founder's bottleneck problem
2. 02:16 Why the business depends on you: tribal knowledge
3. 06:23 What systems thinking is (and isn't)
4. 08:11 Everyday examples of systems
5. 11:57 Processes, triggers, and why automation fails
6. 19:00 Delegation versus abdication
7. 30:00 Practical steps: auditing and mapping your processes
8. 38:10 Starting small this week

Answers

## Questions about this video

What is the main problem this video addresses?

The video addresses solo founders who have become the bottleneck of their own business because all processes and decisions live only in their heads. This makes growth stall, quality inconsistent, and time off impossible.

Why do automation attempts often fail according to the video?

Automation is execution, not intelligence, so it only does exactly what it is told. If the process has not been clearly defined with triggers, steps, and rules, automating it will simply produce failures faster.

What is the difference between delegation and abdication?

Delegation means handing someone a documented process they can run independently. Abdication means handing off a task without context and hoping it works out.

## Full Transcript — Download SRT & Markdown

00:00

Speaker A

It's 7:00 in the evening. Your colleagues, if you have any, left hours ago. The office is quiet, or maybe you're at your kitchen table, laptop open. The rest of the house carrying on without you. You're answering an email you've

00:14

Speaker A

answered a hundred times before. You're chasing an invoice that should have gone out 3 days ago.

00:19

Speaker A

You're fixing something that someone else started but couldn't finish because they didn't know what finished was supposed to look like. And somewhere in the back of your mind, there are six other things you haven't gotten to yet today, and probably won't. This is the

00:34

Speaker A

life of the solo founder, the single-person operation, the entrepreneur who is, in every sense of the word, doing it all. And here's the question I want you to sit with for just a moment before we get into today's

00:46

Speaker A

episode. If you disappeared for 2 weeks, if you went completely off the grid, no phone, no email, no check-ins, what would happen to your business?

01:01

Speaker A

Would it run fine? Would it slow down but survive? Or would it quietly, or not so quietly, fall apart?

01:09

Speaker A

For most solo operators, the honest answer is the third one. And that's not a personal failure. That's a structural problem, and it's exactly what today's episode is about. Because today, we're not talking about a specific app, we're not talking about a particular tool or

01:24

Speaker A

software or AI assistant. We're going to go one level deeper than that. We're going to talk about thinking that makes every tool, every hire, and every automation actually work. It's called systems thinking, and once you see it, you genuinely cannot unsee it. By the

01:41

Speaker A

end of this episode, you're going to understand why most automation attempts fail, even when people choose the right tool. You're going to understand why delegation so often goes wrong, even when you hire the right person, and you're going to understand the one

01:54

Speaker A

mental shift that sits underneath all of it, and how to start making that shift this week with no software, no budget, and no technical background required.

02:04

Speaker A

Let's get into it. If you're new here, my name is Justin. I am a techie lawyer and I have started this podcast, Automate Office Work, which you can find on all the major major platforms. And it's streamed live

02:20

Speaker A

on LinkedIn most Fridays. Can I ask you to comment, like, subscribe, and share wherever you're getting this content. And if you'd like to find all of today's episodes on all the platforms, you can find us at automateofficework.com/podcast.

02:41

Speaker A

Or wherever you're getting this content now, you can search for automate office work and find the other 80-plus episodes.

02:53

Speaker A

Let's start by describing the situation most of you are actually in. Not to make you feel bad about it, but because naming a problem clearly is the first step to solving it. When you start a business on your own, you do everything.

03:05

Speaker A

Of course you do. There's nobody else. You handle the sales calls and write the proposals and deliver the work and send the invoices and answer the support emails and manage the social media and fix the website when something breaks.

03:18

Speaker A

You are the whole operation. In the beginning, that's not just normal, it's necessary. But here's what happens over time. The business grows, slowly or quickly. More clients, more work, more complexity, more emails, more decisions, and the way you work, the fact that

03:34

Speaker A

everything runs through you, doesn't change. You just get busier. You stay later. You start your day earlier. You answer emails on your phone at dinner.

03:45

Speaker A

And at some point, without realizing it, you have become the bottleneck of your own business. Every decision comes to you. Every exception. Every client question that falls slightly outside the ordinary, every piece of work that needs a final check, every email that requires

04:00

Speaker A

a slightly nuanced response, it all routes through you because you're the only one who knows how things are supposed to work. You're the only one holding the full picture. Now, here's something important I want you to hear.

04:11

Speaker A

This is not a personal failing. This is not because you're bad at delegating or because you're a control freak or because you haven't read enough productivity books. This is a structural problem and the structure is this, the work has never been described.

04:26

Speaker A

Everything your business does, every process, every workflow, every decision rule lives entirely inside your head.

04:34

Speaker A

When a new client inquiry comes in, you know what to do with it but only because it's you.

04:40

Speaker A

When something goes wrong with a project, you know how to handle it but only it's be- because it's you. When an invoice needs to be sent, you do it your way but only because it's always been you.

04:53

Speaker A

You are not running a system. You are the system and that means the system cannot run without you. The cost of this is enormous. Growth stalls because your hours are finite. There are only so many of you to go around. Quality becomes

05:07

Speaker A

inconsistent because everything depends on your mood, your memory, your availability on a given day. You cannot take a proper holiday. You cannot get sick without things piling up. You cannot step back and work on the business rather than in it because the

05:23

Speaker A

business needs you to keep it alive on a daily basis. And perhaps most frustratingly, even if you do decide to bring someone in to help, it often doesn't work because there's nothing written down. There's nothing to hand them. You end up spending more time

05:38

Speaker A

explaining things than the work would have taken and you conclude that it's just faster to do it yourself and so the bottleneck tightens.

05:45

Speaker A

So, what's the fix? It starts with a shift. Not in your calendar, not in your software, in how you see your work.

05:55

Speaker A

Systems thinking. It's one of those phrases that sounds like it belongs in a business school lecture or a management consultancy deck. So, let me immediately strip away any of that weight and give you a version of it that is completely

06:08

Speaker A

practical and immediately useful. First, let me tell you what it is not. It is not software. It is not automation. It is not a productivity method or a scheduling technique or a project management framework. All of these things can be expressions of systems

06:23

Speaker A

thinking, but they are not the thing itself. Systems thinking is a way of seeing.

06:31

Speaker A

Specifically, it means looking at your work not as a collection of individual tasks you have to get through each day, but as a set of repeating processes, each with an input, a series of steps, and an output. And the key word there is

06:47

Speaker A

repeating. A system is something that happens more than once. Something goes in, something happens to it, something comes out.

06:54

Speaker A

Reliably, predictably, every single time. Let me give you some examples that have nothing to do with business first, because I think it makes the concept click faster.

07:06

Speaker A

A traffic light. A traffic light is a system. Something goes in, the passage of time or a sensor detecting a car, something happens, the logic of the light decides it's time to change, something comes out, traffic moves in a new direction.

07:22

Speaker A

Nobody has to stand at the intersection and make a judgment call each time. The logic is baked in. The system runs itself.

07:32

Speaker A

A recipe. A recipe is a system. The input is raw ingredients. The steps are the method.

07:39

Speaker A

The output is a finished dish. And crucially, you don't have to be Gordon Ramsay for the recipe to work. A reasonably competent person who has never made that dish before can follow the recipe and produce a good result

07:52

Speaker A

because the knowledge isn't locked in the chef's head. It's been externalized, written down, made transferable.

08:01

Speaker A

The boarding process at an airport. The boarding process at an airport is a system. Hundreds of people all trying to get onto a plane at the same time.

08:11

Speaker A

Without a system, it would be chaos. With a system, zones, boarding groups, clear signage, staff at specific points, it flows. Not perfectly, but consistently. And the same system works whether it's Tuesday in Amsterdam or Friday in Singapore. Notice something

08:30

Speaker A

about all three of these examples. None of them requires a brilliant person to be present for them to function.

08:36

Speaker A

The traffic light doesn't need a genius traffic engineer standing there every morning. The recipe doesn't need the head chef hovering over your shoulder.

08:45

Speaker A

The boarding process doesn't need the CEO of the airline personally directing passengers. They work because the logic has been built into the system itself.

08:56

Speaker A

Now, let's bring that back to your off to your office work. Think about these three things.

09:02

Speaker A

When a new client inquiry comes in, is there a system? Is there a clear set of steps that always happens in a predictable order regardless of who's available or does it depend entirely on who happens to pick it up and how busy

09:15

Speaker A

they are and whether they know what you'd want them to do? When you send an invoice, is there a process? Does it always go out at the same time in the same format triggered by the same event?

09:26

Speaker A

Or do you do it slightly differently depending on the client and sometimes it slips because you forgot and occasionally you realize a week later it never went out at all.

09:36

Speaker A

When someone asks you a common question, one you've answered 50 times, do you retype it each time? Does each version come out slightly differently? Or is there a system that handles it?

09:47

Speaker A

If your honest answer to most of those is, "It depends." or "I just do it when I remember." or "I handle each one differently." then what you have is not a system.

09:57

Speaker A

What you have is tribal knowledge, knowledge that lives in your head and you carry with you everywhere that cannot function without you and that disappears the moment you step away.

10:10

Speaker A

And here is the single most important reframe I want you to take from this episode.

10:15

Speaker A

Write this down if you can. Stop asking yourself, "How do I get this done?" Start asking yourself, "How should this always get done?" The shift from the immediate to the repeatable, from the personal to the transferable, that is systems thinking

10:32

Speaker A

and everything else we're going to talk about today flows from it. All right, now we're getting into the practical backbone of this episode and I want to spend some real time here because this is the model I want you to

10:46

Speaker A

walk away with. It's simple, three layers and once you see how they fit together, you'll start seeing them everywhere in your work.

10:56

Speaker A

Every business system, whether it's simple or complex, whether it runs on software or on people, has three layers.

11:03

Speaker A

The process, the rules and the trigger. Let's go through each one. Layer one is the process. This is simply what needs to happen step by step from start to finish. Let's take a real example that almost every business has

11:20

Speaker A

in some form, onboarding a new client. What are all the steps? Think about it.

11:25

Speaker A

Maybe it starts with sending a welcome email. Then you create a folder for their files. Then Then send a contract.

11:31

Speaker A

Then you schedule a kickoff call. Then you set up their project in whatever tool you use. Then you introduce them to anyone else on your team who'll be involved.

11:40

Speaker A

That's six steps right there. And here's my question. Are all six of those written down somewhere? Or do they exist only in your head? Meaning you remember them when you do it yourself. But if you handed the task to someone else,

11:52

Speaker A

they'd guess at what needed to happen and almost certainly miss something. The first act of systems thinking is to make the invisible visible.

12:03

Speaker A

To take what is currently trapped in your head and put it somewhere that exists independently of you.

12:09

Speaker A

Even a basic numbered list in a Google Doc is a thousand times better than nothing. You are externalizing knowledge. You are building something that can run without you. Most founders have never done this. Not because they're lazy or disorganized, but

12:22

Speaker A

because when you're the one doing everything, you never have a reason to write it down. You just do it. But that means you are perpetually building on a foundation that only you can see.

12:34

Speaker A

Layer two is the rules. Now, steps alone are often not enough. Because inside most processes, decisions get made. And when those decisions aren't written down, every exception escalates to you.

12:48

Speaker A

Let me show you what I mean. Inside that client onboarding process, there might be a moment where you think, "If the client is on the premium package, I send them a different welcome email." A more personalized one with a direct

13:00

Speaker A

phone number. "If they're on the standard package, they get the regular email. Or if the contract hasn't been signed within 3 days, I send a follow-up.

13:11

Speaker A

If I If it still hasn't been signed by day seven, I call them." Those are rules.

13:17

Speaker A

They are the decision logic that lives inside the process. And right now, for most solo founders, those rules exist only in your head. You apply them automatically without thinking because you've done it so many times, but nobody else can apply them because nobody else

13:32

Speaker A

knows they exist. Rules are what allows someone other than you or something other than you to handle exceptions correctly. Without rules, every edge case, every slightly unusual situation, every decision that isn't routine gets escalated back to you, and you become the bottleneck

13:51

Speaker A

again. When you sit down to document a process, go through each step and ask at this point would different circumstances lead to different actions? If yes, write the rule. If X, do this. If Y, do that.

14:07

Speaker A

Those rules are gold. They are the difference between a process that needs you and a process that doesn't.

14:16

Speaker A

Layer three is the trigger. This is the one most people often forget. And it's arguably the most important, especially when it comes to automation.

14:25

Speaker A

A trigger is simply what causes this process to begin. Is it a date? Is it a specific event? Is it an incoming email with a particular subject line? Is it a form being submitted on your website? Is it a payment being received? Think about

14:40

Speaker A

it in the context of your onboarding example. What triggers the onboarding process? Is it when you receive a signed contract? When a payment clears? When you manually decide someone is ready?

14:52

Speaker A

If the trigger isn't clear and consistent, the process gets started at different moments by different people.

14:57

Speaker A

Or worse, it gets started late or not at all, because nobody was sure it was their job to begin it.

15:07

Speaker A

Triggers are also the key to automation. A computer is extraordinarily good at watching for something to happen, a form submission, an incoming email, a new entry in a spreadsheet, and then immediately firing off a sequence of steps. But it can only do that if the

15:22

Speaker A

trigger is clearly defined. If your process starts with whenever I feel like it's time, a computer cannot help you.

15:29

Speaker A

But if your process starts with when a payment is marked as received in the system, a computer can watch for that and begin the whole sequence automatically without you touching it.

15:39

Speaker A

So, trigger, process, rules. Three layers. And here's the payoff. When you have all three, a clear trigger, documented steps, and written decision rules, you have something genuinely powerful. You have a process that you can hand to a person or hand to a computer or split

15:58

Speaker A

between the two. The trigger might be detected by software. The standard steps might be carried out by an assistant.

16:04

Speaker A

The complex exceptions might still come back to you. But the system is running and large portions of it are running without you.

16:14

Speaker A

If you'd like to go deeper into this subject, I recommend the book Systemology by David Jenyns, j e n y n s.

16:23

Speaker A

This is a book to create time, reduce errors, and scale your profits with proven business systems. It's available on Amazon and if you use my link, I will get a small commission. The link is amzn.to/4f2w Thank you for supporting my work and

16:48

Speaker A

let's get back to the show. Let's talk about automation specifically for a moment because I know that's something a lot of you are either actively trying to do or thinking about.

16:59

Speaker A

And I want to explain something that will save you a lot of frustration. Most automation attempts fail or they work for a little while and then break or they work in the simple cases but fall apart the moment anything slightly

17:13

Speaker A

unusual happens. And when this occurs, people usually blame the tool. That software is too complicated. Zapier didn't do what I expected. The AI gave me the wrong answer.

17:26

Speaker A

But almost always, the tool isn't the real problem. The most common reason automation fails is that the process wasn't clear to begin with. People jump straight to tools before they've done the thinking.

17:38

Speaker A

And here's why that doesn't work. Automation is not intelligence. Automation is execution. It does exactly what you tell it to do in exactly the conditions you specify. If you haven't thought through the process clearly, if you haven't identified every step and

17:53

Speaker A

every rule and every trigger, the automation will faithfully execute an incomplete or broken process at high speed.

18:02

Speaker A

Garbage in, garbage out. Automation just makes a broken process run faster and more consistently wrong.

18:09

Speaker A

Let me give you a concrete example. Say you decide you want to automate the follow-up email after a sales call.

18:15

Speaker A

Seems simple enough. Someone you spoke to should get a follow-up email within 24 hours. You think that's easy to automate.

18:23

Speaker A

But then the question starts. When exactly does the 24 hours start? From when the call is scheduled? From when it ends? What if the call was rescheduled and hasn't happened yet? Should the follow-up still go out? What if they

18:37

Speaker A

already became a client during the call? Do they still get the let me know if you have any questions email? What if it was a bad call? They weren't the right fit.

18:46

Speaker A

Should the follow-up be different? What if they were referred by a partner and you have a specific agreement with that partner about how leads are handled?

18:57

Speaker A

None of these are rare scenarios. These are normal business situations. And if you haven't thought through the rules for each one, your automation will either do the wrong thing in those situations, which can be embarrassing or damaging, or it will break and stop

19:11

Speaker A

working. And you'll be back to doing it manually. The automation didn't fail because the tool was bad. The automation failed because the blueprint was incomplete.

19:21

Speaker A

Here's the analogy I want you to keep. Think of systems thinking as a as drawing the architectural plans before you build a house.

19:30

Speaker A

No contractor in the world can build you a house from a description like, "I want something nice with a kitchen and a few bedrooms." They need the plans. They need the measurements, the materials, the exact layout, the electrical routing, the

19:46

Speaker A

plumbing, every detail on paper before a single brick is laid. No software can automate a process you haven't clearly defined either. You have to be the architect first. And here's the genuinely good news in all of this. Once

20:01

Speaker A

you have the blueprint, once you've documented the process with its trigger and its rules, actually plugging in the tool is often the easy part. The thinking is the work. The software is just the contractor that builds what you've already designed.

20:19

Speaker A

So far, we've mostly been talking about automation, handling processes to software. But systems thinking applies equally, maybe even more immediately, to delegation, to handing work to other people. And I want you to spend time here because I think this is where a lot

20:35

Speaker A

of solo founders have been burned, and it's worth understanding why. When most people delegate, here's how it goes.

20:44

Speaker A

You're overwhelmed. You finally decide to bring someone in, a part-time assistant, a virtual assistant, a junior employee. And you sit down and you say, "Can you take over the invoicing?" Or, "Can you handle the client communications while I'm busy?"

21:00

Speaker A

And they say yes. And they seem capable. And you feel relieved. And then a week later, you discover the invoices went out in the wrong format, or they went out to the right clients but with the wrong amounts, or they

21:14

Speaker A

didn't go out at all because the assistant wasn't sure it was the right time to send them out. Or they went out, but the follow-up for unpaid invoices didn't happen because nobody told them that was part of the job.

21:26

Speaker A

And you end up spending two hours fixing what went wrong, and you find yourself thinking, "It would have been faster to just do it myself." And you're right, this time.

21:35

Speaker A

But only because you didn't actually delegate, you abdicated. There's a difference. Delegation is handing someone a process they can run independently. Abdication is handing someone a task with no context and hoping for the best.

21:51

Speaker A

Real delegation, the kind that actually frees up your time, requires four things. First, a documented process. The steps, what actually needs to happen in what order. Second, the embedded rules.

22:05

Speaker A

So that when they hit a situation that isn't obvious, they can make the same decision you would make. Not because they read your mind, but because you wrote down the logic.

22:15

Speaker A

Third, a clear trigger. So they know when to start. Not, "Do the invoicing when you get a chance." But, "Send the invoice within 24 hours of the project delivery being confirmed." And fourth, a defined output. What does done look like? What should exist at the

22:32

Speaker A

end of this process that didn't exist before? An invoice marked as sent, a folder created, an email replied to and labeled. Without a definition of done, people work to different standards, and you get results you didn't ask for.

22:52

Speaker A

When you hand someone all four of those things, something remarkable happens. They can work without you. They can handle the routine cases on their own.

23:00

Speaker A

The exceptions they can't handle are genuinely exceptional, not just anything that wasn't explicitly covered because nothing was written down.

23:09

Speaker A

Now, I want to address something before we move on. I can almost hear some of you thinking, "This sounds like a lot of work up front, writing all this documentation. I don't have time for that." And I understand that reaction.

23:21

Speaker A

But, let me ask you a question. How many times have you done the invoicing this year? If it's twice a month, that's 24 times. How much time does it take each time? If it's an hour, that's 24 hours a

23:34

Speaker A

year spent on invoicing alone. Now, how long would it take you to document the invoicing process once, clearly enough that someone else could do it? Maybe 2 hours, maybe 3.

23:46

Speaker A

You write it down once. It pays back every single time that process runs without you, for as long as your business exists. And one more thing, you don't need to write a 40-page manual.

23:58

Speaker A

Even a short Loom video, where you record your screen and talk through what you're doing while you do it, is a system. A simple numbered checklist in a Google Doc is a system. A short voice note transcribed into bullet points is a

24:13

Speaker A

system. The format doesn't matter. The point is that the knowledge gets out of your head and into something that exists independently of you.

24:25

Speaker A

I want to make this concrete now. I want to walk you through what it actually looks like when a solo founder applies systems thinking, not in theory, but in practice. This is a composite picture based on the kind of transformation I've

24:37

Speaker A

seen play out for individual operators who make the shift. Meet Alex. Alex runs a solo consulting business, specializes in helping small businesses with their marketing strategy. For the first 2 years, Alex does everything.

24:51

Speaker A

Every lead that comes in, Alex handles personally. Every proposal is written from scratch. Every piece of work is delivered directly. Every invoice is sent manually. Every follow-up email is typed by hand. Every new client gets on-boarded through a series of emails

25:08

Speaker A

and phone calls that Alex figures out in the moment, each time differently. [gasps] Alex is good at the work. Clients are happy. But Alex is exhausted. There's no room to take on more clients because there's no room in the day. The business

25:24

Speaker A

has effectively hit a ceiling. Not because the market isn't there, but because Alex is the ceiling. Then Alex applies systems thinking. Not all at once, slowly, methodically. Starting with the highest frequency pain points.

25:38

Speaker A

The first thing Alex does is sit down and list every recurring task in the business. Not the big strategic stuff, the recurring operational stuff. Each type of email that gets sent more than once. Every step in every client

25:51

Speaker A

interaction. Every admin task that happens regularly. Alex fills up two pages of a notepad.

26:00

Speaker A

Then Alex picks the top three most time-consuming and maps them out fully. Triggers steps rules.

26:08

Speaker A

All written down in plain language in a shared document. The client inquiry response. Alex realizes that 80% of initial inquiries ask the same five questions.

26:20

Speaker A

Alex writes a detailed template response that answers all five, personalizes two lines, and sends it within the hour.

26:27

Speaker A

What used to take 20 minutes of thinking now takes 3 minutes of personalization. Then Alex sets up a simple email filter that flags new inquiries and auto-populates the template. Now it's one click.

26:41

Speaker A

The invoice process. Alex documents every step. When to send, in what format, to whom, what the payment terms are, and what happens if payment doesn't arrive within 7 days. Alex then hands this document to a part-time virtual assistant along with access to the

26:56

Speaker A

invoicing software. From that week forward, Alex never touches an invoice again. The virtual assistant runs the process. Exceptions, a client disputing a charge, a payment going to the wrong account, comes back to Alex. But, the routine runs without Alex.

27:18

Speaker A

Client onboarding. Alex builds a sequence. New client signs the contract. Then, contract software automatically notifies both parties. Then, an automated email goes out with the welcome information and a link to book the kickoff call. Then, a folder is

27:35

Speaker A

automatically created in Google Drive. Then, the virtual assistant sets up the project in the project management tool.

27:41

Speaker A

Alex's only involvement, the kickoff call itself. Within 90 days, Alex has freed up roughly 12 hours per week. Not by working harder, not by hiring a big team.

27:56

Speaker A

By designing systems that run predictably without constant input. That 12 hours goes back into the work only Alex can do.

28:05

Speaker A

Strategy deepening. Key client relationships. Developing a new service. Writing content that brings in leads while Alex sleeps.

28:18

Speaker A

And here's the principle that underpins all of this. The thing that I want you to really absorb, a system you build once keeps running. Every hour you invest in designing and documenting a process is paid back every single time that

28:32

Speaker A

process runs without you. Not once, not twice, every single time. For as long as your business exists.

28:40

Speaker A

That is leverage. That is what it means to scale. Not to work more hours, not to hire a large team, but to have more systems running in parallel, each reliably producing outputs without requiring your presence for each one.

28:54

Speaker A

Alex's business didn't scale because Alex hired 10 people. Alex's business scaled because Alex stopped being the business and started running the business. Those are two very different things.

29:10

Speaker A

All right, let's get practical. Everything we've talked about today is conceptual and I hope it's been useful, but I want to make sure you leave this episode with something you can actually do. So, let me give you five steps.

29:22

Speaker A

These are not complicated. They require no software. They require no technical knowledge. They require nothing more than a piece of paper or a document on your computer and about an hour of your honest attention.

29:34

Speaker A

Step one, take inventory. Set a timer for 20 minutes. In that time, write down every task you do more than once. Do not filter. Do not edit.

29:45

Speaker A

Do not worry about whether something is important enough to include. Write everything. Think about your email. How many different types of emails do you send regularly? Think about your client interactions. Think about your financial admin. Think about your scheduling.

29:59

Speaker A

Think about anything that happens on a recurring basis, weekly, monthly, or every time a particular type of client or situation comes along.

30:07

Speaker A

You are probably going to end up with a list of 15 to 30 items, maybe more.

30:13

Speaker A

That's good. That means there's a lot of leverage available. Step two, pick one process and map it.

30:21

Speaker A

Do not try to systematize everything at once. That is the path to overwhelm and inaction. Pick the single process on your list that either takes the most time when you do it or happens most frequently. Frequency matters because

30:34

Speaker A

even a small time saving multiplies. Now, write out every single step of that process, every step, as if you were explaining it to a smart, capable person who has never done this before and has no context about your business. Be

30:49

Speaker A

specific. Not send the email, but send the onboarding email using the template in the drafts folder, personalizing the first paragraph with the client's name and the service they've purchased. The more specific you are, the more transferable the process becomes.

31:06

Speaker A

Step three, identify the trigger and the output. Go to the top of your list. What event, action, or moment starts this process that didn't exist before? What is the concrete output?

31:20

Speaker A

An email sent, a document filled, an invoice marked as paid, a client record updated. Write that down, too.

31:29

Speaker A

Those two anchors, the trigger and the output, transform a vague, informal, recurring task into something with a defined beginning and end, something that can be handed off, something that can be measured, something that can be automated.

31:44

Speaker A

Step four, extract the rules. Go through the steps you've documented and ask yourself at each one, could this step turn out differently depending on the situation? Is there a moment here where I make a judgment call?

31:57

Speaker A

Every time the answer is yes, write the rule. If the client is on the premium package, do this. If the payment is more than 7 days late, do that. If the inquiry comes in after 5:00 p.m. on a

32:09

Speaker A

Friday, do this other thing. These rules are the decision logic that currently lives only in your head. Getting them out, even imperfectly, even as a rough first draft, means someone or something else can apply them. And that means this

32:24

Speaker A

process can run without you, even in the non-standard cases. Step five, decide what to do with the process. Now that it's documented, you have three options. The first option, automate it. If the process is largely rule-based, if a computer could theoretically follow

32:42

Speaker A

the steps and apply the rules without any genuine human judgment involved, then this process is a candidate for automation. We'll talk about specific tools in upcoming episodes. For now, just flag it as an automatable and move on.

32:59

Speaker A

The second option, delegate it. If the process needs a human, if it involves relationship building, nuanced communication, creative judgment, or anything that genuinely requires a person, then this is a candidate for delegation. You now have exactly what you need to delegate it properly. The

33:17

Speaker A

documented steps, the rules, the trigger, the output. Hand it to someone with all of that, and the delegation will actually work.

33:25

Speaker A

The third option, keep it. If, after genuinely reviewing it, this process requires you specifically, your expertise, your relationships, your irreplaceable judgment, then keep it.

33:39

Speaker A

But, do so consciously. Own the fact that this is your work, and make sure everything else around it is systematized so that your time is protected for exactly this.

33:50

Speaker A

That's it. Five steps. An inventory, a map, a trigger, an output, the rules, and a decision.

34:00

Speaker A

You can do all of this with a pen and paper. You can do it in an afternoon.

34:04

Speaker A

And the single process you document in that afternoon, if you then automate or delegate it, will pay you back in time for years.

34:16

Speaker A

I want to take 60 seconds here for a short detour, because there's a business example that I think illustrates all of this better than almost any other. And I promise it's not a cliché.

34:27

Speaker A

McDonald's. Whether you eat there or not, whether you admire the company or not, there is something worth understanding about how that business was built. McDonald's did not become the largest restaurant chain in the world because the food was extraordinary. It

34:41

Speaker A

became what it is because of the system. Ray Kroc, the man who scaled it, famously said that he was not in the food business, he was in the systems business. The whole operation was designed so that a teenager on their

34:54

Speaker A

first week of work could produce a consistent product, the same burger, the same fries, the same experience anywhere in the world, whether that was a branch in London or Tokyo or Buenos Aires.

35:07

Speaker A

That's not an accident. That's the result of obsessive documentation. Every process, every step, every rule, every temperature, every timing, every procedure, all of it documented, standardized, trained, and maintained.

35:21

Speaker A

The point isn't to run your business like a fast-food chain. The point is this, anytime you find yourself thinking, "Systems thinking is for big companies." Remember that McDonald's started as a single burger stand in California. The systems came first, the

35:36

Speaker A

scale followed. Systems don't come after you grow. Systems are how you grow. If you've made it this far, you're probably getting benefit from what I have to share. You might even be thinking about sharing this with colleagues or having a conversation with

35:52

Speaker A

your team. If you're feeling generous and would like to give back to support me in my efforts, you can do so at buymeacoffee.com/automateoffice.

36:02

Speaker A

Donations can be one-time or recurring in any amount that you would like and show me that you appreciate the content I provide.

36:10

Speaker A

We're coming to the end of today's episode, and I want to leave you with the biggest idea, not a tactic, not a step, the deepest shift. Most founders see themselves as doers. That identity, "I am the person who gets things done."

36:24

Speaker A

is what got them this far. It is a genuine strength, don't dismiss it. But at some point, the doer identity becomes the ceiling because a doer can only do as much as one person can do. And the hours run out. The energy runs out. The

36:39

Speaker A

capacity runs out. Systems thinking asks you to add a second identity, not instead of the doer, alongside it. The identity of the designer. A designer doesn't just do the work. A designer asks, "How should this work always get

36:54

Speaker A

done?" A designer looks at a recurring task not as a thing to complete, but as a process to build. A designer creates something that runs without them so that their own time and attention can be pointed at the things that genuinely

37:07

Speaker A

require them. Here's a way to think about it. Every system you build is an asset. It doesn't depreciate. It doesn't take days off. It doesn't have bad weeks. It runs in the background quietly producing its output, whether you're in the office or not,

37:22

Speaker A

whether it's Tuesday or Saturday, whether you're focused on a big new client, or you're finally taking that holiday.

37:28

Speaker A

The founder who builds systems is building a business. The founder who doesn't is building a job, a very demanding, very personal, very hard to escape job.

37:40

Speaker A

And the beautiful thing, the thing that I hope is landing for you by now, is that you don't have to be technical to do this. You don't need to know how to code. You don't need to buy any

37:50

Speaker A

software today. You just need to start looking at your work differently through the lens of what repeats, what are the steps, what are the rules, what's the trigger, what's the output. Start there.

38:02

Speaker A

Pick one process. Document it. Decide what to do with it. That's it. That's the beginning.

38:11

Speaker A

Here is your challenge for this week. Pick one thing, just one, that you did three or more times in the last month.

38:18

Speaker A

Write down the steps. Identify what starts it. Define what done looks like. Don't worry about making it perfect.

38:24

Speaker A

Just get it out of your head. That's your first system, and it's the beginning of a very different kind of business.

38:31

Speaker A

I'm your host, Justin, and this has been Systems Thinking, the secret to escaping the bottleneck.

38:40

Speaker A

If you'd like, you can connect with me on LinkedIn. I am Justin Turman, t u r m a n.

38:46

Speaker A

You can also find me on my website, automateofficework.com. I have a book a call button for anyone who would like to connect with me.

38:55

Speaker A

And I also offer consulting services. And please check out all the other episodes that have already been made.

39:05

Speaker A

And until next time, I wish you happy automating.

Topics: systems thinking automation solo founder delegation process documentation bottleneck workflow small business productivity tribal knowledge

Study this video

- [Flashcards from this video](https://sozai.app/tools/flashcard-maker/?from=transcript&id=90218)
- [Quiz on this video](https://sozai.app/tools/quiz-generator/?from=transcript&id=90218)
- [Crossword from this video](https://sozai.app/tools/crossword-maker/?from=transcript&id=90218)
- [Word search from this video](https://sozai.app/tools/word-search-maker/?from=transcript&id=90218)
- [Study guide from this video](https://sozai.app/tools/study-guide-maker/?from=transcript&id=90218)

Free, made by AI from this transcript. No signup.


---
This is the markdown twin of https://sozai.app/transcript/systems-thinking-escaping-bottleneck/ — the same content, without the markup.
Published by SozAI (https://sozai.app). Reuse and quotation are allowed with attribution and a link back.
Machine-readable index: https://sozai.app/llms.txt · data API: https://sozai.app/api/