# The Document Culture of Amazon ![rw-book-cover](https://justingarrison.com/img/documents-banner.jpg) URL:: https://www.justingarrison.com/blog/2021-03-15-the-document-culture-of-amazon Author:: Justin Garrison ## Highlights > A majority of my meetings start with reading a document. This takes “this meeting could have been…” and flips it upside down. Most of the time, if there isn’t a doc there isn’t a meeting. ([View Highlight](https://read.readwise.io/read/01ggfg50bqzn1qkcjarjrzf5e0)) > Meetings start with reading. Depending on the length of the document, we’ll read anywhere from ten minutes to half an hour. If the meeting has a long document (six-pagers are the longest) and many attendees, the meeting will be scheduled for enough time to read and discuss. ([View Highlight](https://read.readwise.io/read/01ggfg5jrabbpezwhyq3tev1z3)) > There’s a wealth of current and past documents. Want to see what the PR/FAQ looked like for Amazon EKS or AWS Lambda? It exists. ([View Highlight](https://read.readwise.io/read/01ggfg6mhedsjrxgyt3t4r6k16)) > You are not expected to retain document information outside of the meeting. Feedback and discussions happen during the meeting. Comments can be answered asynchronously. If more discussion is needed then the document will be revised and a new meeting will be scheduled to read and discuss it. ([View Highlight](https://read.readwise.io/read/01ggfg6sn8z093gxbyt5saft3y)) > I’ve been told “if there’s no document, it doesn’t get done.” This includes meetings. If there’s no document, we cancel the meeting. ([View Highlight](https://read.readwise.io/read/01ggfg7969gdqb9ybtqzemk45s)) > It’s often difficult to find documents spread across so many tools without an ability to cross search or centrally organize them. ([View Highlight](https://read.readwise.io/read/01ggfg8d0bpv86t3rt9hedsfy3)) --- Title: The Document Culture of Amazon Author: Justin Garrison Tags: readwise, articles date: 2024-01-30 --- # The Document Culture of Amazon ![rw-book-cover](https://justingarrison.com/img/documents-banner.jpg) URL:: https://www.justingarrison.com/blog/2021-03-15-the-document-culture-of-amazon Author:: Justin Garrison ## AI-Generated Summary A look at Amazon's culture of writing and reading ## Highlights > A majority of my meetings start with reading a document. This takes “this meeting could have been…” and flips it upside down. Most of the time, if there isn’t a doc there isn’t a meeting. ([View Highlight](https://read.readwise.io/read/01ggfg50bqzn1qkcjarjrzf5e0)) > Meetings start with reading. Depending on the length of the document, we’ll read anywhere from ten minutes to half an hour. If the meeting has a long document (six-pagers are the longest) and many attendees, the meeting will be scheduled for enough time to read and discuss. ([View Highlight](https://read.readwise.io/read/01ggfg5jrabbpezwhyq3tev1z3)) > There’s a wealth of current and past documents. Want to see what the PR/FAQ looked like for Amazon EKS or AWS Lambda? It exists. ([View Highlight](https://read.readwise.io/read/01ggfg6mhedsjrxgyt3t4r6k16)) > You are not expected to retain document information outside of the meeting. Feedback and discussions happen during the meeting. Comments can be answered asynchronously. If more discussion is needed then the document will be revised and a new meeting will be scheduled to read and discuss it. ([View Highlight](https://read.readwise.io/read/01ggfg6sn8z093gxbyt5saft3y)) > I’ve been told “if there’s no document, it doesn’t get done.” This includes meetings. If there’s no document, we cancel the meeting. ([View Highlight](https://read.readwise.io/read/01ggfg7969gdqb9ybtqzemk45s)) > It’s often difficult to find documents spread across so many tools without an ability to cross search or centrally organize them. ([View Highlight](https://read.readwise.io/read/01ggfg8d0bpv86t3rt9hedsfy3))