5 Biggest Leadership Feedback Mistakes

Leadership

As a leader, giving feedback is an essential part of your role. However, there are some common mistakes that leaders make when delivering feedback that can have huge effects on the individual, the team, and the organization as a whole. As we want to be as efficient as possible and not waste time or effort on insufficient communication, it’s important to be aware of these pitfalls and have ready-to-use ways to avoid them. Here are five things that leaders shouldn’t do while giving others feedback, along with examples of the potential consequences that you can save yourself from. Ready? Let’s dig in.

1. Being overly critical without providing constructive guidance

One of the biggest mistakes a leader can make when giving feedback is being overly critical without providing constructive guidance. For example, if a team member presents a project and the leader simply says, “This is terrible,” “A monkey would do it better” without offering any specific feedback or suggestions for improvement, it can be incredibly demoralizing for the person. This kind of feedback can lead to a huge decrease of intrinsic motivation and confidence in the team member, as well as a thud in an overall team morale. In the long run, it can also result in a decrease in productivity and innovation within the organization.

This is not a feedback from OK-OK quardant at all. We were talking about it why it is crucial to speak from this space in the article and podcast, but I will say it one more time. If you are not in an OK-OK zone, first thing you need to do is to go back there, by covering your motivational needs and only then move to the conversation with the other person. Without that, the conversation will always be stresful, full of aggresion, manipulation or withdrawal of one or both sides.

2. Failing to tailor feedback to the individual’s communication base

Another common mistake is failing to tailor feedback to the individual’s communication preference. For instance, if a leader gives feedback in a direct manner (Promoter) to an employee who prefers a more empathetic and nurturative approach (Harmonizer), it can lead to miscommunication and misunderstandings. This can result in a breakdown of trust and rapport between the leader and the team member, as well as hinder the individual’s ability to fully understand and act on the feedback. Ultimately, this can impact the team’s cohesiveness and collaboration, as well as the organization’s overall communication effectiveness.

When we use a one-size-fits-all approach, we are so surpried that the feedback doesn’t land. Or sometimes it works, and sometimes it doesn’t. So we blame people, sometimes by saying: “What is so hard to understand?!” or “Others get it and you can’t!”. Basically: it’s about you, not about me. So it has a huge cost, for us as leaders, and for our team as well. Let’s not be mad on others: we can be mad on an educational system that doesn’t teach us communication at school, but both ways are a waste of time. I would say that we rather invest this time in learning and practicing on how to match the needs of the other person and crafting feedback so it’s custom-made.

3. Using feedback as a means of control or manipulation

Using feedback as a means of control or manipulation is another mistake that leaders should avoid. For example, if a leader gives feedback with the intention of pushing a team member into conforming to their own agenda or way of thinking, it can create a toxic and disempowering work environment. This kind of behavior can lead to resentment and disengagement among team members, as well as a lack of creativity and initiative within the team. Over time, it can also result in high turnover rates and a negative reputation for the organization.

We are coming back again here to the OK-OK mode. If we don’t have a positive intention while sitting at the table with an employee, there’s no chance to end the meeting with an agreement. At least, not with the honest one. There’s a 4A Feedback Guidline that was created by Reed Hasting at Netflix. And the first A is an “Aim to assist”. Always have that in mind. You don’t have it? Go find it, and then sit with a person to have a proper conversation.

4. Ignoring the emotional impact of feedback

Ignoring the emotional impact of feedback is another critical mistake that leaders often make. Regardless of the personality base of the person, if it’s a Harmonizer or anybody else, it always has an impact on a person. Mostly because we have so bad feedabck experiences from the bast that on each sentence that includes “feedabck” in it, we respond with a higher stress level right away. That kind of lack of awareness and insensivity can result in increased distress (negative stress) and anxiety level for the team member, as well as a decrease in their overall well-being and job satisfaction. Going further, it can lead to the high level of resistance, being close to the suggestions or ideas of the leader. In turn, this can lead to higher levels of absenteeism and decreased productivity within the team, ultimately impacting the organization’s bottom line.

So I say: let’s be more mindful, check with people how they are doing before, during and after the conversation. Ask for feedabck for ourselves: what we do really well? And what can we do better when it comes to leading those conversations? Each situation is an opportunity for us to learn and be better next time. It’s like training and strenghtening a muscle.

5. Failing to follow up on feedback

Finally, failing to follow up on feedback is a mistake that can hinder an individual’s growth and development. For example, if a leader provides feedback on a specific area for improvement but fails to follow up with ongoing support and guidance, it can lead to stagnation and a lack of progress. This can result in missed opportunities for skill development and growth within the individual, as well as a decrease in their overall performance and contribution to the team. Ultimately, this can impact the organization’s ability to adapt and thrive in a competitive market.

As you can see, those mistakes not only influence one person (your employee), but also have a negative impact on a team and sometimes on the whole organization. I can tell that a lot of leaders miss the holistic perspective: seing things not only from the operational point of view, but also from the helicopter picture. If I can advice you to pick a skill to work on in 2025, the ability to give a well-design feedback will definitely be in my TOP3.

Go, practice. Be better.

Udostępnij

Komentarze

0 0 votes

Article Rating

0 komentarzy

Oldest

Newest Most Voted

Inline Feedbacks

View all comments

Czytaj także

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

