Purpose:

The purpose of this doc is to:

1. Understand stakeholder needs from documentation, including who will need to review copy throughout this project.
2. Understand how stakeholders can best help the documentation team (technical writers, UX writers)
3. (Optional) Understand key documentation milestones (E.g. Staging)
4. Review the strings across all marketing, documentation, console, app, and emails. Once aligned and updated here, we’ll update the corresponding docs.

Stakeholders: [Stakeholders to add how they best like to communicate]

What’s needed for documentation: [Stakeholders to input]

●

What’s needed by documentation: [Documentation to input] ●

Documentation milestones: [Can also add a premade spreadsheet from documentation]

*Please note that although I use the word “documentation” to represent a role, this can also be used to work with UX writers and technical writers. The technical writers on my team at AWS helped with UX copy, marketing, and documentation (e.g. developer guides).