Secret #2: A bar chart is usually better
People are not coming to see your slides. They are coming to see you. Everything about your presentation should reinforce that fact. Like any good story, keeping a rapt audience involves doling out the plot in measured increments. Subtitling yourself on your slides might be a great way to organize your thoughts but it’s a surefire way to lose your audience. They read faster than you can possibly speak. You lose their attention twice when you show a slide with bullet points—once when the slide appears and their brain is muting you while they read, and once again when they return their attention to you, because now you’re just repeating what they’ve read. Mitigate this by never ever using bullet points or animation, and writing your content in a fashion that generates more questions than it supplies answers.
(Full Story: http://gazit.me/2012/12/05/designing-presentations.html )
1. The Hockey Stick2. The 2 X 2 Matrix3. The Stoplight or Harvey Ball Chart4. The Diagram: The more complicated the better.5. The Logo Chart: Lots of logos of lots of big name customers.
What the same presentation would look like while following conventional slideware templates found on present day planet Earth. “You can’t see this well on this Micro Galactic ProjectionPoint, but an analysis of the plans provided by Princess Leia has demonstrated a weakness in the battle station. Follow this link at the bottom of the screen for more info if needed.”
(Link: Presentation Zen: A long time ago, before death by PowerPoint)
Developer-driven testing is probably the most influential software development technique of the last 10-15 years. There’s no question that it has improved the practice of building software. And in a dynamic language like Ruby, it’s hard to get by without it. But is it really the best way to find defects? Or is the emphasis on testing and test coverage barking up the wrong tree?
(Link: InfoQ: Testing is Overrated)
It would be easy (and fun!) to discuss PowerPoint (PPT) culture in general: how it ruins meetings, wastes time, confuses audiences, and is a general haven for bad design and writing. But instead, we will use this opportunity to discuss something useful. We will review design techniques that generally meet with approval and praise. We will also review why these techniques are actually quite bad and what you can do to fix them.
(Link: PowerPoint Designs that Executives Love (But Shouldn’t) – WorkAwesome)