Write It Down or It Didn't Happen
If your strategy lives only in someone's head, you do not have a strategy.
The most underrated skill in product management is writing. Not presentations. Not Slack messages. Writing. Long-form, structured, clear writing that captures decisions, rationale, and context in a way that persists beyond any meeting.
Here is why writing matters more than speaking: meetings evaporate. Three people leave the same meeting with three different understandings of what was decided. Slack threads scroll into oblivion. Verbal agreements get reinterpreted. But a written document is a contract. It says "this is what we decided, this is why, and this is what we are not doing."
Amazon got this right with their six-page memo culture. The format matters less than the discipline. A one-page decision doc, a two-page PRD, a half-page strategy summary. The act of writing forces clarity. You cannot write "we will improve the user experience" and feel good about it. Writing forces you to specify: improve which experience, for which users, measured how, by when.
Writing also creates institutional memory. When a new team member joins, they can read the decision log and understand why the product looks the way it does. Without written records, every new hire inherits a product they do not understand, built on decisions nobody can explain.
Write your strategy. Write your PRDs. Write your decision logs. Write your retrospectives. Write your meeting outcomes. If it is important enough to discuss, it is important enough to write down. If it is not written down, it did not happen.
“The act of writing forces clarity. You cannot write "we will improve the user experience" and feel good about it.”
When this goes wrong
Strategy that exists only as a slide deck shown once. Decisions made in meetings with no written follow-up. "We all know what we agreed to" without any documentation. Product roadmaps that live only in someone's head.
In practice
- ✓Write a decision doc for every significant product decision
- ✓Publish meeting outcomes in writing within 24 hours
- ✓Maintain a decision log that new team members can read on day one
- ✓Write PRDs before starting development, not after