Updated October 22, 2026. Based on the official announcement linked below.
Two teams can have the same average turnaround time while giving customers very different experiences. One may finish nearly every task in a similar time; another may alternate between quick completions and long delays. A chart that shows the distribution helps you ask better questions than a single average.
What Google Sheets announced on October 22
Google’s official release notice introduces native box and whisker charts, using raw numeric data without helper formulas. It describes controls for quartile calculation, outliers, and mean indicators, together with improved Excel import and export compatibility.
Rapid Release rollout starts October 22 and can take up to 15 days. Scheduled Release starts November 6. The notice includes Workspace and personal Google accounts. If the chart option is absent today, check the release timing before rebuilding your spreadsheet around a workaround.
Start with one meaningful question
Choose what you want to compare before making the chart. “Which delivery route has the least predictable completion time?” is more useful than “Make these numbers look interesting.” Decide the period, the unit, and which observations belong in each group.
For a hypothetical delivery example, use minutes consistently and separate routes into clearly named groups. Do not mix elapsed calendar time with working time or combine completed jobs with estimates without explaining the difference.
Prepare the data before styling
Keep the underlying observations in a clean range. Check blank entries, accidental text, duplicated rows, and values that came from a different process. Preserve the original data so that a correction can be traced.
A surprisingly large value deserves investigation, not automatic removal. It might represent a data-entry error, or it might capture exactly the delay your reader needs to understand. Write down the reason for any exclusion rather than quietly cleaning away an inconvenient result.
Explain what the reader should notice
A useful chart caption states the question, groups, unit, and reporting period. Discuss where the middle of the observations sits and how much variation appears within each group. Avoid treating a visually neat box as proof that a team performs better.
Check the selected quartile and outlier settings before comparing the chart with another tool. If two charts use different calculation choices or different data ranges, their disagreement may be a setup issue rather than a change in the underlying process.
A small reporting example
Imagine two support queues that both average roughly a day to resolve a request. A distribution chart might prompt you to investigate whether one queue contains a minority of much older requests. The next step is to inspect those cases and their circumstances.
That example is illustrative, not a result from a real dataset. The professional habit is to move from a visual pattern to a question you can check, rather than attaching a confident explanation to the shape alone.
Check the exported result
If you exchange files with an Excel user, inspect the delivered workbook after conversion. Confirm the data range, category names, calculation options, and visible labels. Compatibility is helpful, but it does not replace checking the file your colleague will actually open.
Frequently asked questions
Should I replace every bar chart with this chart type?
No. Use a distribution view when variation within a group is relevant to the question. Pick the display that helps the intended reader make sense of the data.
Are unusual values always mistakes?
No. Investigate them and document any exclusion. Removing a genuine delay can hide a practical problem.
What should I do first?
Write the question in one sentence, then check that the selected observations, units, and groups genuinely answer it.
Related reading: Read AI traffic reports carefully.