Guide

Discover What's Possible — Orientation Guide

A practical orientation that helps teams turn curiosity into repeatable discovery practice: clear phase descriptions, recommended artifacts, roles and rhythms, a 30/60/90 starter plan with measurable milestones, quick wins, and guidance to avoid common traps.

Welcome — what this orientation does for your team

This guide helps teams move from scattered curiosity and ad-hoc pilots to a coherent discovery practice that generates measurable opportunities. It explains a simple journey model, the artifacts and roles that make it work, daily and weekly rhythms that keep momentum, and a 30/60/90 starter plan that produces validated outcomes rather than theater.

Why this matters

Good discovery reduces wasted effort, accelerates learning, and increases the chance that experiments turn into operational change. Use this guide to create repeatable ways of identifying high-value ideas, testing them quickly, and connecting learning to your product, process, or service roadmap.

Journey phases — purpose and practical outputs

Curiosity

Purpose: Surface possibilities worth exploring.

  • Key questions: What anomalies, customer pains, or internal friction are drawing attention? Which data trends hint at opportunity?
  • Recommended artifacts: Opportunity brief (one page), customer observation notes, data snapshot, hypothesis backlog.
  • Timebox: short — a set of lightweight intake and triage activities so curiosity doesn't become noise.
  • Example output: 5 candidate hypotheses with estimated impact and ease-of-test scores.

Frame

Purpose: Turn a candidate into a testable question.

  • Key questions: What specifically will we learn? Who is affected? What would success look like?
  • Recommended artifacts: Framing document (problem statement, target outcome, assumptions), defined metrics, success criteria, chosen experiment owner.
  • Timebox: focused refinement until a clear hypothesis and measurable outcomes exist.
  • Example output: One testable hypothesis with primary metric and guardrails.

Experiment

Purpose: Run fast, low-cost tests to learn against the hypothesis.

  • Key questions: What minimal intervention will produce informative feedback? How quickly can we run it?
  • Recommended artifacts: Experiment plan (method, sample, timeline), data collection template, consent/checklist where relevant.
  • Timebox: days to a few weeks depending on test type.
  • Example output: Raw experimental data, learning notes, initial metric change.

Validate

Purpose: Decide whether to iterate, expand, or stop.

  • Key questions: Did we meet the success criteria? Are effects repeatable and practical to operate?
  • Recommended artifacts: Validation report (data, interpretation, risks), suggested next steps, ROI/impact estimate.
  • Timebox: a short review and decision window following experiment completion.
  • Example output: Decision to continue with a pilot, refine and re-test, or retire the idea.

Scale

Purpose: Move validated ideas into operational delivery and continuous improvement.

  • Key questions: What changes to processes, training, or systems are required? How will we measure sustained impact?
  • Recommended artifacts: Implementation plan, acceptance criteria, standard operating procedures, monitoring dashboard.
  • Timebox: depends on operational complexity; include staged rollouts and monitoring intervals.
  • Example output: Live feature, process change, or policy with tracked KPIs and owner.

Suggested team roles and simple responsibilities

  • Sponsor: Secures resources and removes organizational blockers.
  • Discovery Lead: Guides the journey, runs cadences, keeps the hypothesis backlog healthy.
  • Experiment Owner: Designs and executes an experiment, collects data, and summarizes learnings.
  • Subject Experts: Provide domain, technical, operational, or regulatory input.
  • Data Steward/Analyst: Helps define metrics, sets up data capture, and validates results.
  • Integrator: Owns handoff to delivery/operations when validation recommends scaling.
  • Librarian/Knowledge Lead: Records artifacts, maintains the lessons library, and curates validated opportunities.

Daily and weekly rhythms that sustain momentum

  • Daily/short-sync: Very brief standups for active experiments to surface blockers and quick decisions.
  • Weekly learning huddle: Share experiment results and decisions, refresh the hypothesis backlog, and allocate short experiment capacity.
  • Bi-weekly showcase: Present validated learnings to a broader audience — stakeholders, operators, and sponsors.
  • Monthly strategy review: Connect validated opportunities to roadmap priorities, resource planning, and risk assessment.

30/60/90 starter plan — concrete milestones

Days 0–30

  • Establish roles, basic tooling, and a central hypothesis backlog (one shared doc or simple tracker).
  • Capture candidate opportunities and frame at least three hypotheses with clear success metrics.
  • Run at least two small experiments focused on learning (low cost, short duration).
  • Deliverable: experiment summaries and a decision for each (continue/refine/stop).

Days 31–60

  • Prioritize validated experiments for deeper validation or pilot scale.
  • Connect experiment metrics to operational data sources and define monitoring needs.
  • Prepare a validation report on top candidates and secure sponsor alignment for pilots.
  • Deliverable: validated-opportunity packet (data, risks, implementation outline).

Days 61–90

  • Execute a controlled pilot or staged rollout for a validated opportunity.
  • Finalize ownership, implementation plan, and KPIs for long-term measurement.
  • Document lessons, update the knowledge library, and integrate the outcome into the roadmap.
  • Deliverable: pilot outcome and a go/no-go decision for full scale.

Quick wins and practical tips

  • Start with questions that can be answered through observation or A/B style tests rather than heavy engineering work.
  • Use short experiment timeboxes and pre-agreed stopping criteria to limit sunk cost.
  • Capture a one-paragraph learning summary for every experiment (what we tried, what we learned, what we recommend).
  • Keep a visible backlog ranked by expected value and ease of testing so the team can pull the next experiment quickly.

Common pitfalls and how to avoid them

  • Fragmented curiosity: Avoid many unconnected pilots by maintaining one shared hypothesis backlog and a lightweight triage process.
  • Innovation theater: Prevent activities that look innovative but produce no decisions by requiring measurable success criteria before spending more than a small budget.
  • Lost momentum: Protect a small steady cadence of experiments and keep sponsor engagement visible.

Recommended metrics to track

  • Learning velocity: number of experiments completed per period and percent that produced actionable learning.
  • Validation rate: share of experiments that reach validated status.
  • Conversion to delivery: percent of validated opportunities integrated into roadmap or operations.
  • Time-to-validated: average time from hypothesis to validated decision.

How to use this guide

Adopt the sections you need and adapt artifacts to your context. Start small: pick one hypothesis, run a short experiment, and capture the learning. Use the 30/60/90 plan as a pacing scaffold, not an inflexible schedule.

Next steps & suggested resources

  • Create a shared hypothesis backlog and a simple experiment template.
  • Schedule the weekly learning huddle and monthly strategy review on calendars.
  • Assign a discovery lead or librarian to track artifacts and validated opportunities.
  • Suggested internal topics to explore next: using data to prioritize tests, designing low-cost experiments, and turning pilots into SOPs.

Image suggestion: innovation journey map

Discuss Ask the Librarian

Discussion

Comments and conversation will live here.