Lemanskills.com

How to Manage a Team in a Constant Change?

When we are managers, or we want to become ones in the nearest future, we often realize in a certain moment that there are so many things we need to cover in this role. Being Hiring Manager and recruit new people to the team. Onboard new hires. Organize and conduct team meetings (weekly, bi-weekly, monthly), 1:1 meetings with every person in a team (weekly, monthly, quarterly), summary meetings (monthly, quarterly). Taking care of the team development (on individual and on team level), answering their questions that never end (especially during the time of change). Solving problems, conflicts and other issues that appear on a daily basis. And at the same time, we need to deliver business, by covering endless tasks, participating in other meetings, learning all the time how to be a good manager.

And we need to do all of those things in an environment that changes all the time. The history of the world shows us that there are periods of time where things were more constant, but most of the time we are a part of some kind of transformation, transition, a constant change. And for a manager, this lack of stability and uncertainty is one of the hardest elements of the work environment that influences our plans, actions and decisions that we make every day.

Because how to build a strong, high-performing team, full of engaged people that will deliver results no matter what happens? How to do it when we already know that the change we face will never stop? That we need to operate in the circumstances that are mostly unpredictable? Let’s dig deeper into this subject today.

Why the change never ends?

Interesting thing about the change is that we are so afraid of it, most of the time we resist it, because we think that we are going to loose something when the change will come. Or we are angry that somebody will change something and we are will need to adjust, AGAIN, and it makes us feel like that. But at the end of the day, when we get used to the new reality, we are quite happy about it – sometimes even that much that we don’t want to come back to the previous scenario.

Example? Remote work. When the pandemic came, a lot of people needed to change the way they were working from being at the office, to being at home (of course if the type of the work allowed it). It was dramatic in many cases: living in 2-room apartment, with 2 kids, working partner and a dog. Or living and being alone all the time what brought more depression that anytime before. Weak internet access, lack of technological equipment or abilities to work or learn remotely. Many people were whining that they can’t focus or they never finish working, because their computer is always turned on.

And now? Mostly it is a wave of huge rage when organizations have started to decide that employees should come back to the office, mostly in a hybrid mode. And in many cases it is a no-go, people refuse openly and start looking for another job that will allow them to work remotely 100%. Crazy, huh?

The change never ends because the world develops itself all the time: it is the nature of it. There is a saying that if you don’t grow, you go backwards. That’s true when we think about the individuals, teams, organizations and the whole world. And it happens because we want to be better, smarter, we learn and we automate things. We want to do things smarter, using less time and more technology if possible to achieve better results. To not learn one thing or a skill for 20 years, but to spend couple of hours and learn from people that have already done the life work in a certain area. Changes making us feel in a certain way, no matter if they are positive or negative. In most cases we can’t control it, but what we can do is to make proper decisions to use those changes the best possible way.

What is the most important for people?

In the world of a constant change, managers need to have a proper strategy and tactics to work with it no matter what kind of circumstances comes. It is too frustrating and too exhausting to make a decision how to operate in the situation of change differently every single time. That’s why it’s helpful to have a framework that you can use every time and you adapt it however the situation requires you to act.

What is the most important for people in any situation of a change that the organization can face?

  • Structure. When the change comes, one of the first emotions that appears is fear. Fear that the change will hurt us somehow, that we are going to loose something we care about. And what helps people with dealing better with this emotion is structure: of the day, of tasks, of meetings. Even if it is the slightest repetitive thing that people can be attached to, it makes them feel more secure, even when they experience a massive change. Give your people the structure of their day, week or month, take care of constant elements that appear regularly. Even if everything outside of their bubble is burning, they have something they can rely on.
  • Influence. When you have zero influence on something, you can freeze really easily and no communication, no information and no stimuli will reach your brain out. Of course, there are a lot of different situations when we don’t have influence on something, starting from a certain person’s behavior, through organizational changes to the global issues or transitions. So when you are a manager, use the opportunity to create an environment where your team understands where they have zero influence (so talking or analyzing a certain situation or decision is just a waste of time) and where they actually have influence (and they can focus their energy there). It is going to be more efficient, less frustrating and will give them more calmness in the whole system.
  • Truth. Give people the truth. There are not many things worse that sticking to the bs that you’ve created in your head because you thought that you’ll protect people or something. Of course you need to think about the way that you communicate before you actually do it. It’s not about being brutally honest, no matter what. It’s more about being transparent, honest about what’s really going on, being radically candid. When you lie, people will find out sooner or later and you lose credibility and trust. For what? For a moment of peace and silence before the storm or a brief feeling of “protecting” people? Believe me, it’s not worth it. Your employees will trust you more and they will be calmer when they will have a well-communicated truth, a safe space and time to process it and a support when they need it. That kind of combination gives a bigger chance to succeed, even if it doesn’t look like that in a certain moment.

How to come back to OK-OK position to lead the change successfully?

Sometimes you as a manager don’t fully agree with the changes or decisions that are being made in the organization. And that’s ok – it’s not physically possible to agree with everything. All of us have unique set of values, things that are important for us or those that we don’t accept.

But the leadership function has its own rules that we need to follow: we accepted it once we agreed to have this position. Some of us are not aware of it from the very beginning, but it’s crucial to understand it to be a successful manager. As a manager you are a part of the organization and you are responsible for its success or failure. On a business level, but mostly on a people level. It means that you are the voice of the company that your people hear in the clearest way. And the way you communicate is often the first thing they hear, so they learn from it the most.

When you don’t agree or have a very strong personal opinion about a change that is happening in the organization, it is a high risk that you won’t be in OK-OK position that will allow you to think and communicate clearly. Most of the time the position is OK-not OK (meaning: bad, nasty organization and poor us, employees). Again: it’s a natural reaction to a change, in a root of a fear of losing something. The key thing is to get back to the OK-OK quadrant. To say to yourself: “ok, I don’t need to agree with everything, but I understand why we do this change and what we want to achieve here”. “I am a part of the organization and my role is to pass the information to my people as well as I can, to support them in going through that change as smoothly as possible, without a drop in their productivity and engagement”.

This is the best possible reaction you can have in every change that you experience. You lack of information or you are not sure about the WHY? Go get the information. Don’t blame the organization that THEY didn’t provide you some facts. We are all human, sometimes the communication process is not perfect. But it’s your role to get the information, don’t look for BAD, GUILTY PEOPLE that DID IT TO US. Be wise, think clearly, use the opportunity to learn and be better as a manager every time that the change comes.

The bottom line

Being a manager is a hard work. It’s not just the fancy position title, status, more money or a nice car. It is a real work, effort that you need to put in every day to be a good person for your people. To support them when needed, but also to give them data and structure, so they know what is happening. A good manager chooses wisely how to manage a certain situation, how and what kind of information pass to people, so they understand the reality, and don’t waste their time on gossip, frustration or other negative emotions.

Do you want to be a leader in a change that people follow and trust? Or you rather want to be a person that is “on the peoples’ side”, whine with everybody and resist to everything that is going on? The second option is not a leadership, it’s not doing your job: it’s being a coward.

The choice is yours.

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

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: Underperformance: An employee is consistently missing deadlines or delivering work in a quality we agreed on. Behavioral issues: A team member exhibits disruptive behavior, such as frequent conflicts with peers or unprofessional communication. Career Development: You need to inform an employee that they didn’t receive a promotion or that their role is changing. Restructuring: Delivering news about layoffs or departmental changes. 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. 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. 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. 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: 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.   Persister: Principled, dedicated, values integrity and commitment. – Approach: Appeal to their sense of purpose and principles. – Stress Behavior: May become judgmental or

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