Augment

Jobs To Be Done for Product Teams: A Practical Guide

People do not buy products. They hire them to make progress. Framing work this way changes what you build and how you describe it.

Hands sketching a UX flow on a whiteboard during a design workshop
Photo by Kaleidico on Unsplash, with an Augment halftone treatment
Executive Summary

Key Takeaways

  • A job is the progress a person wants to make in a given situation.
  • Focus on the situation and the desired outcome, not on demographics.
  • Interview people who recently switched or chose a solution to find the real triggers.
  • Use jobs to prioritize features, shape messaging, and spot competitors outside your category.

The idea

Jobs to Be Done is a way of understanding why people choose products. The Christensen Institute describes it as the progress a person is trying to make in a particular circumstance. The product is "hired" to help with that progress.

Two people with the same age and job title may want entirely different things. Two very different people may be trying to do the same job. Looking at the job removes the guesswork.

A job statement

Template

“When [situation], I want to [motivation], so I can [outcome].”

Example: "When I join a new team and need to share designs, I want everyone to see the latest version, so I can avoid rework." The statement is about the situation and the outcome, not about a feature.

How to find jobs

  • Interview recent customers about the moment they decided to switch or sign up.
  • Ask what they used before, what was frustrating, and what finally made them act.
  • Listen for forces: what pushed them away from the old way and what held them back from the new one.
  • Look for patterns in their circumstances, not in their profiles.

Using jobs in practice

UseHow jobs help
PrioritizationRank features by how well they help the main job
MessagingDescribe the progress users get, not the feature list
CompetitionInclude anything people use for this job, including spreadsheets and manual work
OnboardingGuide users toward the first moment of progress

Keep it practical

You do not need a formal program. Start by writing down the top three jobs your product serves, and check each against a few customer conversations. Use them in planning meetings as a quick test: which job does this serve?

Frequently Asked Questions

A framework that explains why people choose a product: they hire it to make progress in a specific situation.

Sources and further reading

  1. Jobs to Be DoneChristensen Institute · Undated page · Accessed
  2. User Interviews 101Nielsen Norman Group · Published · Updated · Accessed

Credits

  • Written by Augment Editorial Team, Product design and engineering, Augment Lab.
  • Cover photo Photo by Kaleidico on Unsplash, with an Augment halftone treatment, used under the Unsplash License.
  • Research Statistics and standards are cited from the sources above. Always check the original page for the latest version.

Augment Product Design

Ready to make your product clearer?

From first concept to go-live, we turn complex product ideas into clear, useful experiences.

Jobs To Be Done for Product Teams: A Practical Guide | Augment. Lab