Prompts for KPI and Dashboard Design

18 ready-to-use ChatGPT prompts for KPI and dashboard design. Fill in the bracketed fields, paste into ChatGPT, and go.

Data & Finance · 18 prompts

01

Design a KPI Framework That Avoids Vanity Metrics

Design a KPI framework with metric purpose, ownership, leading indicators, and misuse guardrails.

You’ll needbusiness modelteam or functiongoalsexisting metricsdecision cadenceknown metric problems
Prompt
You are designing a KPI framework.

Use the context below.

Context:
- Business model: [business model]
- Team or function: [team]
- Goals: [goals]
- Existing metrics: [existing metrics]
- Decision cadence: [cadence]
- Known metric problems: [problems]

Instructions:
1. Define the core KPI layers needed for this context.
2. Distinguish leading indicators from lagging outcomes.
3. Assign ownership and decision use for each metric.
4. Flag vanity metrics and measurement traps.
5. Keep the framework operational rather than theoretical.

Output format:
- KPI framework overview
- Metric table with purpose and owner
- Leading vs lagging indicator map
- Guardrails and misuse risks

Missing information policy:
Ask up to 2 concise questions only if the goals or team context are unclear.

Quality bar:
- Clear decision linkage.
- Ownership clarity.
- No vanity metric drift.
02

Create a Dashboard Specification Template

Create a dashboard specification template covering audience, metrics, filters, decisions, and data definitions.

You’ll needdashboard audiencebusiness areadecision use casesmetrics neededdata sourcesrefresh cadence
Prompt
You are creating a dashboard specification template.

Use the context below.

Context:
- Dashboard audience: [audience]
- Business area: [business area]
- Decision use cases: [use cases]
- Metrics needed: [metrics]
- Data sources: [data sources]
- Refresh cadence: [cadence]

Instructions:
1. Build a template that clarifies what the dashboard is for before it is built.
2. Include business questions, metric definitions, filters, and ownership fields.
3. Prevent ambiguous metric requests from slipping through.
4. Keep the structure practical for BI or analyst handoff.
5. Include validation and adoption notes.

Output format:
- Dashboard specification template
- Required definition fields
- Handoff and validation notes

Missing information policy:
Proceed with assumptions unless the audience or use cases are unclear.

Quality bar:
- Build-ready.
- Strong metric definition fields.
- Good analyst handoff.
03

Review a Dashboard for Signal, Clarity, and Decision Value

Review a dashboard for metric signal quality, visual clarity, hierarchy, and decision usefulness.

You’ll needdashboard description or screenshot notesaudiencemain use casesmetrics shownpain pointsrefresh cadence
Prompt
You are reviewing a KPI dashboard.

Use the context below.

Context:
- Dashboard description or screenshot notes: [dashboard]
- Audience: [audience]
- Main use cases: [use cases]
- Metrics shown: [metrics]
- Pain points: [pain points]
- Refresh cadence: [cadence]

Instructions:
1. Evaluate whether the dashboard surfaces the right signals.
2. Identify clutter, weak hierarchy, or missing decision context.
3. Flag metrics that do not earn their place.
4. Recommend structural and content changes that improve usefulness.
5. Keep the review tied to user decisions, not aesthetics alone.

Output format:
- Overall dashboard assessment
- Signal and clarity issues
- Metrics to remove, revise, or highlight
- Recommended structural changes

Missing information policy:
Ask first only if the dashboard description is missing.

Quality bar:
- Decision-centered review.
- Clear prioritization.
- Useful structural recommendations.
04

Build a Balanced Scorecard for a Team or Business Unit

Build a balanced scorecard with strategic objectives, measure groups, and review logic across performance areas.

You’ll needteam or unitstrategic goalstime horizonstakeholdersexisting reportingpain points
Prompt
You are designing a balanced scorecard.

Use the context below.

Context:
- Team or business unit: [team]
- Strategic goals: [goals]
- Time horizon: [time horizon]
- Stakeholders: [stakeholders]
- Existing reporting: [existing reporting]
- Pain points: [pain points]

Instructions:
1. Recommend the right scorecard dimensions for this context.
2. Map measures to strategic objectives rather than collecting metrics for their own sake.
3. Define how the scorecard should be reviewed and updated.
4. Keep the scorecard manageable.
5. Flag where the scorecard could become too broad or too shallow.

