Choose the Right Chart Type for Your Data

This prompt turns a vague 'what chart should I use?' into a reasoned recommendation: it asks the model to match a chart type to both your analytical goal and the shape of your data, then justify it, offer a fallback, warn about pitfalls, and sketch the axis mapping. Reach for it before building a dashboard or slide when the wrong chart would quietly mislead your audience. Forcing it to name a second option and common mistakes is what separates this from a one-word answer — the trade-offs are usually where the real decision lives.

What you can expect back

1. Ideal: Line chart.
A continuous line is the clearest way to read direction and momentum across 24 evenly-spaced time points.

2. Second option: Bar chart.
Use bars instead if each month is a discrete reporting period you want compared individually rather than read as a flow.

3. Common mistakes:
- Truncating the y-axis (not starting at 0) exaggerates the trend.
- Adding a second y-axis to overlay another metric — it distorts perceived correlation.
- Too many gridlines burying the line.

4. Axis mapping:
- X-axis: Month (Jan 2024 -> Dec 2025), evenly spaced.
- Y-axis: Revenue ($), starting at 0.
- Series: single line, one point per month, points optional.

Illustrative example — your results will vary by tool and inputs.

Get sharper results

• 01Tell it who the audience is — an exec deck and an analyst report justify different chart choices, and the model will weigh simplicity vs. detail accordingly.
• 02Mention the medium (static slide, interactive dashboard, mobile) because some chart types that work interactively fall apart as a printed image.
• 03If you're tempted by a pie chart, ask it specifically when a pie is and isn't appropriate — it'll usually steer you to bars unless you have very few parts of a clear whole.
• 04Ask for the exact encoding (color, size, position) it recommends, not just the chart name, so you don't accidentally encode a category as a continuous gradient.
• 05Push it to flag when your data actually needs two charts instead of one overloaded combo chart.

Adapt it for your case