Summary
A good dashboard request starts with a clear question, not a list of fields. This article explains how KTS scopes and builds dashboards in Metabase, and what to send us when you are ready to ask.
Who this is for
Anyone responsible for reporting, performance, or KPIs who wants a new dashboard built, or an existing dashboard changed.
What to think about first
Before sending the request, try to answer:
-
What decision will this dashboard support? For example, "should we hire another person on the support desk?"
-
Who will use it? A single manager, a team, or leadership
-
How often will they look at it? Daily, weekly, monthly
-
What would make it successful? A specific question you want to answer each time you open it
What to send to KTS
-
A short description of the decision or question
-
The main audience
-
The time period you care about, for example last 30 days or year to date
-
The data source, if you know it, for example "our CRM" or "our helpdesk tool"
-
Any sample numbers you already track manually
You do not need to know field names or have a mockup. KTS will work with you to clarify the detail.
What KTS will do next
-
Acknowledge the request and assign it to the IaaS team
-
Confirm the data source is available and reachable
-
Propose a scope for a first version
-
Build a first draft in Metabase
-
Review it with you and refine based on feedback
Important
Dashboards are most useful when they answer a clear question. Avoid asking for "everything we have" - this usually leads to a slow, confusing dashboard nobody opens.
When to contact the service desk
Contact the service desk when you are ready to submit the request or if you want help scoping it before you send it in.