The DRIVE Framework #

DRIVE is the execution process for Behavioral Strategy. It provides a structured, evidence-based method for achieving each stage of the Four-Fit Hierarchy.

Four-Fit defines what must be validated. DRIVE defines how the work is done.

The relationship is simple:

• Four-Fit Hierarchy defines what must be validated at each stage
• DRIVE Framework defines how you do that validation work

Use Four-Fit to know what to validate. Use DRIVE to know how to do it.

How DRIVE Maps to Four-Fit #

FOUR-FIT HIERARCHY              DRIVE PROCESS
(What to validate)              (How to do it)

┌─────────────────────┐         ┌─────────────────────┐
│   PROBLEM FIT       │ ◄────── │   DEFINE            │
│   Do users seek     │         │   Goal + Population  │
│   solutions?        │         │   + Problem          │
└──────────┬──────────┘         └─────────────────────┘
           │
           ▼
┌─────────────────────┐         ┌─────────────────────┐
│   BEHAVIOR FIT      │ ◄────── │   RESEARCH          │
│   Can and will      │         │   Behavior Fit      │
│   they do this?     │         │   Assessment        │
└──────────┬──────────┘         │   + Observation      │
           │                    └─────────────────────┘
           ▼
┌─────────────────────┐         ┌─────────────────────┐
│   SOLUTION FIT      │ ◄────── │   INTEGRATE         │
│   Does our solution │         │   Enable behavior   │
│   enable behavior?  │         │   through design     │
└──────────┬──────────┘         └─────────────────────┘
           │
           ▼
┌─────────────────────┐         ┌─────────────────────┐
│   PRODUCT FIT       │ ◄────── │   VERIFY + ENHANCE  │
│   Does behavior     │         │   Measure + iterate  │
│   persist at scale? │         │   continuously       │
└─────────────────────┘         └─────────────────────┘

The Five DRIVE Phases #

1. DEFINE → Achieves Problem Market Fit #

Goal: Establish clear strategic objectives and validate that users actively seek solutions to the identified problem.

Key activities:

• Articulate measurable strategic objectives
• Identify and validate target user segments
• Conduct problem interviews until themes converge
• Document evidence of problem-seeking behavior
• Define success metrics in behavioral terms

Exit criteria (Problem Market Fit):

• Clear, measurable strategic objectives defined
• Target user segments validated through research
• Problem-seeking behavior documented with evidence
• Themes converging across interviews

Example (Consumer): Instagram’s team defined their goal (boost engagement), identified their target users (mobile social users), and validated what users actually wanted to do.

Example (Enterprise): Claims operations validates that policyholders experience significant pain from documentation delays and actively seek faster resolution.

2. RESEARCH → Achieves Behavior Market Fit #

Goal: Identify and validate specific behaviors that the target population can and will perform to solve the validated problem.

The Behavior Fit Assessment is a practitioner decision tool for comparing candidate behaviors across Dispositional Fit, Capability Fit, and Context Fit. It is not a validated measurement instrument. Treat the minimum dimension as a bottleneck and prioritization heuristic; it is not a deterministic probability of behavior.

A score of 6 out of 10 on each Behavior Fit Assessment dimension is a starting threshold that must be calibrated by domain, population, context, stakes, and observed behavior.

Key activities:

• Conduct behavioral observation in natural contexts
• Identify multiple candidate behaviors that could solve the problem
• Apply the Behavior Fit Assessment to each candidate:
  • Dispositional Fit: Does this behavior match the population’s relatively enduring tendencies and preferences?
  • Capability Fit: Can they actually perform this behavior?
  • Context Fit: Does the social and physical environment support this behavior?
• Use minimum ratings to identify candidate bottlenecks and prioritize candidates for real-context validation
• Validate selection through realistic testing

Exit criteria (Behavior Market Fit):

• Multiple candidate behaviors identified
• Behavior Fit Assessment completed for each candidate
• Ratings, evidence gaps, calibration choices, and candidate bottlenecks are documented
• Behavior Market Fit is supported by observation in realistic contexts

Evaluation rubric (for scoring each dimension):

Example (Consumer): Instagram’s research revealed photo sharing scored high across all three Behavior Fit Assessment dimensions; check-ins scored low on Dispositional Fit and Context Fit.

3. INTEGRATE → Achieves Solution Market Fit #

Goal: Design solutions that enable and encourage the validated target behavior.

Key activities:

• Map every solution feature to a validated behavior
• Conduct friction analysis (identify and remove barriers)
• Prototype solutions that make the behavior easy and obvious
• Test with users: does the solution trigger the behavior?
• Iterate until the solution reliably enables behavior

Exit criteria (Solution Market Fit):

• Every feature maps to a validated behavior
• Friction analysis completed and addressed
• Prototype testing confirms behavior enablement
• Solution measurably reduces friction and increases payoff

Feature-to-behavior mapping example:

4. VERIFY → Confirms Product Market Fit #

Goal: Confirm that the solution drives the target behavior sustainably in real market conditions.

Key activities:

• Define behavioral KPIs before launch
• Implement tracking infrastructure
• Launch to initial cohort
• Monitor behavior completion rates from day one
• Track bPMF and behavior retention cohorts

