Showing posts with label PPT. Show all posts
Showing posts with label PPT. Show all posts

04 May 2010

Top 4 Don'ts for PPT Presentations

We've all been there, sitting through endless PowerPoint presentations where the speaker drones on and on and the slides are so full of text you squint no matter how close you are to the screen. We each have our least favorite PPT foibles, but here's a list of the four worst offenders:

I never met an animation technique that I didn't like.
Slide decoration doesn't equal slide design. Animation distracts from the content of your presentation and the purpose of the presentation is to convey information, so limit distractions and keep it simple.
Why can't everyone just read what I have on the slide?
Slides make up one portion of the presentation; they should not "stand alone" (even when you are offering copies of slides for notes). If the slides can stand alone, then what is the purpose of you being there? Just write a report instead.
Charts and tables are "islands that speak by themselves".
Charts and tables are never "islands that speak by themselves", whether in presentation or report. Some explanation is required, on the purpose of the table or the conclusions drawn from the data. Once again, a table on a slide augments your spoken presentation and should not be treated as a stand alone.
Everything I know on this topic must go on these presentation slides.
Also known as "cram everything in obsession". All of your knowledge on a topic doesn't need to appear on every page of the slide. Slides should be easy to read, and as brief as possible, otherwise people will spend their time reading your slides instead of listening to and being engaged in the presentation.
And remember, PowerPoint (or Keynote for fellow Mac users) isn't right for all meetings, briefings, and presentations as shown in the article "We Have Met the Enemy and He Is PowerPoint" from the NY Times about the usage of PPT in the US Military. The "bowl of spaghetti" map shown in the article is a great example of why everything shouldn't be crammed into one slide.


Originally published on our Knowledge Management blog

26 August 2009

What’s Wrong with PowerPoint as a Document Authoring Tool?

In our McCulley/Cuppan consulting work we recently had a new client invite us to work with an authoring team on applying best practice to the planning, writing, and reviewing of a regulatory submission document. The document was going to be a significant piece of work, requiring over 500 pages and involving multiple authors across several scientific disciplines.

At the first meeting, the project leader announced she wants to continue the use of PowerPoint (PPT) as the document planning tool. Reasoning for this approach was in part because she and other team members already invested considerable time and effort in generating a 540+ slide deck representing data and messages to be in the regulatory document and PPT was a very familiar tool from extensive use in developing presentations.

I have to say we were mildly surprised by the demand to use PPT as the primary tool to plan and outline such a large, complex document. We have encountered other organizations using PPT for document planning purposes, but never on such a large scale. On the surface, the choice of PPT as the tool to produce initial draft documents seems reasonable. It is familiar to many, provides an authoring environment that produces output that can appear on screen as an outline, can be commented on in oral or remote review, and can be easily augmented and updated. All of these apparent benefits would support an argument for using PPT as an outlining tool to plan any and all documents. However, the use of this tool does not readily scale to developing large, complex technical documents.

Christine Haas, Karen Schriver, Thomas Huckin, Edward Tufte, and others tell us much about how readers interact with and read texts. From this collective body of work we have learned some things that can help us produce texts in an effective manner that, equally, is perceived as of very high quality. The prime method is to use tools that enable the design and review of texts as you expect your readers to engage in the reading and analysis of the text.

Successful collaborative authoring is significantly rooted in careful and thorough front-end planning. Choices of authoring tools are among the critical aspects of the document planning process, as tool choices impact (enabling or constraining) every other aspect of the planning and documentation processes. As authors and managers of authors, it is incumbent upon all of us to choose tools that accommodate our desired set of outcomes. Authors and managers must be cognizant of authoring tools that accommodate not only themselves and their ways of working, but others as well.

It is our position that use of PPT for document planning negatively impacts all potential collaborative authoring and review outcomes. Our claim assumes that the goal of the work is to generate an effective document, economically produced, that meets or exceeds end-user expectations.

I have outlined here key advantages and disadvantages of using PPT to plan and facilitate documentation of a multi-year, complex pharmaceutical development work.

PPT Advantages
  • use is a habituated format; it’s familiar.
PPT Disadvantages
  • presentations constrain data reporting rather than facilitate collaborative/interpretive processes (see my previous blog post on PowerPoint presentations).
  • format creates/maintains a huge but fragmented vision of the process and product, impacting output (see Schriver and Tufte).
  • PPT does not scale well to large documents as it limits information organization and searching is cumbersome, impacting review and the authors' ability to migrate material from PPT into a document-based format.
  • PPT presentations do not accommodate major revisions/reorganization; impacting logic, content, and organization of the ultimate document product (see Schriver).
  • the output decreases in clarity as the number of slides increases, impacting author/reviewer interpretation (see Tufte).
  • PPT output is not a document; conversion to MS Word format is inefficient, time-consuming, and expensive.
The point seems clear in the choice of using PPT as an authoring tool is that familiarity wins, despite that, from a business, work, or quality perspective, the disadvantages of PPT clearly outweigh this single advantage. Eschewing proven document authoring platforms for the familiar may have unintended consequences and bear a high tariff.

Originally published on our Knowledge Management blog