Collection

Reusable Templates Index & Quickstart Pack

An indexed, practical starter pack of discovery and experiment templates with clear use guidance, a three‑template quickstart checklist, and governance tips to help teams copy, adapt, and run discovery cycles faster without losing local ownership or evidence capture.

Welcome — Start discovery faster

This pack is the first stop for teams running discovery, experiments, or small innovation cycles. It collects proven starter templates (briefs, hypotheses, experiment plans, business cases, reports) with short guidance on when and how to use each, links to related playbooks or decks, and a brief quickstart checklist that helps a team begin a first discovery cycle in hours instead of days.

How to use this index

  • Scan the quickstart checklist if you’re ready to run something immediately.
  • Open an individual template to see purpose, required inputs, suggested outputs, and tailoring notes.
  • Copy a template into your team space, adapt the fields to local context, and capture evidence and outcomes during the experiment.

Quickstart checklist — 3 templates to launch a discovery cycle

  1. Discovery Brief — capture scope, target users, business outcomes, and constraints. Action: complete in a 30–60 minute kickoff.
  2. Hypothesis Card — state the assumption you will test, the measures that matter, and the minimum viable experiment. Action: write 1–2 testable hypotheses from the brief.
  3. Experiment Plan (Concise) — define the experiment method, timeline, required resources, acceptance criteria, and how evidence will be recorded. Action: run or schedule a timeboxed pilot (1–4 weeks depending on scope).

Completing these three artifacts gives teams a rapid discovery backbone: why you’re doing this, what you expect to learn, and how you will measure it.

Catalog — key templates and when to use them

Each entry below links to the template and includes recommended use, minimum inputs, and expected outputs. Use tags (risk, customer, tech, cost, compliance) to filter templates for your context.

Discovery Brief

When to use: At project kickoff or before committing budget. Use to align stakeholders and limit scope.

Minimum inputs: problem statement, target user, stakeholders, timebox, constraints.

Outputs: one-page brief, success criteria, owner.

Hypothesis Card

When to use: After you have a brief and at least one testable assumption.

Minimum inputs: hypothesis statement (if X, then Y), primary metric, neutral/alternative outcomes.

Outputs: prioritized hypotheses list and measurement approach.

Experiment Plan (Concise)

When to use: Before running any live test or pilot. Prefer concise plans that are easy to execute.

Minimum inputs: method, sample, timeline, artifacts, success criteria, data collection plan.

Outputs: step-by-step runbook and evidence log.

Business Case (Lite)

When to use: To request funding or senior approval for a scaled pilot; keeps focus on benefits, costs, risks, and measurable outcomes.

Minimum inputs: benefits estimate, cost estimate, timeline, risk summary, go/no-go criteria.

Evidence Report & Learnings

When to use: After an experiment completes. Summarizes findings, decisions, next steps, and evidence artifacts (data, recordings, customer quotes).

Minimum inputs: experiment plan, raw evidence, metric comparisons, interpretation, recommended decision.

Outputs: short report and decision record suitable for archiving.

Stakeholder Briefing Slide Kit

When to use: To present progress, findings, or funding requests to leaders or partners. Designed for clarity and action—one idea per slide.

Tailoring and governance

Templates are starting points, not policies. Follow three simple rules when adapting:

  1. Keep the core purpose and acceptance criteria intact so evidence stays comparable across teams.
  2. Capture any changes and the rationale in a local governance field (who changed it, why, and when).
  3. Review tailored templates periodically (recommended every 6–12 months) to retire outdated fields or re-align with enterprise standards.

One-click copy & recommended habits

How to copy a template for your team: use the platform copy/subscription feature to create an owned copy in your team domain, rename it, and update required metadata (owner, tags, review cadence). After copying, run the quickstart checklist and link the resulting evidence to the template instance.

Useful habits:

  • Keep templates short and field-focused—teams will fill them more reliably.
  • Always attach evidence (raw data, screenshots, recordings) rather than only conclusions.
  • Tag templates with the problem domain, technology, and risk level to make future discovery easier.

Preserve learning — archiving and reuse

When an experiment ends, create an Evidence Report and link it back to the original templates. Add a short lessons-learned snapshot to the team’s knowledge base and tag it so other teams can find similar cases later.

Related playbooks and decks

Each template links to recommended playbooks: experiment design, user interviews, quick analytics, and stakeholder engagement. Use them to scale practice across your organization.

Starter metadata recommended for every copied template

  • Owner
  • Team / location
  • Problem domain / tags
  • Review cadence (e.g., 6 months)
  • Link to Evidence Report(s)

Next steps

Pick the three quickstart templates, copy them into your team space, and schedule a 60‑minute kickoff to fill the Discovery Brief. If you want, run a pilot experiment within the timebox specified in your Experiment Plan and publish an Evidence Report afterwards.

Want this pack tailored to your organization? Consider creating an owned collection that includes tailored templates, standard metadata, and an agreed review cadence so your site or enterprise can operate consistently while preserving local flexibility.

Discuss Ask the Librarian

Discussion

Comments and conversation will live here.