Jobs-to-be-Done Framework

Understands the JTBD framework (Clayton Christensen): People hire products to do jobs. Distinguishes between functional, emotional, and social jobs. Can formulate job stories.

Understands the Jobs-to-be-Done concept and its difference from persona-based approach. Knows how to apply JTBD framework for technical products and developer tools. Can formulate job statements for basic user tasks.

Conducts JTBD interviews, creates job maps. Uses JTBD for feature prioritization (outcome-driven innovation). Builds an opportunity landscape based on unmet needs.

Independently conducts JTBD research for technical users: developers, DevOps, architects. Formulates job maps with functional, emotional and social dimensions. Identifies unmet needs in developer experience.

Applies JTBD as a strategic tool for product discovery. Combines with Opportunity Solution Trees. Defines product positioning based on job differentiation.

Builds JTBD-driven product strategy for a technical platform. Conducts switch interviews with technical users. Defines competitive landscape through lens of jobs. Links JTBD with architecture decisions.

Implements the JTBD approach across the product division. Trains PMs on conducting JTBD interviews. Uses JTBD for strategic product portfolio decisions.

Defines JTBD framework for the product division. Introduces outcome-driven innovation approach for portfolio-level decisions. Trains TPMs on JTBD interviews with technical users.

Identifies market opportunities through a JTBD lens at the company level. Shapes innovation strategy based on unmet jobs. Influences corporate strategy through jobs-based analysis.

Shapes enterprise JTBD practice for the organization. Defines cross-product job maps for complex technical workflows. Integrates JTBD into strategic roadmap and investment decisions at portfolio level.