26 resources from Harvard Business Review we point founders to, and the questions each answers.
📄 Article
✓ Link checkedFreemiumIntermediate
Why we picked it
The canonical HBR article that formalizes JTBD from its originators, the authoritative reference every founder citing 'jobs to be done' should have actually read.
Why we picked it
Sometimes the two ideas are a proxy for a deeper problem: you have no agreed way to make a call when you disagree. This HBR piece treats disagreement as a skill and pushes you to set decision rules in advance, including who gets the final say on which kinds of calls, so a single stuck choice does not calcify into resentment. It is short and pairs well with a disagree and commit rule: back one idea for a defined window with pre-agreed metrics, then review.
Why we picked it
This short piece names the exact bias that trips up experts: once you know something deeply, you literally cannot imagine not knowing it, so you assume your idea is as obvious to everyone else as it is to you. That is the mechanism behind insider bias, and seeing it named makes it easier to catch in yourself. It is a starting point for why 'this is obviously needed' from an expert is a claim to test, not a fact.
Deep expertise makes you a worse judge of what outsiders see, because you unconsciously fill in context they do not have.
The famous tapper and listener experiment shows how badly experts overestimate how clear their own signal is to everyone else.
The fix is concrete language and real stories over abstract certainty, which is also how you check whether your idea lands with people who do not already share your knowledge.
Why we picked it
Most advice assumes the network you are missing is the whole game. Lazarow flips that: founders far from the big hubs are forced to build for real demand instead of hub fashion, and that discipline is where the durable trends actually show up. A good starting point for treating your distance as a source of signal, not a handicap.
Why we picked it
This is the canonical piece that put jobs to be done on the map, written by the people who coined it. It uses the famous milkshake story to show that customers do not buy products, they hire them to make progress in a specific situation, which is the exact lens this question is about. Read it as the clearest short starting point before going deeper into JTBD.
Why we picked it
The faster horse line gets quoted to justify ignoring customers entirely, and that reading is wrong. Vlaskovits, a customer development author, unpacks why a customer asking for a faster horse is still handing you the real job (get me there quicker), even though they named a solution they could imagine. It reframes a feature request as a signal about intent, which is exactly the muscle this question is about. Read it as a way to think, not a rule.
Why we picked it
A dominant player with 80 percent share is almost always over-serving its most profitable customers and quietly ignoring the low end and the overlooked. This is Christensen's core map for exactly that situation: how a small entrant gets a foothold in a segment the incumbent does not care to defend, then moves up. Read it as a starting point for spotting where the giant is soft, not as a promise that disruption is easy.
Why we picked it
This is the piece that names the exact fear: a big player with more money, data, and talent can copy anything you build that is not locked behind a patent. Instead of telling you to out-feature them (you cannot), it argues the survivors compete on things giants cannot easily match, like a specific customer segment, a decoupled step in the buying journey, and a business model the incumbent will not cannibalize. Read it as a starting point for reframing the panic into a question about what you are actually defensible on.
A big competitor announcing your feature is a signal you may have built a feature, not yet a defensible business, so use it to pressure-test what is truly yours.
Giants get slowed down by their own scale and existing revenue: pick the customers or the workflow step they will not fully commit to serving.
Defensibility comes from focus and switching the ground of competition, not from trying to match the incumbent feature for feature.
Why we picked it
This is the cleanest, research-backed answer to the exact question, and it refuses to give you a blanket yes or no. Yohn walks through two academic studies (one finding a name boost, one finding the opposite) and lands on 'it depends' on your business type, which is the honest starting point most founders need before deciding.
Why we picked it
This is the piece that put the phrase minimum viable brand into circulation, and it argues the opposite of both extremes: you do not need a full brand manual, but build it and they will come is not a strategy either. Yohn frames the smallest useful set of brand decisions an early-stage company should make before launch. Read it as a way to decide what to skip, not a checklist to complete.
Why we picked it
Baehr's point is that founders who only reach out when they need something are digging a well during a drought. The fix is building relationships and giving value long before you need the favor, so the network stays genuinely willing to help. Applied to launches, it says the real work happens between launches, not in the ask itself.
Why we picked it
This is the canonical piece on packaging one product into three tiers so it stretches across price-sensitive and premium buyers at once. Mohammed gives real guardrails: rough price gaps between tiers and how much revenue to expect from each, which is exactly the practical framing you need when small startups and large companies are looking at the same product. Treat it as a starting template for your own good, better, best structure, not a rule to copy line for line.
A stripped-down Good tier attracts price-sensitive buyers (small startups), the Better tier holds your core users, and a feature-rich Best tier lets large companies spend more.
Practical guardrails: keep Good within about 25 percent below Better, and Best within about 50 percent above Better, so the ladder reads as coherent.
The tiers do the segmenting for you: buyers self-select by need and budget instead of you negotiating every deal from scratch.
Why we picked it
This is the study that ends the argument, not another opinion piece. Two MIT economists plus the U.S. Census Bureau looked at 2.7 million founders and found the average founder of a fast-growing startup is 45, and a 50-year-old is roughly twice as likely to build a top-tier outcome as a 30-year-old. Read it when the voice in your head says 40 is late: the data says 40 is the sweet spot, and your decade of domain depth is the edge a 24-year-old cannot buy.
From
Harvard Business Reviewby Pierre Azoulay, Benjamin F. Jones, J. Daniel Kim, Javier Miranda9 min read
The mean age of a successful high-growth founder is 45, and success rates keep climbing with age well past 40, not down.
A 50-year-old founder is about twice as likely to reach an IPO or acquisition as a 30-year-old, so your age is signal, not liability.
The young-genius story is survivor bias amplified by VC bias (one YC quote pegs the investor cutoff at 32); the population data tells the opposite story.
Why we picked it
Steve Blank's argument for searching for a business model before building one, the get out of the building philosophy in short form. It contrasts the old write a plan and build in secret approach with testing hypotheses on real customers. A crisp, credible piece to send anyone who thinks planning can substitute for talking to people.
Why we picked it
Mullenweg's HBR first-person account of switching Automattic to paid tryouts after charming interviews kept misfiring. It is the more polished, citable version of the audition idea, with numbers on how many tryouts convert to hires. It sits behind a metered paywall, but it is worth one of your free reads.
Why we picked it
The short HBR version of Wasserman's research if you do not want the whole book. It lays out the rich versus king tradeoff crisply and why sharing equity to bring in the right people usually pays. Good for a founder who wants the core idea in one sitting.
Why we picked it
This is the canonical source for the claim that the customers you already have are far cheaper to keep than the ones a shiny feature might win. Gallo lays out the retention economics, including how acquiring a new customer can cost many times more than keeping an existing one. It gives you hard numbers to justify protecting reliability and promises over the exciting build.
Why we picked it
The written, citable version of the Kanze research, useful when you want the study details and the exact reframing tactic on the page. It documents that the questioning gap, not the businesses themselves, explained much of the funding difference. Keep it handy as evidence and as a script for turning defensive questions into growth answers.
Why we picked it
This is the strategic backbone: how platform businesses take power from traditional pipeline businesses by orchestrating a community and owning the interactions. Understanding the model tells you why the platform behaves the way it does, and where a dependent business can still create value. Denser and more academic, but foundational.
Why we picked it
If you're going to spend a big ask on a launch that really matters, this research tells you how to spend it well: in-person or synchronous requests land dramatically better than a mass text or post. Read it before the next ask you decide is actually worth making, so the goodwill you spend gets you the most in return.
Why we picked it
A pricing consultant's argument that most companies discount reflexively instead of strategically, with a framework for deciding when a discount actually earns you something back. Useful once you're past the first pilot and start seeing discount requests as a pattern, not a one-off. Helps you turn the genuine reason test into an actual policy.
Why we picked it
This lays out the mechanics of anchoring price to the value a customer gets rather than to what competitors charge, which is your only real option when there is no competitor to check against. It gives you the actual questions to ask a prospect to quantify what their current, worse solution costs them. That number becomes your anchor.
Why we picked it
This is the closest thing to a canonical answer to your exact fear: writing to someone who seems too important to reply to you. It breaks down why brevity, specificity, and a low-effort ask beat a polished pitch, which is exactly the muscle you need when you have no brand name to lean on.
Why we picked it
This article names the specific ways a survey misleads you: people rush through it, answer the way that feels acceptable rather than true, and never get a follow up question when their answer is confusing. It is the clearest short case for why surveys are a trap at the start, written for a general business audience, which makes it a good one to send a co-founder who still wants to skip the calls.
Why we picked it
A two minute companion to the longer HBR piece above, this is the one line version of our short answer you can forward to anyone in a hurry: skip the survey, have the conversation, ask the follow up. Keep it as the quick reference you send a skeptical teammate.
Why we picked it
This is the original milkshake essay: researchers sat in a parking lot and watched who bought milkshakes and when, instead of asking customers what flavor they preferred, and found the real job was keeping a bored commuter's one free hand busy. It is the founding case study for researching the job someone is hiring a product to do rather than their stated preferences.
