Define the question before you build the dashboard.
Most dashboards fail because they answer the wrong question. Meridian's structured canvas and AI Mentor help you build a proper business case in about thirty minutes. So every product you build has a reason to exist.
Stop building dashboards nobody uses.
A stakeholder describes what they want in a meeting. The analyst interprets it. Three weeks later the dashboard is built, and neither party agrees it answers the right question. The requirements were never wrong. They were never written down properly.
Confluence pages and email threads capture words, not structure. Nobody challenges whether “improve visibility” is a measurable outcome or whether “the leadership team” is a specific enough audience. The misalignment is baked in before a single chart is built.
A structured canvas, not a blank page
Built on a human-centred design technique, the canvas turns a kickoff conversation into a structured brief. Your analyst fills it in after the meeting, or your stakeholder completes it directly. Either way, the gaps get surfaced before development starts, not three weeks into it.
Dashboard Name
A name that reflects value, not the data source. The AI rejects generic labels.
Problem Statement
The specific business question, with a measurable outcome, timeframe, and clear action.
Audience
A named role, a specific decision, and what they do the morning after viewing.
Desired Outcome
The organisational impact if this project succeeds. Not a technical description: a business outcome.
How Will It Work
Data sources, refresh cadence, and how the dashboard fits into the day-to-day workflow.
Risks to Success
Pre-mortem thinking. The AI suggests risks you may have missed based on your canvas.
What Do We Need to Test First
Your riskiest assumption, how you will validate it, and what success looks like.
What Does Success Look Like
Quantitative and qualitative measures. This field directly feeds your dashboard certification.
An AI that pushes back
The Mentor reads your canvas in real time and surfaces the weaknesses your team would normally catch three weeks into a failing project. Think of it as a team of domain experts in the room at the start: pushing back on vague audiences, flagging unmeasurable outcomes, and surfacing risks you had not considered.
Your team wrote "for the business." The Mentor asks: which business unit, which decision, which person?
"Improve efficiency" is not a KPI. It asks what number changes and by how much.
You listed three risks. Based on your data sources and problem statement, it suggests two more you had not considered.
Your success criteria from Field 08 will be used to certify the finished dashboard. The Mentor makes sure they are specific enough to assess against.
Three artefacts for your steering committee
Shareable brief
A structured document covering every canvas field. Hand it to your Head of Data or steering committee before development starts.
Layout mock-up
A visual mock-up of your dashboard structure, generated from the business case. A starting point that reflects the question you defined.
Certification baseline
Your success criteria carry forward to dashboard certification. When the finished dashboard is assessed, it is scored against the question you defined here.
Know exactly where your canvas is weak
Your canvas is scored across five dimensions so you see exactly what needs work. A score of 72 with weak Audience Clarity tells you something different than 72 with weak Measurability.
Specificity
Are answers specific to this project, or could they describe anything?
Measurability
Does the canvas contain objectively assessable success criteria?
Risk Coverage
Are risks plausible, specific, and connected to the problem?
Audience Clarity
Is the primary user a named role making a specific decision?
Downstream Readiness
Could a data engineer start building from this canvas alone?
Type a number between 0 and 100
75–100 Ready to build.
Strong enough to brief your team and start development.
50–74 Address before briefing.
Sharpen the flagged fields before committing engineering time.
<50 Pause the project.
Critical gaps in the business case need resolving before any build starts.
Start with the question
A strong business case takes twenty minutes. A misaligned dashboard takes three weeks to rebuild. Define the question first.
Request Early Access