Like ‘bunting in the office’ and ‘cake on release days’, ‘slides with big words’ has become one of GDS’s hallmarks. A few weeks on from Sprint 16 I wanted to write about why we encourage that.
Our slides are very simple
Presentation software, like most software, gets used in lots of different ways. That’s normally fine – if you want to use slides to do wireframes then go for it – but it’s a problem when someone’s used presentation software to make, say, an organogram and then gets up to present it without changing a thing.
We’ve all sat through the presentation that ought to be a table emailed to the finance team. Or been shown the complex user journey that ought to be printed out on a wall. Or asked to approve copy on a slide that should, instead, have been emailed. It’s tedious. So we’ve deliberately constructed a template that forces the writer to think of the presentation as a thing they’ll be presenting.
The typical GDS slide is designed to;
- be easy to read (even at the back of a large room, or on a small screen)
- keep the emphasis on the speaker
- force the writer to be extremely clear about what they’re saying
Our ‘normal’ slide is designed to support a single short line of text. Our ‘heading slide’ is designed for even fewer words. We try to make sure our images illustrate the point the speaker is making. We enforce a strict ‘no metaphors’ policy. And, wherever possible, we encourage speakers to use screenshots or demos so they actually show the services or tools they’re talking about.
On the whole, it’s a pretty simple setup.
Clarity comes with preparation
A very plain template gets you about a third of the way. The rest comes with preparation. If you use the template but don’t prepare then it’ll be very obvious that you haven’t given much thought to what you’re saying. You have to put the work in.
The three things you should be asking yourself as you prepare are:
- What is the main point I want to make?
- What else does this particular audience need to know to understand that point?
- What is the best order for those things?
As you ask those questions your answers will start to change. You might realise your audience knows more than you thought initially, so you need to make a different point. Or you’ll see a different order emerge as you rehearse it. Like anything else, iteration will get you where you’re going. Iteration, and deleting things.
Russell Davies used to tell people that each minute onstage should equal about an hour or preparation. It’s a good rule of thumb. (He also wrote a great series of blog posts about preparing talks that’s worth reading).
Slides aren’t your only tool
You don’t have to rely on a presentation alone to get the job done. Need people to approve some text? Send it before or after the meeting. Need to share a chart in a meeting? Email it round or print it out (and use a placeholder slide to prompt people to look at it). Got a big diagram you want to walk people through? Print it out really big and literally walk people through it. It's ok to point to things on the internet too, as long as you use short URLs they can copy from slides quickly, or take a picture of.
We’re not the only bit of government that works like this; DVLA digital, MoJ and much of Cabinet Office use similarly plain slides and often have similar ‘rules’ about what people should include in presentations.
The end results might look extremely plain, but the slides are clear and, more often than not, gel together into a cohesive argument.