SlideMagic Blog

Frequent updates about all things presentations since 2008. Subscribe to never miss a post.

RSS
all posts

Category Keynote

·Keynote

Bottom up versus top down

If your corporation consists of business units, than your corporate presentation is likely to end up as a series of chapters, each talking about a different business unit. If the corporate centre is organised, then each chapter might have the same repetitive template/structure. Each business unit gets airtime based on how important it is (usually in terms of sales). The order of the chapters is probably in line with the seniority of the business unit leader. It all makes sense in the political structure of the company.

Your real story might be different though. A small business unit might have all the growth potential that your investors are curious about. A more junior manager might be a captivating speaker. The same presentation template might not fit the specific story of each business unit. Seeing exactly the same template 10 times is boring. And how do all the business unit stories link together to a bigger picture?

Sometimes it is better going top down than bottom up.

·Investor presentation

"Do something like this"

I get this request sometimes, with an attached presentation of another company. Most of the time, the example presentation is actually not that good.

My theory of why it still appeals to a client? It is written in the same corporate language that she uses. As a company insider in a similar industry, she can instantly decode the language and it all makes perfect sense. Two CEOs communicate to each other in highly efficient compressed CEO speak.

The problem is a competitor CEO is unlikely to be the audience of your presentation…

·Data visualization

Powerpoint vs Keynote - redux

It is a question that comes back all the time: PowerPoint or Keynote. I have given my opinion in the past.

After I got my first Mac, I was really excited to be able to design in Keynote. Now, a few years later, I must say that both products are more or less the same to me. Keynote is cleaner, auto-aligns and distributes objects when you drag them, and does not have the problem of drawing guides that you move by accident, and has a tight integration with the iPad. PowerPoint has a more convenient photo cropping UI and a much better data chart engine (Excel).

But workflow is a very important consideration as well. If the people in your organisation find it difficult to get up the learning curve with Keynote, why torture them? This is especially true if people need to do a lot of copying back and forth between Excel and PowerPoint. Probably 90% of presentations are quick and dirty documents to discuss business data, and in those cases tight integration between the 2 programs is a big time saver.

In the end both applications can deliver exactly the same look and feel of presentations. When I tell clients that Keynote presentations do not automatically look better than PowerPoint ones, they are surprised.

So in short, it actually does not matter what software you use, it is your design that matters.

·Keynote

Technology lecture vs value pitch

Two approaches to pitching your product. I prefer #2

  1. Engineering approach: explain the layered product architecture and the solution process, and after this theory lecture you can make a perfect logical case about why your product delivers this great value to your customer.
  2. Customer-focussed approach: highlight the big issues the customer has (to get that nodding head), go through the benefits that your solution offers and only hint at the technical magic that allows you to deliver them. If the customer is interested, you can do pitch #1 in a second meeting.
·Keynote

Project time wasters

I have submitted price proposals to hundreds of projects and won/completed the majority of them, so I have gotten a pretty good sense of what presentation design activities cost time, and which ones do not. Use them to your advantage when negotiating a project with a freelancer.

Project time wasters:

  1. The most important one: unclear story that needs sorting out
  2. Lots of physical meetings
  3. No clear decision maker on the client side, i.e. freelancer needs to collect and synthesise feedback into one voice
  4. Requirement to run 2 parallel versions of the same presentation (different language, different audience)
  5. Start and stop, pick up the project after a hiatus that was long enough for everyone to forget what it was all about
  6. Inconsistent PowerPoint masters, i.e., client provides feedback pasted in the default PowerPoint template so all colours, fonts, and slide formats are messed up
  7. Requirement for a text 1-pager that summarises all, with lots of iterations on the exact wording of the text
  8. Related: communicating micro edits over the phone to the designer, rather than quickly doing them yourself in PowerPoint (text edits, slide order changes, etc.)

You that slide count does not appear in the list. Adding a few slides with a few new concepts to an existing presentation deck. Once you have understood the story/company, the marginal time required to add things to a presentation is low. Of course a 100 page deck takes more time to complete than a 10 page presentation, but still.

·Keynote

Clicking links in slides

It might seem cool to have an interactive slide full of clickable links in your presentation. In yes, in a 1-on-1 meeting you could permit yourself the luxury of clicking back and forth through slides as you tell your story.

For a big audience, a linear story is much better. And when you need to click on a link in a slide, it is likely to be the exact same link/box/object every time. Why struggle with mouse pointers and try to hit that exact box when you can just click through the next slide that starts playing your video? The audience will not notice the difference.

·Keynote

Simple can be difficult

This is a text editor that only allows you to use the 1,000 most common words in English (“thousand” is not one of them, hence they called it “ten hundred”). Try writing something, it is pretty hard.

Here is a blog where scientists use the tool to describe their research projects.

·Data visualization

Icons that try too hard

Icons can work really well if they can be kept very simple, and refer to very simple things like a cog wheel for settings and a 1980s floppy disk for save.

When you try to summarise very complicated concepts into very complicated icons, things get lost. In those cases, a box with a few words will do a better job explaining what you mean.

·Keynote

Stock image maps

Maps in stock photo sites are not designed for use in presentations. I hope designers are reading below to find out what is wrong with them:

  • Crops are focussed on the target country. But why crop so many of the surrounding areas out? Israel for example has a vertical shape. I would prefer to put in a map of the entire Middle East, and put text boxes over those part of the map I do not need. It will look much better than a narrowly cropped map
  • People use blunt colours and/or gradients. As a designer, I want to set the colour tone of the presentation myself. Much better options are muted greys, or better, vector files I can recolour myself.
  • Map designers add city names hardwired in ugly typography. Also, they add roads and other useless geographical information. I will not be using these maps to find my way, if I need to add cities, I would like to do it myself, in the font of the presentation deck.

So how do I pick maps in stock photo sites? Usually, I go for vector images for a far wider area than I need. I zoom in and strip out all the information I do not need.

·Data visualization

** Footnote

In tables, I prefer to right-align numbers with the same amount of decimals after the dot. A footnote reference can break that line. Two ways to solve it: One: add the ** as a separate text box on top of the table. Two: if you have to use many footnotes use numbers [i.e. 7) instead of ******] to keep your footnote references short.