Foundations: Mindsets, Principles & Core Frameworks

Welcome — why a shared discovery foundation matters

Discovery without shared thinking looks like activity. Discovery with shared foundations looks like progress. This guide helps teams adopt core mindsets, practical systems thinking, and a small set of dependable frameworks so curiosity becomes well‑framed questions, prioritized opportunities, aligned experiments, and measurable learning.

Primary hungers this resource serves

• Create shared mental models so teams approach discovery consistently and effectively.
• Reduce wasted effort from poor framing, misaligned experiments, and premature scaling.

Core mindsets for reliable discovery

Mindsets shape what you notice and what you choose to test. Encourage these four as a baseline for any team doing discovery work:

• Curiosity with focus: Ask specific questions. Broad curiosity is valuable, but turn it into an explicit opportunity statement or JTBD before acting.
• Evidence‑first: Prefer observed behavior and data over anecdotes and assumptions. Treat customer stories as leads, not proofs.
• Fast‑safe failing: Run small, rapid experiments that surface truth without exposing the organization to major risk or cost.
• Customer empathy: Seek the job the customer hires a product, service, or process to do — not just stated preferences.

Key frameworks and when to use them

Rather than a long list of playbooks, use a small toolkit where each framework addresses a clear need.

1) Jobs‑to‑Be‑Done (JTBD) — opportunity identification

Use JTBD when you want to discover unmet needs and reframe features or services around outcomes people seek.

JTBD statement template: When [situation], I want to [motivation], so I can [desired outcome].

Example: When I'm on a 30‑minute commute, I want to learn one practical idea I can apply at work, so I can feel like my commute time helped my day.

2) Causal mapping / causal loops — complexity and system behavior

Choose causal mapping when problems involve feedback, delays, or interacting parts (e.g., operations, supply chains, ecosystem effects). Mapping helps you spot leverage points and unintended consequences.

Simple practice: draw a short causal loop showing the primary variables, direction (+/−), and at least one feedback loop. Ask: where does the system amplify or dampen change?

3) Hypothesis‑driven experimentation — validation

Use this for any idea you plan to scale. Convert assumptions into testable hypotheses, define metrics, and decide the minimum viable test.

Experiment template: Hypothesis: [If we do X for Y], then [we expect Z metric to move] because [rationale]. Measure: primary metric, secondary metrics, duration, sample. Risk & Safeguards: what could harm users or business and how you’ll avoid it.

4) Measurement frameworks — learning, not vanity

Design measurements to answer the discovery question. Distinguish leading metrics that indicate progress from lagging metrics that show final outcomes. Define success criteria before running the experiment.

Example metrics for a retention experiment: activation rate (leading), week‑4 retention (lagging), user satisfaction (qualitative).

How to choose the right framework

Use this quick decision guide:

1. Are you exploring customer needs and unmet outcomes? → Start with JTBD interviews and customer jobs mapping.
2. Is the problem shaped by interdependent processes, delays, or feedback? → Build a causal map to understand system behavior.
3. Do you have a specific assumption you want to test before investing? → Design a hypothesis‑driven experiment with clear metrics.
4. Do you need to decide how to measure success across teams? → Establish a measurement framework with leading/lagging metrics and success criteria.

Many projects combine frameworks. For example, use JTBD to surface an opportunity, causal mapping to understand operational constraints, and hypothesis testing to validate a specific solution.

Concrete examples (short)

• New product direction: JTBD interviews reveal a time‑saving job. Use small prototypes to validate willingness to pay (hypothesis testing) and map organizational processes (causal loops) to ensure delivery at scale.
• Operational bottleneck: Causal mapping uncovers a feedback delay causing inventory oscillations. Hypothesize an inventory policy change and run a controlled pilot measuring fulfillment lead time and stockouts.

Suggested readings and short exercises

• Read: short JTBD primer (30–60 min) and capture three candidate jobs from real users.
• Exercise (30–90 min): Run a 3‑interview JTBD sprint — convert notes into jobs statements and prioritize by frequency + severity.
• Exercise (60–120 min): Map a 1‑page causal loop for a recent unexpected outcome (e.g., sudden churn, a production spike) and identify one leverage point to test.
• Exercise (45–90 min): Design one minimum viable experiment using the hypothesis template; list metrics, sample, duration, and risk mitigations.

Workshop & onboarding use

This guide works as both pre‑work and the core orientation for a discovery cohort. Suggested sequence for a half‑day workshop:

1. Short opener: hunger and recent example of wasted discovery (15 min).
2. Introduce mindsets and JTBD (20 min), followed by JTBD micro‑interviews (30–45 min).
3. Causal mapping demo and rapid mapping exercise (30 min).
4. Experiment design clinic: refine one team hypothesis and measurement plan (45 min).
5. Close with commitments: who will run the experiment, what metrics, and when to review (15 min).

Quick checklist before you run a discovery experiment

• Clear question or job statement defined.
• Framework chosen and reason documented.
• Primary metric and success criteria set.
• Minimum viable test defined and risks mitigated.
• Review cadence and owner assigned.

Next steps & capability opportunities

Turn this guide into a living toolkit by adding:

• JTBD interview templates and recording forms.
• Interactive causal mapping templates and example maps.
• Experiment design worksheet that stores hypotheses, metrics, outcomes, and learning.

These additions can become reusable assets teams acquire and tailor across your organization.

Suggested next actions for teams

1. Run the JTBD 3‑interview sprint as pre‑work for your next planning session.
2. Create one causal map for a recent problem and pick one leverage point to test.
3. Design a single experiment this week with a clear owner and measurement plan.