What Entrepreneurs Can Learn from Thinking in Systems
Founders live inside a loop of urgent, disconnected fires: a churn spike this week, a hiring gap next week, a cash crunch after that. The natural response is to treat each one as its own emergency and solve it in isolation, because that's what the calendar rewards. But in an early company, everything is wired to everything else — pricing touches support load, support load touches morale, morale touches the very sales calls that were supposed to fix revenue. Founders who never step back to see those wires keep "fixing" the same underlying problem under five different names. The habit worth building isn't more hustle; it's a better map of what's actually connected.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
See the business as wiring, not a list of departments
Every startup metric you track is downstream of some other metric, and upstream of a third. Treat your dashboard as a map of connections, not a scoreboard of separate scores.
A founder notices refund requests climbing and assigns a support rep to "handle refunds better." Three months later, refunds are still climbing, because the real driver was a checkout page that overpromised delivery times, which fed frustrated customers into support, which slowed response times, which fed more frustration into refunds. Treating refunds as an isolated department problem left the checkout page untouched.
This week, pick your worst metric and trace it backward through three other parts of the business before proposing any fix.
Tell a growing snowball from a self-correcting one
Some trends in a young company will keep accelerating on their own — word of mouth, technical debt, a hiring backlog. Others are naturally self-limiting and will level off no matter what you do. Confusing the two leads to either panic over something that would have settled anyway, or complacency about something that is about to run away from you.
A two-person founding team sees signups doubling every two weeks and assumes the growth will keep compounding, so they commit to a large lease and a hiring spree. The doubling was actually a one-time bump from a single influencer post, and it flattens the month after — leaving them overstaffed and overcommitted for a plateau, not a rocket.
For your top three metrics, write one sentence each on whether recent movement is self-reinforcing or self-limiting, and what evidence would tell you if you're wrong.
Find the lever, not just the harder push
When a fix keeps needing more force to hold — more ad spend, more overtime, more discounting — that is a signal you are pushing on the wrong point. The better move is usually a small structural change: a default setting, an onboarding step, a pricing rule, a piece of information customers or employees never had.
A founder responds to slipping activation rates by running bigger promotions every month, each one working a little less than the last. The actual fix — moving one confusing setup step to after a user's first success, not before it — takes a single afternoon and outperforms every future promotion the founder never has to run.
List every problem you're currently solving with "more effort" and ask what single structural change could make the effort unnecessary.
Hold the model loosely
Even a sharp read of your business is a sketch, not a photograph, and your company will keep changing under you as it grows. Treat every plan as your current best guess, watch for the moment reality stops matching it, and expect that even a well-built map will still miss something a real customer does.
Seeing the whole system takes time you don't have, while finding the one high-leverage fix demands you act fast on partial information. Resolve this by timeboxing the mapping — thirty minutes tracing connections is enough to catch the most obvious wrong target — then act, and treat the action itself as a test of the map.
Name one thing, honestly
What's one recurring fire in your business that you've fought the same way at least three times — and what might it be connected to that you've never traced?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
List every problem you're currently solving with "more effort" and ask what single structural change could make the effort unnecessary.