Part VI

PART VI: Slide Design

Chapter 11: Build for the Back Row

Your slides need to be readable quickly. Avoid:

• tiny text;
• long paragraphs;
• complicated tables;
• excessive footnotes;
• cluttered charts;
• unnecessary decoration.

The judges should not have to squint. They should not have to read a paragraph while listening to your presentation.

Reduce the Cognitive Load

Every slide asks the audience to process information. You can reduce cognitive load through:

• fewer words;
• clear hierarchy;
• simple visuals;
• consistent formatting;
• meaningful whitespace;
• clear labels;
• logical sequencing.

Good design isn’t about making the deck beautiful. It’s about making the thinking easier to understand.

Consistency Matters

Establish rules for:

• fonts;
• font sizes;
• headings;
• alignment;
• margins;
• chart styles;
• footnotes;
• page numbers;
• colours;
• pacing.

Then follow them. Consistency makes the deck feel professional and lets the judges focus on the content rather than the formatting.

Chapter 12: Don’t Design Your Deck Like a Poster

A presentation slide is not a document. It doesn’t need to contain everything. It should contain what the audience needs at that moment. Your report can contain detail. Your appendix can contain detail. Your speaker can explain detail. The main presentation should contain the information necessary to make the argument.

The Information Hierarchy

Think in three levels:

• Must Know
  • The judge needs this to understand your recommendation.
• Useful to Know
  • It supports the argument but doesn’t need extensive explanation.
• Nice to Know
  • Interesting, but not necessary.

Most teams have too much “nice to know.” Winning teams prioritise “must know.”