1 February 2025 No Comments

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

25 January 2025 No Comments

Leadership

10 Ways to Get Your Time Back: Practical Tips for a Tech Leader

As a Tech Leader, your day is likely filled with endless meetings, urgent emails, project deadlines, and unexpected crises. It’s easy to feel like there’s never enough time to focus on what truly matters—whether that’s strategic thinking, team development, or even your own well-being. But here’s the good news: with a few intentional changes, you can reclaim your time and focus on what drives real impact. This isn’t about pretty theories or abstract advice. Below, you’ll find 10 practical, actionable tips that you can start implementing today to get your time back. Interested? Let’s get to it! #1 Audit Your Calendar Your calendar tells the story of where your time goes—and often, it’s not a pretty picture. Start by reviewing your calendar for the past two weeks. Ask yourself: Which meetings were truly necessary? Could some have been shorter? Were there meetings I didn’t need to attend at all as a leader of my team? Depends on the answers, make some shifts. Move meetings around, if you have influence on them: put them in the time of the day that you’re not in your genius zone. Use the calendar as you source of power, not a thing you are a slave of. Actionable Tip: For every recurring meeting on your calendar, apply the “zero-based budgeting” approach. Assume the meeting doesn’t need to exist unless there’s a compelling reason to keep it. For meetings you do keep, limit them to 25 or 50 minutes instead of the standard 30 or 60 minutes—this will force more focused discussions and give you breathing room between calls. #2 Delegate Like a Pro Leader Tech Leaders often fall into the trap of trying to do everything themselves—whether it’s troubleshooting a technical issue or reviewing every line of code. But delegation isn’t just about offloading tasks; it’s about empowering your team and creating space for you to focus on higher-level priorities. Actionable Tip: Use the “3D Framework” for tasks: Do it, Delegate it, or Delete it. If a task doesn’t absolutely require your expertise, delegate it to someone who can handle it. And if it doesn’t add value, delete it altogether. Make sure of good contracting around the delegation though: it needs to be clear, including context, checking on the skillset of the person who’s going to get the task. Be smart here; don’t assume: ask. #3 Batch Similar Tasks Together Switching between tasks—like coding, answering emails or Slack / Teams messages, and attending meetings—can drain your mental energy and waste time. Instead, group similar tasks together and tackle them in dedicated blocks of time. Actionable Tip: Create “themed” days or blocks of time. For example: – Monday mornings: Strategic planning – Tuesday afternoons: One-on-ones with team members – Friday mornings: Deep work on a long-term project When you batch tasks, you reduce context-switching and increase focus. Let’s say it once for good: there’s no such thing as multitasking. You can switch between tasks really quickly, but it has its cost. Reduce it, be more focused and you’ll see the difference in your efficiency and energy level as a leader. #4 Say “No” More Often Every time you say “yes” to something, you’re saying “no” to something else—often your own priorities. Learning to say “no”, or “yes, and…” is one of the most powerful ways to protect your time as a Tech Leader. Actionable Tip: When someone asks for your time, don’t respond immediately. Instead, say: “Let me think about it and get back to you.” This gives you space to evaluate whether the request aligns with your goals. If it doesn’t, politely decline or suggest an alternative solution. Remember about being in OK-OK space: you don’t want to be rude or aggressive; boundary setting is not about hurting others, it’s about protecting yourself. #5 Leverage Asynchronous Communication Not every conversation needs to happen in real-time. In fact, asynchronous communication can save you hours each week by reducing unnecessary meetings and interruptions. Actionable Tip: Use tools like Slack, MS Teams, or Loom to communicate asynchronously. For example, instead of scheduling a meeting to discuss a project update, record a short video or write a detailed message outlining the key points and next steps. Bonus Tip: Set clear expectations for response times in asynchronous channels (i.e., “respond within 24 hours”) so everyone stays aligned without feeling pressured to reply instantly. #6 Automate Repetitive Tasks If you’re spending time on repetitive tasks that could be automated, you’re leaving valuable hours on the table. Automation isn’t just for developers—it’s a key productivity tool for all of us, regardless of our role in the organization. Actionable Tip: Identify one repetitive task you handle weekly (i.e., generating reports, scheduling meetings, answering emails) and automate it using tools like Zapier, IFTTT, or custom scripts. Example: Automate status updates by integrating project management tools like Jira or Trello with Slack so your team gets real-time progress updates without manual intervention. #7 Create Decision-Making Frameworks Decision fatigue is real—and as a tech leader, you’re probably making dozens of decisions every day. And we have a limited decision capacity: we make around 35,000 decisions daily, but less than 100 are optimal. Creating frameworks can help streamline this process and free up mental energy for more important work and more capacity for better decisions. Actionable Tip: Develop simple decision-making criteria for recurring situations. For example: Hiring decisions: Does this candidate have at least 70% of the required skills? Project prioritization: Does this initiative align with our top three business goals? Task selection: Does this task bring me closer to the OKRs I have on my list for this quarter? By standardizing decisions, you’ll spend less time deliberating and more time executing. #8 Adopt a “Less is More” Leadership Mindset In Tech Leadership, more isn’t always better—more features, more meetings, more initiatives can lead to diminishing returns. Focus on doing fewer things exceptionally well rather than spreading yourself too

Czytaj dalej

5 January 2025 No Comments