
Disclosure: NOXI publishes this guide and is one of the tools it mentions; the method works in any presentation software.
Quick answer: To present data in a presentation, give each slide one question and one comparison, choose the chart that answers that question, and write the answer as the slide title: "Mobile conversion fell from 2.20% to 1.45% after the 4 August checkout change", not "Conversion rate". Then add the context the number needs (a target, the prior period or a benchmark), highlight and annotate the point that matters, state units and periods, start bar charts at zero and put a source line on every data slide.
Most data slides fail for the same reason: they show everything the analyst found instead of the one thing the audience needs to see. This guide gives you the method, a chart chooser, the rules for numbers, scales and labels, a checklist and a worked example: a fictional quarterly KPI review rebuilt so that every title is a finding. The company and its figures are invented; the arithmetic is real and shown in full.
In short
- Question firstEach data slide answers one question, such as "Did we hit plan?" or "What changed?", with one comparison.
- ChartLine for change over time, sorted bars to compare, waterfall for "how we got from A to B", table for exact values.
- TitleThe title is the finding in one sentence, with the number and the comparison: "missed plan by 8.6%".
- ContextEvery number gets a baseline: plan, prior period or benchmark. A number on its own is not a finding.
- Honest scalesBars start at zero, rate changes are written as percentage points, and each data slide carries a source line.
- AppendixDefinitions, full tables and segment cuts go to the appendix, ready for questions.
The method: question, comparison, chart, title
Presenting data well is four decisions made before any design work: the question the slide answers, the comparison that answers it, the chart that shows that comparison most directly, and the title that states the answer. Formatting comes last and matters least.
Make the decisions in order, because each one constrains the next. The last column follows this guide's worked example.
| Step | Decision | In the worked example |
|---|---|---|
| 1. Question | What must the audience know or decide? | "Did Q3 revenue hit plan, and if not, why?" |
| 2. Comparison | Against what: plan, prior period, last year, a peer, another segment? | Actual against plan, split into its drivers |
| 3. Chart | Which form shows that comparison fastest? | A waterfall from plan to actual |
| 4. Title | What is the answer, in one sentence? | "Q3 revenue missed plan by $249K: weaker mobile conversion cost $353K" |
| 5. Support | What does the reader need to trust it? | An annotation of the checkout change, a source line, definitions in the appendix |
The UK Government Analysis Function's chart guidance puts the same test from the other end: if you cannot write down the message of your chart in a few sentences, reconsider the chart. The charts you made while analysing help you find a pattern; the charts you present show one pattern to people who have seconds to read it.
Count slides by questions, not by charts: four real questions need four data slides plus a summary and a decision, however many charts the dashboard holds. For the arc of a whole deck, our guide to consulting-style slides covers the answer-first structure and the ghost-deck method.
Anatomy of a data slide: six parts
A finished data slide has six parts: a title that states the finding, a subtitle with the measure, unit and period, a visible baseline or comparison, one accent colour on the point that matters, an annotation that explains it, and a source line. Anything else must earn its place.

| Part | Its job | Rule of thumb |
|---|---|---|
| 1. Finding title | Says what the data shows | One sentence, two lines at most, with the number and the comparison |
| 2. Subtitle | Defines what is plotted | Measure, unit, period and scope: "Revenue, $ thousands, Q3 2026" |
| 3. Baseline | Gives the number its meaning | Plan, prior period or benchmark drawn on the chart, not left to memory |
| 4. One accent | Directs the eye | Context in grey; one colour for the element the title talks about |
| 5. Annotation | Explains the point | A short label at the place on the chart where it happened |
| 6. Source line | Makes it checkable | System or publication, organisation, period; "team analysis" if you transformed the data |
The Analysis Function recommends the same split for published charts: a headline title that communicates the main message, and a statistical subtitle that says what the data is, the geography it covers and the time period shown. On a slide, the subtitle is one short line under the title.
Chart chooser: match the chart to the question
Choose a chart by the question it must answer: a line for change over time, sorted bars to compare categories, a waterfall to explain how one total became another, a stacked bar for parts of a whole, a scatter plot for a relationship, and a table when people need exact values. A chart chosen for variety usually needs a speaker to explain it.

