Lemanskills.com

Mastering Tough Conversations: A Tech Leader’s Guide to 1:1s (That Nobody Really Wants to Lead)

As a tech leader, you’re no stranger to challenges—tight deadlines, complex projects, and ever-evolving technology are part of the job. But one of the most delicate challenges you’ll face doesn’t involve code or systems; it involves people. Leading tough conversations with employees is an essential skill that separates good leaders from great ones. Whether it’s addressing underperformance, delivering hard feedback, or navigating team conflicts, these moments can define your leadership.

This guide equips you with actionable tools to lead tough conversations effectively, using a structured approach that combines contracting, Communication Intelligence (CQ), including the Process Communication Model (PCM). Let’s dive in.

 

When Tough Conversations Are Necessary: Scenarios You’ll Encounter

 

Before we get into the how, let’s identify the when. Here are common situations where a tough conversation might arise:

  1. Underperformance: An employee is consistently missing deadlines or delivering work in a quality we agreed on.
  2. Behavioral issues: A team member exhibits disruptive behavior, such as frequent conflicts with peers or unprofessional communication.
  3. Career Development: You need to inform an employee that they didn’t receive a promotion or that their role is changing.
  4. Restructuring: Delivering news about layoffs or departmental changes.
  5. Personal Concerns: Addressing sensitive issues like burnout, mental health, or personal struggles impacting performance.

 

Each of these scenarios requires a thoughtful approach to ensure the conversation is productive and respectful. And none of those are easy: there’s no one-size-fits-all approach so it might sound like a hell to a tech leader. But we have some algorytms that you can use to run the meeting with success.

 

The Framework: Contracting, CQ, and PCM

 

To handle these conversations effectively, use three elements to have a success no matter what kind of situation you are facing.

  1. Contracting: Establish clear agreements on three levels—administrative, professional, and psychological. You have more about the contracting itself, the levels and what to do to make sure the contract is fully covered in this article.
  2. Communication Intelligence (CQ) muscle: Flex your communication style to meet the employee where they are emotionally and mentally. Managing reactions that are always emotional (you like it or not) is our job as leaders: we need to know what triggers which behavior and what to do to overcome or address it when it appears.
  3. Process Communication Model (PCM) Framework: Tailor your approach to the employee’s personality base for maximum impact. Match the language and way of communication they need, not your favorite ones. That’s crucial for the conversation to be successful: you’re leading it for them, not for yourself.

 

Part 1: Contracting—Setting the Stage for Success

 

Contracting involves creating clarity and mutual understanding before diving into the conversation. What are the essentials of 3 levels that are inside?

Administrative Contracting: Define the logistics. Where will the meeting take place? How long will it last? What’s the agenda? Example: “Let’s meet in my office at 2 PM for 30 minutes to discuss your recent project performance.” Take care of this during and after as well. “What is the deadline to implement what we’re talking about?”

Professional Contracting: Clarify roles and expectations. Emphasize that this is a professional discussion and its goal is to find solutions, not to blame anybody for anything. Example: “My role is to provide feedback and support you in improving; I would like for your role to share your perspective and be engaged in the next steps we are going to create together during this meeting.”

Psychological Contracting: Set the emotional tone by creating a space for a person. Acknowledge that the conversation might be difficult but make sure you are focused on the positive outcome. Example: “I know this might be uncomfortable, but I want you to know this is coming from a place of support and wanting to help you succeed.”

 

Part 2: Flex Your CQ Muscle

 

Communication Intelligence (CQ) is your ability to adapt your communication style based on the situation and the other person’s needs and preferences. In tough conversations, this means balancing focus with accountability. What are the easiest 3 things that you can do as a leader to make sure you’re using your CQ muscle?

Listen Actively: Truly hear what the employee is saying without interrupting or jumping to conclusions. Make notes. Paraphrase, check if you understand as your employee intended you to. Don’t assume, ask.

Acknowledge Emotions: If the employee feels upset, angry or defensive, name the emotion without judgment. Example: “I can see this feedback is frustrating for you.” or “I understand that situation is infuriating.” Don’t underestimate the state, let it be, check what kind of information is hidden below this emotion. Use it in the solution creation phase.

Stay Calm and Focused: Keep your tone steady and avoid escalating tension, even if emotions run high. I know that’s one of the hardest things to do: most of the time we go angry when the other person is angry. We mirror each other, that’s how our brain is wired. But by being conscious of that, we can stop the automatic pattern and break it by being more mindful and goal-oriented. When you observe something like that, say to yourself: “What is the goal of this conversation? What I want to achieve here?” That kind of reminder is going to take you back to the OK-OK state and continue with more clear view of mind.

 

 

