Chapter 15: Communication Excellence

You are a senior product leader overseeing a critical launch. Your inbox is overflowing with updates that lack a point. You spend your day in meetings where the first twenty minutes are wasted because no one has the same context. You observe product managers who dump data into spreadsheets and expect executives to find the answer. Your engineering partners feel like order takers because you communicate via tiny tickets rather than shared vision. You realize your impact is limited by your ability to transmit ideas through others. You face a situation where a misunderstanding in a Slack thread has delayed a sprint by a week. You see your competitors moving faster because their leaders are aligned on a single source of truth while you are playing a game of telephone. You must decide whether to continue acting as a router of information or to become an architect of clarity. The tension lies between the speed of reactive communication and the discipline of structured thought. You face a reality where your technical skills will not save a product that no one understands. You must either achieve communication excellence or watch your team fail through misalignment.

CORE SKILL OR PRINCIPLE

The core principle of communication excellence is that communication is the primary job of a leader. You do not have impact through personal work but through artifacts and verbalisations that affect other humans. Success depends on your ability to turn ambiguity into extreme clarity. You must move from self expression to strategic transmission. This requires you to view every document and meeting as a product that must solve a specific problem for the audience. You must adopt the full stack builder mindset where you own the outcome of your message rather than just its delivery. If the listener does not understand or take action you must take responsibility for that failure. You must master the balance of caring personally while challenging directly to build a culture of high performance. Communication is not a soft skill but a hard competency that determines the velocity of your entire organisation.

EVIDENCE FROM THE CONVERSATION

Evidence from elite leaders shows that blaming the audience is the most common and damaging mistake. When a team executes the wrong thing after six months it is a failure of leadership communication. Leaders at companies like Meta and Stripe argue that leadership is exclusively done through artifacts. If you do a poor job of writing a strategy you waste a year of team effort. You cannot not communicate because your silence or your facial expressions are always sending signals of trust or responsibility.

Executive presence is often misunderstood as charisma but it is actually about reducing the cognitive load on your audience. Senior executives possess a brontosaurus brain that can only process three facts at once. They rely on product leaders to provide a clear recommendation rather than a catalog of information. At Airbnb Brian Chesky reinforces this by being in the details of every pixel to ensure the vision is executed exactly as intended. This top down approach requires extreme clarity to ensure everyone rows in the same direction.

Mastering concision is a hallmark of the Amazon culture where every employee takes a business writing class. They are forbidden from using subjective words like great because it lacks strategic meaning. They use numbers instead of adjectives to force clarity of thought. This discipline ensures that every word carries weight and that trade offs are intentional. Similarly at OpenAI and Microsoft leaders emphasize that the lines between product and engineering are blurring which makes technical empathy essential for communication.

Naomi Gleit at Meta uses canonical everything to drive extreme clarity. She argues that talking past each other is a result of different nomenclature. By writing down definitions for every term she ensures that conflict is based on actual disagreement rather than misunderstanding. She relies on visuals in meetings to document decisions in real time. This avoids the situation where people leave a meeting with different versions of the next steps.

PRACTICAL BREAKDOWN

You must transform your communication by following a structured and disciplined approach. Start by adopting the Most Obvious Objection or MOO framework. People will not listen to your conclusions if they do not accept your premise. You must identify the primary fear or concern of your audience and address it right at the top. If you are having a problem with a project state it clearly and say you know it matters. This builds the trust necessary for them to hear the rest of your message.

Master concise communication by auditing your documents for adjectives. Delete the word great and replace it with a specific metric or a user benefit. If you say a feature is user friendly explain that it saves a customer twenty minutes each day. Kill your darlings by removing any sentence that does not directly support your one big idea. Your most successful pitches should be no more than three sentences long. Use the mobile phone test where your message must be readable on a single screen without scrolling.

Develop executive presence by always leading with a recommendation. Do not ask your manager what you should do. Instead say that you have noticed a problem and you have started a programme to fix it. Give them a menu of choices and explain the trade offs of each. Use the traffic light system to evaluate options across different criteria like user experience and engineering feasibility. This allows an executive to quickly see where the risks are and rule out bad paths.

