6.2Recurring issues (playbook)
The essentials in 30 seconds
- A symptom first: reproduce and describe the problem before touching the theme or files.
- A probable cause, not a bet: the playbook links each symptom to known causes and targeted action.
- The net before the action: backup, test copy and backup PDF avoid turning an incident into a failed meeting.
Fil Amel — the incident log
Amel keeps an incident log for her presentations. Each entry notes the symptom seen by the public, the probable cause, and the action that resolved the problem. Over the months, the same families come back: misaligned slide, theme without effect, silent video, substituted font, file too heavy and overflowing presentation.
Reflex: name the symptom, check the cause, apply the targeted action — and correct the fundamental behind a recurring incident.
An incident, a symptom
The first mistake is to correct randomly. We start by reproducing the incident and describing it precisely: what slide, what media, what computer, what room. A clear symptom already divides the diagnosis time.
The right reflex: the net
Before any risky modification, duplicate the file, save and keep a frozen PDF. The goal is not to avoid any mistakes, but to be able to go back without losing the work or missing the meeting.
Look for the cause, not the culprit
A recurring incident often hides a missing fundamental: a mask never used, stacked manual formats, linked and unincorporated media, a forgotten technical repetition. Fixing the symptom is not enough if the cause returns the following month.
| Symptom | Likely causes | Actions |
|---|---|---|
| Slide that “never lines up” | Floating zones, stacked manual formats | Home then Restore to layout, redo in reserved spaces (N1.1) |
| Theme applied without visible effect | Hand-picked colors and fonts throughout | Return the objects to the colors and fonts of the theme, purge the manual formats (N1.4) |
| The public reads instead of listening | Paragraphs on screen, lists revealed at once | 5 × 5, 24 pt minimum, appear per paragraph with shading (N1.2, N3.2) |
| Silent video or red cross in theaters | Exotic format, media linked instead of being incorporated, its never tested | Convert to embedded H.264 MP4, test in the room and plan a plan B (N3.4) |
| Morphosis that does not slip | Unrecognized objects across slides | Name the objects in the Selection pane on both sides, then run Morphize again (N4.1) |
| Policy substituted at the customer's premises | Font not embedded in file | Options then embed the fonts, attach a frozen PDF (N4.4) |
| 80 MB file unsendable | Uncompressed media and oversized images | Compress images to 150 ppi and compress media (N1.3) |
| FINAL-v3-bis by email | Round-trip attachments, divergent versions | A living shared link plus a frozen PDF for distribution (N5.3) |
| Presentation that overflows with time | No timing, too many slides | Check timing, cut slides, never speed up speech (N3.5) |
Script ready to say — qualify an incident (30 s)
“On which slide and on which station does the problem appear, and since when? I reproduce, check the media format and correct the cause before testing again. »
To keep to frame an incident with a colleague in a hurry.
Script ready to say — announce backtracking (20 sec)
“I go back to the saved copy so that the meeting is ready, then I look for the cause on a copy. The working file remains intact. »
Reassure: the rollback protects the project.
Copy and paste template — incident sheet
SYMPTOM: [slide / media / message]
STATION / ROOM: [environment]
SINCE: [date]
REPRODUCED: yes / no
PROBABLE CAUSE: [mask / media / theme / file]
ACTION: [description]
TEST AFTER CORRECTION: yes / no
BACKUP / PDF: yes / noCopy and paste template — diagnostic order
1. Describe the symptom and reproduce it
2. Save a copy and a PDF
3. Check media and fonts
4. Isolate: mask, theme, animation, file
5. Correct on the copy
6. Test the projection in real life
7. Document the cause and solutionShort version
Short presentation: the most frequent incidents are alignment and readability.
Remote
Videoconferencing: add screen sharing and sound to the diagnosis.
As a team
As a team: centralize incidents in a common notebook.
Printed version
Without repetition time: save and keep a backup PDF before any modification.
Key takeaways
- Describe the symptom before taking action.
- Save and keep a backup PDF.
- Link the symptom to a known cause.
- Test the correction in real conditions.
48 hour challenge — apply tomorrow
Take three real or simulated incidents, complete the incident sheet and apply the diagnostic order. Note the cause and the regression test. 30 minutes.
- I describe a symptom before taking action.
- I relate the symptom to a probable cause.
- I save and test after correction.
Frequently asked questions
Where to start when nothing is displayed correctly?
The simplest way: open the file on another computer, check the fonts, media and use of the mask. We eliminate a family of causes before looking further.
Should you reinstall PowerPoint if you have any problems?
Rarely. The majority of incidents come from the file: manual formats, linked media, missing font or different version. Resettlement is the last resort, not the first.
How can I prevent the incident from recurring?
Correct the root cause: use the mask, embed the media, lock the model and repeat in the real room.
The video remains silent in the theater. What is the first useful action?
Resources
A recurring incident is not an accident: it is the signal of something fundamental to be corrected, mask, incorporated media or technical repetition.