# Jobs-to-be-Done Positioning: A Research-First Framework > Use jobs-to-be-done to position a product from real customer research. Turn the job a customer hires you for into a positioning angle. By Yasmeen Turayhi — July 9, 2026 Read time: 4 min Section: Positioning from research Topics: jobs to be done positioning, JTBD framework, product positioning framework URL: https://perspiva.com/spaces/jobs-to-be-done-positioning-framework --- To position a product with jobs-to-be-done, name the job the customer hires you for, then position the product as the best way to get that job done in their situation. Find the job in customer interviews. The trigger, the struggle, and the alternatives they weighed become your positioning angle. ## Start with the job, not the feature Most founders position around what the product does. The customer does not buy what it does. They buy the progress it makes possible. Jobs-to-be-done reframes the question. People buy products and services to get a job done, and a job is the task, goal, or objective a customer is trying to accomplish in a given situation (Strategyn). The job is stable. Products change; the underlying job endures. That stability is why the job makes a strong positioning anchor. Feature lists date quickly. The job a customer is hiring you for holds. Position against the job and your message survives the next release. ## The job defines the frame Positioning is a decision about context. Who is this for, against what alternative, for what outcome. The job answers all three. Consider the customer who “hires” a product. They had a trigger. They struggled with something. They weighed alternatives, including doing nothing. Those alternatives are your real competitive set, not the vendors you list on a slide. The job reveals the frame the customer already uses. This is where jobs-to-be-done and positioning meet. If you have read positioning vs. messaging, you know positioning comes first and messaging follows. The job sits underneath both. It tells you what to claim before you decide how to say it. ## Find the job in the interview You cannot invent the job. You find it in how customers describe the moment they went looking. Run interviews around the last time they searched for a solution. Ask what happened right before. Ask what they tried first. Ask what almost stopped them from switching. The functional job, the situation, and the desired outcome surface in that story. Ulwick’s outcome-driven work makes this concrete: customers measure success against specific outcomes they are attempting to achieve while getting the job done (Wikipedia). Listen for the outcome in their words. “I need to look credible to a board I have not met.” “I need the migration done before the quarter closes.” Those are jobs. They carry a situation and a measure of success. Our guide on turning customer interviews into a positioning statement covers the interview mechanics in depth. ## From job interviews to a positioning angle The move from raw interviews to a claim follows a repeatable path. Work it in order. Step, question you answer, output: - 1. Trigger — What situation sent them looking — The context your positioning must name - 2. Job statement — What outcome are they trying to reach — A stable, solution-free job - 3. Alternatives — What did they weigh, including nothing — The true competitive frame - 4. Struggle — Where do current options fail the job — The gap you claim - 5. Angle — Why are you the best way to get this job done — The positioning statement Each step feeds the next. The trigger sets the scene. The job statement stays free of your product, so it does not bias the frame. The alternatives tell you who you are really beating. The struggle names the unmet need. The angle is what falls out when the first four align. A desired outcome statement, in Ulwick’s construction, is devoid of solutions, stable over time, and measurable (Strategyn). Hold your job statement to the same standard. If your product name appears inside it, you have written a use case, not a job. ## Turn the job into a claim The angle from step five is not the finished statement. It is the raw material. A positioning statement built on a job reads differently from one built on features. It names the situation, the job, and why you are the best fit for that job against the alternative the customer actually considered. The claim earns its authority from the interview, not from the roadmap. For the full construction, see how to write a positioning statement from customer research. One caution. A single interview is a story, not a pattern. You are looking for the job that recurs across the people you want to win. When the same trigger and the same struggle appear again and again, you have found the job worth positioning on. When they scatter, you have found segments, and each may need its own angle. ## Where synthesis does the work The hard part is not gathering the stories. It is turning many stories into one direction. Read twelve interview transcripts and the jobs blur. One person’s words are vivid; the pattern across all of them is what you position on. This is a synthesis problem, and synthesis is where most teams stall. They have the interviews and no direction. This is the layer Perspiva sits in. You describe the decision; it designs the research, gathers responses by text, voice, or video, and returns a Customer Intelligence Report with the recurring jobs, the competitive frame, and a positioning angle drawn from what customers actually said. You do not get raw transcripts. You get direction. ## Keep the job at the center Jobs-to-be-done is not a research method you run once and file. It is the discipline of positioning against progress instead of features. The founders who hold this get sharper over time. Every new interview refines the job. Every refinement tightens the claim. The competition keeps launching features. You keep owning the job the customer came to get done. That is the position that lasts. ## FAQ Q: What is jobs-to-be-done in positioning? A: Jobs-to-be-done frames positioning around the progress a customer is trying to make, not your feature list. You position the product as the best way to get that job done in a specific situation. Q: Is a job the same as a use case? A: No. A use case describes how someone uses a feature. A job describes the outcome they want and the situation that triggered the search. The job is stable; use cases change with the product. Q: How many interviews do you need to find the job? A: Patterns usually surface within eight to twelve focused interviews. You are listening for the trigger, the struggle, and the alternatives considered, not counting responses. Q: Does JTBD replace a competitive frame in positioning? A: No. The job defines what the customer is trying to accomplish. The competitive frame defines what they compared you against. You need both to write a sharp positioning statement. ## Sources - Jobs-to-be-Done: The Original Framework (Strategyn / Tony Ulwick): https://strategyn.com/jobs-to-be-done/ - Outcome-Driven Innovation (Wikipedia): https://en.wikipedia.org/wiki/Outcome-Driven_Innovation — Perspiva. Where customer research becomes strategy.