Chapter 16: Difficult Conversations and Feedback

You are a product leader in a high pressure software organisation. Your team has just missed its third consecutive quarterly milestone. You know that one of your senior engineers is consistently over-engineering simple tasks. Your designer is producing beautiful work that cannot be built. You have a product manager who is great at process but fails to understand the business model. You feel a heavy weight in your chest when you think about your next one on one meeting. You want to be liked and you want to be a supportive leader. You tell yourself that things might improve on their own if you just give the team more space. You avoid the hard conversations because you fear the resulting drama and emotional volatility. You worry that being direct will cause people to quit or lead to a negative reputation for you. You are playing life on extremely hard mode because you have not learned how to manage human behaviour. The tension lies between your need for high performance and your desire for a comfortable workplace. You face a choice between ruinous empathy and the radical candor required to save your company. If you do not master the art of difficult conversations your team will continue to produce mediocre output until the business fails.

CORE SKILL OR PRINCIPLE

The core principle of effective leadership is that your impact is determined by the quality of your communication. Leadership is exclusively done through the creation of artifacts or verbalisations that affect other humans. You must transition from a coercive model of management to a model of profound curiosity. Success depends on your ability to deliver hard truths while demonstrating that you care personally about the recipient. This requires you to move from being a bricklayer who manages tasks to an architect who manages outcomes and relationships. You must view every difficult conversation as an opportunity for mutual understanding rather than a battle to be won. You must master your internal state and understand the physiology of fear and safety in the brain. This skill allows you to turn high stakes conflicts into collaborative problem solving sessions.

EVIDENCE FROM THE CONVERSATION

Evidence from executive coaches show that leaders regularly avoid hard conversations because they put too much meaning on top of simple situations. You fear making people sad or triggering a new fire that you will have to manage. However withholding feedback is actually the most selfish thing you can do as a leader. You are choosing your own comfort over the growth of your team members. High performing teams operate by demanding and giving feedback relentlessly.

The brain has an inherent safety system that triggers during conflict. When a person feels threatened their objective shifts from contributing productively to restoring their standing in the universe. This often triggers the amygdala which can grip the whole brain and cause reactive spirals. You can mitigate this by giving people a few seconds to mentally prepare for a hard talk.

Product leaders must be right a lot because their decisions reflect across the entire organisation and spend collective energy. This requires extreme clarity and conviction in your communication. One common mistake is blaming the audience for a misunderstanding. If a team does the wrong thing for six months the leader must take responsibility for failing to communicate expectations clearly.

Successful founders and leaders like those at Airbnb and Stripe stay in the details to ensure clarity and quality. Micromanagement is often used as a negative term but being in the details is what every responsible board does to a CEO. It ensures that everyone is rowing in the same direction at high velocity.

PRACTICAL BREAKDOWN

You must understand the psychology of avoidance to overcome it. Your brain is wired to seek safety and restore your standing when you feel uncertain or resentful. Recognize that ninety nine percent of the time there is nothing wrong with you and you simply lack the tools to manage discomfort. Adopt a growth mentality toward your personality and behavior.

Use the following five scripts for common difficult situations.

• First when someone is underperforming start by setting expectations immediately. Say this is going to be a difficult conversation and I want you to take a few seconds to prepare yourself. State clearly that the person is not living up to your expectations and that you have talked about this multiple times.
• Second when you need to fire someone ensure it is not a surprise. Say I have seen this issue multiple times and we have discussed it but it is still not fixed. I am letting you go and here is why.
• Third to solicit feedback as a leader ask what could I do or stop doing that would make it easier to work with me. Do not ask do you have any feedback for me because the person will usually say everything is fine.
• Fourth when giving praise be specific and careful. Do not just say good job because people cannot learn from vague positive feedback. Explain exactly what they did well and why it mattered.
• Fifth when a peer is being difficult use the inquiry versus advocacy framework. Instead of saying you are wrong say I noticed that in the last three meetings you did not include me in the roadmap discussion. I felt anxious because I had a need for clarity and collaboration.

To handle defensive reactions in the moment use the six second rule. After asking a hard question close your mouth and count to six. Almost no one can endure six full seconds of silence and they will eventually share what is on their mind. If someone gets emotional ask if the conversation can continue now or if you need to pause for them to digest the information.

Always end every meeting with these three questions. What did we decide here? Who needs to do what by when? Who else needs to know? Operationalise this by having everyone write down the answers to ensure you do not have six different versions of the truth in one room.