Output format:
- Scorecard design overview
- Objective-to-measure map
- Review cadence
- Risks and simplification notes

Missing information policy:
Proceed with assumptions unless the strategic goals or team context are unclear.

Quality bar:
- Strategy-linked measures.
- Manageable scope.
- Clear review logic.
05

Create a KPI Definition Sheet for Cross-Functional Teams

Create a KPI definition sheet with formulas, owners, caveats, data sources, and interpretation notes.

You’ll needmetrics to defineteams involveddata sourcescommon confusion pointsreporting cadence
Prompt
You are creating a KPI definition sheet.

Use the context below.

Context:
- Metrics to define: [metrics]
- Teams involved: [teams]
- Data sources: [data sources]
- Common confusion points: [confusion]
- Reporting cadence: [cadence]

Instructions:
1. Build a definition sheet that reduces metric ambiguity.
2. Include formulas, owners, source systems, caveats, and interpretation notes.
3. Distinguish calculation rules from business interpretation.
4. Flag where metric definitions may still require stakeholder agreement.
5. Keep the format usable for recurring reference.

Output format:
- KPI definition sheet template
- Required fields
- Notes on governance and update ownership

Missing information policy:
Proceed with assumptions unless the metrics or teams involved are unclear.

Quality bar:
- Clear calculation fields.
- Governance-aware.
- Easy to reference.
06

Review an Executive Dashboard for Missing or Misleading Metrics

Evaluate an executive dashboard for gaps, misleading measures, weak definitions, and missing context.

You’ll needdashboard or metric listbusiness modelleadership audiencedecisions the dashboard should supportknown reporting pain points
Prompt
You are reviewing an executive dashboard for decision usefulness.

Use the context below.

Context:
- Dashboard, scorecard, or metric list: [dashboard]
- Business model or operating context: [business model]
- Leadership audience: [audience]
- Decisions the dashboard should support: [decisions]
- Known reporting pain points: [pain points]

Instructions:
1. Evaluate whether the dashboard helps leadership make better decisions.
2. Identify missing metrics, misleading proxies, and areas where context is too thin.
3. Flag where definitions, denominators, or time windows may distort interpretation.
4. Recommend what to add, remove, combine, or reframe.
5. Keep the review practical for a real reporting workflow.

Output format:
- Dashboard usefulness assessment
- Missing or weak metrics
- Misleading or risky measures
- Recommended changes
- Open definition or governance issues

Missing information policy:
Proceed with assumptions unless the dashboard or decision purpose is unclear.

Quality bar:
- Decision-oriented review.
- Definition-aware critique.
- Practical reporting improvements.
07

Review a KPI Set for Metric Overload and Weak Signal

Review a KPI set for metric overload, weak signal, duplication, and unclear decision usefulness.

You’ll needcurrent KPI setbusiness contextaudiencedecision useknown confusionreporting cadence
Prompt
You are reviewing a KPI set for overload and weak signal.

Use the context below.

Context:
- Current KPI set or scorecard: [kpis]
- Business context: [business context]
- Intended audience: [audience]
- Decisions the KPIs are supposed to support: [decisions]
- Known confusion or reporting pain points: [confusion]
- Reporting cadence: [cadence]

Instructions:
1. Identify where the KPI set is too broad, duplicative, or weakly tied to decisions.
2. Distinguish primary business signal from supporting diagnostics.
3. Flag metrics that create noise, vanity, or false precision.
4. Recommend what to keep, combine, downgrade, or remove.
5. Keep the review practical for an actual reporting system.

Output format:
- KPI set assessment
- Metrics creating overload or weak signal
- Metrics to keep as primary
- Recommended reductions or restructuring
- Risks if unchanged

Missing information policy:
Proceed with assumptions unless the KPI set or decision use is unclear.

Quality bar:
- Signal prioritization.
- Decision usefulness.
- Practical simplification guidance.
08

Design Drill-Down Logic for an Executive Dashboard

Design drill-down logic for an executive dashboard so leaders can move from top-line signal to root-cause detail cleanly.

You’ll needheadline metricsavailable detail layersleadership audiencedecision needsreporting pain pointstool constraints
Prompt
You are designing drill-down logic for an executive dashboard.

Use the context below.

Context:
- Headline metrics or top-line dashboard view: [headline metrics]
- Available detail layers or supporting data: [detail layers]
- Leadership audience: [audience]
- Decision needs: [decisions]
- Reporting pain points: [pain points]
- Tool or implementation constraints: [constraints]

