We Have Met the Enemy and He Is PowerPoint
nytimes.com
nytimes.com
I keep a copy of Tufte's "The Cognitive Style of Powerpoint" on my bookshelf now. If you ever want some arguments against PowerPoint, I recommend reading it.
There are two books which have made me better at this:
1. The back of the napkin [http://www.thebackofthenapkin.com/]
2. Slide:ology [http://blog.duarte.com/book/]
These books kick-started my journey to understanding (and appreciating) the use of diagrams, colors, fonts, and imagery for the purpose of conveying an idea.
Update: Added links.
It helped me.
One day, with any luck, I'll be able to look back and make the same remarks. Hopefully it will be because I'll be a lot better at it by then.
In a tech talk, you'll never quite match his style. But getting halfway there can improve many talks.
But then the testing team decides that "we have a problem that needs to be solved". It starts of as slides with "vision" with "goals" and how to achieve it we need to develop "critical thinking" and have "better recruitment practices" and what not. Now the ppt is about 50 slides with all kinds of zen pictures and 1 bullet buried inside saying we need automated tests. After a few more reviews it will be presented to the entire organization as "strategy" document.
On the other hand, this is not exactly the common powerpoint presentation, it's just a a deck of specs passed around in that format, so not the same thing at all in the end.
Maybe the problem could be averted if the presentations were replaced with short articles, like blog posts. It would be hard to do worse than what you've described.
Trust is important, because the presenter doesn't have to explain themselves very well. The emotive impact of pictures (or funny stories) can trick you into thinking they have filled the credibility gap. Malicious presenters can leave out details that should really be there - such as how the implementation will actually occur, or the justification of decisions, and so on.
It's also good if you already understand the details, or if you don't know or care about the technicalities. A written report has more space for the technicalities, which is very important if the information has to flow out of the silo you are in, or if the reader wants to drill down and check that you actually know what you are talking about.
I think that the whole "interactions" bit is a little over-hyped. PowerPoint can include interactions, and reports can leave them out.
Although, it would be fun to do a hipster-with-Keynote update of it.
Anyone else tickled by the (presumably unintentional) pun here?
http://www.washingtonpost.com/wp-dyn/content/article/2005/08...
http://www.edwardtufte.com/bboard/q-and-a-fetch-msg?msg_id=0...
After edit: Somehow, I think the most effective international terrorists manage to do without PowerPoint entirely, but have interactive CONVERSATIONS on a need-to-know basis about important operational details. Maybe the United States armed forces should look into doing the same.
This probably sounds eerily familiar to any developer who works in a mid-sized company or larger.
And I thought getting UI designs as PPT slides was bad...
It goes away only when you offer an alternative which is catchier/easier/more elegant.
This would explain why it's so popular for middle management type meetings. People talking about things they don't understand but are responsible for have to give the impression that they're in charge.
Probably not the best aide for /improving/ at public speaking, though.
(Do architects still use drafting tables, or is it all computerized?)
This phrase needs to enter the popular lexicon.
wiki has more about it here: http://en.wikipedia.org/wiki/Pogo_(comics)#.22We_have_met_th...
(grep http://www.acs.org.au/president/1996/atm/npc/im961009.htm fr "powerpoint")
And then, the next step was trying to find a Windows machine... Some employees sometimes had to go to a different building just to fill expense reports.
Good times.
After I read Beyond Bullet Points, my opinion of presentations totally changed. Back of the Napkin helped some, but BBP really ingrained in me the right way to do a deck.
Now when I teach or present, I have a brief deck full of pictures and conveying a simple, reasoned discussion not involving a lot of data.
What happens is that the PPT takes the place of the thinking that goes into analysis. That's really, really bad. Instead, do the thinking, solve the problem, make a recommendation, come up with the couple of points you have to teach, THEN create a multimedia presentation around it. Presentations are like movies -- people absorb them differently than a book. Too often the people making PowerPoints are trying to write a book or impress us with their knowledge of graphics, and the information overload leads to "death by PowerPoint"