Jobs to Be Done
This page contains an interactive diagram exploring the Jobs to Be Done framework. Enable JavaScript to view the interactive version with pan, zoom, and clickable source links.
Source: Wikipedia — Outcome-Driven Innovation
Functional Jobs
The practical tasks people need to accomplish.
Emotional Jobs
How people want to feel or avoid feeling.
- Personal Dimension — How the customer wants to feel: confidence, peace of mind, joy
- Social Dimension — How the customer wants to be perceived: status, identity, belonging
Job Statement Template
(action verb) + (object) + (context)
Examples
- Spotify — Help me find the right music for my mood while commuting
- Uber— Get me to my destination reliably when I can't drive
- Duolingo — Help me learn a language in short daily sessions
Agile — Product Development Wheel
Source: Wikipedia — Agile Software Development
A 7-stage cycle for iterative product development: Plan, Design, Build, Test, Review, Launch, Analyze.
- Plan — Choose what's worth building next so the team stops spreading effort across problems that don't matter (Shape Up: Appetite & Betting Table · Scrum: Sprint Planning · Agile: Adaptive Planning)
- Design — Sketch the solution at the right altitude so the team sees where they're headed without being handed every step (Shape Up: Shaping · Scrum: Refinement · Agile: Emergent Design)
- Build — Let the team solve the problem their way without scope creeping in mid-flight (Shape Up: 6-Week Cycle · Scrum: Sprint Execution · Agile: Iterative Development)
- Test — Catch the gap between what we built and what the customer actually struggles with (Shape Up: Integrated in Building · Scrum: Definition of Done · Agile: TDD & Continuous Testing)
- Review — Face whether the work moved the needle instead of just celebrating that it shipped (Shape Up: Circuit Breaker Evaluation · Scrum: Sprint Review · Agile: Demo & Inspect)
- Launch — Get the work into customers' hands so it stops being theoretical (Shape Up: Ship at Cycle End · Scrum: Potentially Releasable Increment · Agile: Continuous Delivery)
- Analyze — Name what's not working so the team stops repeating the same painful cycle (Shape Up: Cool-Down & Next Shaping · Scrum: Sprint Retrospective · Agile: Retrospective & Kaizen)
Agentic Software Development Lifecycle
Source: Wikipedia — AI-assisted Software Development
A single Team Member — focused on helping customers get their jobs done — delegates across three agent teams (Product, Design, Engineering), each running slash-command skills that cover all 7 product wheel phases.
Agents
- Product Agent — Plan, Review, Analyze
- Design Agent — Design, Review
- Engineering Agent — Build, Test, Launch
Skills
/your-brand-plan — Define what to build next/your-brand-design — Shape the solution/your-brand-build — Implement the solution/your-brand-test — Verify correctness/your-brand-review — Evaluate the outcome/your-brand-launch — Ship to customers/your-brand-analyze — Measure and learn
Tools
- speckit — Spec authoring skills
- GitHub CLI — gh pr, gh issue, gh release
- Vercel CLI — vercel deploy, vercel env
- Supabase — Database, auth, storage via MCP
- Google Analytics — Page views, funnels, events
- Microsoft Clarity — Session replays, heatmaps