Methods & Toolboxes
Practical, role-focused toolboxes organized by the work people do during discovery, with templates, facilitation kits, and experiment-ready methods you can copy and adapt.
View
Preview Cards
Here are the first 5 questions. Create a conversation to invite someone and discuss each card.
- <section> <h2>Find the right toolbox for the discovery job</h2> <p>Discovery work is a sequence of related activities — learning about users and systems, reframing problems, generating ideas, testing assumptions, measuring impact, and making decisions. This index is a pragmatic map: it explains how this collection is organized, when to use each toolbox, what a minimal starter kit looks like, and how to chain toolboxes together so workshops and small teams move from curiosity to measurable experiments.</p> <h3>How this deck is organized</h3> <p>The toolboxes are grouped by the kind of outcomes they help you produce and the roles that typically use them:</p> <ul> <li><strong>User Research</strong> — discovery interviews, observation, persona and journey artifacts that surface real needs and evidence.</li> <li><strong>Systems Thinking</strong> — mapping, causal loops, ecosystem models to reveal leverage points and hidden constraints.</li> <li><strong>Ideation & Creativity</strong> — structured brainstorming, concept development, and convergent techniques for high‑quality options.</li> <li><strong>Decision & Prioritization</strong> — frameworks, decision matrices, and lightweight business case templates to choose what to try.</li> <li><strong>Experimentation & Measurement</strong> — hypothesis templates, experiment design checklists, and minimal metrics to learn fast.</li> <li><strong>Facilitation & Teamcraft</strong> — meeting designs, role sheets, and remote/onsite facilitation kits to run reliable sessions.</li> </ul> <h3>When to pick each toolbox (use cases & team composition)</h3> <div> <h4>User Research</h4> <p>Use when you need to replace assumptions with evidence. Good for early discovery and problem validation.</p> <p>Typical team: researcher or PO, a subject‑matter expert, a note taker; optional: designer or engineer for technical feasibility flags.</p> <h4>Systems Thinking</h4> <p>Use when problems recur, cross teams, or when root causes are unclear. Good for process, policy, or product ecosystems.</p> <p>Typical team: cross‑functional leads, data owner, process expert, facilitator.</p> <h4>Ideation & Creativity</h4> <p>Use when validated problems are ready for multiple solution directions. Good for widening options before narrowing.</p> <p>Typical team: product/design, operations, customer support, engineering, sales — varied perspectives help.</p> <h4>Decision & Prioritization</h4> <p>Use when you must choose what to build or test next under constraints (time, budget, risk).</p> <p>Typical team: decision owner, sponsor, finance/ops rep, technical lead.</p> <h4>Experimentation & Measurement</h4> <p>Use when you want to turn ideas into measurable learning. Good for minimum viable tests and pilots.</p> <p>Typical team: experiment owner, analyst, implementer, user recruiter.</p> <h4>Facilitation & Teamcraft</h4> <p>Use across all phases to keep workshops productive, inclusive, and accountable.</p> <p>Typical team: trained facilitator plus clear session owner and timekeeper.</p> </div> <h3>Starter checklists (quick links to toolbox artifacts)</h3> <p>Below are the minimal artifacts to get a useful session or experiment running quickly. Each item links to a full toolbox artifact you can copy and tailor.</p> <ul> <li><strong>User Research Starter:</strong> interview script, consent note, rapid synthesis template, two‑question recruitment screener.</li> <li><strong>Systems Thinking Starter:</strong> ecosystem map template, stakeholder inventory, simple causal loop sheet.</li> <li><strong>Ideation Starter:</strong> time‑boxed diverge/converge agenda, idea capture board template, 6‑up concept sketch format.</li> <li><strong>Decision Starter:</strong> decision criteria matrix, 1‑page option comparison, risk and dependency log.</li> <li><strong>Experiment Starter:</strong> hypothesis template, primary metric definition form, minimum viable experiment checklist.</li> <li><strong>Facilitation Starter:</strong> session plan template, participant roles sheet, icebreaker and closing templates for alignment and follow‑up.</li> </ul> <h3>Recommended sequencing & common integrations</h3> <p>Toolboxes are most useful when chained intentionally. A common, high‑value flow:</p> <ol> <li>Start with <em>User Research</em> to validate the problem with evidence.</li> <li>Use <em>Systems Thinking</em> to map causes and surface leverage points.</li> <li>Run an <em>Ideation</em> session focused on the highest‑leverage opportunities from the map.</li> <li>Apply <em>Decision & Prioritization</em> tools to pick 1–3 experiments.</li> <li>Design tests with the <em>Experimentation & Measurement</em> toolbox and define success metrics.</li> <li>Use <em>Facilitation</em> artifacts throughout to keep sessions actionable and ensure follow‑through.</li> </ol> <p>Integrations to watch for:</p> <ul> <li>Feed research synth outputs into systems maps so ideas target real constraints.</li> <li>Use decision matrices that include experiment cost and learning velocity, not only impact estimates.</li> <li>Make measurement templates compatible with your analytics tools (capture metric names and owners).</li> </ul> <h3>Quick navigation aid for facilitators and new team members</h3> <p>If you only have a minute to pick a toolbox, answer these questions:</p> <ul> <li>Do we need more evidence about users? → Open the <strong>User Research</strong> Starter.</li> <li>Is the problem repeating across teams or months? → Open <strong>Systems Thinking</strong>.</li> <li>Do we need many diverse options now? → Open <strong>Ideation & Creativity</strong>.</li> <li>Must we decide what to build or test first? → Open <strong>Decision & Prioritization</strong>.</li> <li>Do we want fast learning with measurable outcomes? → Open <strong>Experimentation & Measurement</strong>.</li> <li>Do we need to structure a meeting so people leave with commitments? → Open <strong>Facilitation & Teamcraft</strong>.</li> </ul> <h3>Common mistakes and how to avoid them</h3> <ul> <li>Running ideation without evidence — run a short research sprint first or surface assumptions clearly.</li> <li>Choosing ideas based on opinions — use explicit decision criteria and documented tradeoffs.</li> <li>Designing experiments without metrics — define a primary metric and an owner before launching.</li> <li>Using facilitation scripts without tailoring — adapt timing, language, and examples to context and culture.</li> </ul> <h3>How to adapt these toolboxes to your context</h3> <p>This collection is a starting point, not a prescription. Tailor each toolbox by doing three small things:</p> <ol> <li>Localize language and examples to your customers, industry, and team roles.</li> <li>Reduce artifacts to a minimal working set you will actually use and maintain.</li> <li>Assign clear owners for experiments, metrics, and follow‑up tasks so learning turns into action.</li> </ol> <h3>Where this fits in the Discovery & Innovation Hub</h3> <p>This index is the practical entry for people who want hands‑on methods. When you find a toolbox you like, copy the artifacts, run a pilot workshop, capture what changed, and iterate. Over time, a tailored set of toolboxes can become your team's operating playbook for discovery and experimentation.</p> <h3>Next steps (practical)</h3> <ul> <li>Pick one starter checklist above and run a 90‑minute pilot session next week.</li> <li>Record outcomes and metric definitions using the Experiment Starter so you can compare learning.</li> <li>If this becomes repeatable, adopt the toolbox as a local living kit: rename artifacts, assign owners, and version it.</li> </ul> <p><em>Image search phrase:</em> toolbox index</p> </section>