Instructions:
1. Define how leaders should move from headline signal into the right diagnostic detail.
2. Clarify which questions each layer of the dashboard should answer.
3. Prevent drill paths that create clutter or dead-end browsing.
4. Keep the structure aligned to decisions, not raw database structure.
5. Recommend where summary should stop and deeper analysis should begin elsewhere.

Output format:
- Drill-down logic overview
- Headline-to-detail map
- Questions answered at each layer
- Risks or clutter traps
- Recommended next design moves

Missing information policy:
Proceed with assumptions unless the headline metrics or decision needs are unclear.

Quality bar:
- Decision-aligned drill paths.
- Clean signal hierarchy.
- Practical dashboard structure.
09

Build a Leadership Metric Watchlist with Triggers and Follow-Ups

Build a leadership metric watchlist with trigger levels, likely implications, and follow-up actions.

You’ll needmetrics to watchbusiness contexttrigger logicknown risksownersreview cadence
Prompt
You are building a leadership metric watchlist.

Use the context below.

Context:
- Metrics to watch: [metrics]
- Business context: [business context]
- Trigger logic or rough thresholds: [triggers]
- Known risks tied to these metrics: [risks]
- Owners or teams connected to the metrics: [owners]
- Review cadence: [cadence]

Instructions:
1. Define which metrics belong on the watchlist and why.
2. Clarify what movement should trigger attention, questions, or follow-up.
3. Distinguish normal variation from risk-bearing changes.
4. Recommend who should respond and what they should check next.
5. Keep the watchlist selective and operational.

Output format:
- Metric watchlist overview
- Trigger conditions
- Likely implications by metric
- Follow-up actions and owners
- Review notes

Missing information policy:
Proceed with assumptions unless the metrics or business context are unclear.

Quality bar:
- Selective watchlist.
- Clear triggers.
- Operational follow-up logic.
10

Review Whether Teams Are Optimizing to the Wrong Metrics

Review whether teams are optimizing to the wrong metrics and identify better measures or balancing signals.

You’ll needcurrent team metricsbusiness goalsobserved behaviorknown distortionsstakeholdersdecision context
Prompt
You are reviewing whether teams are optimizing to the wrong metrics.

Use the context below.

Context:
- Current team metrics or scorecards: [metrics]
- Business goals these metrics are meant to support: [goals]
- Observed behavior or local optimization patterns: [behavior]
- Known distortions, complaints, or unintended effects: [distortions]
- Stakeholders involved: [stakeholders]
- Decision context: [decision context]

Instructions:
1. Assess whether the current metrics are steering behavior in the wrong direction.
2. Identify where local optimization is fighting broader business outcomes.
3. Distinguish bad metric design from poor management usage.
4. Recommend better measures, balancing metrics, or review logic.
5. Keep the review tied to behavior and incentives, not metric theory alone.

Output format:
- Metric alignment assessment
- Signs of misoptimization
- Likely causes
- Better metric or review design
- Risks if unchanged

Missing information policy:
Proceed with assumptions unless the current metrics or business goals are unclear.

Quality bar:
- Behavior and incentive aware.
- Clear misalignment diagnosis.
- Practical fixes.
11

Review Conflicting Metric Definitions Across Teams

Review conflicting metric definitions across teams and recommend harmonization, governance, and caveat handling.

You’ll needconflicting metric definitionsteams involvedcurrent reporting usageknown disputesdecision impactgovernance context
Prompt
You are reviewing conflicting metric definitions across teams.

Use the context below.

Context:
- Conflicting metric definitions or formulas: [definitions]
- Teams involved: [teams]
- Current reporting usage: [usage]
- Known disputes or confusion: [disputes]
- Decision impact of the conflict: [impact]
- Governance or ownership context: [governance]

Instructions:
1. Clarify where the definitions conflict and why that matters operationally.
2. Distinguish harmless variation from definition drift that breaks trust or decisions.
3. Recommend a harmonization path or a clear caveat structure where full alignment is unrealistic.
4. Note ownership and governance requirements.
5. Keep the review practical for teams that need to keep reporting while fixing the issue.

Output format:
- Definition-conflict summary
- Where the conflicts matter most
- Harmonization or caveat recommendations
- Ownership and governance notes
- Risks if unresolved

