LEADERSHIPOngoing practice

The Hire When It Hurts Method

Only hire to relieve sustained pain, never to fill imagined future needs

Problem it solves

ineffective leadership

Best for

["growing companies hiring their first few employees","founders who tend to hire preemptively based on growth projections","managers who want to build high-autonomy teams","companies whose headcount has grown faster than their actual workload"]

Not ideal for

["large enterprises with established HR processes and workforce planning requirements","companies in hyper-growth mode where hiring speed is a genuine competitive advantage","industries with long training ramps where just-in-time hiring creates dangerous skill gaps"]

Overview

Why this framework exists

Most companies hire wrong because they hire too early, too fast, and for the wrong reasons. Some are addicted to hiring, inventing positions for impressive candidates who have nothing meaningful to do. Others rush to replace every departing employee without questioning whether the position is still needed. This framework replaces proactive hiring with reactive hiring: you only add someone when the pain of not having them becomes unbearable.

The method starts before you even consider hiring. Do the job yourself first. If you have never done the work, you will not understand it well enough to evaluate candidates, write a realistic job description, or manage the person effectively. 37signals did not hire a system administrator until one of the founders spent an entire summer setting up servers alone. They handled customer support themselves for three years before hiring a dedicated person. This firsthand experience made them infinitely better at hiring and managing those roles.

When you do hire, the profile that matters most is what the authors call managers of one: people who set their own goals, determine what needs to be done, and execute without daily check-ins or heavy supervision. These self-directed individuals free the rest of your team to work more and manage less. To identify them, look for people who have launched projects on their own or built something from scratch.

The framework also challenges conventional hiring signals. Resumes are exaggerations that anyone can mass-produce. Years of experience beyond six months tell you almost nothing. Formal education credentials miss the vast majority of talented people. Instead, evaluate cover letters for genuine voice, hire the best writer among finalists regardless of role, and test-drive candidates with real miniprojects before committing.

Core principles

6 total
  1. Do every job yourself before you hire someone to do it
  2. Hire to kill pain, not for pleasure; if it does not hurt, you do not need someone yet
  3. Pass on great people if you do not have a real need; great has nothing to do with it
  4. Hire slowly to avoid the strangers-at-a-cocktail-party problem where everyone is polite but nobody challenges bad ideas
  5. Look for managers of one who set their own direction and execute autonomously
  6. Hire the best writer regardless of role because clear writing is a sign of clear thinking

Steps

5 steps
  1. Do the job yourself first
    Before hiring for any role, spend at least several weeks doing the work yourself. This gives you firsthand understanding of what the job requires, what good performance looks like, and what questions to ask in interviews. You will be a dramatically better manager for having done the work.
  2. Wait until it hurts
    Only hire when you have more work than you can handle for a sustained period and quality is visibly slipping. If someone leaves, do not replace them automatically. See how long you can function without that position. You will often discover you needed fewer people than you thought.
  3. Evaluate cover letters over resumes
    Resumes are mass-produced spam. Cover letters require actual communication and genuine interest. Look for a real voice that resonates with your company. Trust your gut on the first few paragraphs. If there is no hook, there is probably no match.
  4. Test-drive before committing
    Hire candidates for a miniproject of twenty to forty hours before making a full offer. See how they make decisions, how they handle ambiguity, and whether you work well together. Interviews reveal what people say they can do; test drives reveal what they actually do.
  5. Look for managers of one
    Prioritize candidates who have demonstrated self-direction: people who have launched their own projects, run their own businesses, or built something from scratch. These people set their own goals and execute without supervision, freeing everyone else to work rather than manage.

Examples

2 cases
37signals three-year customer support journey

When the company launched, one of the founders personally handled all customer support for three full years. Only after deeply understanding the role, the customer pain points, and what great support looked like did they hire a dedicated support person.

OutcomeThe intimate knowledge of the support role meant they could hire precisely the right person, write an accurate job description, and manage the role effectively. The hire was successful because it was informed by thousands of hours of firsthand experience.
BMW's simulated assembly line hiring

BMW built a simulated assembly line at a factory in South Carolina where job candidates spent ninety minutes performing a variety of work-related tasks. Instead of relying on resumes and interviews, they evaluated candidates through actual performance.

OutcomeThe test-drive approach revealed candidate capabilities that traditional hiring processes missed entirely, resulting in better hires who were proven performers before they ever started the real job.

Common mistakes

3 traps
Hiring someone just because they are impressive
Bringing in talented people who have no meaningful work to do creates artificial projects, busywork, and unnecessary complexity. Impressive candidates without a real need become expensive overhead that generates make-work for everyone else.
Hiring rapid-fire and creating the cocktail party problem
When you add many new faces quickly, the team dynamic shifts to polite small talk where nobody challenges bad ideas. You lose the psychological safety needed for honest disagreement. Hire slowly enough that the team can absorb each new member.
Over-weighting years of experience and formal credentials
There is surprisingly little difference between a candidate with six months of experience and one with six years; the curve flattens quickly. And ninety percent of Fortune 500 CEOs did not attend Ivy League schools. What matters is how well someone works, not how long or where they studied.

Origin story

How this framework came to be

Fried and Hansson built 37signals to a multimillion-dollar company with a deliberately tiny team. They discovered that every unnecessary hire created artificial work, which led to artificial projects, which led to real costs. The most productive periods were when the team was smallest. They codified their hiring approach after watching other companies balloon their headcount only to lay people off when the work did not materialize.

Source

Traced to primary
Source · BOOK
Rework
Jason Fried & David Heinemeier Hansson · 2010
Open source →

Related frameworks

Browse all Leadership →