The product

What Evidence Bank does

Four stages, one thread. Each record links back to the evidence behind it, so any decision can be traced to what the team actually observed.

  1. 01

    Capture what the team hears

    Evidence is one observation: something a customer said, a pattern in the analytics, a support ticket, a complaint, or a request from an employer or the commercial team. It takes under a minute, and the source stays attached so anyone can check it.

    • Paste an interview transcript and get suggested observations to review — nothing saves until you confirm.
    • Every record carries its source, date, product, theme and audience.
    • New items land in a review queue so nothing sits unread.
  2. 02

    Find the patterns on a board

    A board is your evidence as sticky notes on a canvas, grouped by theme, product, source type or review status. Cluster it with other people in a workshop, then turn a cluster straight into an insight.

    • Group by source type to see when a theme rests on one channel alone.
    • Select a column or drag a box around a cluster, then create the insight from it.
    • Copy the board into Figma or FigJam when the workshop needs to happen there.
  3. 03

    Frame the problem, with the evidence attached

    An opportunity says what the problem is, who it affects, what supports it and what you still need to find out. The open questions are answered in place, and the decision is recorded with its reason.

    • Ready to decide is derived: it has support, its questions are answered and it has an owner.
    • Decisions are a dated history — keep investigating, commit, stop or park, each with a reason.
    • Committing creates a draft bet and carries the evidence trail across.
  4. 04

    Commit, then come back

    A bet records the hypothesis, the change, and the measure that would tell you it worked — baseline, target and a date to look again. When results are due, you record the outcome against the target.

    • A measure needs a target, so a result can be judged rather than admired.
    • Outcomes capture what happened, what was learned and the next decision.
    • A missed target is kept, because it stops the next team repeating it.

Also in the box

The rest of it

Ask a question

Ask Evidence Bank answers in plain language from your own records, and shows every record it used.

Search by meaning

Searching “worried about money” finds the evidence about affordability, whether or not it uses those words.

Teams

Each team has its own evidence, categories, people and admins. Nothing is shared between them.

Boards

A canvas view of the evidence for workshops, with a Figma export for when the session moves there.

Coverage

Themes against products, so the gaps — the questions nobody has evidence for — are visible.

Roles

Editors capture and decide. The wider business can read everything and send things in.

Try it with a team of your own

Starting a team takes a minute, and it comes with nothing in it but your own categories.