Implement signposting in all your documentation to help readers navigate complex information. Use the What? So What? Now What? structure for every update. State what the product is then explain why it is important to the company and then define exactly what comes next. Use canonical docs that act as a single source of truth for every project. These docs must list every work stream with a single threaded owner so that there is no ambiguity about who is responsible for what.

Adopt a strategy not self expression mindset for feedback. Use the HIP CORE framework to ensure your feedback is helpful and objective. HIP stands for humble and helpful and in person and private. CORE stands for context and observation and result and next step. Do not criticize someone's personality. Instead describe the specific behavior in a meeting and the resulting impact on the team's credibility. Always provide a clear next step like visiting a speech coach or doing more of a specific task.

SKILL APPLICATION

Apply these skills to your managing up strategy to build trust and credibility. Trust is built by repeatedly setting and meeting expectations. You must proactively keep your leader in the loop by sending regular updates. Use the HPM or Highlight People Me format for your weekly emails. List the big ticket items and the people who are doing amazing work and then share how you are personally doing. This gives your manager a mental model of your progress and makes it easier for them to unblock you when you are stuck.

When you need help from a senior leader make it cheap for them to assist you. Do not just state that you are blocked. Provide a draft email they can send to another leader or a specific set of yes or no questions they can answer. This reduces the effort required for them to help you and increases your reputation for urgency. You must also have the backbone to disagree when you have a different point of view. Voicing your disagreement provides additional information that the team may not have considered.

Use the 10 percent planning rule to maintain your team's metabolism. Do not spend more than one week planning for a quarter. This prevents you from getting bogged down in endless circular discussions that do not lead to results. Move to a two way write up phase where discussion and feedback are part of the document itself. Use a sentiment table or a pulse check to see how the entire audience feels about a proposal. This includes introverts who might not speak up in a large meeting.

Operationalise your vision by being a torch bearer who dissipates fear. You do not need to see the future perfectly but you must provide enough light for the next eight feet. Communicate your vision visually and repeatedly because people absorb information at different rates. Use the headline and subtitle method to describe the impact of your work in a way that a child can understand. This forces you to focus on the painkiller you are providing rather than the features you are building.

Manage conflict by staying on your side of the net. Describe behaviors and your own feelings rather than making assumptions about someone else's motivations. Use the information and impact and invitation and implications structure for difficult conversations. This invites the other person to join you in problem solving rather than bestowing your opinion upon them. Always ask what you could do or stop doing that would make it easier to work with you.

ACTION CHECKLIST

• Audit your last three emails and remove every subjective adjective like great or amazing.
• Identify your brontosaurus brain executive and ensure your next update contains only three core facts.
• Write a one sentence recommendation for every data point you present this week.
• Create a canonical doc for your current project with a list of all work streams and single threaded owners.
• Use the What? So What? Now What? structure for your next team standup update.
• Schedule a five minute meeting with your manager to sync your schedules and show your time boxed calendar.
• Draft one email for your leader to send that would unblock a current project for your team.
• Address the most obvious objection at the start of your next product review.
• Use the CORE framework to give one piece of praise and one piece of criticism this week.
• Ask your lead engineer to shred your next strategy document and provide raw feedback.
• Implement a sentiment table in your next major proposal doc to capture team alignment.
• Create a one page strategic plan that fits on a single mobile screen without scrolling.
• Define your nomenclature by writing out definitions for five core terms used by your team.
• Send your meeting agenda and pre read at least twenty four hours before every meeting.
• Record your next decision by real time editing a visual during the meeting.
• Send meeting notes that list only the action items and owners within twenty four hours of the meeting.
• Conduct a walk the store review of your primary user journey with your triad leads.
• Delete the first two paragraphs of every document you write this week to get straight to the point.
• Ask one coworker for a relevant experience they have had instead of asking them for generic advice.
• Identify a high conviction low consensus bet and write down the evidence for your belief.
• Commit to checking your inbox only twice a day as an experiment to improve your deep work focus.