Too many bullet points make slides harder to follow when the audience has to read, listen, and work out the relationships between ideas at the same time. The problem isn’t the small dot at the start of a line. It’s the amount of language on the screen and the work the slide leaves unfinished.
A short checklist can be exactly what an audience needs. A long list of explanations, exceptions, and supporting facts can turn a live presentation into an uncomfortable reading exercise. Before removing every bullet, ask what kind of information the list contains and what listeners need to do with it.
A list can hide the structure of an argument
Bullet points make items look similar. That is useful when the items genuinely belong at the same level, such as three materials needed for a task. It is less useful when one item is a problem, another is its cause, and a third is a proposed response.
Consider a slide containing “late requests,” “missing information,” “extra follow-up,” and “new submission form.” The list names relevant things, but the audience must infer how they connect. Does missing information cause the delay? Is follow-up the solution or part of the problem? What would the new form change?
You can improve the slide by making that relationship explicit. A short process view might show incomplete submissions leading to follow-up and then delay, with the proposed form addressing the first stage. The structure now communicates something the bullet list left to the audience.
Reading ahead can separate attention from the speaker
When a full list appears, listeners may read the later points while you explain the first. This isn’t necessarily rude or inattentive; the slide has offered visible information, and people naturally try to understand it. The difficulty comes when your spoken explanation and the text demand attention to different ideas.
If the slide repeats your script almost word for word, the audience receives little help deciding whether to read or listen. If you discuss something different from the text, they must choose which stream to follow. Neither arrangement is solved simply by asking people to concentrate harder.
Keep on-screen language focused on what listeners need to retain or inspect. A brief phrase can orient them while your explanation supplies context. Where exact wording matters, give people time to read it before discussing its implications.
Smaller type creates another problem
Long lists often lead to reduced font size, tighter spacing, and more nested levels. These adjustments make the slide hold more content but can make the content less usable. A line that is readable on your monitor may be difficult to read across a room or inside a video-call window.
Don’t treat shrinking text as the final step in slide editing. If the slide needs smaller and smaller type to fit, reconsider its purpose. Some information may belong in speaker notes, a supporting document, or a separate slide with a clear reason to exist.
Nested bullets can also make the hierarchy difficult to hear. A listener may not know whether a spoken sentence develops the main point or starts a new one. Use headings, spacing, or a different visual structure when those relationships matter.
Choose a format that matches the relationship
If the information describes a sequence, use a short sequence with the important transitions visible. If it compares options, a compact table may make the differences easier to inspect. If it explains a physical relationship, a labeled image or diagram may be more useful.
A claim supported by evidence can use a clear sentence headline and the relevant chart, example, or image beneath it. The assertion-evidence approach offers this as an alternative to the familiar topic-heading-and-bullets format in technical presentations.
Don’t replace every list with decorative icons. An icon beside each line may preserve all the original reading demands while adding another set of symbols to interpret. The replacement should clarify the information, not merely make the same content look more designed.
For a broader look at visual competition, see what happens when a slide gives the eyes too many places to look.
Keep bullets when the audience needs a list
A list is appropriate when the items are parallel and the audience needs to inspect or remember them as a set. A checklist before a demonstration, a short collection of options, or a summary of agreed actions can work well as bullets.
Write each item at a consistent level of detail. If one line contains three sentences and another contains one word, check whether you are mixing an explanation with a label. The list may need a short introduction or a separate discussion of the longer item.
There is no universal bullet count that makes a slide effective. Five short labels can be easier to follow than two dense paragraphs disguised as bullets. Judge the slide by readability, purpose, and the amount of explanation the audience must process alongside it.
Reveal items only when the sequence benefits from it
Showing points one at a time can prevent reading ahead during a step-by-step explanation. It can also make a comparison harder if listeners need to see all the options together. Choose the timing based on the task rather than applying the same animation to every list.
If you reveal items progressively, keep earlier points visible when the audience needs them to understand the next one. Avoid elaborate movement that makes people wait for the text to settle. A simple appearance is often enough.
Check the final shared or printed version as well. A deck that works during a live build may be confusing when exported as individual animation states or viewed without your narration. Prepare a readable reference version if people will use the slides afterward.
Separate the live slide from the document people take away
A presentation slide and a reference document serve different reading conditions. During a talk, the speaker supplies explanation and timing. A person reading later needs enough context to understand the material independently.
You can use concise slides for delivery and provide fuller notes or a short companion document. That avoids forcing every detail onto the screen merely because someone might need it afterward. It also lets the written explanation use complete paragraphs where the relationships need more space.
Keep essential labels, captions, and accessibility support. Research about reducing redundant instructional text is not a reason to remove captions needed by participants or to hide information that makes a chart interpretable.
Test one slide by asking what survives
Choose your busiest slide and state its main point aloud without reading it. Then identify the smallest amount of visible information that supports that point. Move secondary explanation elsewhere and check whether the remaining slide still tells the truth.
Show the revised version to someone unfamiliar with the material. Ask what they think the slide says and which part they would inspect first. If their interpretation differs from yours, the problem may be the relationship between ideas rather than the number of bullets.
Finally, check where the slide belongs in the talk. Our guide to presentation structure can help you decide whether it develops the argument or repeats something already established. A useful list earns its place by helping the audience do a specific job.
Sources and further reading
Assertion-Evidence Presentations — a message-and-evidence approach to technical slides.
The Cambridge Handbook of Multimedia Learning: Principles for Reducing Extraneous Processing — research context for coherence, signaling, and redundancy in instructional materials.