What Entrepreneurs Can Learn from The Year Without Pants
Maya had built her twelve-person product studio the way most founders do, everyone crammed into one loft, decisions made by whoever stood near the whiteboard. Then her best engineer moved for family reasons, and within a year half the team was scattered across three time zones. Maya kept scheduling calls at odd hours to keep everyone aligned, and productivity slid anyway. Her cofounder finally asked a harder question: was she managing the work, or trying to recreate the loft she missed. Maya realized she had never designed a way of working for a distributed company, she had only improvised around the absence of one, and it was starting to cost her the team's trust.
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
Leading without walking the floor
A founder used to reading the room loses that instrument the moment the team disperses. Trust has to be built through visible follow-through instead: commitments kept, decisions explained, problems named before someone else has to. Employees watch what a founder does under pressure far more than what a founder says in a rally speech, and in a distributed company that behavior has to be documented, because nobody is in the room to witness it directly.
Founders default to constant pinging because it feels like leadership, but it reads as anxiety and erodes the autonomy they claim to want.
Before sending a check-in, ask whether it serves the work or your own discomfort, and if the latter, write the worry down instead and revisit it tomorrow.
Writing as the new hallway
Without a shared office, the founder's job shifts from being seen to being legible. Strategy, rationale, and priorities need to live in documents anyone can find later, not in a conversation only a few people overheard. This is uncomfortable for founders who think fast and talk faster, but written decisions scale in a way spoken ones never do, letting new hires and quiet contributors catch up without special access to the founder's calendar.
Founders write announcements but skip the reasoning behind them, so the team complies without understanding, and questions resurface weekly.
Attach a short why to every major decision you post, even three sentences, so people reason from it instead of just obeying it.
Resisting founder-shaped process
Small companies often add process because the founder feels less anxious with visibility, not because the work needs it. A new approval step, a mandatory daily check-in, a dashboard nobody reads, each one narrows the autonomy that made early hires join in the first place. The instinct to control tightens exactly when trust should be extended further.
A founder introduces a new tracking ritual after one missed deadline, and it outlives the problem it was meant to solve, becoming permanent overhead.
Put an expiration date on any new process you add, and only renew it if you can name the specific failure it prevented.
Keeping a scattered company one company
Culture in a distributed startup is not the loft or the snacks, it is the shared story about why the work matters and how people treat each other. Founders have to narrate that story deliberately, because it will not happen by osmosis. Onboarding, informal recognition, and conflict resolution all need intentional substitutes for what used to happen by proximity, or the company fragments into loosely connected freelancers who share a payroll.
The tension shows up fastest between transparency and minimal process: writing everything down so the team stays informed can itself become new overhead, another dashboard, another required update, if the founder is not careful. A founder chasing visibility might over-document routine work, unintentionally recreating the surveillance culture the model was meant to avoid. The fix is not less writing, it is writing that explains decisions rather than tracking activity, so transparency serves trust instead of becoming a new kind of supervision.
Name one thing, honestly
Which of your current check-ins exist because the work needs them, and which exist because you would feel anxious without them? Where in your company does important reasoning live only in your head or a single conversation?
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
Put an expiration date on any new process you add, and only renew it if you can name the specific failure it prevented.