The example titles below are illustrative. Each one states a finding the chart beside it can prove.
| Question | Chart | Avoid | Example title |
|---|---|---|---|
| How did it change over time? | Line chart; columns for a handful of periods | Uneven time gaps drawn evenly; more than four lines | "Weekly orders returned to the July level by week 38" |
| Which is biggest or smallest? | Bar chart sorted by value; horizontal bars for long labels | Unsorted bars; a pie with many slices | "The North region brought in 41% of new contracts" |
| How far are we from target? | Bars with a target line, or variance bars above and below zero | Two bars per item that leave the reader to subtract | "Four of six stores missed target; Store 4 by 12%" |
| What moved us from A to B? | Waterfall (bridge) | Stacked bars that hide the individual steps | "Price increases offset 70% of the volume decline" |
| What is it made of? | Stacked or 100% stacked bar; a pie only for a few parts of a real whole | 3D pies; more than about four segments per bar; two pies side by side | "Subscriptions are now 62% of revenue, up from 48%" |
| How are values spread? | Histogram or dot plot | An average alone, which hides the tail | "Most tickets close within a day, but 9% take over a week" |
| Do two measures move together? | Scatter plot | Two lines on dual axes; implying cause | "Stores with more staff hours convert better, with wide variation" |
| Where do we stand on several KPIs? | Table or scorecard with the comparison in each row | Gauges and dials that take a slide each | "Two of five KPIs beat plan; conversion is the one to fix" |
| What are the exact values? | Table | A chart with every value labelled | "Unit costs by supplier, Q3 2026" |
For a larger catalogue, the Financial Times' Visual Vocabulary groups chart types by nine relationships in the data: deviation, correlation, ranking, distribution, change over time, magnitude, part-to-whole, spatial and flow. Use it when none of the rows above fits.
Bar chart or pie chart?
Use a bar chart by default. People compare positions and lengths more accurately than angles and areas: in a 1986 experiment that followed their 1984 paper on graphical perception, William Cleveland and Robert McGill found position judgments the most accurate, length second, angle and slope third and area last. Jeffrey Heer and Michael Bostock repeated the comparison with online participants in 2010 and again found angle (pie) and circular-area (bubble) judgments worse than position judgments.
A pie still works for a simple part-to-whole message. The Analysis Function allows one only for five categories or fewer that add up to a meaningful whole, with one dominant category; if the parts are similar in size, it advises a bar chart. "Two-thirds of support tickets now arrive by chat" works as a two-slice pie; eight similar slices do not.
Write the title as the finding
A data slide's title should state what the data shows, as a full sentence with the number and the comparison, for example "Q3 revenue missed plan by 8.6%", rather than label the topic ("Q3 revenue"). Someone who reads only the titles should be able to follow the whole argument.
There is evidence that it helps. In a 2006 study in a large geoscience course at Virginia Tech, Michael Alley and colleagues taught some sections from slides with mostly phrase headlines and others from slides whose headlines stated the main assertion as a sentence. On 15 exam questions about those assertions, the sentence-headline groups averaged 79% correct against 69%, a statistically significant difference. The redesigned slides also replaced bullet lists with visual evidence, so the result supports the pattern as a whole.
A reliable formula is [measure] [moved how much] [against what] [because, after or so what]. Five rewrites:
| Topic title | Finding title | What changed |
|---|---|---|
| "Q3 revenue" | "Q3 revenue grew 17.9% on last year but missed plan by 8.6%" | Both comparisons, with the one that matters last |
| "Conversion rate by device" | "Mobile conversion fell from 2.20% to 1.45% after the 4 August checkout change" | The segment, the size of the move and the event |
| "Customer survey" | "Satisfaction held at 4.3 out of 5; delivery scores fell for a second quarter" | The stable result and the exception |
| "Headcount" | "Headcount is 6 below plan because two senior hires moved to Q4" | The gap and its cause |
| "Key metrics" | "Two of five KPIs beat plan; conversion is the one to fix" | The verdict and the priority |
Keep titles under about 15 words and two lines, with the rounded number the audience should remember and a verb: grew, fell, missed, held. Match the wording to the evidence: write "after" when you have timing, and "because" only when the slide or the appendix shows why. "No clear difference between the two pilots after six weeks" is a finding too.
Give every number a comparison
A number on its own is not a finding; it needs a comparison that tells the audience whether it is good, bad or normal. Pick the comparison that matches the decision: plan or target for performance reviews, the prior period for momentum, the same period last year for seasonal businesses, and a benchmark for competitive position.
| Comparison | Answers | Watch out for |
|---|---|---|
| Plan or target | Are we on track? | Targets revised mid-period: say which version you compare with |
| Prior period | Is it getting better or worse? | Seasonal swings that make neighbouring periods incomparable |
| Same period last year | Are we growing? | Calendar effects such as holidays or a different number of trading days |
| Benchmark or peer | How do we compare? | Different definitions in external sources |
| Segment against segment | Where is the difference? | Mix effects: segment shares can shift as well as rates |
Show one comparison per chart. Actual, plan, last year and last quarter in four colours leave the audience guessing which one the title means; put the comparison the meeting is about in the chart and the others in the subtitle or a scorecard. When a figure is a forecast or an estimate, label it as one; our guide to presenting forecasts and uncertainty covers ranges, scenarios and revisions.
If you show actuals, plans and forecasts together, use one visual convention everywhere. The International Business Communication Standards (IBCS) draw actuals as solid dark shapes, plans as outlined shapes and forecasts as hatched shapes, and show a previous period in a lighter tone when it is the comparison, under rule UN 3.2, "Unify scenarios" (IBCS working group note). The anatomy figure above uses the same idea: an outlined plan bar and a solid actual bar.
Get the numbers right: units, rounding and percentages
Round numbers on slides to the precision a decision needs, usually two or three significant digits; put the unit and period in the subtitle; use the same number of decimal places for numbers that are compared; and write "percentage points" when a rate changes by subtraction. In practice, many credibility problems in data decks are number problems, not chart problems.
| Weak | Strong | Why |
|---|---|---|
| "$2,631,200" | "$2.63M" | Seven digits hide the size; the decision needs three |
| "Conversion down 0.3%" | "Conversion down 0.30 points, from 2.50% to 2.20%" | A fall of 0.3% and a fall of 0.3 points are different numbers |
| "Revenue up 18%" | "Revenue up 17.9% on Q3 2025" | Names the comparison; keeps one decimal like its neighbours |
| "−8.6%" | "$249K below plan (−8.6%)" | Absolute and relative change answer different questions |
| "1.5%, 3%, 2.25%" | "1.50%, 3.00%, 2.25%" | The ONS asks for the same decimal places across a sequence of percentages |
| "64% agree" | "64% of 412 respondents agree" | A percentage needs its base; 64% of 25 people is a different claim |
Rounded parts may not add up to the rounded total; add "Figures may not sum due to rounding" rather than adjusting a component to force it. Before any design work, recalculate every percentage from its inputs, confirm that segments add up to the total and check that all figures share one data cutoff. Our guide to turning spreadsheet data into a briefing deck covers preparing the workbook so these checks are quick.
Scales and axes: when to start at zero
Bar and column charts should start at zero, because readers compare bar lengths and a cut axis exaggerates differences. Line charts may use a non-zero axis when the movement is the message, but mark the break, label the scale and keep the same scale on slides that will be compared.
The Analysis Function calls breaking the axis on a bar chart "problematic and highly controversial" and suggests a Cleveland dot plot when a zero baseline hides the story; it accepts a broken y-axis on a line chart when necessary. Research supports caution even with warnings: in crowdsourced experiments, Michael Correll, Enrico Bertini and Steven Franconeri found that truncated y-axes made differences look larger, and that the effect persisted when the truncation was flagged visually.
- Bars from zero. If the differences that matter are small relative to the values, use a dot plot, or plot the differences themselves as variance bars around zero.
- One scale for comparable charts. Small multiples and slides that will be compared side by side share the same axis range.
- No dual axes. Two y-axes suggest a relationship created by the choice of scales; the Analysis Function advises separate charts, each with its own y-axis.
- Time spaced as time. A missing month is a gap in the line, not a join.
- Log scales only for audiences who read them, labelled as logarithmic.
- No 3D. Perspective changes the apparent size of bars and slices.
Honest scales sometimes make a difference look small. That is information: in the worked example, the traffic and basket steps are slivers beside the conversion step.
Highlight and annotate the point that matters
Draw context in grey and the element the title talks about in one accent colour, label lines and bars directly instead of using a legend, and write a short annotation on the chart where the important thing happened. The audience should see the finding before you say it.
- One accent colour. If everything is coloured, nothing is highlighted.
- Direct labels. Series names at the ends of lines, values on or beside bars; the Analysis Function prefers this to legends.
- Annotations that explain. Mark launches, price changes, outages and definition changes where they apply, in a few words.
- Four lines at most. The Analysis Function warns that more than four lines often clutters a chart; use small multiples instead.
- Less decoration. No shadows, 3D or boxed legends; a few light gridlines at most.
Never let colour carry the meaning alone. The Web Content Accessibility Guidelines require that colour is not the only visual means of conveying information, and that chart elements needed to understand the content have a contrast ratio of at least 3:1 against adjacent colours. It is practical too: the US National Eye Institute says about 1 in 12 men have a colour vision deficiency, and the most common type makes red and green hard to tell apart. A red-and-green variance table should also use signs, arrows or labels. For the full review of an exported deck, see our presentation accessibility checklist.
Tables or charts: when to show the numbers
Use a table when the audience needs exact values or will look up individual numbers, and a chart when they need to see a pattern, a trend or a difference. In a live presentation, a table works best when you highlight the row or cell the title is about.
The Analysis Function's table guidance draws the same line: tables to compare values or to show values of very different sizes, charts for patterns, trends and relationships.
| Situation | Better choice | Why |
|---|---|---|
| Several KPIs with different units | Table or scorecard | One chart cannot hold dollars, percentages and counts on one honest scale |
| A trend over twelve months | Line chart | The shape is the message; twelve numbers in a row are not |
| Exact figures for a decision | Table | Prices, quotes and budgets are read, not estimated |
| One difference to see in seconds | Chart | Length and position are compared at a glance |
| Values from 12 to 4,800,000 | Table | A shared scale squashes the small values to nothing |
Format slide tables the way statisticians do: right-align numbers and their headings, keep one precision per column, put units in the headers (or the title, if all columns share one), keep gridlines light and put totals at the bottom or right. Then add one emphasis: bold the row the title is about. A KPI scorecard is such a table with one row per KPI, ordered by importance, and status shown with a word or symbol as well as colour. Our QBR presentation guide covers scorecard design for quarterly business reviews in more depth.
Sources, definitions and the appendix
Every data slide needs a source line that names where the numbers come from and for which period, and every data deck needs an appendix with the definitions, full tables and cuts that people will ask about. The main deck carries the argument; the appendix carries the proof.
Write the source line in the same place and size on every slide. The Analysis Function's format for published charts is the publication or dataset, then the organisation, with a direct link rather than a homepage. Inside a company, "Source: order system and web analytics, Q3 2026; team analysis" is enough.
The appendix holds, each slide titled by the question it answers: metric definitions ("Conversion rate = orders ÷ sessions"), method notes such as the order of steps in a bridge, the full scorecard and detailed tables, the segment cuts people are likely to request, and data-quality notes. Figures from outside your organisation need their publisher and year on the slide, and someone should open each source before the deck circulates, especially when an AI tool supplied the number. Our guide to AI presentations with research and citations covers checking them.
How to talk through a data slide
When presenting a chart live, say the finding first, then orient the audience (what is plotted, the units, what the colours mean), point to the evidence, and finish with what it means for the decision. As a rule of thumb, a data slide needs 60 to 90 seconds; if it needs five minutes, it probably holds more than one finding.
- Claim. "Mobile conversion fell sharply in August."
- Orient. "This shows conversion by device, by month. Mobile is in red, desktop in grey."
- Point. "Mobile was at 2.20% in July, the same as in Q2. From August it is 1.45%. Desktop stayed at 3.00% throughout."
- Explain. "The drop starts when the new mobile checkout launched on 4 August; the desktop checkout did not change."
- So what. "At current traffic, that costs about 2,760 orders a month. The decision on slide 7 is how we test the fix."
Do not read every number: the audience will remember one or two. Reveal complex charts in stages, such as the plan bar first, then each step of the bridge. A pre-read has no presenter, so put the explanation on the slide as an annotation. To plan the length of the talk, see our slides-per-minute table.
Worked example: a quarterly KPI review, before and after
Quillmoor Home is a fictional online homeware retailer reviewing Q3 2026 (July to September) with its leadership team. The first draft opened with a slide titled "Q3 KPIs" that put five metrics on one clustered chart, followed by topic-titled charts such as "Conversion rate". The rebuilt section answers the review's real question, and every number below can be recalculated.
The numbers
| KPI | Q3 2026 actual | Q3 plan | Against plan | Against Q3 2025 |
|---|---|---|---|---|
| Revenue | $2,631,200 | $2,880,000 | −$248,800 (−8.6%) | +17.9% (from $2,232,000) |
| Orders | 40,480 | 45,000 | −4,520 (−10.0%) | +12.4% (from 36,000) |
| Sessions | 1,840,000 | 1,800,000 | +40,000 (+2.2%) | +22.7% (from 1,500,000) |
| Conversion rate | 2.20% | 2.50% | −0.30 points | −0.20 points (from 2.40%) |
| Average order value | $65.00 | $64.00 | +$1.00 (+1.6%) | +4.8% (from $62.00) |
Two true headlines compete: revenue grew 17.9% on last year, and it missed plan by 8.6%. A review against plan exists to answer the second, so the deck leads with the miss.
Step 1: split the miss into drivers
Because revenue is the product of three drivers, the gap to plan can be split into a traffic effect, a conversion effect and a basket-size effect, changing one driver at a time:
| Step | Calculation | Revenue |
|---|---|---|
| Plan | 1,800,000 sessions × 2.50% × $64.00 | $2,880,000 |
| Traffic | +40,000 sessions × 2.50% × $64.00 | +$64,000 |
| Conversion | 1,840,000 sessions × (2.20% − 2.50%) × $64.00 | −$353,280 |
| Basket size | 40,480 orders × ($65.00 − $64.00) | +$40,480 |
| Actual | 1,840,000 sessions × 2.20% × $65.00 | $2,631,200 |
The steps reconcile: $2,880,000 + $64,000 − $353,280 + $40,480 = $2,631,200. Traffic and basket size added $104,480; lower conversion removed $353,280. The order of steps matters a little: here the 5,520 lost orders (1,840,000 × 0.30%) are priced at the planned $64.00, while putting conversion last would price them at $65.00 and show −$358,800 for conversion and +$46,000 for basket size. Neither is wrong; state the order in a footnote and keep it every quarter.
Step 2: find where the conversion fell
Splitting conversion by device and month shows where it fell:
| Month, 2026 | Mobile sessions | Mobile conversion | Desktop conversion |
|---|---|---|---|
| July | 414,000 | 2.20% | 3.00% |
| August | 368,000 | 1.45% | 3.00% |
| September | 368,000 | 1.45% | 3.00% |
| Q3 | 1,150,000 | 1.72% | 3.00% |
Desktop had 230,000 sessions a month and converted at 3.00% throughout, as it did in Q2. Mobile converted at 2.20% in July, its Q2 rate, then at 1.45% in August and September, after a redesigned mobile checkout launched on 4 August. Had mobile held 2.20%, August and September would have produced 2 × 368,000 × 0.75% = 5,520 more orders: exactly the conversion shortfall in the bridge.
At August–September traffic, each further month at 1.45% instead of 2.20% costs about 2,760 orders (368,000 × 0.75%), or about $179,400 at the Q3 average order value of $65.00. That number turns the diagnosis into a decision.
Step 3: rebuild the slide

