The Job Is Half Thinking, Half Communicating

You can have the best product strategy in the world, but if you can't communicate it clearly — to your team, to your stakeholders, to leadership — it won't get built. Communication isn't a soft skill for PMs; it's an execution skill.

The Four Communication Modes of a PM

1. Upward Communication (to leadership and stakeholders) Goal: Build trust, manage expectations, get resources and buy-in. Key principle: Lead with outcomes, not activities. Your VP doesn't care that you ran five user interviews. They care what you learned and what it means for the roadmap. Use BLUF: Bottom Line Up Front. State your conclusion first.

2. Lateral Communication (to peers: design, engineering, data, legal, marketing) Goal: Alignment and coordination without hierarchy. Key principle: Be specific about what you need and by when. "Can you review this spec?" gets a slow, vague response. "Can you flag any technical risks in sections 2 and 3 by Thursday?" gets action.

3. Downward Communication (to your direct team) Goal: Clarity, context, and direction. Key principle: Explain the why, not just the what. Engineers and designers do better work when they understand the user problem and business context behind a request.

4. External Communication (to users and customers) Goal: Gather honest feedback, build relationships, close the loop. Key principle: Listen more than you talk. Every external communication is an opportunity to learn.

The One-Page Brief: Your Most Useful Document

A good brief forces you to clarify your thinking before you ask for anyone's time.

A PM brief covers: - Context: What situation prompted this? - Problem: What specific problem are we trying to solve? - Proposed approach: What are you recommending and why? - Key tradeoffs / alternatives considered: Why didn't you choose the alternatives? - Ask: What do you need from the reader — a decision, feedback, or awareness?

One page forces you to prioritize. If you can't explain your thinking in a page, you haven't done enough thinking yet.

Running Effective Meetings

Before: Every meeting has a single owner and a clear purpose: "We're deciding X" or "We're aligning on Y." Only invite necessary people.

During: Start with the outcome. Drive toward a decision or clear next action. Assign every action item to a named person with a date.

After: Send a 3-line follow-up: decisions made, open questions, next steps with owners. This single habit builds trust faster than almost anything else.

Handling Stakeholder Pushback

• Listen fully first. Don't defend before you've understood the full argument. Sometimes the pushback contains valid information.
• Separate the problem from the solution. "I hear that you need to close this enterprise deal. Let me understand the customer's underlying need — there may be a different way to address it."
• Show your work. If you've deprioritized something, explain the prioritization criteria. It's much harder to override a data-backed decision than an opinion.
• Know what requires escalation. Some decisions aren't yours alone. Know when to hold firm vs. when to escalate.

Key Takeaway: PM communication is an execution skill. Lead with outcomes for leadership, be specific with peers, explain the why to your team, and listen externally. One-page briefs and tight meeting follow-ups are two habits that compound quickly into credibility.