Part 3: Tailor Your Approach with PCM—Speak Their Language

 

The Process Communication Model (PCM) identifies six personality types, each with unique communication preferences and stress patterns. Understanding these types allows you to tailor your message effectively. Here’s a quick breakdown:

  1. Thinker: Logical, organized, values data and structure.

– Approach: Be clear, factual, and provide detailed explanations.

– Stress Behavior: May become overly critical or perfectionistic, attack others for lack of thinking or logical approach.

 

  1. Persister: Principled, dedicated, values integrity and commitment.

– Approach: Appeal to their sense of purpose and principles.

– Stress Behavior: May become judgmental or inflexible, push their beliefs on others, attack for lack of following the process or not having clear values.

 

  1. Rebel: Playful, spontaneous, values fun and creativity.

– Approach: Use humor and keep the conversation dynamic.

– Stress Behavior: May become sarcastic or disengaged, not taking responsibility for their actions, blaming others.

 

  1. Harmonizer: Empathetic, warm, values relationships and connection.

– Approach: Focus on emotions and personal impact.

– Stress Behavior: May become overly apologetic or withdrawn, making mistakes, people pleaser.

 

  1. Imaginer: Reflective, introspective, values solitude and imagination.

– Approach: Give them time to process and reflect before responding.

– Stress Behavior: May become passive or unresponsive.

 

  1. Promoter: Persuasive, adaptable, values results and action.

– Approach: Be direct and focus on outcomes.

– Stress Behavior: May become manipulative or dismissive, create drama when they are bored.

 

Example in Action: If you’re addressing underperformance with a Thinker, provide specific data points about missed deadlines or errors and suggest a structured plan for improvement. For a Harmonizer in the same situation, start by acknowledging their effort and expressing empathy before discussing areas for growth.

 

The Checklist: Before, During, and After the Conversation

 

Before the Meeting:

  1. Prepare Your Message: Write down key points you want to address.
  2. Gather Evidence: Have specific examples to support your feedback.
  3. Anticipate Reactions: Consider how the employee might respond based on their PCM personality base.
  4. Set Intentions: Decide on the desired outcome of the conversation.

 

During the Meeting:

  1. Start with Contracting: Clearly outline the purpose of the meeting.
  2. Use CQ Techniques: Listen actively, acknowledge emotions, and stay alert to the signals and react accordingly.
  3. Tailor Your Approach: Adjust your communication style based on PCM insights.
  4. Collaborate on Solutions: Work together to identify actionable next steps and make sure that there’s a full contract attached to the action plan.

 

After the Meeting:

  1. Document Key Points: Summarize what was discussed and agreed upon.
  2. Follow Up: Check in with the employee to ensure progress and provide additional support if needed. Schedule a meeting or reocurring check-ins to make sure that there’re no misalignments between you.
  3. Reflect on Your Approach: Assess what went well and what could be improved for future conversations.

 

Real-Life Example: Navigating Underperformance with a Harmonizer

 

Imagine you need to address underperformance with Sarah, a Harmonizer who values relationships and emotional connection.

  1. Before the Meeting: You prepare specific examples of missed deadlines but also note her positive contributions to team morale, atmosphere or relations that we build together as a team.
  2. During the Meeting: You start by saying, “Sarah, thank you for meeting me today. I really appreciate how supportive you’ve been to your teammates lately.” Then transition gently into feedback: “I’ve noticed some delays in your recent deliverables, and I’d like us to work together on improving that.” Don’t use BUT or HOWEVER (these are the killers of this part of conversation).
  3. Tailor Your Approach: Use empathetic language like “I know things have been busy lately—how can I support you in staying on track? What do you feel would be useful for you right now?”
  4. After the Meeting: You follow up a week later with a quick check-in email: “Hi Sarah, just wanted to see how things are going with the new timeline we discussed—let me know if there’s anything else I can do to help.”

 

Final Thoughts: Tough Conversations Are Opportunities

 

Tough conversations may never feel easy, but they don’t have to feel impossible either. With preparation, understading and adaptability, you can turn these moments into opportunities for growth—for both you and your employees. By leveraging contracting, CQ, and PCM, you’ll not only navigate difficult discussions more effectively but also build stronger relationships and a healthier team culture.

So next time you’re faced with a tough 1:1 conversation, remember this guide—and lead with confidence!

PS. Do you want more content like that? Go and sign into the Leman Leadership Pulse!

Udostępnij

Komentarze

