How to use the Dashboard requirements template

Start a board from it
Use this template opens a new Freero board with the Dashboard requirements template on it (sign up free first). On a board you already have, open Templates in the toolbar and search for “Dashboard requirements”.
Follow the instruction on the board
“Start from decisions, not charts: ask “what will you do differently when this number moves?”. Cut any chart nobody can answer that for.”
Fill in each part
- Who uses it The people who will open it, and how often.
- Decisions it supports What will they decide with it?
- Numbers it needs Each measure, defined in one line.
- Filters and detail How people slice it and what they drill into.
- Freshness and sources Where the data comes from and how current it must be.
- Out of scope What this dashboard will not do.
Bring your team and your agents
Invite people to the board or share a link, and work on it together live. The timer is in the top bar, private mode and voting in the board menu, and Claude or ChatGPT can join through Freero’s MCP server.

Work on it with an AI agent

Connect an assistant once and it works on the board with you, with your permissions: by default it reads and proposes, and people decide.

You ask: “Fill in the Dashboard requirements board from these notes.”
What happens It reads the board, then proposes sticky notes for it. Nothing changes until someone on the board accepts them.
You ask: “Group what we wrote into themes and list the actions.”
What happens It proposes clusters with a title each and task cards for the actions, labelled with its name and yours.

Metric definitions
One agreed definition per product metric: what it counts, how it’s calculated, its target, owner and where the data comes from.
Data pipeline map
Follow data from where it comes from to where it’s used: each stage, its owner, the checks and how fresh it is.
Domain events workshop
Map a business process as the events that happen in it, with the commands, people and rules around each one.
Feature flag rollout
Roll out a feature behind a flag in stages, with who sees it at each stage, what you watch and when you move on or back.
Bug bash plan
Organise an hour where everyone tries to break a feature before launch: scope, roles, test ideas, how to report and prizes.
Metric drop investigation
Work out why a key number suddenly changed, step by step: is it real, where is it, when did it start and what caused it.