Thanks! It's less a spec and more of, choose the tool that fits the job. A lot of these documents fit the overall structure of "high-level situation & recommen

Thanks! It's less a spec and more of, choose the tool that fits the job. A lot of these documents fit the overall structure of "high-level situation & recommendation; industry / product / customer context; more depth on recommendations considered; FAQ" I don't have any examples, anymore (I left Amazon some years ago), but here are a couple of links that have reasonable takes on the structure and guidelines: https://www.anecdote.com/2018/05/amazons-six-page-narrative-structure/ https://www.anecdote.com/2018/05/amazons-six-page-narrative-... https://use-cases.org/2018/01/03/the-evil-genius-of-the-amazon-six-page-narrative/ https://use-cases.org/2018/01/03/the-evil-genius-of-the-amaz... https://www.geekwire.com/2017/prepared-6-page-memo-geekwire-summit-session-amazons-jeff-wilke-please-read-silently/ https://www.geekwire.com/2017/prepared-6-page-memo-geekwire-... Bottom line: the purpose of the document is to drive a high-quality decision, so include what will help, and leave out anything extraneous. (I know, that's not very actionable.)