| Element | Before | After |
|---|---|---|
| Title | "Conversion rate" | The finding, with both rates and the date |
| Subtitle | None | "Conversion rate by device, %, July–September 2026" |
| Chart | Clustered columns in two equally strong colours | Line chart: mobile in the accent colour, desktop in grey |
| Labels | Legend box and a decimal axis | Direct labels with the start and end values |
| Context | None | A dashed marker for the 4 August checkout launch |
| Source | None | "Source: web analytics, monthly rates" |
The title says "after", not "because". The timing, the device split and the unchanged desktop flow support the checkout explanation without proving it, so the deck proposes a test rather than declaring a cause.
The rebuilt section, slide by slide
| # | Finding title | Chart or layout |
|---|---|---|
| 1 | "Q3 revenue missed plan by 8.6% despite 17.9% growth; lower mobile conversion drove the miss" | Summary: three numbers and the decision needed |
| 2 | "Traffic and basket size beat plan; conversion missed by 0.30 points" | Scorecard table, conversion row highlighted |
| 3 | "Q3 revenue missed plan by $249K: weaker mobile conversion cost $353K" | Waterfall from plan to actual |
| 4 | "Mobile conversion fell from 2.20% to 1.45% after the 4 August checkout change" | Line chart by device and month, launch marked |
| 5 | "Each month at the current mobile rate costs about 2,760 orders, or $179,400" | The calculation in one row, with its inputs |
| 6 | "The checkout change is the supported explanation; a two-week test will settle it" | Evidence for, open questions, owner |
| 7 | "Approve a two-week test of the previous mobile checkout from 12 October" | Decision card: what, who, when, read-out date 26 October |
| 8 | Appendix: definitions, bridge method and data sources | Table |
Read the titles in sequence and the review makes sense without a single chart: the test for any data deck.
We also generated the after version as a deck in NOXI from the slide titles and numbers above and exported it to PDF without edits. Two of its slides:


