Every founder I know who has built something genuinely durable โ a business that grows without requiring their constant intervention โ shares one characteristic that isn't talked about nearly enough: they think in systems.
Not in tasks. Not in projects. Not even in goals. In systems โ the underlying structures that produce outcomes, repeatedly, whether the founder shows up that day or not.
Systems thinking isn't a new concept. It comes from engineering, ecology, and organisational theory. But its application to early-stage business building is, in my experience, one of the most powerful โ and least practised โ advantages available to any founder who chooses to develop it.
What Systems Thinking Actually Is
At its core, systems thinking is the practice of seeing your business not as a collection of tasks and people, but as a set of interconnected feedback loops that produce your results.
Every business outcome โ revenue, customer satisfaction, employee retention, product quality โ is the output of a system. The question a systems thinker asks isn't "how do I improve this outcome?" It's "what is the structure generating this outcome, and which part of that structure, if changed, would produce a better outcome with the least effort?"
"Hustle can produce a result once. A system produces a result every time, without requiring the same amount of effort each time."
The Three Core Concepts
1. Feedback Loops
Every system contains feedback loops โ mechanisms by which outputs influence future inputs. There are two types:
Reinforcing loops amplify change in one direction. More content โ more audience โ more leads โ more revenue โ more budget for content. This is the compounding loop every founder is trying to activate. The challenge: reinforcing loops amplify in both directions. If the initial signal is negative, reinforcing loops accelerate decline.
Balancing loops resist change and seek equilibrium. When your team is overwhelmed, quality drops. Quality drop โ customer complaints โ team spends time on support โ less time for delivery โ more overwhelm. These loops are why businesses plateau โ the system is compensating for growth with friction.
The skill is learning to identify which loops are operating in your business, and which to strengthen or disrupt.
2. Stocks and Flows
A stock is anything that accumulates over time: your reputation, your client relationships, your team's skills, your cash reserves, your content library. Stocks change slowly. They can't be built overnight, but they compound remarkably over time.
A flow is the rate at which a stock changes: monthly revenue, new clients won, content pieces published, team members hired. Founders obsess about flows. Systems thinkers obsess about stocks โ because changing a stock changes the ceiling on every flow downstream.
Practical implication: when you're deciding where to invest time, ask which activity builds a stock (durable asset) versus which just increases a flow temporarily. Writing a comprehensive knowledge base builds a stock. Answering the same support question for the hundredth time is just a flow โ with no cumulative value.
3. Leverage Points
Not all parts of a system are equally influential. A leverage point is a place in the system where a small change produces a disproportionately large effect. Donella Meadows (the foundational systems thinker) identified a hierarchy of these โ the highest leverage point being the ability to change the goal of a system entirely.
For founders, identifying leverage points means asking: "Of all the things I could change in my business right now, which one would move the needle most on the outcomes I care about?" The answer is rarely the most obvious intervention. It's usually something structural โ a pricing model, a hiring criterion, a positioning statement, a process that sits upstream of multiple downstream outcomes.
How to Map Your Business as a System
The fastest way to start applying systems thinking is through a causal loop diagram โ a visual map of the feedback loops in your business. You don't need special software. A whiteboard or a Notion page works fine.
Exercise: The Business Loop Map
Step 1: Pick one outcome you most want to improve (e.g. inbound leads per month).
Step 2: List everything that directly causes that outcome to go up or down.
Step 3: For each of those causes, list what causes them.
Step 4: Draw arrows connecting them. Mark each arrow as reinforcing (+) or constraining (-).
Step 5: Circle the biggest reinforcing loop in the diagram. Ask: what would it take to strengthen that loop?
Most founders who do this exercise for the first time surface at least one systemic constraint they hadn't consciously identified โ usually something they've been treating as a fixed limitation rather than a changeable system parameter.
High-Leverage vs. Low-Leverage Activities
Once you can see your business as a system, the distinction between high-leverage and low-leverage work becomes obvious โ and it's often the opposite of what feels urgent.
- High leverage: Defining a hiring criterion that ensures every new team member raises the average. Building a sales playbook that means your next hire closes at 80% of your rate from day 30. Writing a content framework that produces consistently high-engagement posts across all platforms. These are activities that produce compounding outputs.
- Low leverage: Answering individual emails. Reviewing deliverables one at a time. Making decisions that your team should be able to make. Doing tasks that your processes should handle automatically. These are activities that produce linear outputs โ or worse, activities that other people or systems could handle.
The trap most founders fall into is optimising low-leverage activities. They get faster at answering emails. They build more efficient processes for doing things that shouldn't require their involvement at all. The systems thinker asks a different question: "How do I remove myself from this loop entirely?"
Building Compounding Systems
The practical payoff of systems thinking is the ability to build systems that compound โ where the output of one period becomes the input for the next, producing exponential rather than linear growth.
The content engine I wrote about elsewhere is a compounding system. The audience built in month 3 makes month 4 content more powerful. The leads generated in month 6 become testimonials and case studies that make month 12 content more persuasive. The system grows its own inputs.
Your hiring process, your product development cycle, your client relationship management, your pricing model โ all of these can be designed as compounding systems rather than linear processes. The difference is intentionality: designing for accumulation, not just execution.
The Mindset Shift
The real shift that systems thinking produces isn't a new framework or a better process. It's a different question you ask before taking any significant action:
Instead of: "How do I solve this problem?"
Ask: "What is the structure generating this problem, and what would need to change to make it stop recurring?"
Instead of: "How do I grow faster?"
Ask: "Which loop in my business, if strengthened, would produce faster growth as a natural output?"
Instead of: "Why isn't this working?"
Ask: "What balancing loop is preventing this from gaining momentum, and how do I disrupt it?"
Founders who develop this habit of asking structural questions make different decisions. They invest in things that build stocks rather than just increasing flows. They identify leverage points instead of spraying effort broadly. And over time, they build businesses that grow themselves โ because the systems were designed to.
Apply This to Your Business
The Founder Systems OS is built on systems thinking principles โ a complete Notion workspace for designing your business as a set of interconnected, compounding systems rather than a pile of tasks.
Get the Founder Systems OS โ