Template

Learning Loop Capture Template (Interactive)

An interactive, saveable template to capture experiment context, hypothesis, metrics, outcomes, insights, decisions, and recommended next steps — plus a short facilitator guide and publication controls for durable organizational learning.

Interactive Tool

Learning Loop Capture

Purpose

Use this Learning Loop Capture form to turn experiments, pilots, and local discoveries into durable organizational knowledge. Capture enough context so others can understand what you tried, why, what happened, and what to do next. Save the record to your knowledge base and assign clear follow-up ownership.

How to use

  1. Fill the required fields with concise factual details.
  2. Use bullet points in the 'What we learned' area — short, actionable statements.
  3. Choose a decision (adopt/adapt/reject) and assign follow-up ownership and a review rhythm.
  4. Attach or link to artifacts (reports, dashboards, code, playbooks) in the related artifacts field.

Quick example

Experiment summary: A/B test new onboarding email flow for first-week retention. Hypothesis: Personalized onboarding increases week-1 retention by 10%. Metrics & outcomes: Week-1 retention: 24% (control) vs 28% (variant). Decision: Adapt and roll out with minor content changes. Owner: Growth Lead.

Short, factual description of the experiment, project, pilot, or change. Include scope and context. (Required)
State the testable hypothesis in plain language. If possible, include the expected measurable change.
Person responsible for the experiment and this record. Use full name and role.
Start date (YYYY-MM-DD). Use text field for portability.
End date (YYYY-MM-DD) or current if ongoing.
List the primary metrics tracked and their measured values. Include baseline and variant values where relevant.
How confident are you in the result (data quality, sample size, confounders)? 1 = low, 5 = high.
1.0 10.0
Write 3–6 short, actionable learning statements. Prefer clarity over narrative. These become the reusable lessons.
Choose the immediate decision about the experiment results.
Explain why this decision was made and any conditions or caveats.
Person or role accountable for follow-up actions and publishing results. (Required)
Concrete next steps with owners and due dates where possible. Use short action-oriented items.
Target date for the next action or review (YYYY-MM-DD).
How often should the outcome be reviewed or revalidated?
Paste links to reports, dashboards, code, playbooks, or attachments. Prefer stable URLs.
Comma-separated tags to help others find this learning (e.g., onboarding, retention, email, personalization).
Where might this learning apply? List teams, products, processes, or sites that may benefit.
If yes, this record will be marked for publication review. Publication workflows may vary by organization.
Control who initially sees this record.
Short prompts to guide a 15–30 minute debrief: What surprised us? Which assumptions were wrong? What should we stop doing? Who needs to know?
Date of the post-experiment debrief (YYYY-MM-DD).
Who attended the debrief (names and roles).
Optional guidance for the person who curates or publishes this record (taxonomy, suggested collection, sensitivity, retention policy).
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.