What you’ll take away
01Give the deck one job02Check the denominator03Follow a revision everywhere01 / Give the deck one job
State who the presentation is for and which decision it should support. A weekly support update needs a different level of detail from a board presentation. Set the audience, the length and the source material before you draft.
02 / Check the denominator
In our fictional example, resolved tickets rise from 100 to 107: a 7% increase. Incoming tickets also rise, from 120 to 140. The first number alone does not establish faster service, higher productivity or a smaller backlog. Include the context that changes the interpretation.
03 / Follow a revision everywhere
If the resolved count changes from 107 to 110, inspect the headline, the chart, the labels and the notes. The new increase is 10%, not 7%. A polished slide can still carry the old number in another location.
04 / Inspect the file you hand off
Open the exported presentation and check text, images, charts and layout at the size the audience will use. Decide what must remain editable. A good preview does not prove that the delivered file kept the same structure.
05 / Keep the evidence with the story
Attach the original data and note which figures are examples. Record the date of the source and the assumptions behind any conclusion. Then ask a reviewer to explain the slide back to you: if the meaning changes, revise it.
Source material
Use the original documentation for changing product capabilities and account availability.
ChatGPT release notes Creating and collaborating on slides