Create a Weekly CEO Dashboard From the Numbers You Already Have

A useful CEO dashboard does not need dozens of charts. It needs a small set of trusted numbers that lead to decisions, owners, and action every week.

This guide helps you create a one-page weekly dashboard with definitions, source owners, targets, trends, questions, and actions.

What you need

• Your current business objective and operating bottleneck
• A short list of numbers you already collect reliably
• Metric definitions, data sources, owners, and update cadence

The workflow

1. Start with decisions

List the decisions you need to make weekly. Choose metrics that change those decisions instead of collecting numbers because they are available.

2. Separate results from drivers

Revenue and profit are outcomes. Pipeline movement, conversion, delivery capacity, retention, and cash collection may explain what happens next.

3. Define every number

Write the formula, source, owner, update time, and caveats. A dashboard cannot be trusted when people calculate the same label differently.

4. End with action

Each review should produce a small number of actions with owners and dates. Commentary without decisions is reporting theater.

Copy this working prompt

Replace every bracketed field with verified information from your business. If you do not know something, write unknown instead of guessing.

Help me design a weekly CEO dashboard using only numbers my business can collect reliably.

Current 90-day objective:
[DESCRIBE]

Most important operating constraint:
[DESCRIBE]

Weekly decisions I need to make:
[LIST]

Available metrics with definitions and sources:
[LIST EACH METRIC, FORMULA, SOURCE, OWNER, AND KNOWN LIMITS]

Targets or guardrails already approved:
[LIST OR WRITE NONE]

Design a one-page dashboard with:
1. Three to five outcome metrics
2. Three to five leading or driver metrics
3. Definition, source, owner, update day, target, and caveat for each
4. Current value, prior value, trend, and confidence fields
5. Questions triggered by meaningful movement
6. Weekly review agenda under 30 minutes
7. Action log with owner and due date
8. Metrics to exclude and why

Do not invent data, targets, benchmarks, formulas, or causes. If a metric cannot support a decision, recommend removing it.

Run a second-pass review

The first output should not be the final answer. Use this challenge prompt to find weak evidence, hidden assumptions, or avoidable risk.

Act as a skeptical operator. Identify vanity metrics, duplicate measures, lagging indicators with no actionable driver, unclear definitions, and numbers that are too unreliable for weekly decisions.

What good looks like

• Every metric changes a decision
• Definitions and sources are visible
• The review ends with owned actions

Review before you use it

• Can another person reproduce each number?
• Are trends interpreted with enough data?
• Do you separate signal from a one-week fluctuation?

Privacy and judgment guardrails

• Remove passwords, payment details, private health information, and confidential customer data before pasting anything into an AI tool.
• Treat the output as a working draft. A person remains responsible for the decision, promise, price, and final send.
• Do not let AI invent customer quotes, financial figures, legal terms, capabilities, deadlines, or proof.

Your next action

Run the dashboard for four weeks before adding any metric. Remove anything no one uses to decide or act.

If your AI tool still lacks the context to do this well, first Turn a big goal into daily work.