|
Hello Reader, Most people think the job of a toothbrush is to clean their teeth. But if you studied what people do, you might discover something else: some rinse or sanitize their brush every time. That behavior isn’t about plaque—it’s about reassurance, about feeling clean and safe. Unless you ask the right questions and observe the job behind the job, you’d miss it entirely. That gap, the one between what we assume and what people need, is exactly what Jobs to Be Done helps reveal. While the toothbrush example is hypothetical, it shows how a little curiosity and observation can unlock powerful insights into unmet needs. Jobs to Be Done is a way of understanding customer behavior through the lens of progress: what is someone trying to accomplish, and how can your product help them get there? The “job” isn’t the product—it’s the underlying need or outcome they’ve hired it to solve. That’s why this model is part of Re:Mind, our deck of 100 mental models for better thinking. We hit $8.5K on Kickstarter and unlocked both stretch goals—thank you. If you missed it, late pledges are still open. Why Use ItPeople don’t buy products. They hire them to do a job. That shift in thinking reframes innovation from building features to solving meaningful problems. Use this model to:
When to Use ItUse this model when you’re trying to understand not just what people are doing, but why they’re doing it. Jobs to Be Done helps uncover motivations that traditional metrics or interviews often miss. Use this model when:
How to Use ItIn The Founder, Ray Kroc realizes McDonald’s isn’t just selling burgers; it’s selling speed, consistency, and a dependable experience. Customers aren’t hiring food; they’re hiring a fast, frictionless routine in the middle of a chaotic day. That insight leads to the systemization and scaling of one of the most iconic service models in the world. That’s Jobs to Be Done thinking: uncovering the real progress people are trying to make. Here’s how to apply it:
Next StepsList 3 reasons someone might use your product or service—then challenge them. Are they features, or outcomes? Rewrite each one as a job: “Help me __ so I can __.” Where It Came FromThe theory originated with Harvard Business School professor Clayton Christensen, who popularized it as a way to understand innovation beyond traditional demographics. It gained traction when researchers studied why people bought milkshakes in the morning (hint: it wasn’t about taste—it was about a quiet commute ritual). Since then, it’s been used to drive customer-centric innovation in industries from tech to healthcare. Until next time, keep exploring and questioning. Your unique perspective is your greatest asset. Think Independently, JC Share or Join 👉
|
Re:Mind is a weekly newsletter exploring mental models and frameworks that help you think clearly and make better decisions. Each week, I share practical insights and tools that transform complex ideas into wisdom you can apply immediately. Join me in making better decisions, together.
Hello Reader, You're in a meeting. The proposal sounds terrible: vague timelines, unclear ROI, obvious blind spots. You wait for someone else to say it. Surely everyone sees this. The room nods. The decision passes. You leave confused. The truth isn't that everyone agreed. The truth is, you assumed they did, and that assumption kept you quiet. That's the False Consensus Effect. Your brain projects your beliefs, values, and behaviors onto others, then treats that projection as if it were...
Hello Reader, Your competitor launched three features last quarter. You're still debating org structure. They pivoted twice in six months. Your product roadmap has seventeen stakeholder sign-offs. You diagnose: "Our organization is too complex. We need to streamline. Simplify. Flatten the hierarchy." Wrong problem. Your organization isn't complex. The market is. And you're blaming the ant when you should be reading the beach. This is Simon's Law of Complexity—and it reveals why most...
Hello Reader, You're researching vendors for a major decision. You compare features, check reviews, and build a spreadsheet. Three months later, you discover a critical requirement you never thought to ask about (and it's going to cost you). The problem wasn't what you didn't know. It was what you didn't know you didn't know. That's the Rumsfeld Matrix, though most people remember the quote without grasping the framework. It's about recognizing that the most dangerous territory in any...