Data-slide checklist
Run this checklist on every data slide before the deck circulates. If a slide fails the first two checks, fix them before touching the design.
- The slide answers one question.If there are two, make two slides.
- The title states the finding with its number and comparison.Fifteen words or fewer; "after" for timing, "because" only with evidence.
- The subtitle gives the measure, unit, period and scope."Revenue, $ thousands, Q3 2026".
- The chart matches the question.Use the chooser table above.
- A baseline is visible.Plan, prior period or benchmark, and only one per chart.
- Bars start at zero; any axis break is marked.No dual axes and no 3D.
- One accent colour, context in grey.Meaning never depends on colour alone.
- Labels are direct.No legend where a label fits; four lines at most.
- The point that matters is annotated.At the place on the chart where it happened.
- Numbers are consistent.Same decimals for compared values; points versus percent right; bases shown.
- A source line is on the slide.Definitions and method notes are in the appendix.
- A colleague can state the finding without the title.Cover the title and ask; if they cannot, simplify the chart.
3 AI prompts for data slides
Use them in NOXI after attaching your spreadsheet, or in any AI tool that has your data. Replace the brackets.
Create a [eight]-slide [quarterly KPI review] for [leadership] from the attached file. Each data slide answers one question with one comparison: [actual against plan]. Write every title as a finding with its number and comparison, under 15 words. Use a waterfall for [plan to actual revenue], a line chart for [conversion by device and month] and a table for the [KPI scorecard]. Add a subtitle with measure, unit and period, and a source line "[Source: system, period]" on every data slide. Use only numbers in the file and change none of them. Put definitions and method notes in an appendix slide.
Rebuild slide [4]. Title: "[finding with number and comparison]". Subtitle: "[measure, unit, period]". Use a [line chart] with [mobile] in the accent colour and [desktop] in grey, labels at the end of each line instead of a legend, and the [start and end values] labelled. Add a dashed marker at [date] labelled "[event]". Start the value axis at zero. Add the source line "[source]". Keep every number unchanged.
For all slides: rewrite each title as a one-sentence finding under 15 words, using only numbers already on that slide. Use "after" instead of "because" unless the slide shows evidence of the cause. Write changes in rates as percentage points, give compared values the same number of decimal places, and show the base for every percentage from a sample. Add a source line to any slide that shows data without one. Do not change any number.
How to build data slides in NOXI from your spreadsheet
NOXI turns an Excel or CSV file into a structured deck with charts, in the style of your own template. It is free, with no card and no watermark; uploading files needs a free account, and a full deck uses about 25 of the 1,000 monthly credits.
Step 1: Prepare the data file
Save the period's numbers as one Excel or CSV file with clear headers and units, plus a short definitions tab. NOXI accepts Excel (XLS, XLSX, ODS), CSV and TSV, as well as PDF, Word, PowerPoint, text and image files, up to 200 MB per file.
Step 2: Match your template
Choose Match reference and attach your company PowerPoint template, a previous review deck as PPTX or PDF, or a screenshot of one slide. NOXI builds the new deck in that style: colours, typography, layouts and visual rhythm.
Step 3: Review the outline first
Attach the file with Prompt 1 and choose Plan mode to review the outline before generation. Check that every title is a finding with its number and comparison, then generate and watch each slide being built.
Step 4: Check every chart against the file
NOXI builds charts in twelve types, including line, bar, horizontal bar, waterfall, scatter and stacked bar. Open the chart data editor to compare each value with your spreadsheet, and edit text and tables right on the slide.
Step 5: Refine with AI
Ask for changes to one slide or the whole deck in plain English or Arabic, using Prompts 2 and 3. Click a chart and tell the AI what to change; on desktop, circle the point that needs an annotation and the AI follows your drawing.
Step 6: Share, export and present
Invite reviewers by email to edit together in real time, or share a view-only link, and restore earlier versions from version history. Download an editable PowerPoint (.pptx) with real text boxes and embedded fonts, or a PDF pre-read, free and with no watermark, and present full-screen from NOXI.
Frequently asked questions
- What is the best way to present data in a presentation?
- Give each slide one question and one comparison, choose the chart that answers that question, and write the answer as the slide title with its number, such as "Revenue missed plan by 8.6%". Show the baseline the number is judged against, highlight the point that matters in one colour, annotate it, state the unit and period, and add a source line. Put definitions and detailed tables in an appendix.
- Which chart is best for comparing values?
- A bar chart sorted by value is usually best for comparing categories, because people judge lengths and positions on a common scale more accurately than angles or areas. Use horizontal bars when labels are long, start the axis at zero and highlight the bar the title is about. To compare against a target, add a target line; to compare change over time, use a line chart.
- Should I use a bar chart or a pie chart?
- Use a bar chart by default. A pie chart suits only a simple part-to-whole message with a few parts that add up to a meaningful whole and one clearly dominant part; the UK Analysis Function sets the limit at five categories. When slices are similar in size, readers cannot rank them reliably by angle, so a sorted bar chart shows the same data more clearly.
- How many numbers or charts should one slide have?
- One chart and one finding per slide is the reliable rule for a live presentation, with the one or two numbers that prove the title labelled on the chart. A scorecard table can hold five to seven KPIs if one row is highlighted. Pre-read decks can carry more detail, but each slide should still lead with a single finding in its title.
- Should the y-axis always start at zero?
- For bar and column charts, yes, because readers compare bar lengths and a cut axis exaggerates differences. Line charts may use a non-zero axis when the movement is the message, provided the axis is labelled and any break is clearly marked. If zero hides a meaningful difference in a bar chart, switch to a dot plot or plot the differences as variance bars.
- When should I use a table instead of a chart?
- Use a table when the audience needs exact values, will look up individual numbers, or must compare several measures with different units, as in a KPI scorecard. Use a chart when the message is a pattern, a trend or a difference. On a slide, right-align numbers, keep consistent decimals in each column, put units in the headers and highlight the row the title is about.
- How do you present survey results in a presentation?
- Show the question wording, the number of respondents and the survey dates in the subtitle, and give percentages with their base, such as "64% of 412 respondents". For agreement scales, use 100% stacked bars ordered from most negative to most positive. Compare groups only when the samples are large enough to support the difference, and title each slide with the finding, not the question.
Sources & methodology
How this guide was made: it applies published data-visualisation guidance and graphical-perception research to presentation practice. The method, chart chooser, title formula, timings and checklist are editorial recommendations, not a standard. Quillmoor Home, its figures and its checkout change are fictional; the arithmetic is real. All sources were checked on 9 October 2026.
- [1] Headline title and statistical subtitle; stating the chart's message; zero baselines for bars and the dot-plot alternative; axis breaks on line charts; pie-chart conditions; dual axes; line limits; direct labelling; source format — UK Government Analysis Function, Data visualisation: charts (published 19 May 2022).
- [2] When to use tables; right-aligned figures, consistent precision, units in headers, totals and gridlines — UK Government Analysis Function, Data visualisation: tables (published 19 May 2022).
- [3] Percentage points versus percentage change; consistent decimal places in a sequence of percentages — Office for National Statistics, Service manual: Percentages (no date displayed).
- [4] Accuracy of basic graphical judgments: position, then length, then angle and slope, then area — William S. Cleveland and Robert McGill, An experiment in graphical perception, International Journal of Man-Machine Studies 25, 491–500 (1986).
- [5] Crowdsourced replication of the position, length, angle and area comparisons — Jeffrey Heer and Michael Bostock, Crowdsourcing Graphical Perception: Using Mechanical Turk to Assess Visualization Design, CHI 2010.
- [6] Truncated y-axes increase perceived effect sizes, even when the truncation is signalled — Michael Correll, Enrico Bertini and Steven Franconeri, Truncating the Y-Axis: Threat or Menace? (CHI 2020; arXiv, revised January 2020).
- [7] Sentence headlines and audience recall in a geoscience course (79% against 69% on 15 questions) — Michael Alley, Madeline Schreiber, Katrina Ramsdell and John Muffo, How the Design of Headlines in Presentation Slides Affects Audience Retention, Technical Communication 53(2), 225–234 (May 2006).
- [8] Colour must not be the only visual means of conveying information — W3C, Understanding WCAG 2.2: Success Criterion 1.4.1 Use of Color.
- [9] A 3:1 contrast ratio for graphical objects needed to understand content — W3C, Understanding WCAG 2.2: Success Criterion 1.4.11 Non-text Contrast.
- [10] About 1 in 12 men have a colour vision deficiency; the most common type affects red and green — US National Eye Institute, Color Blindness (last updated 5 November 2025).
- [11] Chart types grouped by nine data relationships — Financial Times Visual Journalism Team, Visual Vocabulary (no date displayed).
- [12] Rule UN 3.2, "Unify scenarios": actuals solid, plans outlined, forecasts hatched, previous periods lighter in comparisons — IBCS Association, Work group 3 for IBCS Version 1.2: Application of semantic notation (12 December 2018).
Build your next data deck in NOXI, free: attach your spreadsheet, match your company template, review finding titles in the outline, check every chart in the data editor, and export an editable PowerPoint or PDF.



