{
  "$type": "site.standard.document",
  "canonicalUrl": "https://justingarrison.com/blog/2023-07-31-document-driven-meetings-at-amazon",
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreidozu33dqsjkzv5yab4tnkbgk7zntgnun2puuysqnqo4cslplli2q"
    },
    "mimeType": "image/png",
    "size": 31628
  },
  "description": "How Amazon uses document reading to conduct meetings and stay focused.",
  "path": "/blog/2023-07-31-document-driven-meetings-at-amazon",
  "publishedAt": "2023-07-31T20:06:38.000Z",
  "site": "at://did:plc:p7uix7mresfq4nfzxp3klgfa/site.standard.publication/3mmdn7mg2qm2d",
  "textContent": "This article is best to experience before reading the details.\nHere is a video with a mock Amazon meeting complete with PR/FAQ.\n\nWatch here and come back if you have more questions.\n\n{{< youtube -_mQBaoN5mQ >}}\n\nDocument driven meetings PR/FAQ\n\nDocuments are the core of Amazon meetings\n\nIn this instance, our document is a press release and frequently asked questions (PR/FAQ) style, generally employed for new features or enhancements.\nThis simulates a press release announcing a new feature.\nNow, we can discuss the document and the associated details.\n\nAmazon methodically begins meetings with document reading, a practice that differentiates it from many companies.\nHaving a document is the standard and meetings without documents to read are usually in small groups—less than 5 people—or not decision focused.\nEvery regularly scheduled meeting I attend has a document at its core, whether it's for discussing data, realising the PR fact narrative for a feature, or analysing a new service.\n\nComments are enabled in documents, but they are not always reviewed synchronously during the meeting.\nThis ensures that questions can be resolved later by the document author.\nThe meeting discussion is focused on seeking clarity and discussing important points or discrepancies in data.\n\nAdding Value to the Future Meetings\n\nQuestions from the current meeting discussion usually end up in the FAQ section.\nThey provide valuable insights to future readers, as each document goes through several iterations and even multiple reviews from various audiences over time.\n\nWeekly recurring meetings that are data intensive are stored in the same document so it's easy to find historical data about a topic.\nThis often involves new feature launches, long term issues, or data trends.\n\nAmazon uses other types of documents as well, but the emphasis is on the information being brought forward to the meeting and the use of meeting time for learning this information.\nResearching for a meeting is not a pre-meeting chore; the document reading session is part of the whole meeting time which can be very beneficial for a wider group.\n\nHaving document writing as the first step for a meeting has a lot of benefits around historical decision making and putting the deep thoughtful work upfront.\n\nWriting and Consuming Documents\n\nWriting a document can get easier with templates and patterns.\nThe templates define the layout and help steer away from the daunting task of starting from scratch.\nIn a PR/FAQ, we include a problem statement, a solution, a quote from a person, and a call to action for further reading.\nThis can also help the reader know what to expect and drill into the important parts of the document.\n\nRelying on documents also helps eliminate some bias we might have towards the person presenting.\nIt allows me to focus more on the content rather than concentrating on the presenter.\nDuring typical meetings when we read for 10 to 30 minutes depending on the length of the document.\n\nStruggles with a Document Driven Meeting\n\nNot to say that this practice is without challenges.\nBeing a slow reader, sometimes, I fall behind on fully grasping the document's content during the allotted period.\nIt's especially tough when I'm juggling this meeting with other work or when I've joined late.\n\nAdditionally, it's difficult to manage comments in real-time using some document software, and it can be overwhelming if multiple people remark on similar points or ask the same question.\nSearching for the latest version of a document or keeping tabs on its review status can be a challenge, especially if several teams are creating documents or your role involves multiple areas.\n\nFor over three years at Amazon, I've found the practice of document reading vastly beneficial.\nThis workflow enforces better time management, ensures meeting preparedness, provides a wealth of information and reduces redundant meetings.\n\nConclusion\n\nAlthough there are some difficulties with the document reading process, it has undeniably enhanced the overall meeting quality.\nI recommend trying document driven meetings in your workplace teams and give it a try.",
  "title": "Document Driven Meetings at Amazon"
}