Create KPI Dashboards

Act as a senior business intelligence analyst and KPI dashboard designer.

Your objective is to design a clear, decision-ready KPI dashboard for the specified business department. The dashboard must help its users understand current performance, compare results over time, identify problems early and decide what action to take next.

Do not create a generic list of metrics. Every KPI, visualization and dashboard section must connect directly to the supplied business goals.

INPUT VARIABLES

Business department:
[BUSINESS DEPARTMENT]

Specific business goals:
[SPECIFIC BUSINESS GOALS]

Preferred number of dashboard columns:
[NUMBER OF DASHBOARD COLUMNS]

Required KPI names:
[REQUIRED KPI NAMES]

WORKING RULES

- Use the supplied variables as the foundation of the dashboard.
- Do not invent performance results, targets, benchmarks or data availability.
- Clearly separate supplied facts, recommendations and assumptions.
- Retain all relevant KPIs provided under Required KPI Names.
- Recommend additional KPIs only when they directly support the stated goals.
- Explain why each recommended KPI is useful.
- Distinguish leading indicators from lagging indicators.
- Prefer a dashboard that a solo operator or small team can realistically maintain.
- If essential information is missing, ask up to four focused questions before creating the dashboard.
- If the information is sufficient, proceed without unnecessary questions.

DASHBOARD DESIGN PROCESS

Step 1: Understand the business context

Review the business department and its specific goals. Translate each goal into the decisions the dashboard must help its users make.

Identify:

- The primary dashboard audience
- The decisions they need to make
- The reporting period that would be useful
- The level of detail required
- Any missing context that may affect the dashboard design

Step 2: Evaluate the KPIs

Review every supplied KPI and determine:

- What business question it answers
- Which goal it supports
- Whether it is a leading or lagging indicator
- How frequently it should be reviewed
- Whether it can lead to a practical action

If a supplied KPI is unclear, redundant or not connected to a goal, retain it but flag the issue and recommend an improvement.

Step 3: Define each KPI

For every supplied or recommended KPI, specify:

- KPI name
- Business purpose
- Calculation or formula
- Required data
- Likely data source
- Reporting frequency
- Responsible owner
- Target or threshold
- Comparison period
- Recommended visualization
- Action to take when performance is outside the expected range

Never invent a formula when the KPI definition depends on information that has not been supplied. Mark it as requiring confirmation.

Step 4: Design the dashboard layout

Create a dashboard layout using the requested number of columns.

Arrange the information in a logical visual hierarchy:

1. Place the most important headline indicators first.
2. Group related KPIs together.
3. Separate summary metrics from diagnostic details.
4. Make warnings and performance exceptions easy to notice.
5. Keep supporting information available without overwhelming the main view.

Describe what should appear in every row and column. Explain the purpose of each dashboard section.

Step 5: Select visualizations

Choose the clearest visualization for every KPI.

Consider:

- Scorecards for headline values
- Line charts for trends over time
- Bar charts for category comparisons
- Stacked charts for composition
- Tables for detailed operational data
- Progress indicators for goals
- Funnel charts for stage conversion
- Heatmaps for patterns across periods or segments

Avoid decorative charts. Explain why the selected visualization is appropriate for the KPI and decision being supported.

Step 6: Define interactions

Recommend useful filters, comparisons and drill-down options.

Possible controls include:

- Date range
- Team or owner
- Product or service
- Region
- Customer segment
- Marketing or sales channel
- Current period versus previous period
- Actual performance versus target

Only include interactions that help users answer a meaningful business question.

REQUIRED OUTPUT

1. DASHBOARD SUMMARY

Provide:

- Business department
- Stated business goals
- Intended dashboard audience
- Decisions the dashboard will support
- Recommended reporting frequency

2. KPI DEFINITION TABLE

Create a table with these columns:

- KPI
- Goal supported
- KPI type
- Formula
- Data source
- Frequency
- Owner
- Target
- Visualization
- Recommended action

3. DASHBOARD LAYOUT

Describe the proposed dashboard row by row and column by column, using the requested number of columns.

For every dashboard component, include:

- Position
- KPI or content displayed
- Visualization
- Purpose
- Related interaction or drill-down

4. FILTERS AND INTERACTIONS

List the recommended filters, comparisons and drill-down paths. Explain what question each control helps answer.

5. DATA REQUIREMENTS

List:

- Required data fields
- Suggested data sources
- Missing information
- Data-quality risks
- Calculations requiring confirmation
- Recommended refresh frequency

6. IMPLEMENTATION GUIDANCE

Provide:

- The recommended build order
- The minimum viable first version
- Metrics that can be added later
- Validation checks before launch
- A practical dashboard-review schedule

7. FINAL QUALITY CHECK

Confirm that:

- Every KPI supports a stated business goal
- Every visualization has a decision-making purpose
- The requested KPIs have been included
- The layout follows the requested column count
- Assumptions and missing information are clearly marked
- The dashboard can be maintained with the likely available resources

Use descriptive headings, concise explanations and readable tables. Produce a practical dashboard specification that can be handed directly to someone building it in Excel, Google Sheets, Looker Studio, Power BI, Tableau or another business intelligence tool.