A useful data visualization answers a specific question and lets the reader check the comparison. For the Google Data Analytics Certificate, that means selecting an appropriate chart, validating the underlying calculation, labeling the measure and population, and explaining what the result can support. A visually polished dashboard cannot repair an incorrect join or an undefined metric.
The current certificate curriculum includes Share Data Through the Art of Visualization and Tableau. The synthetic example below connects a table, a chart, and a recommendation. It is independent practice, not a course assessment answer or a claim about a real business.
What question should the chart answer?
Suppose an operations team asks which regions recorded the most completed orders in a sample month. The measure is completed-order count, the grouping is region, and the period is the same for all regions. Cancelled orders are excluded by definition. Each order must appear once in the source used for the chart.
Define those details before selecting colors or chart types. “Sales by region” is ambiguous: sales could mean order count, revenue, units, or profit. A title such as “Completed orders by region, synthetic monthly sample” tells the reader much more. If the analysis is for a real organization, include its actual reporting period and the source refresh date.
| Region | Completed orders | Recorded revenue (USD) | Revenue per completed order (USD) |
|---|---|---|---|
| East | 40 | 2,400 | 60 |
| West | 60 | 3,000 | 50 |
| North | 20 | 1,600 | 80 |
| Total | 120 | 7,000 | 58.33 |
The overall revenue per order is 7,000 / 120, or approximately $58.33. It is not the unweighted mean of the three regional averages, which would be about $63.33. This distinction matters if your dashboard recalculates a metric after filtering. Verify the denominator rather than averaging precomputed averages without considering their weights.
Why is a bar chart appropriate here?
A horizontal bar chart makes three category counts easy to compare. All bars start at zero, the region labels are readable, and exact values appear at the ends. West has 60 completed orders, East 40, and North 20. The chart shows an ordering and a difference; it does not establish why those differences occurred.
A pie chart could represent shares of the total, but it makes the precise differences harder to read. A line chart connecting the three regions would suggest an order or continuity that these categories do not have. Choose the visual encoding that serves the question rather than the one that looks most elaborate.
How does the chart change when the question changes?
If the question becomes “Which region has the highest recorded revenue per completed order?”, North leads at $80 even though it has the fewest orders. A chart of order counts cannot answer that question. Show the average alongside its denominator so a reader can see that North's figure comes from only 20 orders in this sample.
If the question becomes “How did orders change during the month?”, you need daily or weekly observations. Use a chronological axis, consistent intervals, and a clear treatment of missing dates. A missing day is not automatically a day with zero orders. If the question concerns the relationship between two numeric measures, a scatter plot may be appropriate, with a clear statement that association alone does not establish causation.
Keep charts focused. Putting counts, revenue, and averages on one unlabeled axis mixes units. A second axis can also confuse readers when scaling choices make unrelated series appear aligned. Separate panels or a compact table may communicate the comparison more clearly.
What should you check in Tableau?
Tableau distinguishes dimensions and measures as well as discrete and continuous fields. A numeric field can function as a dimension, such as a numeric identifier. Do not classify every number as something to sum. The official field roles documentation explains these distinctions.
For the synthetic summary table, region is the category and completed orders is the measure. If you load order-level data instead, count the appropriate order identifier and confirm its uniqueness. If a join has produced duplicate order rows, a simple row count may inflate the chart. Check the source grain before choosing an aggregation that merely makes the display look plausible.
Compare the visualization with an independent calculation: the three regions should total 120 completed orders and $7,000 recorded revenue. Then test one filter, such as selecting East only. The count should become 40 and revenue $2,400. Reset the filter and confirm that the overall total returns. Save the metric definition with the workbook.
How do you make the result accessible?
Use descriptive titles, readable labels, sufficient contrast, and an explanation in ordinary text. Do not make red versus green the only way to distinguish categories. Labels, patterns, or positions should carry the information even when the viewer cannot perceive the color distinction.
Provide a data table or concise text equivalent for the main finding. A screenshot with tiny text is difficult to inspect on a phone and unavailable to a screen reader unless it has a meaningful alternative. In an interactive dashboard, ensure that filters have understandable labels and that the initial view contains useful information without requiring a complex sequence of clicks.
Test the chart at the width where it will be read. If long labels wrap awkwardly, change the layout or shorten the label while preserving its meaning. Do not shrink everything until the numbers become unreadable. For a portfolio, a simple static result and a readable explanation can be more useful than an overloaded dashboard.
What recommendation does this example support?
A defensible observation is: “West recorded half of the sample's completed orders: 60 of 120. North recorded fewer orders but a higher average recorded revenue per order.” The next question might concern capacity, product mix, or demand, depending on the decision the team needs to make.
The sample alone does not justify moving staff or advertising money. It contains no staffing levels, customer counts, profit margins, or comparable prior period. A qualified recommendation is to investigate those additional fields before changing resource allocation. Stating that limitation makes the analysis more useful because it prevents a chart from being mistaken for evidence it does not contain.
What belongs in a portfolio visualization?
Include the question, source, reporting period, metric definitions, validation checks, chart, and interpretation. If you publish through Tableau Public, review the publishing guidance and share only material you are authorized to make public. Removing a visible column does not necessarily remove sensitive information from the underlying workbook.
Verified October 14, 2026: course scope checked against Coursera and Tableau behavior against its official documentation. The dataset, chart, calculations, and recommendations are original illustrative examples.
Practice next
Use the Google Data Analytics Certificate overview to place this topic in the current course sequence. Use the cleaning validation checklist before charting and the capstone guide to connect a visual with a complete case study.
The Google Data Analytics study guide PDF includes visualization references, practice questions, and capstone templates. The 242-page expanded edition includes current Python labs, 120 multiple-choice questions, 69 applied prompts, and companion practice files. It is an independent supplement to the official coursework. For questions as you practice, explore the separate SimpuTech Google Data Analytics study coach.