What Entrepreneurs Can Learn from Work Rules!
A founder named Mara, running a twelve-person logistics startup, has always approved every client discount herself. One Friday a major account threatens to leave over a shipping delay, and her account manager, Devon, has already drafted a fix, but waits for her sign-off, since that's how things work there. She is in back-to-back calls for six hours, and by the time she says yes, the client has signed with a competitor. That night Mara realizes the bottleneck wasn't Devon's judgment; it was her habit of routing every decision through herself. She had hired him for a strong résumé, but had never watched him handle a messy problem first.
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
Open the Books Before You Feel Ready
For an entrepreneur, sharing real numbers and reasoning behind decisions feels riskier than for a large company, since a small team sees every gap. But withholding information doesn't protect the business; it leaves employees guessing, often badly. Treating early hires like partners who deserve context lets them represent the business well when the founder isn't in the room.
A founder who shares wins but hides financial strain trains the team to distrust every announcement, so when a real crisis hits, no one believes the optimism.
Before your next team meeting, name one thing you'd normally withhold — a client risk, a cash concern, a strategic doubt — and share it, with what you're doing about it.
Test the Hunch Against What Happened
Founders trust their gut because it built the company so far, but instincts that spotted a market opportunity aren't automatically reliable for judging people. Evidence-based thinking means checking what a hire actually produced, not how confident the decision felt. A habit of comparing outcomes to expectations catches moments when product and people instincts quietly diverge.
A founder promotes whoever agrees with them most, mistaking comfort for competence, and only notices the gap after the strongest performer quietly leaves.
After your next hiring or promotion call, write down what you expect that person to accomplish in ninety days, then check the outcome before the next call.
Judge the Story, Not the Résumé Line
A polished résumé tells you what someone claims; a specific story about a real problem solved tells you how they think under pressure. For an entrepreneur without a recruiting department, this matters more, since one poor hire in a ten-person company reshapes the culture. Asking candidates to walk through an actual situation, what they tried, what failed, reveals more than asking if they seem like a good fit.
A founder hires someone mainly for a prestigious school and a shared hobby, then discovers months later the person has never had to fix a problem they caused.
In your next interview, swap one generic question for "tell me about a time something you built failed, and what you did next," listening for specifics.
Give Away the Decision Before It Feels Safe
For a founder, letting go of a decision you could still make yourself is the hardest freedom to grant, since every mistake feels like it happens under your name. But a company that only moves as fast as the founder's calendar caps its own growth. Handing over real authority, on hiring, budget, or client commitments, before it feels comfortable is often the only way the business becomes larger than the founder alone.
Sharing information and granting real freedom can pull against evidence-based caution: the fastest way to learn if someone deserves authority is to give it before full proof exists, exactly the leap founders resist. Waiting for airtight evidence before delegating keeps a founder the permanent bottleneck. The workable middle treats early freedom as a bounded experiment, generating evidence a cautious approach would otherwise wait forever to see.
Name one thing, honestly
What is one decision you are still making yourself that someone on your team has already shown, through real evidence, they are ready to own?
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
In your next interview, swap one generic question for "tell me about a time something you built failed, and what you did next," listening for specifics.