0 0 votes
Article Rating
Subscribe
Notify of
0 komentarzy
Oldest
Newest Most Voted
Inline Feedbacks
View all comments

Czytaj także

Leadership

3 Leadership Lessons I Learned from Bad Recruitment Processes

Recruitment is often described as both an art and a science—a delicate balance of intuition, data, and strategy. But sometimes, even with the best intentions, things can go awry. I’ve learned this the hard way. Over the years, my experience in leadership have taught me that recruitment mistakes are not just costly in terms of money but also in terms of time, energy, and efficiency. Today, I want to share with you three of my biggest lessons from bad recruitment decisions that I hope will help you to not repeat those in your leadership practice.   #1 The Rush: When Speed Wins With Strategy   There was a time when I was desperate to fill a position on my team. Aren’t we really in constant situations like that? I remember that we had a critical project coming up, I was drowning under the amount of tasks I had on my list and I convinced myself that having “someone”—anyone—on board quickly was better than waiting for the better fit. I rushed through the process, skipping some of the deeper evaluations and settling for a candidate who seemed “good enough.” The result? It ended up costing me more than I ever anticipated. The person lacked the skills and mindset needed for the role, and within six months, we had to part ways. Not only did this mean starting the recruitment process all over again, but it also disrupted my work, again.     According to research by the Society for Human Resource Management (SHRM), the average cost per hire is around $4,700. However, if you make a bad hire, the costs skyrocket. Studies estimate that replacing an employee can cost anywhere from 8 to 12 months of their salary. For example, if you hire someone with an annual salary of $50,000, replacing them could cost you between $33,000 and $50,000. And that’s just the financial side—what about the lost productivity and influence on yourself? On the team? This experience taught me a crucial lesson: rushing to fill a position is like building a house on quicksand. It may seem like you’re saving time in the short term, but in reality, you’re setting yourself up for long-term instability.   #2 The Bias Trap: Judging by Brands, Not Skills   Another mistake I’ve made is being overly impressed by the organizations listed on a candidate’s CV. When someone came from a big-name company or a well-known brand, I found myself assuming they must be ready to do the job. After all, if they worked at such prestigious places, they must be highly capable, right? Wrong.  One candidate I hired had an impressive resume filled with experience at top-tier organizations. I was so dazzled by their background that I overlooked some red flags during the interview process—things like their lack of enthusiasm for the role or their vague answers about past achievements. It turned out that their success in previous roles was largely due to the systems and teams already in place at those organizations. In my smaller, more dynamic team, they struggled to adapt and contribute effectively. This mistake taught me to focus on the specific person, not just their past affiliations. A brand name on a CV doesn’t guarantee a cultural, personality-based or skill set fit for your organization. Now, I dig deeper during interviews, asking specific questions about their contributions and how they handle challenges in different environments.   #3 Ignoring the Personality Match   As someone deeply invested in Communication Intelligence (CQ) and the Process Communication Model (PCM), I know how critical personality dynamics are in any working relationship. Yet, there have been times when I ignored this knowledge during recruitment—and paid the price for it. I once hired someone who looked perfect on paper: they had the right skills, experience, and even glowing references. But what I failed to assess was how well we would work together on a personal level. Our communication styles clashed almost immediately. Where I value directness and proactive problem-solving, they preferred a more passive approach and avoided conflict at all costs. Data vs emotions. Logic vs relationship care. Nothing wrong about that, don’t get me wrong! But it comes with a cost, especially when you work in a small setup. This mismatch didn’t just affect our one-on-one interactions; it also impacted the overall efficiency. When there isn’t alignment between a leader and their team members, it creates friction that slows down decision-making and execution. According to Gallup research, disengaged employees can cost organizations up to 18% of their annual salary in lost productivity. Imagine what happens when that disengagement spreads across an entire team! Now, I make personality assessments a non-negotiable part of my recruitment process. Tools like PCM are there to use: I’m not saying that you do a questionnaire for every single candidate since it’ll cost a lot (if you can afford it, go for it!). It’s about using the framework in practice. Listen, observe, connect the dots. Everything is there, you just need to know what you’re looking for.   Moving Forward: How to Avoid These Pitfalls    Here’s what I’ve learned to do differently: Prioritize Fit Over Speed: Take the time to find someone who aligns with your team’s needs and culture—even if it means extending your search timeline. Remember that fast recruitment can cost you so much more time in the future. Dig Deeper Into Experience: Don’t be swayed by big names on a CV; focus on understanding what the candidate actually contributed in their previous roles. Assess Personality Compatibility: Use tools like PCM or other personality assessments or knowledge from the framework to ensure alignment between you and your potential hire. Recruitment is never going to be an exact science, but by learning from past mistakes and implementing more thoughtful strategies, you can significantly improve your chances of finding the right person for your team—and avoiding costly missteps along the way.   Final Thoughts    As leaders, we often feel immense pressure to make quick decisions and keep

