What Entrepreneurs Can Learn from Distributed Teams
A founder running a five-person startup out of a spare bedroom and two laptops set up in different countries notices, six months in, that the company has no place anything lives. Decisions get made in whichever chat thread happened to be open when someone had an opinion, and half of them never make it past that thread. A contractor finishes a feature late on a Friday and waits eleven hours before anyone in the founder's own time zone notices the message. The founder starts most mornings scrolling three separate apps, trying to reconstruct what happened overnight while everyone else slept. By the following week, two people are quietly building different versions of the same feature, unaware the other exists. Growth has simply outrun the informal habits that used to hold the small team together, and the founder starts to suspect the real problem is structure, not effort.
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
Building the record before you need it
Communication infrastructure usually gets added once a company feels real, which is backwards: the earliest days are when habits are cheapest to set. Deciding on purpose where decisions get written down and which channel is for what turns founder knowledge into company knowledge. This is not about generating documents; it is about making a few places reliably authoritative.
The founder answers in private messages instead of updating the record, and the record becomes decoration nobody trusts.
Pick one shared document as the source of truth, and treat anything decided elsewhere as provisional.
Designing around the calendar you actually have
Once a startup has one person outside the founder's time zone, real-time meetings stop being neutral and become a cost someone else pays. Assuming anyone can hop on a call whenever inspiration strikes asks part of the team to stay on call. A written proposal instead of a scheduled discussion lets the company run on hours its people actually live in.
Calls keep happening at the founder's convenience, and contributors elsewhere disengage from decisions that affect them.
Default new discussions to a written thread, and reserve live meetings for topics that truly need real-time back and forth.
Hiring and growing people without an office to lean on
A founder used to judging fit by gut feel in a shared room needs something more explicit once hiring goes distributed, since no hallway conversation catches what an interview missed. Onboarding remotely means writing down what used to be absorbed by osmosis: who owns what, how requests move, what good work looks like. Career growth needs the same deliberateness, or people assume the company itself is the only thing anyone tracks.
A new hire spends a month guessing at unwritten norms and leaves quietly, and the founder blames the hire, not the missing structure.
Write a short onboarding path for the first two weeks, and hold a real growth conversation each quarter.
Measuring contribution without an office to watch it in
Without an office to measure activity by, a founder must decide what success looks like for each role, or the team rewards whoever is most visible online. Founders under pressure easily mistake a fast reply for real progress. Measuring outcomes, a feature shipped, a question resolved, instead of hours logged or messages sent, keeps the company honest about what it pays for, and protects people doing careful work that never announces itself.
Documentation discipline and speed pull against each other, since writing things down takes time a founder feels they cannot spare while a customer waits. Async collaboration collides with the instinct to just get on a call and settle things in minutes. A careful hiring process moves slower than a founder desperate to fill a seat wants. None of this resolves cleanly; the job is choosing, case by case, what the company can skip this week without paying for it later.
Name one thing, honestly
Which piece of company knowledge currently lives only in your head, and what happens the week you are unreachable? If you judged contribution by outcomes alone for one month, whose work would look different than it does today?
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
Write a short onboarding path for the first two weeks, and hold a real growth conversation each quarter.