What is a JTBD dashboard and how does it differ from a standard product analytics dashboard?

A JTBD dashboard tracks whether users are completing the jobs they hired the product to do, using Outcome Yield as the core metric. A standard dashboard tracks feature usage and session metrics, which do not directly indicate whether users are achieving their intended outcomes.

What is Outcome-Driven Innovation (ODI) and how does it apply to SaaS product dashboards?

ODI is Tony Ulwick's framework for structuring product decisions around customer-defined desired outcomes. Applied to SaaS dashboards, it means measuring how well users complete functional, emotional, and social outcome milestones rather than tracking activity volume.

What is an Opportunity Score in the JTBD framework?

The Opportunity Score is calculated as Importance + (Importance minus Satisfaction), where both values are survey-rated by users. A score above 10 indicates an underserved outcome — a market opportunity where users place high value but the product is not delivering adequately.

How do you identify underserved market segments using a JTBD dashboard?

By segmenting users based on which desired outcomes they rate as highly important but poorly satisfied, teams can identify groups with unmet needs. These segments often represent product expansion opportunities or indicate where the current product is failing a specific user type.

What events should be tracked in a JTBD-aligned analytics implementation?

JTBD-aligned tracking captures milestone completions that represent progress toward core jobs — such as 'first report created', 'team member invited', or 'integration connected' — rather than generic UI events like button clicks that have no inherent meaning without job context.

JTBD Dashboard Template: The Outcome-Driven Innovation (ODI) Guide

TL;DR

From Features to Outcomes: Replace "DAU/MAU" with "Outcome Yield"—the percentage of users who successfully complete a Job Statement (e.g., "Minimize the time to sync EHR data").
The Opportunity Score: Use the ODI formula `Importance + Max(Importance - Satisfaction, 0)` to identify exactly which features to build next.
Quantitative Job Mapping: Build a 3-layer dashboard hierarchy: 1) Core Functional Job, 2) Related Jobs, 3) Emotional/Social Jobs.
HogQL Instrumentation: Map behavioral event sequences to discrete "Job Milestones" to calculate real-time Satisfaction scores without manual surveys.
Strategic Moats: Products that solve a job with >15.0 Opportunity Score create 3x higher retention than features-first competitors.

In the world of SaaS, we are drowning in data but starving for insight. Most product dashboards track **mechanisms**: how many people clicked a button, how many people logged in, how many people used a feature. But customers don't buy features. They "hire" your product to do a job.

The "Jobs-to-be-Done" (JTBD) framework, specifically the Outcome-Driven Innovation (ODI) methodology developed by Anthony Ulwick, provides the mathematical rigour required to connect product telemetry to human value. This guide provides the technical template for building a JTBD-first dashboard.

Features are temporary. Jobs are permanent. The best products win by solving the job better than the existing alternatives.

1. The ODI Framework: Quantifying the Job

At the heart of a technical JTBD dashboard is the **Opportunity Score**. This metric tells you which areas of your product are underserved by the current market. We use a 402-outcome study (found in our `scale-insights` research) to map every feature request to a desired outcome.

The Opportunity Formula

Opportunity Score = Importance + Max(Importance - Satisfaction, 0)

Importance: How critical is this outcome to the user? (1-10)
Satisfaction: How well does your current product (or competitors) solve this? (1-10)

"An Opportunity Score > 15.0 is a 'Hidden Goldmine.' For a client in the medical space, we identified a 15.3 score for 'Minimizing the time to reconcile patient forms.' Solving this led to a 34% conversion lift in one quarter."
— Jake McMahon, ProductQuant

2. The JTBD Dashboard Hierarchy

A functional JTBD template moves beyond flat lists. It organizes data into three layers of customer realization.

Dashboard Layer	Technical Goal	The "Tried & True" Metric
Layer 1: Functional Job	Execution Velocity	Outcome Yield (%)
Layer 2: Related Jobs	Platform Stickiness	Expansion Surface Area
Layer 3: Emotional Jobs	Retention Moat	Confidence Index

Outcome Yield: The New North Star

Outcome Yield measures the success rate of a specific job. In PostHog, we instrument this by tracking the sequence from **Trigger** to **Value Realization**.

-- HogQL: Calculate Outcome Yield for 'EHR Sync'
SELECT 
    countIf(event = 'ehr_sync_completed') / countIf(event = 'ehr_sync_started') as outcome_yield
FROM events
WHERE timestamp > now() - interval 30 day
        

3. Practical Implementation: Quantitative Job Mapping

To build your template, you must map your event taxonomy to your Job Map. We follow a standard 8-step execution process:

Define the Job: Use the syntax: `[Verb] + [Object] + [Context]`.
Outcome Discovery: Identify the 50-100 metrics users use to judge success.
Opportunity Audit: Survey users to calculate the Opportunity Score.
Event Mapping: Connect `object_action` events to specific outcomes.
Milestone Tracking: Instrument the "Moment of Value" for each job.
Segment Analysis: Use HDBSCAN to find behavioral clusters that solve jobs differently.
Friction Detection: Track `rage_clicks` during high-importance Job steps.
Iterative Refinement: Update the dashboard as Job satisfaction improves.

34% Lift

By focusing the dashboard on 'Minimizing data entry friction' (Opportunity Score 15.3) instead of 'Feature X usage,' we prioritized a 2-week sprint that increased signup density by 34%.

FAQ

How do I identify Emotional Jobs in data?

Look for **Retention Surpluses**. If a user has low functional usage but high retention, they are likely hiring your product for a Social or Emotional job (e.g., "Maintaining professional status" or "Feeling in control"). We track these via qualitative survey prompts triggered by PostHog cohorts.

Can we use this for B2B Enterprise?

Yes. In B2B, the "Job" is often an organizational one (e.g., "Minimize the cost of compliance"). You must use **Group Analytics** to track Job Completion at the account level rather than the individual level.

What is a 'Job Statement'?

It is a stable statement of user intent. Example: "Manage patient intake forms efficiently." Unlike features (which change with technology), Job Statements remain constant for decades, providing a stable foundation for your product roadmap.

Sources

About the Author

Jake McMahon is a PLG & GTM Growth Consultant who specializes in Outcome-Driven Innovation (ODI). He has helped Series A-C SaaS platforms identify hidden market opportunities and build data-proven product roadmaps that drive 30%+ increases in activation density.

Learn More Work with Jake