Czytaj dalej
Leadership

What Are Most Common Beliefs That Hold Tech Leaders Back?

As a Tech Leader, you’re tasked with guiding innovation, meeting deadlines, and managing diverse teams—all while navigating the complexities of human dynamics. It’s no small challenge. But what if I told you that some of the beliefs you hold about leadership might actually be holding you back from creating an environment where people want to stay and thrive? Let’s take a closer look at three of the most common beliefs that I encounter when working with Tech Leaders and explore actionable solutions to shift your mindset and approach.   Belief 1: “If I’m not the expert in the room, I’ll lose respect.”   Many Tech Leaders feel immense pressure to always have the answers. After all, you’ve likely climbed the ranks because of your technical expertise. But leadership isn’t about being the smartest person in the room—it’s about enabling others to shine (it hurts, I know). The problem is that when you focus on showcasing your expertise, you risk micromanaging or overshadowing your team’s contributions. This can stifle creativity and lead to disengagement: your people think won’t have enough space to try out new solutions, make mistakes and learn from them to build their own expertise. Solution? Shift from being the “expert” to being the “facilitator.” Ask open-ended questions like, “What do you think we should do here?” or “How can we approach this differently?” Empower your team to take ownership of their ideas and solutions. Remember, respect is earned not by knowing everything but by fostering trust and collaboration.   Belief 2: “Feedback will demotivate my team.”   I often hear leaders say they avoid giving constructive feedback because they fear it will hurt morale. While it’s true that poorly delivered feedback can cause friction, avoiding it altogether is far more damaging in the long run. The problem is that without feedback, your team doesn’t know where they stand or how they can improve. This ambiguity can lead to frustration, disengagement, and even turnover: all those things are not the ideal situation for you, as a leader, and for your team as well. There are very costly: losing one employee is a cost of 8-12 monthly salaries of this person (in average). Solution? Reframe feedback as an opportunity for growth rather than criticism. Use a structured approach, even the most common ones like “Start-Stop-Continue” will be a huge help (and easy to implement): – Start: What new behaviors or actions could help them grow? – Stop: What habits or approaches might be holding them back? – Continue: What are they already doing well that they should keep up?   Deliver feedback with using Communication Intelligence (CQ) muscle, tailor the communication to your employee’s needs, be specific, and always tie it back to their potential and goals.     Belief 3: “People leave because of better opportunities, not because of me.”   It’s easy to blame external factors when someone leaves your team—higher salaries, exciting projects elsewhere, or personal reasons. While those factors do play a role, research consistently shows that people leave managers, not companies. The problem is that assuming turnover is out of your control absolves you of responsibility for creating a supportive environment. This mindset prevents you from addressing underlying issues within your team dynamic. Solution? Conduct regular one-on-one check-ins where you ask questions like: – “What’s one thing I could do to support you better?” – “Do you think that you’re challenged and fulfilled enough in your role? If not, what can we do to move a needle here?” – “What’s your long-term vision, and how can I help you get there?”   By showing genuine interest in your team’s well-being and career aspirations, you’ll build loyalty and reduce turnover. It’s not so obvious to have a leader that actually care and think about their employees’ in more holistic approach.   The bottom line   Leadership is as much about unlearning as it is about learning. By challenging these common beliefs and adopting a more people-centric mindset, you’ll not only become a stronger leader but also create a work environment where people feel valued and inspired to stay. Remember: great leaders don’t just manage tasks—they cultivate trust, growth, and connection. That’s the kind of environment people don’t want to leave. Ready to challenge more leadership beliefs? Go and listen to the latest episode of Leman Tech Leadership Podcast!

Czytaj dalej
Leadership

Breaking the Code: Myths About Mistakes in Tech World