FOUNDER PRENUP AND PERSONAL OPERATING MANUALS

For founding teams you must align on a founder prenup before starting a company. This is a set of questions to ensure you are aligned for the long term journey. You must discuss how you will handle disagreements upfront so that you have a process to follow when they inevitably occur.

If you are not a founder you should still use a Personal Operating Manual or a README file. This prompts you to talk about your working style with your team. Include questions like what communication style do you like best? How do you like to work? What is your delegation style? What are your pet peeves? How can someone get a gold star with you? This removes the mystery from collaboration and reduces friction.

GIVING AND RECEIVING HARD FEEDBACK

To give hard feedback effectively you must care personally and challenge directly. Go into the conversation with humility and admit that you might be wrong. State your intention to be helpful and deliver the feedback immediately rather than waiting for a better moment. Use synchronous communication and consider phone calls over video because facial expressions on a screen often contain more noise than signal.

Use the Nonviolent Communication framework of observations feelings needs and requests. State a factual observation that no one would argue with. Express your feelings without blaming the other person. State your universal human needs like clarity or connection. Finally make a small and easy request as an olive branch.

When receiving feedback let yourself feel the negative emotions without reacting immediately. Once the emotional wave passes be curious about where the feedback came from and why it was given. Ask yourself how you might be complicit in creating the conditions you are complaining about.

PUSHING BACK ON EXECUTIVES

To push back on executives without saying no use the options and trade offs approach. Instead of a binary yes or no give them a menu of choices and explain the consequences of each. Use the magic questions which are statements that end with do you agree or is that right. This forces the executive to make an assertion and helps you calibrate your mental model against theirs.

Assume that executive questions are an attempt to learn rather than a test of your knowledge. Provide a clear recommendation rather than just a catalog of information because executives often have limited cognitive load for details. Use numbers instead of subjective adjectives like great or user friendly.

If you disagree with a direction have the backbone to voice your point of view during the decision making process. Your obligation is to provide a new perspective or additional information that the team has not considered. Once a decision is made commit to it fully to ensure the organisation can row in the same direction.

SKILL APPLICATION

Apply the 15% rule to your relationships by disclosing slightly more than you feel comfortable with. Admitting a mistake when everyone knows you made one builds more credibility than ignoring it. Use the Vegas rule of confidentiality in small group discussions to build trust.

Use the RIDE framework for decision making clarity. Define who is requesting the change who can give input who is the decider and who will execute. This prevents teams from becoming paralysed by ambiguity.

Practice the walk the store ritual where you and your engineering and design leads experience your product as a new user would. Friction logging helps you understand the pain points that metrics often hide. This visceral understanding helps you advocate for quality without getting bogged down in subjective arguments.

Manage your manager by schedule syncing. Print out your time boxed calendar and show it to your boss to demonstrate what you are working on and what new requests you cannot fit in. This makes the trade offs of your time explicit and forces a prioritisation conversation.

ACTION CHECKLIST

• Identify one person you have been avoiding a hard conversation with and schedule it for this week.
• Write down your most obvious objection at the start of your next project proposal.
• Draft your own Personal Operating Manual and share it with your direct reports.
• Ask your manager what is one thing you could do differently to make them more successful.
• End every meeting this week by asking what did we decide here and who needs to do what by when.
• Practice the six second rule of silence in your next one on one.
• Audit your recent documents and remove all subjective adjectives like great or amazing.
• Create a founder prenup if you are starting a new venture with partners.
• Perform a walk the store review of your primary user journey on a mobile device.
• Use the observation feeling need request framework to address a interpersonal pinch this week.
• Identify your top two strategic pillars and explain them in three pages or less.
• Ask your lead engineer to shred your current roadmap and find its technical flaws.
• Set a personal SLA to respond to all team blockers within four hours.
• Schedule a peer coaching call with someone in a similar role at another company.
• Write a job mission with OKRs for your current role and review it with your manager.
• Ask yourself if you would fully fund your own team if you were the CEO today.
• Identify one way you are complicit in a team dynamic that you do not like.
• Use a magic question to calibrate with an executive during your next review.
• Commit to checking your inbox only twice a day to improve your deep work focus.
• Give one piece of specific praise to a colleague for a task they completed today.
• Attend an interpersonal dynamics or coaching training to build your soft leadership skills.