Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Framework guide
Jobs to be Done / Outcome-Driven Innovation Framework
Framework bundle for applying Jobs to be Done and Outcome-Driven Innovation without inventing customer research, job maps, outcomes, or opportunity scores.
Read the fileWorkflow
Jobs to be Done / Outcome-Driven Innovation Output Planning
Plan a Jobs to be Done / Outcome-Driven Innovation deliverable or recommendation with source-aware checks.
Read the fileWorkflow
Jobs to be Done / Outcome-Driven Innovation Evidence Review
Review Jobs to be Done / Outcome-Driven Innovation evidence before recommendation or publication.
Read the fileTemplate
Jobs to be Done / Outcome-Driven Innovation Brief
Decision-facing brief for Jobs to be Done / Outcome-Driven Innovation work.
Read the fileIs this bundle right for your task?
Who it is for
- Practitioners using Jobs to be Done / Outcome-Driven Innovation to structure analysis, decisions, facilitation, or review
- Teams working in software, digital-products, technology
When to use it
- A team needs to apply Jobs to be Done / Outcome-Driven Innovation to a concrete decision without skipping evidence, constraints, or stakeholder judgment.
- An existing analysis needs its assumptions, reasoning, affected parties, and review criteria checked.
What you need to provide
- The decision or question, available evidence, operating constraints, affected stakeholders, and desired outcome.
- Existing analysis, definitions, assumptions, examples, and review criteria that the framework must reconcile.
Tasks and expected outputs
Questions it helps answer
- Frame customer research around jobs and desired outcomes without inventing interviews or evidence.
- Separate JTBD/ODI source concepts from local market, segment, and customer evidence.
- Draft opportunity briefs that expose assumptions, missing research, outcome statements, and prioritization risks.
What it helps produce
- JTBD opportunity brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the decision or question, available evidence, operating constraints, affected stakeholders, and desired outcome. Ask the agent to apply Jobs to be Done / Outcome-Driven Innovation and produce JTBD opportunity brief that shows how evidence maps to the framework, where judgment is required, and what remains unresolved. Begin with Strategyn Jobs to be Done, then confirm that the reference is current and applicable. Inspect Jobs to be Done / Outcome-Driven Innovation Framework before drafting.
Context path: bundles/frameworks/jobs-to-be-done
What the bundle includes
Frameworks
- Jobs to be Done
- Outcome-Driven Innovation
- job map
- outcome statement review
Commands
/review-jtbd-opportunity
Evaluations
- Jobs to be Done / Outcome-Driven Innovation guidance quality check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Applying the framework mechanically when the decision requires missing evidence, stakeholder judgment, or qualified review.
Known limitations
- Not a complete Jobs to be Done / Outcome-Driven Innovation implementation, administration, legal, research, or professional-advice reference.
- Requires user-provided local evidence before final conclusions about Jobs to be Done / Outcome-Driven Innovation usage, readiness, scoring, configuration, or commitments.
- Does not replace qualified product, design, engineering, data, legal, privacy, security, or administrator review.
Safety notes
- Require confirmation before claiming customer needs, market opportunity, prioritization scores, or roadmap recommendations without verified research evidence.
- Do not claim access to private systems, customer data, workspaces, documents, dashboards, roadmaps, repositories, accounts, or source records unless the user provides evidence or authorized tool access.