Template

Trend Map Template & Watchlist

An interactive watchlist entry template to capture signals, evidence, triage decisions, and suggested experiments. Designed to turn weak signals into prioritized discovery questions and reusable opportunity briefs while supporting repeatable monitoring and ownership.

Interactive Tool

Trend Map Entry / Watchlist Row

Use this entry form to capture a signal, surface the evidence and implied hypotheses, and pick a triage lane with a suggested next step. The goal is to reduce noise, preserve context, and convert promising signals into testable research questions or small experiments. Fill what you know and return later as evidence arrives.

Quick triage guidance

  • Scouting — low evidence or early insight worth watching (keep cadence monthly or quarterly).
  • Watch — signal with some supporting evidence and plausible impact; schedule focused research or lightweight validation (weekly–monthly).
  • Active discovery — high confidence & impact or strategic fit; run small experiments, simulations, or partnerships (daily–weekly tracking).

Scoring tips: use the scales for confidence and potential impact. As a simple rule, consider Active discovery for entries scoring 4+ on both impact and confidence, Watch for mixed scores, and Scouting for low confidence or one-off signals. Adapt thresholds to your organization.

Write a concise description of the signal — e.g., 'AI-generated product descriptions reaching parity with human writers' or 'Local supplier adopts biodegradable packaging'.
YYYY-MM-DD or a short date description. Helpful for tracking when the signal emerged.
Where did this signal come from? Paste a URL, report title, event, person, or sensor ID.
Describe the evidence supporting the signal: sample size, repeated observations, vendor claims, pilot results, citations. Be specific about what has been observed vs. what is claimed.
1 = Very weak/no evidence, 3 = Some corroboration, 5 = Strong/repeatable evidence
1.0 10.0
1 = Minor/process tweak, 3 = Noticeable operational or product change, 5 = Strategic or business-model level impact
1.0 10.0
Who or what would be affected? Use roles, customer segments, product lines, or process names. Helps prioritize downstream experiments and stakeholders.
Turn the signal into 1–3 testable hypotheses. Example: 'If we deploy X, conversion will increase by Y%' or 'This supplier's packaging reduces waste by Z%.'
Concrete next steps: quick A/B tests, small pilots, simulations, customer interviews, or supplier audits. Include scope, a rough success criterion, and estimated duration if possible.
Choose how to handle this signal now.
How often should this entry be revisited or updated? Choose a cadence that matches the triage lane.
A practical immediate action to move the signal forward.
Person or team responsible for next steps and monitoring.
Anything else useful: budget constraints, compliance flags, dependencies, competitive intel.
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.