# Jobs to Be Done — Theory to Practice ## PROMPT 0 — Retrieval, provenance, and evidence boundary ### Source record The local EPUB identifies Anthony W. Ulwick as author, Alex Osterwalder as foreword writer, Idea Bite Press as publisher, and 2016 as publication year. Its metadata provides ASIN B01M73AP2I; the author’s [publications page](https://anthonyulwick.com/publications/) confirms the October 2016 Idea Bite Press edition. The EPUB archive passes integrity testing. The complete local source includes the foreword, introduction, chapters 1–9, six case studies, glossary, historical timeline, resources, and author material. It contains no reader-selected highlights. I use chapter anchors `ODI-INTRO`, `ODI-C01` through `ODI-C09`, and `ODI-GLOSS` as Layer 1 anchors. The book claims that ODI has an 86% innovation success rate, five times an industry average. Its website continues to present the same figure ([Strategyn](https://strategyn.com/jobs-to-be-done/)). The source describes an “independent” study, but does not include its full design, sample frame, client-selection rule, outcome definition, raw data, conflicts review, or a replication. Treat the percentage as an author/company claim, not a settled empirical estimate. ### Source hierarchy | Layer | Supplies | Limit | | --- | --- | --- | | L1 | Ulwick’s theory, ODI workflow, case narratives, definitions, and success-rate claim | Author and company have commercial interest in ODI | | L2 | Official author and Strategyn pages | Confirms current self-description, not independent validity | | L3 | Applied research using ODI-style outcomes, such as a [hotel-service study](https://www.mdpi.com/2071-1050/13/1/391) | Shows possible use, not universal causal success | | L4 | Vault synthesis and safeguards | Review inference, not Ulwick’s claim | ### Connection contract This review completes a JTBD methods cluster with [[4. Archives/Book reviews/The Jobs to Be Done Playbook]] and [[4. Archives/Book reviews/The Jobs-to-be-Done Pyramid]]. It also connects to [[3. Resources/MOCs/DevRel MOC]], [[4. Archives/Book reviews/On Value Creation in Developer Relations (DevRel) - A Practitioners' Perspective]], [[3. Resources/Permanent Notes/A Metric Is Vanity Only Against Your Own Outcome Data]], [[3. Resources/Permanent Notes/A Feedback Signal Not More Automation Is What Makes a System Self-Improving]], and [[3. Resources/Literature Notes/Making Data-Driven Product Decisions]]. Ulwick offers the most formal path for turning discovery into prioritization. Use that path only when the decision warrants the research cost and when the team can document the instrument, sampling, analysis, uncertainty, and participant protections. ## PROMPT 1 — Reading contract, priors, and open questions > [!warning] Inferred inputs > No personal purpose was supplied. I infer a professional, syntopical purpose: decide which elements of the ODI method can responsibly inform product and DevRel research in this vault. Change this if your purpose differs. ### Reading contract - **Purpose:** test Ulwick’s needs-first innovation method against the practical method in Kalbach and the motivational taxonomy in Burleson. - **Intended use:** scope research before a major product or ecosystem decision; avoid idea-first workshops that lack a participant evidence trail. - **Success criteria:** preserve the six customer-input types, job maps, desired-outcome syntax, segmentation logic, and explicit rigor requirements; downgrade broad performance claims. - **Evidence that would change the view:** an independently reproducible study with defined ODI sample, comparison group, success measure, attrition record, and confidence intervals. - **What the book cannot establish:** that an 86% success rate will transfer to a specific team, that a high score causes adoption, or that customer needs override public-interest, labor, accessibility, or safety constraints. - **Constraints:** no reader highlights, no source dataset, no access to client research, and no requested changes to existing MOCs. ### Open questions 1. What does “success” mean in the 86% claim: launch, revenue, adoption, margin, duration, or client judgment? 2. How were ODI engagements selected, excluded, and compared with traditional innovation? 3. Does Ulwick’s desired-outcome syntax improve reliability between researchers? 4. When does a functional core job become too narrow for a multi-actor system? 5. Can quantitative opportunity scores preserve the uncertainty of qualitative discovery? 6. How do price, regulation, access, trust, distribution, and power shape adoption beyond unmet needs? 7. What counts as an independent market segment rather than a cluster artifact? 8. When are customer preferences constrained by structural injustice rather than freely chosen? 9. How should an ODI project include maintenance workers, caregivers, administrators, and other affected people? 10. What prevents a needs-first method from becoming an extraction process? 11. Does “better and/or cheaper” capture accessibility, repairability, privacy, ecological cost, or dignity? 12. Can a team run a lighter method without reproducing the false precision Ulwick criticizes? 13. How does a competitive analysis distinguish direct solution alternatives from non-consumption or workarounds? 14. How can DevRel use job and outcome data without turning community participation into market research by default? 15. What outcome would tell a team to stop an investment rather than optimize it? 16. How can AI-assisted clustering preserve raw evidence and enable challenge? ### Prior seeds | Claim | Prior | Reason | Evidence needed | | --- | ---: | --- | --- | | Needs-first research can reduce feature-first bias | Moderate-high | Plausible mechanism | Decision comparison and traceable research | | Desired outcomes can be measured | Moderate | Depends on wording and instrument validity | Cognitive testing and reliability data | | Importance/satisfaction data can prioritize opportunities | Moderate | Useful framework with measurement constraints | Sampling, analysis, and predictive validation | | ODI has an 86% success rate | Low | Claim lacks inspectable independent detail here | Full study and replication | | Functional jobs remain stable across technologies | Moderate-high | Often plausible, not universal | Longitudinal/context analysis | | Innovation success is explained chiefly by unmet needs | Low-moderate | Many market and institutional causes exist | Comparative causal evidence | | A common language can improve decisions | Moderate | Shared categories can help or constrain | Decision-quality and dissent evidence | ### Drift assumptions The book’s 2016 claims are fixed. Applied conditions drift: AI-supported research, privacy regulation, product-market structures, accessibility standards, price and distribution conditions, and Strategyn’s own current claims. Reassess use of opportunity scores annually and before any high-stakes decision. ## PROMPT 2 — Inspectional map and central project ### Book map | Unit | Contribution | Anchor | | --- | --- | --- | | Foreword + introduction | Frames innovation failure and ODI’s origin story | ODI-FORE; ODI-INTRO | | 1. Why projects fail | Argues that teams lack a shared definition of need | ODI-C01 | | 2. Needs framework | Defines six categories of customer inputs | ODI-C02 | | 3. Growth strategy matrix | Connects under/overserved markets to five strategies | ODI-C03 | | 4. ODI process | Lays out a ten-part research-to-strategy workflow | ODI-C04 | | 5. Case studies | Microsoft, Kroll Ontrack, Arm & Hammer, Bosch, Abbott, Hussmann | ODI-C05 | | 6. Becoming a practitioner | States 84 execution steps and skill requirements | ODI-C06 | | 7. Transforming organization | Three phases for an outcome-driven organization | ODI-C07 | | 8. Language | Defines vocabulary and formulas | ODI-C08; ODI-GLOSS | | 9. Learn more | Historical timeline and resources | ODI-C09 | ### Central project Ulwick argues that innovation fails because organizations lack an agreed definition and measurement of customer need. His answer is Jobs-to-be-Done Theory plus Outcome-Driven Innovation: define a core functional job; capture desired outcomes as customer-defined metrics; measure importance and satisfaction; identify underserved and overserved outcomes; segment the market by outcome patterns; then use the result to form market, product, and growth strategy. This is a practitioner and consulting-method book. Its modes are explain, persuade, teach, and sell a formal approach. Its intended audience is leaders, product and innovation teams, researchers, strategists, and consultants who can fund substantial qualitative and quantitative research. A **full analytical read plus syntopical comparison** is justified because this source is the most prescriptive and quantitatively ambitious book in the cluster. ### Provisional summary Jobs to Be Done: Theory to Practice presents ODI as a needs-first innovation process. Ulwick divides customer inputs into core functional jobs, desired outcomes, related jobs, emotional and social jobs, consumption-chain jobs, and financial desired outcomes. He insists that desired outcomes state the metrics people use to judge successful job execution. ODI then proceeds through customer selection, core-job definition, qualitative discovery, job mapping, desired-outcome wording, quantitative opportunity analysis, segmentation, value proposition, competitive analysis, innovation strategy, and market/product strategy. The book’s Growth Strategy Matrix names differentiated, dominant, disruptive, discrete, and sustaining strategies based on whether a job is served better or cheaper. Case studies and an 84-step practitioner workflow show how the author believes this produces more predictable innovation. The method’s conceptual discipline is stronger than its public evidence for the claimed success rate, which remains insufficiently documented in the source. ## PROMPT 3 — Classification and terminology controls ### Classification This is a proprietary, needs-first innovation method drawn from quality management, market research, segmentation, and JTBD. It treats innovation as a process that can be measured and controlled. It is neither an independent evaluation of ODI nor a general theory that subsumes ethics, public value, or organizational power. ### Controlled vocabulary | Term | Author’s use | Operational use here | Confusion risk | Anchor | | --- | --- | --- | --- | --- | | Core functional job | Fundamental goal an end user seeks in a situation | Scope anchor for a research study | Treating a feature or company task as the job | C02; GLOSS | | Desired outcome | Metric used to judge successful job execution | Participant-centered condition to investigate | Calling an untested feature request an outcome | C02; C04 | | Related job | Functional job performed alongside the core job | Adjacent objective with possible trade-offs | Adding every related goal to scope | C02 | | Emotional/social job | Desired feeling or perception while doing a core job | Participant-described experiential/social condition | Inferring identity or emotion from data traces | C02 | | Consumption-chain job | Installation, maintenance, disposal, and support work | Job performed around product lifecycle | Treating buyer journey as core job | C02; GLOSS | | Financial outcome | Buyer’s cost/revenue-related evaluation metric | Separate purchase decision criterion | Equating buyer economics with end-user benefit | C02 | | Opportunity | Important/poorly satisfied or unimportant/well-satisfied outcome | Hypothesis requiring valid measurement | Treating formula output as truth | C04; GLOSS | | Outcome-Based Segmentation | Groups defined by unmet desired outcomes | Segmentation method to audit for stability and harm | Reifying clusters as natural populations | C04; GLOSS | | ODI | Qualitative, quantitative, and strategy process | High-rigor method with implementation dependence | Calling a workshop ODI | C04; C06 | | Needs-first innovation | Find unmet needs, then devise ideas | Evidence-before-solution workflow | Delaying harmless prototyping when evidence is adequate | C01; GLOSS | | Idea-first innovation | Ideas first, then preference evaluation | A method Ulwick criticizes | Assuming all ideation is uninformed | GLOSS | | Growth Strategy Matrix | Five strategy types based on better/cheaper job completion | A strategic hypothesis map | Treating categories as exhaustive | C03 | ### Category-error watchlist | Error | Status | Control | | --- | --- | --- | | Needs metric = complete human need | Present | State scope and preserve qualitative context | | Score = causal market prediction | Present | Validate prospectively and publish uncertainty | | Segment = natural identity group | Present | Use as provisional pattern, not a person type | | Customer value = public value | Present | Add affected people, accessibility, safety, and ecological review | | Better/cheaper = equitable or accessible | Present | Test distribution of access and burden | | Consulting case = independent evidence | Present | Treat all company stories as dependent source family | | Absence of an unmet outcome = absence of harm | Present | Run a separate risk and equity assessment | ## PROMPT 4 — Claims, evidence, and dependencies ### Claim inventory | ID | Claim | Type | Label | Expected evidence | Falsifier | Anchor | | --- | --- | --- | --- | --- | --- | | C-001 | Innovation fails partly because teams lack a shared definition of need. | Causal | EA | Comparative organizational research | Teams align on needs yet fail for unrelated causes | C01 | | C-002 | Customer needs can be organized into six categories. | Methodological | EA | Coding reliability and decision usefulness | Categories fail to code cases or guide decisions | C02 | | C-003 | Desired outcomes are metrics for successful job execution. | Definitional | EA | Participant language and outcome-item testing | Outcomes cannot be tied to job success | C02 | | C-004 | Needs-first research reduces idea-first innovation error. | Causal | EA | Comparative prospective studies | Idea-first method performs equally/well after controls | C01; C04 | | C-005 | Importance and satisfaction scores identify under- and overserved outcomes. | Methodological | EA | Valid instrument, sample, analysis, prediction | Scores do not predict unmet need or choice | C04; GLOSS | | C-006 | Outcome-based segments produce better opportunities than demographic segments. | Causal | EA | Segment stability, size, and response tests | No advantage over alternatives | C04 | | C-007 | Growth strategy type follows whether a job is done better and/or cheaper. | Strategic | EA | Market comparisons and boundary cases | Strategy succeeds without predicted conditions | C03 | | C-008 | ODI’s ten-part process makes innovation more predictable. | Causal | EA | Independent comparative implementation study | Comparable teams see no predictive gain | C04 | | C-009 | ODI has an 86% success rate, five times the average. | Quantitative causal | EA | Full independent track-record study | Missing/biased sample or nonreplication | Intro; C04; GLOSS | | C-010 | An 84-step practitioner process is required for reliable ODI execution. | Methodological | EA | Fidelity/outcome comparison | Reduced process delivers equal valid results | C06 | | C-011 | Common innovation language can transform organizational decisions. | Organizational | EA | Longitudinal decision and culture evidence | Language adoption without decision change | C07–C08 | | C-012 | Case studies show ODI in use across industries. | Descriptive | EA | Case documentation | Cases do not follow described process | C05 | | C-013 | Needs-first research should include access, safety, power, and affected people. | Ethical/practical | RI | Stakeholder and impact evidence | Job-executor-only study captures material effects | Review inference | | C-014 | ODI scores should not determine a DevRel or community decision without consent and an appeals path. | Ethical/practical | RI | Governance and participant feedback | A coercive or opaque process is needed for validity | Review inference | | C-015 | A null outcome or weak market signal should be retained as evidence against investment. | Practical | RI | Decision log and review | Removing nulls improves decision accuracy | Review inference | EA means explicit author claim. RI means review inference; it is not Ulwick’s sentence. C-009 is the book’s central empirical promise and faces the highest verification bar. ### Dependency graph ```mermaid flowchart TD A["Core functional job C-003"] --> B["Job map and desired outcomes C-002 to C-005"] C["Recruitment and qualitative research"] --> B B --> D["Quantitative opportunity and segmentation C-005 to C-006"] D --> E["Growth strategy and value proposition C-007"] E --> F["Innovation and market decisions C-008"] G["Implementation fidelity C-010"] --> F H["Consent, access, power, null findings C-013 to C-015"] -.-> C H -.-> D H -.-> E ``` The load-bearing link is B → D: if desired outcomes are not validly elicited and measured, segmentation, strategy selection, and the success-rate claim lose their basis. C-009 can fail while C-002–C-005 remain useful research discipline. ## PROMPT 5 — Quantitative rigor policy Ulwick explicitly asks readers to quantify desired outcomes. That makes this the right book for a full calibration policy, not a ceremonial numeric table. | Band | Structured judgment | | --- | --- | | Very low | 0–20% | | Low | 21–40% | | Uncertain | 41–60% | | Moderate | 61–75% | | High | 76–90% | | Claim | Prior | Evidence in source | Posterior | Why | | --- | ---: | --- | ---: | --- | | C-002 | 65% | Coherent taxonomy and extensive practitioner use | 70% | Useful, though no coding reliability shown | | C-004 | 65% | Logical argument and cases | 68% | Modest update; comparison evidence absent | | C-005 | 55% | ODI method description | 60% | Needs full instrument and validation | | C-006 | 50% | Author cases and claimed studies | 55% | No independent segment comparison in source | | C-008 | 50% | Process claim plus case narratives | 55% | Implementation and context likely matter greatly | | C-009 | 20% | Author-described independent study and company claim | 28% | Design and data unavailable; source dependence dominates | | C-010 | 55% | Practitioner fidelity argument | 60% | Plausible; reduced-form evidence absent | These are judgment encodings, not measured probabilities. The principal constraint is dependence: author narrative, Strategyn cases, corporate testimonials, and current company pages are linked sources rather than independent confirmations. ### Calibration warnings - **Success definition:** high severity. A launch, revenue threshold, adoption rate, and client satisfaction are different outcomes. - **Selection bias:** high severity. Consulting engagements may be better funded, more committed, or selectively reported. - **Survivorship bias:** high severity. A track record must list failures, partial successes, and discontinued work. - **Denominator opacity:** high severity. We do not know all eligible engagements or the comparison population. - **Metric validity:** high severity. Importance and satisfaction wording can reshape responses. - **False precision:** high severity. An opportunity formula does not remove judgment from data collection or strategic choice. - **Confounding:** high severity. Team quality, timing, distribution, price, regulation, and product execution can drive results. ## PROMPT 6 — Analytical scaffold ### Argument spine 1. Innovation failure stems from a poorly specified “need.” 2. Jobs Theory organizes customer inputs around a core functional job. 3. Desired outcomes translate successful job execution into measurable criteria. 4. ODI uses qualitative discovery, job maps, quantitative scoring, and segmentation to find opportunities. 5. Strategy matrices and competitive analysis turn opportunity data into investments. 6. Organizations need trained practitioners, common language, and phased transformation to sustain the method. ### Evidence ledger | Evidence family | Claim support | Independence | Limit | | --- | --- | --- | --- | | Ulwick’s IBM/Cordis narrative | Method origin and possible mechanism | Low | Retrospective self-report, no counterfactual | | Strategyn client case studies | Cross-industry application | Low | Provider-selected success cases | | Author-described track-record study | 86% rate | Low-medium | Full protocol and dataset absent | | Outcome syntax and process definitions | Reproducible method language | Moderate | Still needs reliability/validity test | | External ODI applications | Possible contextual use | Medium | Different methods and sectors, not replication | ### Weakest link and repair The weakest link is the 86% claim. Repair requires preregistered or fully transparent retrospective evaluation: defined eligible projects; fixed success criteria; all outcomes; independent assessors; a comparable non-ODI group; adjustment for project type and resources; and uncertainty intervals. Without it, retain the number only as an ODI/Strategyn claim. ### Prompt 7 entry criteria Evaluate only after separating method definitions, case descriptions, performance claims, author/company claims, and review inferences. Any applied project needs a sample plan, outcome-item review, privacy plan, accessibility check, decision rule, and null-result record. ## PROMPT 7 — Fair criticism and updated judgments ### Strongest reconstruction Ulwick’s valuable argument is narrower than the marketing claim: innovation teams often move from a technology or idea to a product decision without sufficiently defining how participants judge successful progress. A fixed grammar for core job, process, desired outcomes, related jobs, consumption support, and buyer economics can discipline research and make a later quantitative study possible. The method’s insistence on separating discovery from idea selection is an important corrective to feature-first planning. ### Evaluation summary | Claims | Grade | Current conclusion | | --- | --- | --- | | C-002–C-003 | B | Strong analytical vocabulary for research and synthesis | | C-004 | B/C | Useful direction, but not an exclusive path to good innovation | | C-005–C-006 | C | Plausible methodology needing open instruments and comparative validation | | C-007 | C | Strategic categories organize questions; markets may exceed the matrix | | C-008 | C | Structured process may help; claimed predictability remains unproven | | C-009 | D | Credible enough to investigate, insufficiently documented to accept | | C-010 | B/C | Fidelity matters for formal ODI; smaller scopes may need different methods | | C-011–C-012 | C | Possible organizational benefit and documented case use, not universal effect | | C-013–C-015 | B/N/A | Necessary review safeguards, not author claims | ### Counter-observations and repairs Ulwick acknowledges that ODI requires substantial qualitative and quantitative work and devotes an entire chapter to practitioner skill. That concession supports the claim that a team should not call a short workshop “ODI.” His explicit syntax and outcome framing also make the method more inspectable than vague calls to “empathy.” Repairs: - Replace “ODI makes innovation predictable” with “ODI creates explicit hypotheses and evidence requirements for innovation choices.” - Replace “86% success rate” with “Strategyn reports an 86% client track record; the public materials reviewed here do not permit independent causal verification.” - Treat strategy-matrix cells as candidate strategies, then test assumptions about price, access, regulation, distribution, and alternatives. - Add an affected-person and ethics map before finalizing an opportunity score. ### Bias and fallacy scan - **Selection bias and survivorship bias:** likely in the track record and case collection; high impact on C-009. - **Authority and testimonial bias:** Osterwalder foreword and executive testimonials provide credibility signals, not independent validation. - **False precision:** a formula can give numerical appearance to subjective wording, recruitment, and strategic choice. - **False dilemma:** “ideas-first” versus “needs-first” is too sharp when responsible teams can use informed prototypes to investigate needs. - **Causal overreach:** a post-ODI product result may rely on many factors outside customer need measurement. ## PROMPT 8 — Systems, history, and trio synthesis ### Context Ulwick links ODI to quality management and Six Sigma: break a customer process into steps, define metrics of success, then manage innovation through data. His account treats the 1990s–2010s as a movement from product and customer descriptions toward job and outcome measurement. Contemporary applied research still adapts ODI-style outcome structures in specific domains, such as hotel service, but adaptation is not a general replication ([study](https://www.mdpi.com/2071-1050/13/1/391)). ### JTBD methods cluster | Question | Ulwick | Kalbach | Burleson | Working recommendation | | --- | --- | --- | --- | --- | | Core unit | Functional job and measurable desired outcomes | Objective/process under circumstances | Five motivational levels | Start with job and circumstance | | Actor model | End user, buyer, support team | Performer, buyer, approver, reviewer, technician, manager, audience, assistant | Job executor persona | Use Kalbach’s wider actor map plus affected people | | Research | Formal qualitative + quantitative ODI | Interviews, Switch accounts, maps, optional ODI | Research feeds a strategic analysis | Match rigor to decision risk | | Quantification | Central: importance, satisfaction, segmentation, formula | Helpful but hard to execute well | Ratings presented without validation | Publish items, sample, method, and uncertainty | | Emotion/identity | Emotional/social needs around functional job | Functional, emotional, social jobs | Role, image, and emotional levels | Use direct participant language; avoid inference | | Main risk | Method implemented without fidelity | Lightweight use mistaken for full evidence | Taxonomy mistaken for psychology | Keep an evidence and consent trail | The comparison is convergent review analysis, not documented influence between these authors. ### Vault connections | Note | What ODI adds | Constraint from the vault | | --- | --- | --- | | [[3. Resources/MOCs/DevRel MOC]] | Outcome language for developer progress | DevRel includes public, community, and ecosystem duties beyond product demand | | [[4. Archives/Book reviews/On Value Creation in Developer Relations (DevRel) - A Practitioners' Perspective]] | A disciplined route from activity to outcome hypothesis | Do not treat business value as proof of participant value | | [[3. Resources/Permanent Notes/A Metric Is Vanity Only Against Your Own Outcome Data]] | Desired outcomes provide a candidate metric grammar | Metrics need denominator, method, and decision context | | [[3. Resources/Permanent Notes/A Feedback Signal Not More Automation Is What Makes a System Self-Improving]] | Needs-first research supplies an upstream feedback question | Evidence must reach a response and repair loop | | [[3. Resources/Literature Notes/Making Data-Driven Product Decisions]] | Quantification can follow qualitative discovery | Data preparation and model choice can create false certainty | | [[4. Archives/Book reviews/The Jobs to Be Done Playbook]] | ODI defines the high-rigor end of the method spectrum | Start lighter when stakes and evidence need are lower | | [[4. Archives/Book reviews/The Jobs-to-be-Done Pyramid]] | ODI protects functional/outcome rigor | The Pyramid can add identity hypotheses only when data supports them | ## PROMPT 9 — DEIB, accessibility, and power audit ### Inclusion strengths The needs framework distinguishes end user, buyer, and lifecycle-support worker. This creates an opening to notice that the person paying, installing, maintaining, or disposing of a product may have different needs and costs. Its focus on circumstances can also reveal access barriers when researchers actually ask about them. ### Risks and required controls | Risk | Why it matters | Control | | --- | --- | --- | | Quantified need treated as neutral fact | Wording and samples can encode a dominant group’s assumptions | Cognitive-test items, publish recruitment, examine subgroup variation | | Functional-job primacy | Safety, dignity, disability access, and community obligation may be treated as secondary | Include them as conditions for successful completion | | Customer as sole value holder | Workers, maintainers, families, public systems, and environment can bear costs | Map affected people and harms before strategy choice | | Segmentation reification | Clusters can become labels imposed on people | Keep segment boundaries provisional; do not infer protected characteristics | | Extractive research | Companies can collect intimate context without a participant benefit | Consent, minimization, compensation, withdrawal, and clear use limits | | Formula governance | Scores can overrule local knowledge or dissent | Keep raw evidence, challenge sessions, and documented overrides | ### Transfer table | Setting | Responsible adaptation | | --- | --- | | Product discovery | Use desired outcomes as testable hypotheses, then validate item wording | | Enterprise software | Map performer, buyer, admin, security reviewer, support worker, and people affected by workflow changes | | DevRel | Study developer progress only with clear research purpose; do not treat community activity as passive market data | | Open-source ecosystem | Add maintainer labor, governance, accessibility, funding, and public benefit | | Health, public service, education | Use independent ethics and domain review; do not automate segmentation into a service decision | The prose is accessible to business readers but reference density is high because it assumes familiarity with market research, segmentation, and strategy. It needs a companion on research ethics, accessible research, and causal evaluation before high-stakes use. ## PROMPT 10 — Notes pipeline ### Fleeting notes - A desired outcome is a candidate measure of successful job execution, not a fact about what people value. - A “successful” innovation method needs a published success definition and denominator. - A job map can organize process evidence without being a record of a specific company’s funnel. - Quantification makes wording, sample, missing data, and incentives more consequential. - An outcome score should invite challenge, not close it. - An ODI workshop is not ODI unless it preserves the method’s stated research rigor. ### Literature notes | Candidate | Source anchor | Connection | | --- | --- | --- | | Six customer-input types | ODI-C02 | [[4. Archives/Book reviews/The Jobs to Be Done Playbook]] | | Opportunity formula and score limit | ODI-C04; ODI-GLOSS | [[3. Resources/Permanent Notes/A Metric Is Vanity Only Against Your Own Outcome Data]] | | ODI fidelity | ODI-C06 | [[3. Resources/Literature Notes/Making Data-Driven Product Decisions]] | | Track-record evidence boundary | ODI-INTRO; ODI-C04 | [[4. Archives/Book reviews/On Value Creation in Developer Relations (DevRel) - A Practitioners' Perspective]] | | Jobs language and organization | ODI-C07–C08 | [[3. Resources/MOCs/DevRel MOC]] | ### Permanent-note candidates 1. **An opportunity score inherits the validity of its outcome statement, sample, and decision rule.** Confidence: high. Scope: quantitative prioritization. 2. **A desired-outcome inventory is a hypothesis map until participant evidence validates its wording and relevance.** Confidence: high. Scope: early discovery. 3. **A consulting track record needs an eligible-project denominator and independent success definition before it supports a causal rate claim.** Confidence: high. Scope: method evaluation. 4. **A functional job analysis must include people who bear access, maintenance, governance, or harm costs.** Confidence: high. Scope: product and ecosystem decisions. 5. **A null outcome is a decision-relevant result, not a failure to be hidden.** Confidence: high. Scope: research governance. Do not attribute the permanent-note wording or cross-vault synthesis to Ulwick. These are review inferences. ## PROMPT 11 — Teaching pack ### Audience and objectives For product strategy, research, DevRel, design, support, and community leaders who are considering an ODI-style process. Learners can: 1. distinguish a functional job, desired outcome, related job, emotional/social job, consumption-chain job, and buyer financial outcome; 2. identify when a research question needs qualitative discovery versus valid quantitative measurement; 3. audit an opportunity claim for instrument, sample, denominator, and confounders; 4. map affected people, access, and consent before a strategy decision. ### Lesson sequence | Session | Activity | Misconception check | | --- | --- | --- | | 1. Define the job | Rewrite feature requests as core-job and desired-outcome hypotheses | A job is not a product feature | | 2. Inspect a score | Find missing assumptions in a mock importance/satisfaction study | A formula does not validate its inputs | | 3. Choose method rigor | Compare a workshop, interviews, and an ODI-like study for different decisions | Small samples cannot estimate a market | | 4. Decide responsibly | Add access, affected actors, null findings, and a stop rule | Customer benefit is not the only value at stake | ### Facilitator cautions - Do not present the 86% figure as independently settled. - Do not teach segmentation as a way to label or infer protected characteristics. - Do not gather community or workplace data covertly. - Do not make an emotion or identity claim when functional, access, or safety evidence better explains the behavior. ## PROMPT 12 — Actions, experiments, and drift ### Action inventory - **Take:** require an outcome statement, evidence source, and decision rule before scoring a product or DevRel opportunity. - **Consider:** use a small qualitative job-map exercise to expose assumptions before funding a larger quantitative study. - **Avoid:** using a proprietary success rate as an ROI promise for a team with different resources and context. - **Need evidence:** whether a scoring method predicts adoption or stakeholder benefit better than the current decision process. The most likely misuse is converting people’s goals into a numerical permission slip for a prechosen growth plan. The safeguard is a public research purpose, consent, data minimization, challenge process, affected-person review, and retained null findings. ### Reversible experiments | Experiment | Hypothesis | Measure | Stop condition | | --- | --- | --- | | Draft 10 desired outcomes | Outcome syntax exposes vague feature requests | Item review by researchers and participants | Stop if wording assumes a solution | | Map one core job | Process steps reveal access or support work missing from a roadmap | Actor map and evidence log | Stop if the map excludes material affected people | | Run a small discovery round | Qualitative accounts identify repeated constraints | Contradictions and themes, not prevalence | Stop if consent or compensation is inadequate | | Audit an opportunity score | Missing denominator/instrument changes confidence | Completed evidence checklist | Reject score if inputs cannot be reconstructed | | Preserve a null | A presumed need is not important or not poorly satisfied | Decision log | Keep the result even if it blocks a favored initiative | ### Decision rules and drift Adopt desired-outcome language when it makes a question, evidence source, and decision clearer. Adapt the six-input framework when affected people or access conditions require expansion. Defer quantification without a validated instrument and sufficient sample. Reject a strategic claim whose only support is the method owner’s track record. Review live use at least yearly and whenever AI research tooling, privacy requirements, recruitment access, market structure, accessibility standards, or organizational incentives change. The source’s historical account and declared definitions do not require routine drift review. ## PROMPT 13 — Visual thinking pack ### ODI evidence flow ```mermaid flowchart LR A["Core functional job"] --> B["Job map and qualitative discovery"] B --> C["Desired outcome hypotheses"] C --> D["Validated quantitative study"] D --> E["Opportunity and segment hypotheses"] E --> F["Market/product decision"] G["Consent, accessibility, affected people, nulls"] -.-> B G -.-> D G -.-> F ``` ### Claims boundary ```mermaid flowchart TD M["Method definitions\nStrongest support"] --> P["Process discipline\nPlausible"] P --> S["Strategy outcome\nNeeds local evidence"] T["Author cases and testimonials"] -.-> S R["Reported 86% rate\nPublic methods incomplete"] -.-> S X["Independent replication and transparent denominator"] --> R ``` ### JTBD trio decision tree | Need | Start with | Add only when justified | | --- | --- | --- | | Scope people, context, and interview evidence | [[The Jobs to Be Done Playbook]] | ODI measurement where decision stakes warrant it | | Test desired outcomes at market level | Ulwick’s ODI discipline | Independent method audit and participant protections | | Surface role, image, and emotion questions | [[The Jobs-to-be-Done Pyramid]] | Direct participant evidence and consent | | Plan DevRel/community work | Actor, job, and affected-person map | Community governance and public-benefit review | No timeline is included because the book’s internal history is already summarized in Prompt 8. No causal-loop diagram is included because the source does not provide enough independent evidence about feedback dynamics to support one. ## Session completion check | Check | Result | | --- | --- | | EPUB integrity and source identity verified | PASS | | Complete source coverage recorded | PASS | | Reader-emphasis absence disclosed | PASS | | Prompts 0–13 have usable output | PASS | | Prompt 7 uses Prompt 5 and Prompt 6 | PASS | | Author/company claims separated from review inference | PASS | | 86% track-record claim bounded by evidence limits | PASS | | Accessibility, consent, power, and affected-person audit included | PASS | | Existing vault connections verified as outbound links | PASS | | One-file constraint honored | PASS | ### Final verdict Ulwick provides the most exacting operational core in the vault’s JTBD cluster: a needs framework, outcome syntax, job maps, formal quantitative study, segmentation, and a strategy path. Its discipline is valuable when a high-stakes decision can fund high-quality research. Its central performance promise is weaker than the method language: the public source does not allow an independent evaluation of the reported 86% success rate. Use ODI to make assumptions inspectable, not to claim certainty. Pair it with Kalbach’s actor and interview discipline, Burleson’s optional motivational prompts, and explicit consent, accessibility, public-value, and null-result controls.