I'm guessing you copy/pasted the title in from the blog but you should probably remove the CAPS.
I like this way of doing meetings, I haven't heard of anything similar before. Although I've always hated slide shows. Do I read the bullet points? Listen to the presenter? Does the presenter read the bullets and go into detail on each one? What does it mean if there is a bullet but the presenter doesn't mention it during the presentation? There's too much going on at once. A good slide show can work very well (using a slide to illustrate your point with a graph etc.) but most people can't create good slide shows.
Not the OP, but the last time I submitted an article on HN, it auto corrected the title to match what the link said (which was much more vague than the title I gave). Perhaps HN auto corrects verbatim, including caps.
This reminds me of when I was back in school and the instructor would have stuff in Powerpoint on the projector screen. It was only interesting when a photograph or image would be displayed (this was an East Asian history class) but the rest of the time was just me listening to him speak about the topic rather than paying attention to the slides at hand.
Why? Because he was pretty much just narrating what he already had on the screen.
I have always found that Powerpoint is useless for displaying anything in a meeting or seminar and yet I still find myself doing that when I myself choose to give a presentation. Additionally, I have yet to see anything that replaces it well enough that also mimics the speed and simplicity of the application, and I also find more value in just listening to the person rather than seeing what is on the screen.
I had so many professors that just read me the powerpoints. I would literally miss nothing from the lecture if I just downloaded the slides after every class, but no, attendance was mandatory. Makes me feel all warm and fuzzy to know that I'm still paying off an education I could've gotten most of by reading a few pages of bullet points every week.
Yeah, I think this practice originated at Amazon not long after Edward Tufte's article “The Cognitive Style of PowerPoint” was published. I think I heard that Bezos read that article and was influenced by it.
Probably true. The reason I was introduced to Tufte is when he was invited to give a talk at an Amazon Fishbowl (informal, internal lecture/music series). This had a strong stamp of Jeff-approval. I don't think that this particular practice was adopted immediately but Bezos plays a long game and this was probably an opening move.
I'm not sure about just reading a six page memo out loud to everyone. That seems like a great thing to email to everyone. Some of my least favorite memories from college are the couple of classes I went to where the professor basically read the book to us. The difference is, I'm guessing, that attendance isn't optional at an Amazon meeting.
Personally I like keeping presentations on the short side - only using slide shows for ancillary data like citations (which I find awkward to fold into the flow of a speach) and graphical data. Unless something is really interesting or very important, it's only going to get 5-10 minutes of people's attention.
You don't read it out loud. You bring printed copies (or send electronically) and everyone reads it for themselves, in silence, at the beginning of the meeting.
For clarification, the 6 page memo is not read aloud. Each person is provided a copy at the beginning of the meeting and the first 10-15 minutes of the meeting are completely silent.
This actually works pretty well because in the real world people usually only skim the info provided in advance of most meetings because they only need to "get the gist" of what's being said. This forces everyone to have a thorough understanding and promotes more thoughtful discussion.
I don't think powerpoints are inherently bad, but they're misused enough that I wouldn't begrudge anyone who wanted to ban them outright.
The two best ways to use them, from experience, seem to be:
- Super dense slides. These slides have a lot of text and are information-rich. You're not expected to read them, and the presenter will just skim over them, presenting a high-level view of each topic, but definitely not reading off of the slides. The slides are there as a rough guide to the talk, and as an in-depth resource afterwards.
- Super spare slides. These slides have few-to-no bullet points, and are heavy on pictures. They're pretty much there to guide the speaker's narrative, and nothing else. At worst, there might be an inherently visual data element, like a graph.
The common element being that the slides are there to guide the talk, not be the talk. The reason powerpoints are so reviled is because people tend to just write a speech, put a bullet point in front of each sentence, and read it off a projected slide.
My preferred powerpoints support the talk. They provide things the speaker cannot- pictures, tables, graphs. Sometimes bullets are nice for openings and closings to summarize.
I did a presentation recently regarding Git and git-enabled workflows to a room of people with SVN and TFS backgrounds. The only slide I relied on was the git-flow workflow graph. Everything was a live demonstration of the workflow by actually using git live on the screen.
A projector during a presentation should be used to show what you cannot say or to clarify a point graphically.
Of course they aren't inherently bad. Powerpoint is a tool. There are good ways and bad ways to use it. It's easier to use Powerpoint ineffectively than with other mediums.
I don't know about that. I've seen a lot more bad power points than bad speakers. In my experience truly good power points and truly bad speakers are both rather rare.
Quite, the problem isn't powerpoint it is that people don't know how to give presentations (or often why they are giving the presentation). Consequently they use powerpoint like a drunk uses a lamp post.
In my experience the people who give shitty presentations with powerpoint would also be perfectly capable of giving shitty presentations without powerpoint.
This is a witty point, but OTOH powerpoint has become the ubiquitous hammer of the business presentation which has everyone searching for nails.
There is a time and place for slides with a few talking points per, but in many ways it's contorted most all meetings into PR events even when there's nothing to sell.
Well said! I am in complete agreement. Why are we blaming tools when it's the presenters fault themselves for not being able to present? If your staff can't articulate his/her idea properly, train them. Not everyone knows everything right off the bat.
In my experience at amazon, a shitty presentation never gets presented. "I won't schedule a meeting with our VP if you don't fix this" is the basic filter they use, and it works.
I would disagree at least in the part that spending endless hours on meaningless non revenue generating flair / graphics art work, could theoretically be devoted toward either improving the presentation content, or toward revenue generating activities resulting in better results contained in the powerpoint.
I would also disagree in that its a crutch for the absolute bottom of the barrel presenters, because no matter how bad awkwardly reading slides to the audience is, its better than silence / choking up / repeating themselves / skipping intermediate concepts. Being read to like a preschool child is better than not getting a presentation at all, well, at least most of the time.
This just doubles my question from reading the original post: A full half-hour, for a six-page memo? Are these incredibly dense and full of new information to the readers? People don't really read that slowly. Average adult reading speed is something like 250 wpm. Average memo might be, what, 300 wpp? So, six minutes to read, maybe ten if you're taking your time?
Not sure anyone has the answer, but that length of reading time vs. the presumed number of words to be read struck me as notable.
I worked at AWS for a while. So a lot of times when I've been in such meetings, the 6-page document was actually full of technical details (design docs, product FAQs, post-mortem reports, etc). So taking 20-30 mins to read through the full document, re-read some sections and write down questions/comments is not that unusual.
Maybe it's just being on a team that's more focused on nontechnical users, but I still see plenty of PowerPoint. Product, sales, and business process people seem to swim in the stuff.
When I was with AWS last year none of our meetings followed this type of structure. Someone put together a presentation in PowerPoint if needed, went through their items, people asked questions and action items were assigned. Pretty typical of any company I've worked for. Although I thought there were too many meetings to attend which took away many peoples development time.
Although I've seen all the 'bad examples' come by, on average I don't have much of a problem following ppt backed presentations, contrary, apparently, to others.
Nevertheless I think this is a great idea on itself. I've seen too many meetings where there was reading material but so few people read it that the talk actually focussed on them.
There's one issue though, and only experience will tell whether it is relevant. I for myself am fond of taking in knowledge via paper but the effectiveness of this highly depends on the moment I'm reading. Also I've noticed I find it harder to concentrate when I'm reading 'together in a group'. I feel a bit rushed by it. But perhaps that's just me or something that is easy to get used to.
When I was in high school I tried to ban powerpoint, arguing that it inhibited our ability to grow as public speakers. I wrote Edward Tufte and told him about it and he shipped me 20 copies of "The Cognitive Style of Powerpoint: Pitching Out Corrupts Within" (http://www.edwardtufte.com/tufte/books_pp).
Some teachers opposed it and I ended up losing. I'm sure Powerpoint was more convenient for them. I use deck.js for slides now but mostly for images - the other slides tend to have 3-4 words while I try and tell a story to draw in readers.
My last project pitch to management I printed out copies of a written proposal and had everyone read for ten minutes to start the meeting. It was actually really nice.
Using it right is a little bit of a skill. Too much panning and zooming can be bad, but just the right amount makes the presentation seem more fresh and alive than a ppt.
I've been using prezi for a few years now, and almost always get good audience feedback. Like any tool, you still have to know how to use it, it will not do all the work for you.
I looked at a sample Prezi, and it had way too much panning and zooming. Of course, then again, I was quickly clicking through it, whereas normally I'd imagine there'd be a couple minutes of talking and delay between each step.
When transmitting information on screens, you can only fit ~7 lines of ~7 words each at a readable font. This inhibits the transfer of complex narratives.
Fancy animations and zooms can't fix this inherent limitation of the slide format.
I was so anti PowerPoint that I used to actually build presentations in Flash (im saying in the late 90s) so as to avoid using it. But most teachers would reject the option since traditionally everyone knew just about PowerPoint.
My girlfriend is a teacher, and I can say for sure that it is a lost cause.
Teachers know that their slides suck, but it's what they are taught, and is what their curriculum demands. They demand bright colours, Comic Sans for dyslexic students, and tons of text on each slide.
For a middle-management role in the school, I designed her slides using one of those JS slide scripts, and it went down a treat. It took me the best part of two hours to port her content from Powerpoint to these slides, and I was able to add videos, animations, and to embed Google Apps data directly into the slide. Apparently, the interviewers had their minds blown by being able to view a Google Docs spreadsheet (where I had written the formulas) directly into the slide. I'd still say that it was fairly poorly designed, but it was a lot better than what kids are forced to read.
Edward Tufte hosts seminars, and this 1 page report is what he was talking about this year (I don't know how much content varies from year to year).
For information density, you can't beat paper, and there's a number of things you can do to make the paper very information dense, like sparklines. He argues that in some ways, sparklines are actually typography and not charts.
With the paper report people can drill into the information they want, and ask questions from there, as well as refer back to the information during Q&A. One quote he said was "They didn't get to become your peers because they can't read fast."
He also said to not give homework. When you make these reports, you spend meeting time reading the paper. It's not something they have to do before, because everyone is busy and no one will actually read it.
Amazon, when I worked there, had the worst meeting discipline of all the companies I have worked for. Meetings normally started 10 minutes late and most people didn't show up until 5 minutes after the start time. Being punctual it drove me up the wall.
This is pretty accurate. Most of the meetings start with reading, and if people arrive a few minutes late, they grab a memo and get to marking it up silently without disrupting everyone.
As an audience person (ie, listening to talks) I believe "Powerpoint is easy for presenter, hard for audience" is crazy talk.
I generally follow using the slides, not listening to the dude who's talking for 30min-1h thank you very much.
Making things simple as you present something complex has nothing to do with having a powerpoint presentation or not. Nothing.
Giving a paper to read is just the same as powerpoint, except if the speaker sucks, you don't have to endure that. So yeah. Wrong punch line, okay approach.
This reminded me the way we did Design Reviews at some multinational corporation.
I would write and print a design document of 30-50 pages long, schedule a 1-2 hours meeting and send the document in advance to those 5-10 people attending.
Off-course only 1-2 persons would actually read in advance.
Then we were reading it page by page and discussing it, giving special attention to various diagrams, such as flow charts, sequence diagrams, FSMs and UMLs.
We almost never were able to finish in time, so the next meeting should be scheduled (in 1 or 2 weeks because of scheduling constraints) ...
I'm in love with this idea. The information density (in terms of time) of a well written memo is much greater than that of a presentation. Many 30 minute presentations could be read in 5 minutes.
The written word is also a great equalizer. A "presenter" can be judged based on their content rather than their public speaking ability.
6 pages is a bit too long, though. In a famous Ranked 1st Consumer Goods company (i'll let you guess which one) all team memos to management are only allowed to be of a single page. This is really hard to adapt to it at the beginning but decision making is so much faster.
It does not mean it does not have details, but you have to sort out the details that matter for management. That's how they can make decisions instead of drowning them in pages and pages of information.
While it is a valid goal to cut down on irrelevancies (like empty lingo), it's the exact the wrong mentality to consider detail the enemy of good decisions.
Good decision making stems from understanding a problem comprehensively, not via often misleading generalities. I would even question whether it's possible to accurately summarize anything more trivial problems in a single page; the sort of menial issue that doesn't warrant a widely-distributed memo in the first place.
Then your doubts are not limited to 6 pages either. How do you determine the right number of pages then? 6 pages may be summarizing thousands of pages of information for all you know. How is this enough ?
In the end what really matters CAN and SHOULD be summarized, and if additional details are needed there is always a place for sharing and discussion with management.
>In a famous Ranked 1st Consumer Goods company (i'll let you guess which one) all team memos to management are only allowed to be of a single page. This is really hard to adapt to it at the beginning but decision making is so much faster.
I'm sure less info makes decisions faster, but this seems rather the opposite of a virtue. Eg. GWB "the decider".
It does not mean there is less info. It means the info is more dense, more concise, well prepared and summarized and straight to the point. It's not because you have 6 pages that it's a guarantee to avoid putting 5 pages of garbage or unnecessary prose.
It also means you can, by definition, not put more than 1 page of details into a given issue.
As usual the Navy/DoD seems to have this figured out:
BLUF: "Bottom-Line Up Front": Concise description of the problem, recommended solution w/out corroborating detail.
FYSA: "For Your Situational Awareness": This may help the boss understand the problem better, but it isn't something they need to know or understand right now.
FYI: "For Your Information": Boss, you need to read this before making your decision.
If you can't trust your underlings to use each appropriately so that you can triage what you have time for, then you either need new underlings or you need to take responsibility for training them better.
A 1-page limit on decisional memorandums is just as artificial as a 64-KB limit on code page size for executable programs.
Most 6-page memos I've found in the wild are 1-page memos that the author felt had to be padded to look more "professional."
And everybody's always busy. If you send them a 6-page memo, they won't read it before the meeting. One page? Yeah, that's doable. So they go to the meeting knowing what it's about.
Cynicism not necessary. It depends on the culture of internal communications and the purpose of the memo. Are these weekly update memos on activities to be discussed at the staff meeting? Is it asking for permission on something? Is it just informational? Receiving dozens of these a day can be daunting, and forcing limits on length force articulation of what's new and a clear question being asked. Sounds very basic, but lots of memos are poorly written.
Google and other companies are known for very brief updates (may be called memos in your organization), as short as a single line, sent per week. No need to send multiple pages of details: http://blog.idonethis.com/post/16736314554/silicon-valleys-p...
These memos are different from the author's post, which is really not about memos, but rather an alternative means of presenting all of the information required to get to the key discussion in a meeting. I don't think is anyone is suggesting that 6 pg emails should be the memos, and something is wrong if the 6pg emails are replacing decks that are being sent around via email.
Presumably management can (and should) drill down. I suppose it stops middle managers from covering their asses with excuses like "Yeah, I said there was a risk of it all exploding, in paragraph 3 of Appendix II".
If they find out something important was left out, they know there was an attempt to hide it.
One page suffices to give an immediate “yes” or “no” for the vast majority of decisions. If more details are required, you could just ask for them, or even call a meeting.
It does depend on the structure of those 6 pages. If I had to do these regularly I can easily imagine settling on a (largely) routine format, e.g 1st page is overview, 2nd page is problem detail, 3rd page is solution/implementation, 4th page risks/mitigation blah blah blah.
Note that the article says the first 30 minutes of the meeting is reading the memo. It doesn't take 5mins to read a page so there's ample time for people to formulate an opinion/questions before discussion actually starts (based on enough info in the memo). This is already an order of magnitude better than any powerpoint talk I've been in where people just shoot from the hip.
I guess the 6 page idea comes from getting more substance from these presentations. Sure you can threw around 1-page bulleting lists all day, but if you want to include stats, references, screenshots, visualizations and have some reading-friendly formatting, the 6 page look about right.
Not in the slightest. I just didn't want to spell out each heading (I just threw out the ones obvious to me). If I'd said "etc" instead of "blah" would you still have picked on it? (I sometimes use those interchangeably when speaking).
In any case, the actual structure I'd use would evolve over time, based on my experience of such meetings.
Back in the day, President Reagan insisted that all decisions he needed to make be given to him in the form of a one page memo with a yes/no checkbox. We made fun of him for being stupid back then, but now I appreciate the wisdom of it. If he needed to know more, he could always ask, but a one-page yes/no decision forced some efficiency.
Of course, the effectiveness of this approach depends a great deal on the quality of your staff.
They don't have to be 6 pages at Amazon (and the discussion starts after everyone's done reading, not after a prescribed 30-minute period). Oftentimes what is requested is a 2-pager. However, even the 6-page ones are not full of fluff; they're usually packed with data and analysis. Fluff tends to get pulled out pretty aggressively in favor of more information that's been requested sometime during the drafting and review process. By the time a document gets to Jeff, many eyes have seen it.
It has been my extensive experience that anyone above mid-level manager will ONLY read a power point -- ie a summary, a graph, and a couple of bullet points. Never a email longer than four sentences and never, ever a report.
Its worse than that. In many companies, a slick powerpoint presentation weighs far more than thoughtful analysis. I've done the experiment and presented the same recommendations based on the same logic in two ways. The concise email got a 'good idea we should think about that' - the powerpoint three weeks later (same words, nothing in the business had changed) got a 'brilliant work we need to drop everything and do that now'.
These are smart and capable people too. They're just somehow got this deep bias about only pretty powerpoint could be important.
One of the hardest things I've learned over the years is how to condense information into quick slides, quick demos, quick presentations. People don't have the capacity that some of us might have. We're used to the material, so it's second nature to us. And other people don't see things that way. Especially when you're communicating with older people who will be lucky to understand 50% of a keynote, product demo, idea, task, problem, etc. They need the facts, and they need them quickly. I love the Amazon approach behind memos, and everything being shorter and to the point in general. The way to go. It's crazy how much you can condense that shouldn't have been there in the first place. Beautiful.
This seems pretty much what Steve Yegge said a few years back - cannot find the ref but he had to write a essay for Bezos to read - no PowerPoint.
I think it's sensible - you can write a PowerPoint in ten minutes and not have to think things through. Try not thinking while writing 6 pages of argument - it will be impossible or achingly clear when it's read.
I think the best points:
- Reserved time for everybody to read and understand the issues before meeting starts
- Something tangible for those not able to participate in the meeting
It's odd how tied some folk are to slides even when it's a completely inappropriate tool for the situation at hand.
On the viewing side as as well as the presenter side.
I occasionally workshops on various things. Some (not all) of them <gasp> don't have any slides.
None.
On the grounds that the point of the workshop, as far as I'm concerned, is to pay a lot of attention to what I'm telling you - and do the practical exercises. You learn by doing - not by reading. A slide deck just gets in the way of that. It's a barrier between me and the class.
Every time there's one or two people who really hate that and complain about the lack of the deck. Not the quality of the workshop - that they're fine with - but the fact they don't have a slide deck.
Occasionally it's because they want to take away the deck and run the workshop inside their own company for free (and hey - I don't mind about that. Honest. It actually helps sales ;-).
But more often folk seem to need "a thing" to take away and look at again. Not so much as a learning tool, but as token that they were there.
I'm seriously considering making some physical "things" for folk. Maybe postcards with the key learning points on and a reading list. Just to see if that'll help.
I do a bit of magic (the performance art, not the card game) and attend lectures. Typically it's just a guy with no tech demoing new effects and methods. At the end they always sell lecture notes. It's a detailed overview of everything they did that night and it's usually indexed well so I can jump straight to a particular effect I want to learn.
I really enjoy this approach. It allows my to pay attention without worrying about remembering or note taking during the presentation and still allows me an almost perfect reference.
All the meetings I do are voluntary. Most of the people who attend work with the problems in some way.
Your time is incredibly valuable. If you're sitting there for 30 minutes while someone reads your memo, if you're getting everyone together in one place to read your memo, with all that implies for their schedules, then that's a waste of a lot of extremely important time for a lot of people.
Meetings are for discussions that you can only have with everyone together. They're so that people who don't understand something can ask you questions, or so that you can work with others who do understand the problems. Not for reading groups.
While this is totally true (what's the point in gathering people to get them to read instead of talk?) this is just how it works in most places. Ask people to read something before a meeting: 80% show up without having read, no matter how easy to read or important the paper is.
But what's great about this system is that under this 6-page system meetings are voluntary AND important. Knowing in advance that a meeting will start with 30 minutes of intense scrutiny makes it much more likely that people will not schedule meetings unless a problem /deserves/ that scrutiny.
PowerPoint is a presentation tool, and like any tool it can be misused to the point of frustration. At best, PowerPoint offers a good way to provide a visual aid for a presentation. People who present crappy PowerPoint decks would have no trouble delivering a similarly crappy speech, or writing an indecipherable memo.
As I mentioned to a similar comment, powerpoint has become the ubiquitous hammer of the business presentation which has everyone searching for nails.
There is a time and place for slides with a few talking points per, but in many ways it's contorted most all meetings into PR events even when there's nothing to sell.
This article could not have been posted at a better time! I seriously think that these form of presentations do put their audience to sleep whilst also being non productive.
I personally don't think one can do without slides as sometimes it helps the audience visualise what one is discussing. Therefore I believe it should be more about the essence of the content.
In summary, just keep each slide to a max of 2-3 words or just one image that best describes the topic you are discussing.
I feel that this could work well for many organisations, irrespective of their size, especially when one factors in how much time could saved on meetings.
I posted "Death to PowerPoints" -- http://www.strategicmessaging.com/powerpoints/2008/02/02/ -- 5 years ago, and still live by it. I almost never sit through a conventional presentation in a 1-on-1. I almost never attend presentations where a deck is presented to a group.
That said, I frequently edit slide decks for my clients to inflict on other people. And on the rare occasions I give presentations, I use PowerPoint, commonly in old-fashioned bulleted-outline style.
Complicating the discussion yet further:
* I write stuff for people to read MUCH more than I give presentations.
* My writing involves a lot of lists of bullet points. :)
125 comments
[ 2.8 ms ] story [ 194 ms ] threadI like this way of doing meetings, I haven't heard of anything similar before. Although I've always hated slide shows. Do I read the bullet points? Listen to the presenter? Does the presenter read the bullets and go into detail on each one? What does it mean if there is a bullet but the presenter doesn't mention it during the presentation? There's too much going on at once. A good slide show can work very well (using a slide to illustrate your point with a graph etc.) but most people can't create good slide shows.
Why? Because he was pretty much just narrating what he already had on the screen.
I have always found that Powerpoint is useless for displaying anything in a meeting or seminar and yet I still find myself doing that when I myself choose to give a presentation. Additionally, I have yet to see anything that replaces it well enough that also mimics the speed and simplicity of the application, and I also find more value in just listening to the person rather than seeing what is on the screen.
(Not all courses of mine are like this one, though.)
Personally I like keeping presentations on the short side - only using slide shows for ancillary data like citations (which I find awkward to fold into the flow of a speach) and graphical data. Unless something is really interesting or very important, it's only going to get 5-10 minutes of people's attention.
This actually works pretty well because in the real world people usually only skim the info provided in advance of most meetings because they only need to "get the gist" of what's being said. This forces everyone to have a thorough understanding and promotes more thoughtful discussion.
The two best ways to use them, from experience, seem to be:
- Super dense slides. These slides have a lot of text and are information-rich. You're not expected to read them, and the presenter will just skim over them, presenting a high-level view of each topic, but definitely not reading off of the slides. The slides are there as a rough guide to the talk, and as an in-depth resource afterwards. - Super spare slides. These slides have few-to-no bullet points, and are heavy on pictures. They're pretty much there to guide the speaker's narrative, and nothing else. At worst, there might be an inherently visual data element, like a graph.
The common element being that the slides are there to guide the talk, not be the talk. The reason powerpoints are so reviled is because people tend to just write a speech, put a bullet point in front of each sentence, and read it off a projected slide.
A projector during a presentation should be used to show what you cannot say or to clarify a point graphically.
There is a time and place for slides with a few talking points per, but in many ways it's contorted most all meetings into PR events even when there's nothing to sell.
The article itself supports this as they don't just skip Powerpoint, they skip the presentation entirely in favour of a 6 page memo.
I would also disagree in that its a crutch for the absolute bottom of the barrel presenters, because no matter how bad awkwardly reading slides to the audience is, its better than silence / choking up / repeating themselves / skipping intermediate concepts. Being read to like a preschool child is better than not getting a presentation at all, well, at least most of the time.
https://plus.google.com/110981030061712822816/posts/AaygmbzV...
Not sure anyone has the answer, but that length of reading time vs. the presumed number of words to be read struck me as notable.
Nevertheless I think this is a great idea on itself. I've seen too many meetings where there was reading material but so few people read it that the talk actually focussed on them.
There's one issue though, and only experience will tell whether it is relevant. I for myself am fond of taking in knowledge via paper but the effectiveness of this highly depends on the moment I'm reading. Also I've noticed I find it harder to concentrate when I'm reading 'together in a group'. I feel a bit rushed by it. But perhaps that's just me or something that is easy to get used to.
Some teachers opposed it and I ended up losing. I'm sure Powerpoint was more convenient for them. I use deck.js for slides now but mostly for images - the other slides tend to have 3-4 words while I try and tell a story to draw in readers.
My last project pitch to management I printed out copies of a written proposal and had everyone read for ten minutes to start the meeting. It was actually really nice.
http://prezi.com
(I work there.)
Just waiting for an opportunity to using it in a real context!
To really focus the presentation to the speaker's voice I find that HAIKU DECK for iOS really removes bullet point syndrome. http://www.haikudeck.com/
(I don't work there.)
I've been using prezi for a few years now, and almost always get good audience feedback. Like any tool, you still have to know how to use it, it will not do all the work for you.
The best slide presentation software I've seen so far is SlideShow, but its for programmers only :)
http://www.cs.utah.edu/plt/publications/icfp04-ff.pdf
Fancy animations and zooms can't fix this inherent limitation of the slide format.
Teachers know that their slides suck, but it's what they are taught, and is what their curriculum demands. They demand bright colours, Comic Sans for dyslexic students, and tons of text on each slide.
For a middle-management role in the school, I designed her slides using one of those JS slide scripts, and it went down a treat. It took me the best part of two hours to port her content from Powerpoint to these slides, and I was able to add videos, animations, and to embed Google Apps data directly into the slide. Apparently, the interviewers had their minds blown by being able to view a Google Docs spreadsheet (where I had written the formulas) directly into the slide. I'd still say that it was fairly poorly designed, but it was a lot better than what kids are forced to read.
For information density, you can't beat paper, and there's a number of things you can do to make the paper very information dense, like sparklines. He argues that in some ways, sparklines are actually typography and not charts.
With the paper report people can drill into the information they want, and ask questions from there, as well as refer back to the information during Q&A. One quote he said was "They didn't get to become your peers because they can't read fast."
He also said to not give homework. When you make these reports, you spend meeting time reading the paper. It's not something they have to do before, because everyone is busy and no one will actually read it.
I generally follow using the slides, not listening to the dude who's talking for 30min-1h thank you very much.
Making things simple as you present something complex has nothing to do with having a powerpoint presentation or not. Nothing.
Giving a paper to read is just the same as powerpoint, except if the speaker sucks, you don't have to endure that. So yeah. Wrong punch line, okay approach.
I would write and print a design document of 30-50 pages long, schedule a 1-2 hours meeting and send the document in advance to those 5-10 people attending. Off-course only 1-2 persons would actually read in advance.
Then we were reading it page by page and discussing it, giving special attention to various diagrams, such as flow charts, sequence diagrams, FSMs and UMLs.
We almost never were able to finish in time, so the next meeting should be scheduled (in 1 or 2 weeks because of scheduling constraints) ...
The written word is also a great equalizer. A "presenter" can be judged based on their content rather than their public speaking ability.
Yeah. God forbid that anyone making decisions should have to deal with actual details; in the worst case, this would actually make them have to think.
Good decision making stems from understanding a problem comprehensively, not via often misleading generalities. I would even question whether it's possible to accurately summarize anything more trivial problems in a single page; the sort of menial issue that doesn't warrant a widely-distributed memo in the first place.
In the end what really matters CAN and SHOULD be summarized, and if additional details are needed there is always a place for sharing and discussion with management.
>In a famous Ranked 1st Consumer Goods company (i'll let you guess which one) all team memos to management are only allowed to be of a single page. This is really hard to adapt to it at the beginning but decision making is so much faster.
I'm sure less info makes decisions faster, but this seems rather the opposite of a virtue. Eg. GWB "the decider".
As usual the Navy/DoD seems to have this figured out:
BLUF: "Bottom-Line Up Front": Concise description of the problem, recommended solution w/out corroborating detail.
FYSA: "For Your Situational Awareness": This may help the boss understand the problem better, but it isn't something they need to know or understand right now.
FYI: "For Your Information": Boss, you need to read this before making your decision.
If you can't trust your underlings to use each appropriately so that you can triage what you have time for, then you either need new underlings or you need to take responsibility for training them better.
A 1-page limit on decisional memorandums is just as artificial as a 64-KB limit on code page size for executable programs.
Well look at the intros of 64kb, you can still do amazing things with no space :)
And everybody's always busy. If you send them a 6-page memo, they won't read it before the meeting. One page? Yeah, that's doable. So they go to the meeting knowing what it's about.
Google and other companies are known for very brief updates (may be called memos in your organization), as short as a single line, sent per week. No need to send multiple pages of details: http://blog.idonethis.com/post/16736314554/silicon-valleys-p...
These memos are different from the author's post, which is really not about memos, but rather an alternative means of presenting all of the information required to get to the key discussion in a meeting. I don't think is anyone is suggesting that 6 pg emails should be the memos, and something is wrong if the 6pg emails are replacing decks that are being sent around via email.
If they find out something important was left out, they know there was an attempt to hide it.
It does depend on the structure of those 6 pages. If I had to do these regularly I can easily imagine settling on a (largely) routine format, e.g 1st page is overview, 2nd page is problem detail, 3rd page is solution/implementation, 4th page risks/mitigation blah blah blah.
Note that the article says the first 30 minutes of the meeting is reading the memo. It doesn't take 5mins to read a page so there's ample time for people to formulate an opinion/questions before discussion actually starts (based on enough info in the memo). This is already an order of magnitude better than any powerpoint talk I've been in where people just shoot from the hip.
uhh.. 6th page: "Questions?" page with a cute picture
In any case, the actual structure I'd use would evolve over time, based on my experience of such meetings.
Of course, the effectiveness of this approach depends a great deal on the quality of your staff.
Maybe meetings are different?
These are smart and capable people too. They're just somehow got this deep bias about only pretty powerpoint could be important.
I think it's sensible - you can write a PowerPoint in ten minutes and not have to think things through. Try not thinking while writing 6 pages of argument - it will be impossible or achingly clear when it's read.
And my general opinion is that the presentation should be supportive towards the presentator. Not the other way around.
On the viewing side as as well as the presenter side.
I occasionally workshops on various things. Some (not all) of them <gasp> don't have any slides.
None.
On the grounds that the point of the workshop, as far as I'm concerned, is to pay a lot of attention to what I'm telling you - and do the practical exercises. You learn by doing - not by reading. A slide deck just gets in the way of that. It's a barrier between me and the class.
Every time there's one or two people who really hate that and complain about the lack of the deck. Not the quality of the workshop - that they're fine with - but the fact they don't have a slide deck.
Occasionally it's because they want to take away the deck and run the workshop inside their own company for free (and hey - I don't mind about that. Honest. It actually helps sales ;-).
But more often folk seem to need "a thing" to take away and look at again. Not so much as a learning tool, but as token that they were there.
I'm seriously considering making some physical "things" for folk. Maybe postcards with the key learning points on and a reading list. Just to see if that'll help.
Or verbs.
I really enjoy this approach. It allows my to pay attention without worrying about remembering or note taking during the presentation and still allows me an almost perfect reference.
Your time is incredibly valuable. If you're sitting there for 30 minutes while someone reads your memo, if you're getting everyone together in one place to read your memo, with all that implies for their schedules, then that's a waste of a lot of extremely important time for a lot of people.
Meetings are for discussions that you can only have with everyone together. They're so that people who don't understand something can ask you questions, or so that you can work with others who do understand the problems. Not for reading groups.
One great book on delivering awesome presentations - Presentation Zen (http://www.amazon.com/Presentation-Zen-Simple-Delivery-Editi...)
There is a time and place for slides with a few talking points per, but in many ways it's contorted most all meetings into PR events even when there's nothing to sell.
http://www.amazon.com/Nancy-Duarte/e/B002BMAA0K/?_encoding=U...
I personally don't think one can do without slides as sometimes it helps the audience visualise what one is discussing. Therefore I believe it should be more about the essence of the content.
In summary, just keep each slide to a max of 2-3 words or just one image that best describes the topic you are discussing.
I feel that this could work well for many organisations, irrespective of their size, especially when one factors in how much time could saved on meetings.
That said, I frequently edit slide decks for my clients to inflict on other people. And on the rare occasions I give presentations, I use PowerPoint, commonly in old-fashioned bulleted-outline style.
Complicating the discussion yet further:
* I write stuff for people to read MUCH more than I give presentations.
* My writing involves a lot of lists of bullet points. :)