Missing information policy:
Proceed with assumptions unless the conflicting definitions or teams involved are unclear.

Quality bar:
- Operational consequence awareness.
- Practical harmonization path.
- Clear governance implications.
12

Build a Spend Watchlist with Thresholds and Follow-Up Logic

Build a spend watchlist with thresholds, likely causes, and follow-up logic for finance and leadership review.

You’ll needspend categoriesbudget contextthreshold ideasownersreview cadenceknown volatility
Prompt
You are building a spend watchlist with thresholds and follow-up logic.

Use the context below.

Context:
- Spend categories or lines to watch: [categories]
- Budget or planning context: [budget context]
- Threshold ideas or concern triggers: [thresholds]
- Owners or teams attached to the spend: [owners]
- Review cadence: [cadence]
- Known volatility or seasonality: [volatility]

Instructions:
1. Select the spend areas that belong on an active watchlist.
2. Define thresholds or patterns that should trigger follow-up.
3. Distinguish normal variance from spending that deserves attention.
4. Recommend who should review each item and what they should check next.
5. Keep the watchlist operational rather than exhaustive.

Output format:
- Spend watchlist
- Thresholds or trigger patterns
- Owners and follow-up checks
- Items to monitor but not escalate

Missing information policy:
Proceed with assumptions unless the spend categories or planning context are unclear.

Quality bar:
- Selective watchlist.
- Sensible trigger logic.
- Actionable follow-up.
13

Review a Finance Dashboard for Clutter and Weak Hierarchy

Review a finance dashboard for clutter, weak hierarchy, confusing grouping, and poor decision support.

You’ll needdashboard layout or metric listaudiencereview use caseknown confusionavailable drill-downsbusiness context
Prompt
You are reviewing a finance dashboard for clutter and weak hierarchy.

Use the context below.

Context:
- Dashboard layout, sections, or metric list: [dashboard]
- Audience: [audience]
- Review use case or decisions it should support: [use case]
- Known confusion or dashboard complaints: [confusion]
- Available drill-downs or supporting detail: [drill-downs]
- Business context: [business context]

Instructions:
1. Assess whether the dashboard surfaces the right signal in the right order.
2. Identify clutter, duplication, weak grouping, or visual hierarchy problems.
3. Clarify where the dashboard is forcing too much interpretation work onto the reader.
4. Recommend the highest-leverage simplifications first.
5. Keep the review grounded in actual leadership use.

Output format:
- Dashboard review summary
- Clutter or hierarchy issues
- Grouping and interpretation problems
- Recommended improvements
- Risks if unchanged

Missing information policy:
Proceed with assumptions unless the dashboard or use case are unclear.

Quality bar:
- Signal hierarchy focus.
- Reader-interpretation awareness.
- Practical simplification guidance.
14

Review Whether Current KPIs Are Too Lagging to Be Useful

Review whether current KPIs are too lagging to be useful and identify stronger leading indicators or balancing signals.

You’ll needcurrent KPIsbusiness modeldecision timingknown surprisesoperators using themconstraints
Prompt
You are reviewing whether current KPIs are too lagging to be useful.

Use the context below.

Context:
- Current KPIs or scorecard: [kpis]
- Business model or context: [business model]
- Decision timing or action horizon: [timing]
- Known surprises or things the KPIs failed to warn about: [surprises]
- Operators or leaders using the KPIs: [operators]
- Constraints: [constraints]

Instructions:
1. Assess whether the KPIs help the team act early enough.
2. Distinguish lagging confirmation metrics from indicators that can shape decisions sooner.
3. Surface where the current set may be too backward-looking.
4. Recommend leading indicators, balancing signals, or better review logic.
5. Keep the review practical for real reporting.

Output format:
- KPI usefulness review
- Where the set is too lagging
- Better leading indicators
- Review logic improvements
- Risks if unchanged

Missing information policy:
Proceed with assumptions unless the current KPIs or decision timing are unclear.

Quality bar:
- Early-warning focus.
- Practical indicator suggestions.
- Reporting realism.
15

Plan Dashboard Governance for Ongoing Quality

Plan dashboard governance with ownership, definition control, refresh discipline, and change-management rules.

You’ll needdashboard setaudiencesdata ownersmetric change issuesrefresh cadencegovernance maturity
Prompt
You are planning dashboard governance.

Use the context below.

