Choose a chart that answers the business question

Translate a dataset and decision into a chart specification with justified encodings, aggregation rules, accessible labels, and caveats.

PLPromptByte Library@promptbytePublished Sep 8

TextData & Analysis #chart selection #dashboards #data analysis #data visualization

Version 1 of 1 · published Sep 8, 2026Version 1 · only version

Example output

No public result for version 1 yet

Nobody has shared what a model actually produced from this exact version, and PromptByte never generates examples itself. Run the prompt and add yours to fill this in.

Add your result

Prompt

Version 1 · 3 variables · 3 required

Fill in the values below — the customized prompt updates as you type. marks a required value.

Business question{{business_question}}

The decision or comparison the chart should make understandable. Default: Did the share of support tickets resolved within one business day change over the past quarter, and does it differ by priority?

Data description{{data_description}}

Field names, types, units, row grain, date coverage, and quality limitations. Default: One row per ticket: ticket_id, created_at (UTC), resolved_at (UTC or null), priority (low/normal/high), team. Business-day calendar is not yet defined. Unresolved tickets remain in the dataset.

Audience context{{audience_context}}

Who will read the visualization and where it will appear. Default: Support operations managers reviewing a weekly dashboard on a laptop.

Customized prompt

live preview

Resolved user prompt19 lines

Recommend a visualization for this question:
Did the share of support tickets resolved within one business day change over the past quarter, and does it differ by priority?

Available fields, units, grain, and known data limits:
One row per ticket: ticket_id, created_at (UTC), resolved_at (UTC or null), priority (low/normal/high), team. Business-day calendar is not yet defined. Unresolved tickets remain in the dataset.
Audience and display context:
Support operations managers reviewing a weekly dashboard on a laptop.

Begin by checking whether the supplied data can answer the question. Identify missing denominators, incompatible units, ambiguous grain, or coverage gaps that would change the interpretation.

Recommend one primary chart and up to two alternatives only when they answer a useful related question. For each, specify:
- The analytical task: comparison, trend, distribution, relationship, or composition.
- The exact fields and any aggregation, denominator, filtering, date bucketing, or derived calculation required.
- Axes, units, ordering, scale, labels, and use of color or facets.
- Why this encoding suits the question and one misleading interpretation it could encourage.

Provide a build-ready specification for the primary chart: title, subtitle, axis labels, legend, tooltip content, and a concise annotation plan. Use text labels and sufficient visual distinction so color is not the only way to read it. State when a table would communicate the result better.

Do not invent observations, statistical significance, trends, or chart values from a schema. If only metadata is provided, produce a visualization plan and a checklist of calculations to validate. Separate descriptive patterns from causal claims.

Resultsfor version 1

All models

Version 1 · only version

No public examples yet for version 1

Results show what a model actually produced from this exact version. Share yours to help others decide.

Usage notes

Provide the data grain and units as well as column names. A schema is enough for a chart plan, but actual data is required to report findings. The prompt does not create or validate a rendered chart.

Attribution: adapted by PromptByte from prompts/analysis/data-analysis-expert.md in aj-geddes/useful-ai-prompts, by AJ Geddes, licensed MIT. This version changes the wording, scope, and input/output structure; see adaptation notes. No source example outputs are republished as model results.

Original MIT notice (retained verbatim):

MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

code · sql
```
**Assumptions**

- `order_items.order_id` joins to `orders.id`, and `products.category_id` joins to `categories.id`. These are inferred from the naming convention, since no foreign keys were listed.
- "Last 90 days" is measured against `orders.order_date` relative to today, inclusive of today.
- Revenue is `quantity * unit_price` summed over line items; there is no discount or tax column in the schema, so none is applied.
- Cancelled orders are excluded. If `status` uses different values than `'
```
Code preview: **Assumptions** - `order_items.order_id` joins to `orders.id`, and `products.category_id` joins to `categories.id`. These are inferred from the naming convention, since no foreign keys were listed. - "Last 90 days" is measured against `orders.order_date` relative to today, inclusive of today. - Revenue is `quantity * unit_price` summed over line items; there is no discount or tax column in the schema, so none is applied. - Cancelled orders are excluded. If `status` uses different values than `'
SQL query generator from a plain-English request
Converts a natural-language data requirement plus a table schema into a syntactically correct SQL query for a named database, with its assumptions stated up front.
CodeData & Analysis OpenAI · GPT-5.5
PL@promptbyteAug 27
Score 1
0 comments1 results
No public results yet
Audit SQL joins for duplicate rows and inflated totals
Check join cardinality and aggregation grain to explain duplicate rows or double-counted measures before changing a reporting query.
TextData & Analysis
PL@promptbyteSep 8
Score 0
0 comments0 results
No public results yet
Design a forecast backtest that respects time and information
Specify temporal evaluation, leakage checks, baselines and business-relevant metrics before judging a forecasting model.
TextData & Analysis
PL@promptbyteSep 8
Score 0
0 comments0 results
No public results yet
Critique an existing chart for misleading interpretation
Review a chart's scales, labels, aggregation and claims, separating visual issues from data questions that need verification.
TextData & Analysis
PL@promptbyteSep 8
Score 0
0 comments0 results
No public results yet
Classify comment sentiment with traceable evidence
Label supplied comments consistently while preserving mixed opinions, unclear cases and the exact words supporting each label.
TextData & Analysis
PL@promptbyteSep 8
Score 0
0 comments0 results
No public results yet
Reshape a wide CSV into tidy records without losing meaning
Produce a deterministic transformation from repeated measure columns to tidy rows with explicit keys, types and missing-value rules.
CodeData & Analysis
PL@promptbyteSep 8
Score 0
0 comments0 results

Browse Data & Analysis

Choose a chart that answers the business question

Example output

Prompt

Customized prompt

Resultsfor version 1

Something wrong with this prompt?

SQL query generator from a plain-English request

Audit SQL joins for duplicate rows and inflated totals

Design a forecast backtest that respects time and information

Critique an existing chart for misleading interpretation

Classify comment sentiment with traceable evidence

Reshape a wide CSV into tidy records without losing meaning

Discussion 0

Example output

Prompt

Customized prompt

Resultsfor version 1

Something wrong with this prompt?

Related prompts

SQL query generator from a plain-English request

Audit SQL joins for duplicate rows and inflated totals

Design a forecast backtest that respects time and information

Critique an existing chart for misleading interpretation

Classify comment sentiment with traceable evidence

Reshape a wide CSV into tidy records without losing meaning

Discussion 0