Foundations of Discovery & Innovation — Orientation Journey

Preview Cards

Here are the first 5 questions. Create a conversation to invite someone and discuss each card.

1. <section> <h2>Welcome — why a shared discovery foundation matters</h2> <p>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.</p> <h3>Primary hungers this resource serves</h3> <ul> <li>Create shared mental models so teams approach discovery consistently and effectively.</li> <li>Reduce wasted effort from poor framing, misaligned experiments, and premature scaling.</li> </ul> <h2>Core mindsets for reliable discovery</h2> <p>Mindsets shape what you notice and what you choose to test. Encourage these four as a baseline for any team doing discovery work:</p> <ul> <li><strong>Curiosity with focus:</strong> Ask specific questions. Broad curiosity is valuable, but turn it into an explicit opportunity statement or JTBD before acting.</li> <li><strong>Evidence‑first:</strong> Prefer observed behavior and data over anecdotes and assumptions. Treat customer stories as leads, not proofs.</li> <li><strong>Fast‑safe failing:</strong> Run small, rapid experiments that surface truth without exposing the organization to major risk or cost.</li> <li><strong>Customer empathy:</strong> Seek the job the customer hires a product, service, or process to do — not just stated preferences.</li> </ul> <h2>Key frameworks and when to use them</h2> <p>Rather than a long list of playbooks, use a small toolkit where each framework addresses a clear need.</p> <h3>1) Jobs‑to‑Be‑Done (JTBD) — opportunity identification</h3> <p>Use JTBD when you want to discover unmet needs and reframe features or services around outcomes people seek.</p> <p>JTBD statement template: <em>When [situation], I want to [motivation], so I can [desired outcome].</em></p> <p>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.</p> <h3>2) Causal mapping / causal loops — complexity and system behavior</h3> <p>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.</p> <p>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?</p> <h3>3) Hypothesis‑driven experimentation — validation</h3> <p>Use this for any idea you plan to scale. Convert assumptions into testable hypotheses, define metrics, and decide the minimum viable test.</p> <p>Experiment template: <strong>Hypothesis:</strong> [If we do X for Y], then [we expect Z metric to move] because [rationale]. <strong>Measure:</strong> primary metric, secondary metrics, duration, sample. <strong>Risk & Safeguards:</strong> what could harm users or business and how you’ll avoid it.</p> <h3>4) Measurement frameworks — learning, not vanity</h3> <p>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.</p> <p>Example metrics for a retention experiment: activation rate (leading), week‑4 retention (lagging), user satisfaction (qualitative).</p> <h2>How to choose the right framework</h2> <p>Use this quick decision guide:</p> <ol> <li>Are you exploring customer needs and unmet outcomes? → Start with JTBD interviews and customer jobs mapping.</li> <li>Is the problem shaped by interdependent processes, delays, or feedback? → Build a causal map to understand system behavior.</li> <li>Do you have a specific assumption you want to test before investing? → Design a hypothesis‑driven experiment with clear metrics.</li> <li>Do you need to decide how to measure success across teams? → Establish a measurement framework with leading/lagging metrics and success criteria.</li> </ol> <p>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.</p> <h2>Concrete examples (short)</h2> <ul> <li>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.</li> <li>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.</li> </ul> <h2>Suggested readings and short exercises</h2> <ul> <li>Read: short JTBD primer (30–60 min) and capture three candidate jobs from real users.</li> <li>Exercise (30–90 min): Run a 3‑interview JTBD sprint — convert notes into jobs statements and prioritize by frequency + severity.</li> <li>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.</li> <li>Exercise (45–90 min): Design one minimum viable experiment using the hypothesis template; list metrics, sample, duration, and risk mitigations.</li> </ul> <h2>Workshop & onboarding use</h2> <p>This guide works as both pre‑work and the core orientation for a discovery cohort. Suggested sequence for a half‑day workshop:</p> <ol> <li>Short opener: hunger and recent example of wasted discovery (15 min).</li> <li>Introduce mindsets and JTBD (20 min), followed by JTBD micro‑interviews (30–45 min).</li> <li>Causal mapping demo and rapid mapping exercise (30 min).</li> <li>Experiment design clinic: refine one team hypothesis and measurement plan (45 min).</li> <li>Close with commitments: who will run the experiment, what metrics, and when to review (15 min).</li> </ol> <h2>Quick checklist before you run a discovery experiment</h2> <ul> <li>Clear question or job statement defined.</li> <li>Framework chosen and reason documented.</li> <li>Primary metric and success criteria set.</li> <li>Minimum viable test defined and risks mitigated.</li> <li>Review cadence and owner assigned.</li> </ul> <h2>Next steps & capability opportunities</h2> <p>Turn this guide into a living toolkit by adding:</p> <ul> <li>JTBD interview templates and recording forms.</li> <li>Interactive causal mapping templates and example maps.</li> <li>Experiment design worksheet that stores hypotheses, metrics, outcomes, and learning.</li> </ul> <p>These additions can become reusable assets teams acquire and tailor across your organization.</p> <h2>Suggested next actions for teams</h2> <ol> <li>Run the JTBD 3‑interview sprint as pre‑work for your next planning session.</li> <li>Create one causal map for a recent problem and pick one leverage point to test.</li> <li>Design a single experiment this week with a clear owner and measurement plan.</li> </ol> <footer> <p><strong>Image suggestion:</strong> diagrams of innovation frameworks or a simple causal loop sketch.</p> </footer> </section>