I love a paper trail. Documentation brings structure, it helps keep things consistent, sometimes it answers “what were we thinking?” I create a playbook for anything that can be repeated or scaled: pages, components, error messages, and so on. I keep these as lo-fi as possible and plug the information into presentations or Confluence pages or email chains customized to individual stakeholders’ needs.
What’s included
- Background explaining what has changed and why
- Objectives for the content and its intended audience
- Content requirements including character count and terms to use or avoid
- Best-in-class examples and examples that don’t meet requirements
- Decision framework for approving and implementing changes
- Rubric for evaluating quality and value
Meetings and events
Golf
