Communication
If I could keep only one skill for a PM, it would be this one. Not strategy, not product sense, not data. Communication. Everything a PM produces, whether a spec, a roadmap, a decision, or a vision, is inert until it is transmitted into another person's head and changes what they do. A brilliant idea you cannot communicate is functionally identical to no idea at all.
#My point of view: this is the #1 PM skill
I am not alone here. Lenny Rachitsky, after studying what separates great PMs, ranks the skills in order: communication first, execution second, product sense third. Communication sits above execution, not beside it. His logic matches my experience. A PM's leverage is entirely indirect, because you act through other people, so your effectiveness is capped by how clearly you can move information and conviction between minds.
Brandon Chu put it even more sharply. The PM is "the API" of the team, the interface every other function calls to coordinate. An API with a garbled contract breaks everything downstream. That is what a PM with poor communication is: a broken interface.
Good PM communication is not measured by how much you said. It is measured by what the listener does next. If your update did not change a priority, unblock a decision, or align a team, it did not communicate. Output is words; outcome is behavior.
#Written vs verbal
These are different skills and most PMs are lopsided. Know which you're weaker at.
| What it's for | Where PMs fail | |
|---|---|---|
| Written | Async alignment at scale, durable decisions, the spec, the update | Burying the point; writing for themselves, not the reader; length as a proxy for rigor |
| Verbal | Real-time alignment, persuasion, conflict, reading the room | Talking past the point; not listening; mistaking talking for communicating |
Writing is the higher-leverage half, because it scales. One well-written doc aligns fifty people you will never meet, and it persists after you leave the room. It is also the more honest half, because muddled writing is a reliable tell for muddled thinking. The named behaviors in my model reflect this: clear, concise, empathetic communication across formats shows up under both Product Delivery and Stakeholder Management.
#Tailoring to the audience
The single highest-leverage habit is the same message, rebuilt for each audience. A roadmap change is not one communication. It is at least four.
- To engineering, the why behind the trade-off, the constraint, the technical context.
- To design, the user problem and the experience bar.
- To executives, the business impact, in one line, up front (Executive Communication).
- To the wider org, the narrative: what is changing, why it matters, what to do (Storytelling with Data).
A PM who sends the same generic update to everyone has confused broadcasting with communicating. The information went out; the alignment did not happen.
The charismatic PM who dominates meetings is often a worse communicator than the quiet one whose docs are crystalline. Communication includes active listening, and the loud ones are frequently the ones not listening. Do not confuse presence with effectiveness.
#How AI is changing it
This is the most interesting tension in the whole domain. AI is a phenomenal writing tool. It drafts the update, tightens the prose, restructures the doc. So one reading is that AI erodes the value of communication. I think the opposite is true. As the Reforge "higher ground" framing argues, when first drafts get cheap, the bottleneck moves to clarity of thought, knowing what you actually want to say and to whom. AI can fix your grammar. It cannot decide your point. Lenny describes PMs becoming editors of super-intelligent suggestions, and editing is a communication skill. The medium gets easier while the judgment underneath gets more valuable. (Competencies AI Commoditizes vs Elevates.)
#Continue Reading
- Executive Communication for the specialized craft of communicating with people short on time.
- Storytelling with Data for how to make a message persuasive, not just clear.
- Cross-Functional Collaboration for why communication is the substrate trust is built on.
- Writing PRDs and Specs for the highest-stakes piece of written PM communication.
- Influencing People for why communication is the engine under every competency here.