Context:
- Dashboard set or reporting environment: [dashboards]
- Audiences: [audiences]
- Data or metric owners: [owners]
- Current metric change issues: [issues]
- Refresh cadence: [cadence]
- Governance maturity: [maturity]

Instructions:
1. Define the minimum governance structure needed to keep dashboards trustworthy.
2. Clarify ownership for metric definitions, data quality, and change approval.
3. Include review cadence, archive logic, and stale-dashboard cleanup.
4. Keep the system pragmatic rather than bureaucratic.
5. Distinguish governance of content from governance of tooling.

Output format:
- Governance model
- Ownership structure
- Review and change-control process
- Maintenance and cleanup rules

Missing information policy:
Proceed with assumptions unless the dashboard environment or ownership context is unclear.

Quality bar:
- Trustworthy governance.
- Clear ownership.
- Pragmatic process.
16

Create a KPI Ownership and Review Matrix

Create a KPI ownership and review matrix with owners, definitions, cadences, thresholds, and action expectations.

You’ll needmetricsteams involvedreview cadencesdecision forumsknown ownership confusion
Prompt
You are creating a KPI ownership and review matrix.

Use the context below.

Context:
- Metrics to include: [metrics]
- Teams involved: [teams]
- Review cadences: [cadences]
- Decision forums or meetings: [forums]
- Known ownership confusion: [confusion]

Instructions:
1. Build a matrix that clarifies who owns definition, data quality, review, and action.
2. Include review cadence and threshold or escalation notes where helpful.
3. Distinguish passive visibility from real ownership.
4. Keep the matrix practical enough for operating teams to use.
5. Include notes on where governance still needs agreement.

Output format:
- KPI ownership matrix
- Field explanations
- Governance notes

Missing information policy:
Proceed with assumptions unless the metric list or teams involved are unclear.

Quality bar:
- Clear ownership.
- Review and action clarity.
- Practical matrix structure.
17

Review a Metric Set for Redundancy and Blind Spots

Review a metric set for redundancy, blind spots, weak leading indicators, and decision misalignment.

You’ll needcurrent metricsbusiness goalsaudiencedecision cadenceknown reporting pain points
Prompt
You are reviewing a KPI set rather than a single dashboard.

Use the context below.

Context:
- Current metrics: [metrics]
- Business goals: [goals]
- Audience: [audience]
- Decision cadence: [cadence]
- Known reporting pain points: [pain points]

Instructions:
1. Identify which metrics are overlapping, noisy, or low-value.
2. Flag blind spots where important business dynamics are not being measured well.
3. Check whether the set has useful leading indicators.
4. Recommend what to remove, combine, add, or redefine.
5. Keep the review tied to decisions and management use.

Output format:
- Metric-set assessment
- Redundant or weak metrics
- Blind spots and missing measures
- Recommended changes

Missing information policy:
Ask first only if the current metrics are missing.

Quality bar:
- Decision alignment.
- Redundancy scrutiny.
- Strong blind-spot analysis.
18

Design a Financial Dashboard Blueprint for a Nonprofit

Design a nonprofit financial dashboard blueprint with mission-relevant KPIs, budget-versus-actual logic, and restricted-funds visibility.

You’ll neednonprofit typeannual budget sizeleadership audiencefunding modelreporting cadenceknown oversight needs
Prompt
You are designing a financial dashboard blueprint for a nonprofit.

Use the context below.

Context:
- Nonprofit or organization type: [organization]
- Annual budget size or scale: [budget]
- Leadership or board audience: [audience]
- Funding model or revenue mix: [funding]
- Reporting cadence: [cadence]
- Known oversight needs or pain points: [needs]

Instructions:
1. Recommend the most decision-useful financial KPIs for this nonprofit context.
2. Include budget-versus-actual logic, cash or runway visibility where relevant, and restricted-versus-unrestricted fund views if applicable.
3. Clarify what each dashboard section should help leadership decide or monitor.
4. Flag common dashboard mistakes for nonprofit finance oversight.
5. Keep the blueprint practical for finance and leadership review, not just BI design.

Output format:
- Dashboard blueprint summary
- KPI set and rationale
- Dashboard sections and purpose
- Oversight risks or common mistakes

Missing information policy:
Proceed with assumptions unless the nonprofit model or audience is unclear.

Quality bar:
- Nonprofit-specific relevance.
- Oversight usefulness.
- Practical dashboard structure.