Key metrics:

Common verification mistakes:

1. Vanity metrics focus: tracking downloads instead of behaviors
2. Delayed measurement: waiting months before checking data
3. Aggregate blindness: overall looks good but segments are failing

5. ENHANCE → Sustains Product Market Fit #

Goal: Continuously refine the solution based on behavioral data to maximize long-term impact.

Key activities:

• Analyze behavioral performance data weekly
• Identify underperforming segments or behaviors
• Run experiments on behavior enablement
• Iterate on the solution based on learnings
• Scale what works; fix or remove what doesn’t

Enhancement decision tree:

Current Performance
       │
       ├── Below Target
       │   └── Diagnose: Which behaviors? What barriers? Which segments?
       │       └── Actions: Reduce friction, increase motivation, improve ability
       │
       ├── At Target
       │   └── Optimize: Which behaviors drive most value? How to expand?
       │       └── Actions: Scale success, expand reach, deepen engagement
       │
       └── Above Target
           └── Sustain: What maintains performance? What risks regression?
               └── Actions: Reinforce habits, monitor threats, innovate ahead

DRIVE in Practice: Full Example #

Scenario: A healthcare app improving medication adherence

DEFINE (→ Problem Market Fit) #

• Objective: increase medication adherence from 60% to 85%
• Population: chronic condition patients on daily medication
• Problem validation: interviews reveal patients forget doses, feel unsure medication helps, lack routine integration
• Problem Market Fit achieved: clear evidence patients seek solutions to adherence challenges

RESEARCH (→ Behavior Market Fit) #

• Candidate behaviors:
  1. Set daily phone alarm → Dispositional 5, Capability 8, Context 7 (minimum: 5; investigate the dispositional bottleneck)
  2. Use smart pill bottle → Dispositional 4, Capability 6, Context 5 (minimum: 4; weaker candidate pending evidence)
  3. Link to existing morning routine → Dispositional 7, Capability 9, Context 8 (minimum: 7; stronger candidate for field validation)
  4. Weekly pill organizer prep → Dispositional 6, Capability 7, Context 7 (minimum: 6; plausible candidate for field validation)
• Selected behavior: link medication to existing morning routine (highest minimum score)
• Behavior Market Fit achieved: behavior validated through observation; patients can and will integrate medication into existing routines

INTEGRATE (→ Solution Market Fit) #

• Solution design: app identifies the patient’s existing morning routine, suggests a specific anchor (e.g., “after brushing teeth”), sends contextual reminder
• Friction removed: generic reminders replaced with routine-linked prompts
• Prototype testing: 25 patients tested; 85% successfully linked medication to routine (example)
• Solution Market Fit achieved: solution measurably enables the validated behavior

VERIFY (→ Product Market Fit) #

• Behavioral KPIs: daily adherence rate, streak length, routine completion
• Launch results: 78% of users maintain adherence at 30 days (example)
• bPMF: 78% > 70% default threshold
• Product Market Fit confirmed: behavior persisting at scale with viable engagement metrics

ENHANCE (→ Sustain Product Market Fit) #

• Analysis: evening medication users underperform (only 65% adherence; example)
• Hypothesis: evening routines less consistent than morning
• A/B test: flexible evening window vs fixed time
• Result: flexible window increased evening adherence to 74% (example)
• Sustain Product Market Fit: continuous iteration maintaining and improving behavior rates

Frequently asked questions #

What’s the difference between DRIVE and Four-Fit? #

They work together: Four-Fit defines what must be validated (Problem → Behavior → Solution → Product). DRIVE defines how you do the work (Define → Research → Integrate → Verify → Enhance).

Can we skip phases if we already have a solution? #

Usually not. The most common failure is skipping Behavior Market Fit. Even with an existing solution, re-validate the problem, verify the target behavior is feasible in real context for the population, then confirm the solution actually enables it.

When should I use the Behavior Fit Assessment vs. the full Behavioral State Model? #

Use the Behavior Fit Assessment for fast screening and behavior selection. Use the full Behavioral State Model when diagnosing why a selected behavior is not occurring (or why segments differ).

How long does a DRIVE cycle take? #

It depends on domain constraints and how much you already know. You can often de-risk early stages in a 10-day validation sprint; deeper domains (healthcare, policy, enterprise) may take weeks. The rule is to validate Behavior Market Fit before committing to large build work.

Does DRIVE depend on habit formation or nudges? #

No. Habit formation applies mainly to simple, cue-stable behaviors; most meaningful behaviors remain goal-directed. DRIVE focuses on behavior selection, Behavior Market Fit validation, and system enablement. Nudges can be marginal optimization after fit, not a strategy.

DRIVE Maturity Model #

Licensing #

Content © Jason Hreha. Text licensed under CC BY-NC-SA 4.0 unless a more specific asset notice applies. Framework names may be used accurately without implying endorsement.

See also:

• Four-Fit Hierarchy: The validation gates DRIVE achieves
• Behavior Fit Assessment: The behavior screening tool used in Research
• Behavioral State Model: Deeper diagnostic for troubleshooting
• Behavior Matching: How to select the right behavior

← Back to Methodology