Summary of Jobs-To-Be-Done and Customer Personas

## Introduction Understanding why customers choose a product or service is central to building successful solutions. This lesson explains the **Jobs-To-Be-Done (JTBD)** framework and shows how it helps you discover customers' true motivations so you can design better offerings and craft meaningful customer profiles. > **Definition:** Jobs-To-Be-Done (JTBD) is a framework that focuses on the real task, goal, or problem a customer “hires” a product or service to accomplish. ## Why JTBD matters Breaking apart customer choices into underlying jobs helps you: - Focus on the **problem** customers want solved rather than on features alone. - Design products that fit into customers’ real lives and workflows. - Reduce the risk of building solutions that sound good but don’t get used. Did you know that Clayton Christensen found that roughly 75–85% of new products fail financially because they do not target a job customers are trying to get done? ## Core JTBD concepts ### The central idea - Customers don’t buy products; they “hire” them to complete a job. - A job is stable over time; solutions that successfully accomplish that job can change and evolve. > **Definition:** A “job” is the progress a customer seeks in a particular circumstance — practical, emotional, or social. ### Types of jobs Use these three lenses to map customer needs: | Job type | What it answers | Example (smartphone) | |---|---:|---| | Functional | What task must be done? | Make calls, navigate, take photos | | Emotional | How must the customer feel? | Feel secure, confident, or relaxed using the phone | | Social | How does the purchase affect social perception? | Appear trendy, professional, or tech-savvy | ### How JTBD informs decisions - Product design: prioritize features that directly accomplish the job. - Positioning: highlight how your product gets the job done better than alternatives. - Metrics: measure success by effectiveness at completing the job, not only by usage counts. ## Building JTBD-based insights (step-by-step) 1. Select a primary customer segment to study. 2. Observe or interview real people in context: ask what they were trying to accomplish, alternatives they considered, and what disappointed them. 3. Translate observations into job statements using the three job types. 4. Prioritise jobs by frequency, urgency, and willingness to pay. 5. Iterate product concepts to better satisfy the highest-priority jobs. > **Definition:** A job statement is a concise sentence describing the customer’s goal in context, e.g., “When I travel for work, I want to charge my phone quickly so I can stay connected and feel reassured.” ## Example: JTBD for a commuter - Functional job: Get from home to work reliably and on time. - Emotional job: Feel calm and in control during the commute. - Social job: Appear productive and professional to colleagues. From these jobs you might design features like real-time traffic alerts (functional), calming in-app audio or simplified UX (emotional), and seamless calendar integration (social/productivity signaling). Fun fact: Tony Ulwick developed outcome-driven innovation, a formal method for turning JTBD insights into product requirements and measurable outcomes. ## Using JTBD to create initial customer profiles Note: This section focuses on JTBD-driven profile content and avoids duplication of material covered elsewhere. 1. Gather demographic and psychographic cues only to the extent they clarify context for the job (e.g., commute length, tech comfort level, values related to status). 2. Anchor the profile with concrete job statements (functional, emotional, social). 3. Add preferred solutions and common frustrations linked to each job. 4. Use these profiles in ideation, prototyping, and messaging to ensure alignment with the jobs. > **Definition:** A JTBD-anchored profile centers a real, contextual job and lists measurable outcomes the customer seeks rather than merely demographic labels. ## Pra