A persona is a research-grounded archetype of a user segment that summarizes goals, behaviors, context, and frustrations to help teams empathize and design consistently. A persona differs from a segment in that a segment is a real group in the data, defined by shared attributes, whereas a persona is a narrative composite built from real segment members to make that group memorable and actionable. A proto-persona is a draft persona built from team assumptions and used to guide early research and align vocabulary; it becomes a research-backed persona once validated against real interview and behavioral data. A useful way to capture what a customer is trying to accomplish is the Jobs-to-Be-Done job statement, a short framing such as "When I [situation], I want to [motivation/progress], so I can [expected outcome]" that names the progress the customer was trying to make.
JTBD analysis distinguishes three layers. Functional jobs are the concrete tasks to accomplish; emotional jobs are how the customer wants to feel; and social jobs are how they want to be perceived by others. A jobs diagram visually breaks down the main job, related sub-jobs, emotional and functional dimensions, and context, used to scope a JTBD study and find the most underserved sub-jobs. The famous "milkshake moment" illustrates how situational the job can be: a fast-food chain discovered its morning milkshake sales were driven not by hunger but by commuters wanting a single-handed, long-lasting, legal-to-eat-in-the-car option. Switching behavior can be analyzed with the push, pull, anxiety, and habit model: push forces customers away from the current solution, pull attracts them to a new one, anxiety creates hesitation, and habit keeps them on the old path. A forces diagram is a four-quadrant visual of these forces applied to a specific switching moment. The outcome-driven innovation (ODI) approach, developed by Strategyn, defines customers by the outcomes they are trying to achieve and the constraints they face, then surveys them to find underserved outcomes that predict purchase intent.
Researchers also distinguish needs, wants, and demands. Needs are underlying human or job requirements; wants are culturally and personally shaped expressions of those needs; and demands are wants backed by purchasing power and intent. A pain point is a specific friction, cost, or risk that blocks an outcome, while a need is the underlying job or outcome itself — pain points imply needs, but needs do not require pain. An unmet need is one that current solutions, including workarounds, do not adequately address, usually revealed when customers report inventing their own tools or processes. A "hair on fire" customer is a segment whose current problem is so urgent and costly that they actively seek out and pay for solutions, the strongest signal of a real market opportunity. The Kano model categorizes features by customer satisfaction impact: basic or "must-be" quality (customers expect by default and are dissatisfied without it), performance quality (more is better), and delighters or "attractive" quality (unexpected positives). A value proposition canvas pairs a customer's jobs, pains, and gains with the product's pain relievers and gain creators to test fit between an offering and a researched segment.
Customer journeys and blueprints add spatial structure. A customer journey map is a visual representation of the steps, touchpoints, emotions, and goals a customer experiences while trying to accomplish a goal with a product, service, or workaround. A touchpoint is a specific moment of interaction between a customer and a product, brand, support agent, or channel during that journey. A "moment of truth" is a specific touchpoint where the customer forms or updates their opinion of the brand, often disproportionately influencing satisfaction, conversion, or churn (such as first use, a support call, or renewal). A service blueprint maps the visible customer journey alongside the behind-the-scenes processes, systems, and actors required to deliver each step, exposing handoffs that often cause friction. To prioritize insights, researchers often use a frequency versus intensity framework: frequency asks how many customers experience something, intensity asks how severely it affects them, and the most actionable insights tend to be high on both axes.