Free guide + printable graph plan
Turn simulation results into a chart that answers one business question without hiding the baseline, exaggerating change, or confusing association with cause.
Quick answer
First state the decision question and identify the evidence needed to answer it. Then choose the simplest display that makes the comparison visible. A chart should preserve the baseline, units, time period, scenario, and important guardrail; otherwise a visually impressive result can still be weak evidence.
Use bars or dots for profit across three staffing plans, waste across products, or occupancy across room prices.
Use a line for daily cash, weekly demand, queue length by hour, or another measure recorded at equal time intervals.
Use a scatter plot for price versus demand or wait time versus satisfaction across several comparable runs.
| Question | Good display | Required context | Common trap |
|---|---|---|---|
| Which option produced more profit? | Bar or dot chart | Same scenario, time span, and starting conditions | Truncated bar axis exaggerates a small gap |
| When did cash become tight? | Line chart | Equal time intervals and a visible zero or risk threshold | Connecting unrelated categories as if time passed |
| How is each dollar of revenue used? | Stacked bar | Components sum to the same whole and use one unit | Comparing angles in several pie charts |
| Do higher prices appear with lower demand? | Scatter plot | Several matched runs and both numeric axes labeled | Calling association proof of causation |
| How variable are repeated outcomes? | Dot plot or box plot | All repeated runs, median, and sample size | Showing only the best or average run |
| What should a manager notice quickly? | Small dashboard | One outcome, two drivers, one guardrail, targets | Too many gauges, colors, and competing priorities |
A concise table is often better when exact values matter or there are only two results. A chart earns its space when it reveals a comparison, trend, distribution, or relationship faster than the table.
Worked example
A team tests whether adding a helper during the same ten-day lemonade scenario improves the business. All other planned decisions remain matched. The baseline earns $84 profit, serves 164 cups, wastes 22 cups, and has a longest wait of 8 minutes. The helper run earns $91 profit, serves 190 cups, wastes 31 cups, and has a longest wait of 4 minutes.
| Run | Profit | Cups served | Waste | Longest wait |
|---|---|---|---|---|
| Baseline | $84 | 164 | 22 cups | 8 min |
| Helper | $91 | 190 | 31 cups | 4 min |
| Change | +$7 | +26 | +9 cups | −4 min |
The helper run produced $7 more profit and cut the longest simulated wait by four minutes, while waste rose by nine cups. The result supports repeating the matched test and monitoring contribution after labor and waste. It does not prove that hiring always increases real profit.
For calculating absolute, relative, and percentage-point changes before charting, use the business simulation results-analysis guide. For comparisons across several teams or runs, use the matched-run benchmarking guide.
Every finished chart should be accompanied by four short statements:
Printable student page
Decision question:
Chosen display and why it fits:
What the chart shows:
Tradeoff, limitation, or alternative explanation:
Qualified recommendation and next test:
Give students one table and two candidate charts. They identify the clearer display, find one misleading choice, and write a bounded chart note.
Pairs compare a baseline and changed run, select a display with CLEAR, sketch it, exchange plans, and revise after a peer accessibility check.
Teams run a controlled test, calculate changes, create one outcome chart plus a guardrail display, and present a claim, limitation, and next test.
Print the lemonade table above and the graph plan. A strong response uses a zero-based bar chart for $84 versus $91 profit, keeps the other metrics in a labeled table or aligned small charts, calls the $7 gain modest, names rising waste as a guardrail, and recommends a repeated matched run. Accept another chart when the student explains how its encoding fits the question and preserves scale, units, comparison, and limits.
Teacher look-fors: the question precedes the chart; categories or time are ordered logically; precision matches the source; annotations point to evidence rather than decoration; and the written conclusion is narrower than the visual pattern.
Use fictional simulation data or anonymous run codes. Do not put student names, personal information, confidential business records, or identifiable rankings into charts. Do not manipulate scales, omit inconvenient results, or imply guaranteed real-world performance. Legal, safety, privacy, labor, accessibility, environmental, licensing, and consumer duties remain constraints even when they reduce a simulated financial result.
The xdage simulators are simplified educational models, not sampled markets or professional forecasts. Real business reporting may require data governance, consent, accessibility review, current accounting definitions, sector-specific rules, and qualified legal, financial, safety, or technical advice.
Use a bar or dot chart for a few categories, a line chart for a true time sequence, and a scatter plot for a possible relationship between two numeric variables. Show the baseline and changed run clearly and label units.
Bars should normally start at zero because their length represents magnitude. A line chart may use a narrower scale when small changes matter, but the range must be obvious and should not exaggerate the result.
Usually one metric is clearest. Two measures can share a chart only when their units and scales are compatible. Otherwise use aligned small charts or a concise table.
Yes. Students can use the printable graph plan and draw a bar, line, or dot chart by hand from a teacher-provided result table.
Common problems include a truncated bar axis, unequal intervals, hidden units, selective time periods, missing comparison runs, decorative three-dimensional effects, and claims of causation the experiment cannot support.
Design matched runs with the controlled experiment guide, interpret changes with the results-analysis workflow, calculate unfamiliar measures with the formula and vocabulary reference, organize a decision dashboard in the business analytics lesson, and turn the finished visual into a recommendation with the decision brief template. Browse every activity in the complete resource index.