What Entrepreneurs Can Learn from Hiring for Attitude
Dana ran a twelve-person logistics startup and needed an operations lead fast. The candidate she hired had six years at larger companies, fluent command of the inventory software, and references who called her "sharp." Three months in, the woman was technically flawless and quietly corrosive: she overrode drivers' judgment calls, treated missed deliveries as someone else's failure, and stopped asking questions once she assumed she had the answer. Dana had asked about software experience and five-year plans, never about what the candidate does when a plan she owns falls apart. By the time Dana noticed the team going quiet in meetings, the hire had trained three good people to say less.
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
The Resume That Hides the Real Risk
For a founder, technical competence is the easiest thing to verify and the least likely thing to cause a hire to fail. What sinks a promising hire in a small company is usually something else: an unwillingness to be coached, a habit of blaming circumstances, or a mismatch between how someone handles ambiguity and how much the job contains. Stretched thin, founders weight the visible, checkable stuff and treat attitude as something to sort out later.
A founder builds an interview loop around technical tests, then is blindsided when the strongest candidate demoralizes the team within the first hard month.
Add one interview round dedicated to attitude, asking the candidate to describe a time a plan they owned failed, and listening for ownership rather than blame.
Values You Can Actually Point To
Many founders say they want a "good fit" without writing down what the company's values are, so fit quietly becomes "someone I enjoy talking to." That standard hires for charm, not compatibility with how the company needs to operate. Genuine fit means checking behavior against specific, named values, not how comfortable someone made the room feel.
A founder passes on a blunt candidate who would have thrived in the company's direct culture, then hires an agreeable one who needs reassurance the company cannot provide.
Write down three to five specific behaviors the company actually values, and ask every candidate for a concrete story testing each one.
Interview Questions That Do More Work
Founders often ask candidates the same open-ended questions everyone asks, which reward rehearsed answers more than honest ones. A more useful interview asks for a specific past instance: a time they got tough feedback, or a project they cared about got cut. The specificity makes the answer hard to fake.
A founder asks how a candidate handles stress, accepts a smooth generic answer, then discovers under real deadline pressure that stated calm and actual calm are two different things.
Replace one generic interview question with a request for a specific story, and require a concrete example before moving on.
The First Ninety Days Decide the Outcome
Even a genuinely good attitude hire can curdle fast if the day-one job doesn't match what the interview described, or if the founder is too busy to give direction to calibrate against. A hire sold on "wearing many hats" but handed no priorities will start guessing, and guessing under uncertainty is where even a coachable person starts to look like a problem.
Sometimes the instinct to hire fast for values-fit competes with the discipline of asking specific questions: a founder meets someone who feels right and is tempted to skip harder questions because the gut read already feels confirmed. That is precisely the moment structure matters most, since a strong first impression is easiest for a skilled but poorly suited candidate to produce.
Name one thing, honestly
Think of the last person you hired mostly because you liked them: what value did you actually verify, versus simply assume?
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
Replace one generic interview question with a request for a specific story, and require a concrete example before moving on.