|
|
|
|
|
by sandGorgon
2693 days ago
|
|
This is super helpful ! Is there a format that you can create/share ? Like - is it like a spec (with "goal", "stakeholders", stuff like that). I'm betting it's not ...and that's makes this a little hard to get started on. You guys had the benefit of looking at your peers' work - what would be a good two pager that we can learn from ? |
|
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-...
https://use-cases.org/2018/01/03/the-evil-genius-of-the-amaz...
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.)