Skip to main content

PowerPoint vs White Papers

Rick noted that he had to get his materials ready (right after announcing the winner of the Southwest Fox Scholarship winner - congratulations Dan Taylor!) and it reminded me of this post on Presentation Zen.

Now I will be the first to say that I often use PowerPoint too much and I have tried incredibly hard in the past few years to only use it as an enhancement for presentations, rather than the main focus - (thanks to Beyond Bullets).

However, if you are one of the great speakers getting ready for your sessions at any of the upcoming conferences, read this post. In the tech world, we tend to take for granted that Powerpoint can be useful way of getting across a point and then throw up some code to show "how to get it done" - but would you want your military doing the same?

This is a great read - I almost hate to quote an entire paragraph but it gives you an idea of what's in the post.

Bad presentations are one thing. They are certainly a waste of time (that's perhaps the least harm they do). But even in the worst of presentations, if we really need to know the answer to something we could interrupt or ask the question during the Q&A. With documents and handouts, of course, we have no such luxury. If a document is poorly designed and poorly written, where do we go to get a clarification? And if the document is crucial — even a matter of life and death — is it not paramount that the document be easily searchable with the appropriate depth of data and information? At no time should the reader be saying to themselves: "WTF!— what does this %#@*! mean?!!!"


Presentation Zen: PowerPoint printouts used for communicating battle plans?

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...