There are more than a few different frameworks for Jobs to be Done (JTBD) out there. The aim of this documentation is to adapt those frameworks and create a shared understanding of a JTBD process which fits our needs here at GitLab.
Our goal is to make products that people want, as well as make people want our products. Using JTBD can help us do that.
Use JTBD throughout the design process, but most notably to:
A core strength of JTBD is its structure, which clearly separates out various aspects of achieving objectives. The who, what, how, why and when/where are analyzed individually, giving both precision and flexibility to JTBD methods.
The contextual factors that frame job execution. When and where does the job get done?
JTBD can be viewed at different levels, rather than just two levels—big and little. Jim Kalbach states that you can view JTBD at four different levels:
Follow this guidance.