I wish this could happen where I am. No one wants to bother reading anything ahead of the meeting to be prepared for a discussion. Then the same people don't have the patience to let the group review the material during the meeting before starting the discussion.
If you want to bring this to wherever you work, I encourage it. All you need to do is lead the meeting yourself with a strong, assertive voice. Tell them this is what we're doing. When someone inevitably complains just ask them to please wait to ask questions until everyone is done.
If somebody really needs my time, they can tell me why -- or go through my manager which they should be doing anyways.
I had to do that to a co-worker, and all I got back was "Product Foo". Okay, but what about Product Foo? Blood from a stone, every damn time, and it wears me down.
It wasn't in my situation, mostly because everyone sucked at meetings at an astounding level. But I'm not there anymore thankfully!
The main value of it felt that enshrining factual objective information and basing all discussion around that.
On the other hand, I am indeed able to add a lot more value as a reviewer if I can read the document ahead of the time. So whenever I am the prime reviewer, I request the document to be sent one day ahead of meeting even if it is incomplete at that time.
Besides, very few people in decision making positions have time to study all the prep material beforehand. I sure as hell don't do that when I have back-back-back meeting schedules.
Nevertheless, I'm a supporter of the approach and have introduced it into the most important review meetings that we hold in my group. (We do bar laptops and other electronics, other than video conferencing equipment.) Results after 18 months seem quite positive on balance.
The way that I personally explain this to new Amazonians is that I want their documents to tell a story. Now, I'm in engineering so the the story is going to be about some kind of highly technical topic, but it should start with an introduction, and it should lead the reader to the point that they have a pretty solid understanding of the problem space. If we put a document in front of a leader who has never even heard of our team before they should walk away understanding what the problem we're trying to solve is. That's part of what makes it so hard -- writing for an audience that might not be familiar with ANY of your internal jargon.
The documents must also be quite dry; they should avoid unnecessary adjectives, opinions should be called out as such, etc. Don't say, "high throughput," say, "72k TPS." That kind of thing.
Honestly there isn't anything that you couldn't get by simply reading and applying the advice from "The Elements of Style" by Strunk and White[1] and "On Writing Well" by Zinsser [2].
The primary philosophy is that if you can't write well, then you haven't thought it through. The act of writing is an act of reasoning.
0. Practice in a strong feedback loop. This applies for anything, not just writing.
1. Ruthlessly reduce your sentences. Repeat until you can't eliminate or combine any more words.
2. Avoid adverbs. Use "dashed" or "sprinted" instead of "ran quickly". Learn more words.
3. Avoid weasel words like "should" "could" "might". Take a stance and give concrete reasons.
4. Use concrete data over descriptors. "+5% profit" over "increased profit".
5. Write in active voice. Look up the "by Zombies" trick.
6. Use the simplest word that maintains your meaning. No one needs to use the word "utilize".
[1]: https://www.amazon.com/Elements-Style-Fourth-William-Strunk/...
[2]: https://www.amazon.com/Writing-Well-Classic-Guide-Nonfiction...
These style guides, especially points #1 through #6, came about from bureaucrats who were essentially filibustering or otherwise obfuscating in their writing.
The root problem there was not the long-winded writing, it was their intent to hide bad things.
If you can make sure you're not carrying water for corrupt officials, you best strategy is to try to write natural prose. Yes, do look for wordy phrases or cliches, but don't obsess over adverbs or the passive voice.
[1] https://languagelog.ldc.upenn.edu/nll/?p=15509 [2] http://itre.cis.upenn.edu/~myl/languagelog/archives/003366.h...
This is something I struggle with so I took your advice and found this:
https://www.grammarly.com/blog/a-scary-easy-way-to-help-you-...
Thanks!
[1]: https://smile.amazon.com/Style-Clarity-Chicago-Writing-Publi...
Article: https://www.geekwire.com/2017/prepared-6-page-memo-geekwire-...
6-Pager Example: https://cdn.geekwire.com/wp-content/uploads/2017/10/Jeff-Wil...
Guidelines: https://blog.usejournal.com/writing-docs-at-amazon-e02580861...
Previous HN Discussion: https://news.ycombinator.com/item?id=19115686
Any info on what the writing class covers ?
- Some light style rules about having no qualifiers e.g. words like "really significant" were banned
- Keep language super concise and non-flowery. Don't try to sound clever, Keep It Simple, Stupid for language basically
- Structure arguments a bit like the Minto pyramid[0] was another one I was told while there
- No one cares how much work or effort went into your doc, or how clever it is, only the final artefact of your work/thought should make it into the doc no matter how concisely you can express it
[0] https://www.amazon.co.uk/Pyramid-Principle-Logic-Writing-Thi...
Who does this 1-page explainer go to ? who is the gate-keeper ?
Also sounds like the Chair did not control the meeting.
I see the Amazon approach as an augment to the chair to keep the discussion on-topic. If it's not discussed on the paper, the burden is on the dissenter to provide info / present credentials to rebut.
One argument is that we could've done that outside of the meeting, in its own meeting. But that actually wouldn't have saved any time, but would've probably cost more. Basically, we set aside the afternoon to accomplish the task at hand. If we had broke it into multiple days, there would've been memory debt we'd have to refresh.
As an engineer, I feel that requiring pre-homework for a meeting can be detrimental. As other posters mentioned, going through it all together in the scheduled meeting ensures that everyone is on the page. Additionally, it means that an hour long meeting doesn't actually require an hour and a half of my time, so I can better judge and plan my schedule.
Asking everyone to please do these actions before the meeting is a good intention. Everyone wants to, but you know things happen and well I skimmed it but I didn't really have time and now I'm going to ask questions that page 2 answers clearly because I didn't read it. Everyone's time is wasted.
Forcing everyone to spend 15 minutes right now is a mechanism. It's much more effective.
There are internal classes offered on writing better documents (and it's a great class). There's videos, guides, documents, everything. Writing well at Amazon is key to a successful career here. Got a project idea? Write a very good 1-pager explaining it and you've got a much higher chance of it actually happening. Want to share a design? Write a 6-pager (often 10-15 pages with appendices) explaining what, why and how you're going to build the system.
I've been in meetings that start with 15 minutes of silent reading, then 45 minutes of discussion. No PowerPoint presenting.
It's very weird for newcomers, but I don't know anyone who finds that it isn't better than the alternatives.