As Tech Leaders, we often find ourselves navigating a world of constant change, high stakes, and the persistent pressure to deliver. In this fast-paced environment, mistakes are inevitable. Yet, despite their inevitability, mistakes often carry an unnecessary stigma, especially in the technology sector. We’ve all been there: a bug in production, a failed sprint, or a product launch that didn’t hit the mark. These moments can feel like personal failures, but they’re also opportunities for growth—if we allow them to be. Unfortunately, many of us are held back by persistent myths about mistakes that do more harm than good. Let’s unpack these myths and explore how tech leaders can reframe their thinking to foster innovation and resilience within their teams.   Myth 1: Mistakes Are a Sign of Incompetence This is perhaps the most damaging myth of all. In a field as complex as technology, mistakes are not just normal—they’re expected. Yet, many Tech Leaders (and their teams) fear that admitting to errors will make them appear unqualified or incapable. Here’s the truth: mistakes are not a reflection of incompetence but rather a natural byproduct of working on resolving complex problems. In fact, some of the most groundbreaking innovations in tech have come from mistakes. Take the accidental creation of Post-it Notes or the discovery of penicillin—while not directly tech-related, these examples remind us that groundbreaking discovery often follows missteps. As a leader, it’s your job to model curiosity. When you own up to your own mistakes and frame them as learning opportunities, you create a culture where your team feels safe to take risks and innovate.   Myth 2: Perfection Is the Goal Let’s face it: perfection in tech doesn’t exist. There will always be bugs in the code, unforeseen edge cases, or unexpected user behaviors. Yet, many leaders fall into the trap of striving for perfection, believing that flawless execution is the ultimate measure of success. And we do know that’s far from the truth. The pursuit of perfection can paralyze teams, leading to analysis paralysis and delayed decision-making. Worse yet, it can stifle creativity and experimentation—two critical drivers of innovation in technology. Instead of chasing perfection, focus on progress. Encourage your team to adopt an iterative mindset: ship, learn, and improve. Agile methodologies are built on this principle for a reason—they prioritize adaptability over rigid adherence to an idealized end state. Remember, your job as a leader isn’t to eliminate mistakes but to create an environment where mistakes lead to better outcomes.   Myth 3: Mistakes Waste Time and Resources    It’s easy to view mistakes as setbacks that cost time and money. But what if we flipped that perspective? What if we saw mistakes as investments in future success? Consider this: every mistake your team makes is a chance to uncover blind spots, refine processes, and build resilience. A bug in production might reveal gaps in your testing strategy. A failed product launch could highlight misalignment between engineering and marketing teams. These insights are invaluable—they help you course-correct and prevent larger issues down the line. Of course, not all mistakes are created equal. As a leader, it’s important to distinguish between reckless errors (caused by carelessness or lack of preparation) and intelligent (or even necessary) ones (made in the pursuit of innovation). Celebrate the latter and use them as teachable moments for your team.   Myth 4: Leaders Should Have All the Answers    As Tech Leaders, we often feel pressure to be the smartest person in the room—the one with all the answers. But this mindset is not only unrealistic; it’s counterproductive. When you position yourself as infallible, you surprisingly discourage your team from speaking up or challenging assumptions. This can lead to groupthink, missed opportunities for improvement or other limiting biases that rob us from achieving extraordinary results. Instead, embrace a mindset of continuous learning. Ask questions, seek input from your team, and admit when you don’t know something. By doing so, you demonstrate humility and foster a culture of collaboration and shared ownership. Remember, leadership isn’t about having all the answers—it’s about empowering your team to find them together.   Myth 5: Mistakes Are Best Swept Under the Rug    In some organizations, there’s an unspoken rule: don’t talk about mistakes. This culture of silence can be incredibly toxic, leading to fear, blame-shifting, and a lack of accountability. As a leader, it’s your responsibility to break this cycle. Encourage open dialogue about mistakes and frame them as opportunities for growth. Conduct retrospective sessions after incidents or project failures to identify root causes and actionable takeaways. Transparency is key here—not just within your team but across your organization. When leaders openly discuss their own missteps and what they’ve learned from them, it normalizes the idea that mistakes are part of the process.   Reframing Mistakes as the Golden Key   So how can we, as Tech Leaders, shift our perspective on mistakes? Here are a few practical strategies: Lead by example: Share your own experiences with failure and what you learned from them during team meetings or one-on-ones. Celebrate learning moments: Recognize team members who take risks and learn from their mistakes—even if the outcome wasn’t what they hoped for. Create psychological safety: Foster an environment where team members feel safe to admit errors without fear of punishment or being laughed at. Encourage reflection: After a mistake occurs, ask your team reflective questions like “What did we learn?” or “How can we do better in the future?” Focus on systems: Instead of blaming individuals for mistakes, look at the systems and processes that contributed to them and identify areas for improvement.   The bottom line   Mistakes are not the enemy—they’re an essential part of growth in the tech world (and beyond). As leaders, our role is not to eliminate mistakes but to create a culture where they’re seen as opportunities for learning and innovation. By reframing these common myths and our approach to failure, we can build teams that are resilient, creative,

Czytaj dalej
0
Would love your thoughts, please comment.x
()
x