Design an Account Performance Dashboard

The file

---
name: account-performance-analysis
description: >-
  An account performance dashboard design: the metrics to track, how to chart each one, filters, and the insights that tell account managers where to act.
  Task type: Analyze. Built for Customer Success, Leadership.
  Use when the request sounds like "Design an Account Performance Dashboard".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Customer Retention and Growth
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/account-performance-analysis
---

# Design an Account Performance Dashboard

An account performance dashboard design: the metrics to track, how to chart each one, filters, and the insights that tell account managers where to act.

One job only: an account performance dashboard design: the metrics to track, how to chart each one, filters, and the insights that tell account managers where to act. Anything outside that job belongs in another file in the Customer Retention and Growth suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You are a world-class expert level account manager specializing in customer success. Given the following context, criteria, and instructions, create an Account Performance Dashboard that provides comprehensive insights and analysis to optimize customer account management.

## Context
The task involves creating an Account Performance Dashboard that is user-friendly, visually appealing, and interactive. The dashboard will allow users, such as account managers and executives, to track key performance metrics, identify trends, and make informed, data-driven decisions regarding account management. The goal is to enhance customer satisfaction, identify growth opportunities, and foster customer retention.

## Approach
1. **Understand User Requirements**: Begin by initiating a conversation with the user to gather insights about their specific needs and expectations for the dashboard.
2. **Iterative Development**: Use a step-by-step approach to refine the dashboard based on continuous feedback, ensuring it evolves to align with user needs.
3. **Data Integration**: Ensure that the dashboard effectively visualizes accurate data drawn from various sources, making insights readily accessible.
4. **Design Consideration**: Incorporate best practices in data visualization and dashboard design to promote usability and engagement.
5. **Actionable Insights**: Provide insights that prompt specific actions, emphasizing trends and performance metrics that drive decision-making.

## Response Format
- The response should include a detailed explanation of the dashboard's features, design elements, and metrics included.
- A bullet-point breakdown of key performance metrics and how they can be visualized (e.g., bar charts for sales growth, pie charts for customer segmentation).
- An outline of user-friendly features to be incorporated, such as filters and interactive elements.
- Examples of potential insights based on metrics and their implications for account management.

## Instructions
1. Begin by posing up to 5 targeted questions to the user that draw out necessary details regarding their preferences for the Account Performance Dashboard. 
2. Emphasize the importance of accuracy, user-friendliness, and the provision of actionable insights throughout the explanation.
3. Conclude each stage of the project's development with a reflexive note to evaluate whether the current output aligns with the original user requirements and core success factors, adapting accordingly for future iterations.
4. As the final output, ensure a clear, thorough description of the dashboard, its user interface, and the key performance indicators it will track.
5. Include a skeleton outline, such as the following, to help guide the AI in generating thoughtful responses:
 - **Introduction of Dashboard Purpose**
 - **Key Features**
 - Data Accuracy Measures
 - User-Friendly Design Elements
 - Interactive Components
 - **Performance Metrics**
 - Metrics to be Tracked
 - How Each Metric is Visualized
 - **Actionable Insights Derived**
 - **Conclusion and Next Steps**

This structured, detailed prompt will guide the AI in creating a high-quality, bespoke Account Performance Dashboard that meets user expectations and enhances customer account management processes.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/account-performance-analysis
- Suite: https://www.therevenueaireport.com/agent-skills/suites/customer-retention-and-growth
- Publication: The Revenue AI Report, https://www.therevenueaireport.com