What Entrepreneurs Can Learn from Who
Maya had grown her subscription skincare business to seven employees when she admitted she couldn't answer every customer email herself. She posted an ad for a "customer experience lead" and hired the applicant who seemed most enthusiastic about the brand. Three months later, she realized she and her new hire had never agreed on what the job was supposed to accomplish: Maya wanted someone who could cut response time and build a support system from scratch, while her hire assumed the role meant answering tickets exactly as Maya always had. Neither was wrong; they had simply never named the target, and Maya only wrote the job's goals down once frustration had set in.
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
Name the First-Year Win Before You Post the Job
Founders tend to describe a role by tasks — answer emails, manage the calendar, ship the feature. What matters more is agreeing, before interviewing anyone, on what this person must accomplish within a year for the hire to count as a win. That sentence, shared with any co-founder, turns a vague posting into a real yardstick.
A founder hires quickly to relieve pain, then discovers months later the hire optimized for the wrong thing because no one defined what winning looked like.
Before posting any job, write one sentence describing the specific outcome this hire must produce in twelve months, and reread it before you interview anyone.
Recruiting Never Stops Just Because You're Not Hiring
Founders treat hiring as a fire to put out only when a seat opens, so every search starts from zero. A stronger habit is treating every strong person you meet — a vendor, a customer, a competitor's employee — as a future hire worth staying in touch with, long before a role opens. When the moment comes, you're choosing among people you already trust.
A founder suddenly needs an operations lead, posts a job that week, and chooses among whoever applied in ten days instead of someone they'd have wanted.
Keep a running list of impressive people you meet through work, and message one of them every month just to stay in touch, with no ask attached.
Ask for the Whole Story, Not the Highlight Reel
Founders often fall for charisma, judging a candidate the way they'd judge a sales pitch. A better approach is asking someone to walk through their work history in order — what they were hired to do at each stop, what happened, and why they left — rather than hypothetical questions about handling a crisis. Real patterns show up in real history, not rehearsed answers.
A founder hires the most polished interviewee in the room, only to learn later that the same early-enthusiasm-then-disengagement pattern showed up at every previous job.
In your next interview, ask the candidate to walk chronologically through each past role and why they moved on, before asking any hypothetical questions.
The Pitch Only Works If It's About Them
Once you've found the right person, founders often oversell the mission as if enthusiasm alone closes a hire. But the person you want is usually weighing something specific — proximity to family, creative control, a chance to build from scratch, or stability after a rocky stretch. Naming what that individual needs, and speaking to it directly, closes a hire far better than repeating how exciting the company is.
Defining the year-one outcome and staying open to a promising person you meet unexpectedly can pull against each other: a rigid outcomes list may cause you to overlook someone whose history suggests they'd exceed it a different way. Founders who build relationships continuously risk falling for a likable person before checking whether their history matches the role. Treat the outcome as the anchor and the person as the variable.
Name one thing, honestly
If you had to write down, in one sentence, the outcome your last hire needed to produce in their first year, could you do it 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
In your next interview, ask the candidate to walk chronologically through each past role and why they moved on, before asking any hypothetical questions.