Do I Even Want to Be a Leader?

Leadership

Why people accept being leaders? Is this something we dream about as kids? When we get the question: “Who you would like to be when you grow up?”, do we answer: “A middle manager in the huge, global organization”?

Is it a matter of a “natural talent” we have and show as children to lead or maybe a set of skills that every person can learn and then use quite successfully?

Why is that some people are great leaders for their teams and the others (statistically bigger representation) are making people miserable and in consequence: quitting?

Let’s unpack this subject today.

The Story of One Tech Leader…

I work a lot with First Time Managers. Those are people who are fresh in leadership positions, statistically up to 3 years in the role. Most of the time there were great SMEs (Subject Matter Experts) and a natural move for them to grow was to be offered with a Team Leader role of the team there work in.

I remember very well one story that relate to a Tech Leader I worked with in the mentoring process a couple years back.

He was a very skilled expert in one of the leading technologies that was used in the core product of the company. He started as a junior, but learned very quickly, constantly participating in trainings, conferences and projects, working on different implementations and most of the time building functionalities from scratch. When he grew to the expert position, he also got the task of teaching others, onboarding new team members and acting as a technical mentor to them. He was doing great.

Then, as an obvious offer for the organization he got a proposition to become a Team Lead of the team: the same one that he was an expert within. He took the job: the money wasn’t extremely bigger, but potentially more organizational and strategic impact was an argument that he was sold to. He thought: “I know everything about the scope of the team’s work, what else can there possibly be?”

A few weeks later in the role showed him otherwise. He started to be a completely different person: like he had some hidden personality that was there, waiting to be awaken for so long. He started to be mean to team members, getting angry and mad very quickly when he saw any mistakes or imperfections in what the team delivered. He even got constructive feedback, by name on team daily meetings: what was unacceptable and never happened before. The team engagement started to drop; first people made decisions about leaving the area that they loved working within.

That was the moment when he was redirected to me, so I support him in this situation.

Why People Accepting Leadership Roles?

This story shows us a few aspects of why we accept those roles connected to People Management when they are on the table. What I see from working with different cases and circumstances, there are 5 reasons that are the most common: I would say they cover 80% of all decision about choosing this career path:

1. The only way to grow. Sometimes people don’t see other options. They think that accepting leadership position is the only way they can be promoted or have possibilities to learn. Either is their strong belief that can have a root even in childhood (if it was a home conviction, being expressed loudly so we picked it up as children and we took it for life) or an experience from different organizations from the past. Sometimes it is true that organizations offer more, i.e. trainings, workshops, mentorship opportunities for leaders. It shouldn’t take place, so if you see if, I would advise to reach out your supervisor or HR person to take a closer look on that.

2. Fancy position name. Team Lead, Manager, Director, Head: the higher in the structure, the fancier it sounds. And the better it looks on LinkedIn or the resume. Potentially of course. The question is: do you want to grow in the leadership space in your current and different organizations on the market in the future? If yes, ok: the name of the positions matters, since recruitment process is marketing process (for both sides). If not: it doesn’t really matter. So, first: go and answer this question.

3. More potential influence / power. Sometimes we take leadership positions because we believe that’s the only way to make a real change. To get a seat at the table, to have opportunities to say things out loud, to be an advocate of what we say as a team. To have more positive influence or power to reshape a work environment, even if it’s just a small piece of it. The question is: is it a really a truth that by changing the role to be a leader, you will have this influence, more than you have as an expert?

4. Better visibility. I hear this one a lot. And it’s connected with the more influence and power element described above, sometimes treated as one thing. “If I’m a leader, I’ll be more visible = I’ll have more credibility to make a real change.” It also comes with the visibility on the market or in the specific part of the industry: when I’m a leader, I will be more reliable, my LinkedIn will blow out and I will have countless invites as an expert / speaker / podcast guest etc. Is it really a truth? Can’t you be all of these as a real expert in your area?

5. More money. Here comes a catch. The money part most of the time comes at the very beginning of the list of reasons on why to accept the leader role. And you know what? It’s not always the case. I saw multiple examples of extremely skilled, well-known experts that earned way more money than their supervisors. Because their skillset was super niched out, and there were literally few people in the area that could’ve done what they were skilled at.

So, the real question is: what are you passionate about? What you can do all day, in the flow state, sometimes even forgetting about going to the bathroom or eat properly because you’re so into the process? If it is being a leader, taking care of the team’s work environment, give feedback and recognition, organizing the work, solve conflicts and misunderstandings every single week? If yes, that’s great: you have a lifetime of learning ahead of you to be a leader that people don’t quit.

If you are passionate about something else: being a developer, analyst, accountant, employer branding or an expert in a chosen marketing area, the leadership job is not for you. You can’t have the cake and eat the cake.

Why?

What Are the Consequences of Hating Being a Leader?

When we take leadership position and we really don’t want to deal with people, there is a high probability that we are going to make ourselves and our people miserable.

1. You won’t want to learn. Leadership skillset is quite different that the SME skillset. Yes, you can use some of the skills that you’ve acquired over the years of being a specialist, but the truth is that there are a lot of things you’ll do as a leader that you’ve never done as a non-leader. And if you don’t have a heart to it, you will reject the opportunities to learn, you won’t be willing to get new knowledge and tools to put it into practice.

2. Your frustration will influence your people. The influence of a leader on a team is bigger than we think. If we are frustrated, angry, disappointed as leaders, our people will get there too. Even when the circumstances of those emotions or reactions are different than ours, they will behave in a parallel way. Our fixed mindset will become their fixed mindset. You won’t be an advocate of the organization if you are not in the right place: and you won’t’ help your team to thrive.

3. If you hate your job, your team will their too. It is quite visible when someone loves what they do professionally. We see the passion and energy when a person talks about it, we see how much time they spend on working on some tasks, learning about the field, participating in conferences, meetups, workshops etc. It’s inspiring: even if our area of expertise is different, those behaviors itself are making a positive impact. If it’s not there, the person whines all the time on how hard it is, how exhausted they are, how pointless is everything we do here… You see the difference.

So… What is the Conclusion Here?

The conclusion is simple: you need to decide if you want to be a leader. It’s one way or the other, there is no other option here. When you decide: yes, I want to be a leader, you go all in. You delegate SME tasks, and you learn how to be a real leader for your people.

When you decide: you know what Alex? I really don’t want to be a leader: I want to do my SME tasks and grow in this space. That’s great! You can expand in the current scope or learn new things to become a broader expert. Or pivot a little bit and learn something new, reskill yourself. That’s fine as well!

What if you’ve already made a decision about being a leader and you know now that it was a bad decision?

Quit.

It’s nothing wrong with it, it doesn’t mean that you are a weak person. It means that you are a brave person, who took time to really get to know yourself and is mindful about yourself and others. It means that you don’t want to be miserable for the 60% of your life (that’s approximately how much time we spend at work: doing and thinking about it). Don’t listen to other people who say that you should suck it up and just hang on there to get another promotion in 2 years. It’s not worth it.

But working on what you are passionate about every single day? I bet it’s quite the opposite.

PS 1. You want to know what happens with the manager from the story? After few mentoring sessions with me, he had decided to quit being a leader to come back to the SME role. And you know what? He’s never been happier in his life.

PS 2. If you want to expand more on the topic from this article, go check out my newest course “3 Ways to Be a Leader that People Don’t Quit”!

Udostępnij

Komentarze

0 0 votes

Article Rating

0 komentarzy

Oldest

Newest Most Voted

Inline Feedbacks

View all comments

Czytaj także

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

Leadership

Why Habits Are Better Than Goals: A Guide for Leaders

As technology leaders, we live in a world driven by deadlines, KPIs, and ambitious goals. We’re taught to set objectives and measure progress. But what if I told you that focusing on habits rather than goals might be the game-changer you’ve been looking for? Especially if you’re struggling to find time for your own professional development or noticing low engagement within your team, shifting your mindset to prioritize habits could transform not only your leadership but also your entire organization. Let’s explore why habits are more powerful than goals and how they can help you lead with greater impact. The Problem with Goals Goals are seductive. They promise a future where everything is better: you’ve mastered a new skill, your team is more engaged, or you’ve finally achieved that elusive work-life balance. But here’s the catch: goals are outcome-focused. They emphasize the “what” rather than the “how”. For example, let’s say your goal is to improve team engagement. You might set metrics like increasing participation in meetings or boosting employee satisfaction scores. But once you hit those targets, what happens next? Without a system in place, the progress often stalls or even reverses. Goals also have an inherent flaw: they’re temporary. Once achieved, they leave a void. This is why so many of us experience the post-goal slump: a sense of “what now?” after crossing the finish line. Moreover, as busy technology leaders, goals can feel overwhelming. When your calendar is already packed with back-to-back meetings and project deadlines, adding another goal to the mix can feel like just another task on an endless to-do list. Why Habits Are the Better Alternative? Habits, on the other hand, focus on the process. They are small, consistent actions that compound over time to create meaningful change. Instead of chasing a distant outcome, habits anchor you in the present and guide your daily behavior. Here’s why this matters: Habits Build Identity. While goals are about achieving something external, habits shape who you are. For example, instead of setting a goal to “become a better communicator,” you could develop the habit of asking open-ended questions during one-on-one meetings. Over time, this habit reinforces your identity as a leader who listens and connects deeply with their team. Habits Are Sustainable. Unlike goals, which have an endpoint, habits are ongoing. They create a foundation for continuous improvement without requiring constant resets. A habit like setting aside 15 minutes every day for professional reading or reflection becomes part of your routine:no extra mental energy required. Habits Reduce Decision Fatigue. As a leader, you make countless decisions every day. Habits automate certain behaviors, freeing up mental bandwidth for higher-priority tasks. For instance, if you establish a habit of starting each morning by reviewing your team’s priorities, you don’t have to waste time deciding how to begin your day: it’s already decided for you. Habits Drive Engagement. When it comes to team dynamics, habits can be contagious. If you consistently model behaviors like active listening or celebrating small wins, your team is likely to adopt those practices as well. Over time, these shared habits create a culture of engagement and collaboration without requiring constant top-down interventions. How to Build Habits That Stick? Now that we’ve established why habits are so powerful, let’s talk about how to build them effectively. Here are some practical steps tailored for busy technology leaders: #1 Start Small One of the biggest mistakes people make is trying to change their entire routine overnight. Instead, focus on one small habit at a time. For example, if you want to prioritize professional development, commit to reading just one article or watching one TED Talk per week. Once this becomes second nature, you can build on it. #2 Anchor New Habits to Existing Routines Habits are easier to establish when they’re tied to something you already do regularly. For instance, if you want to foster better communication with your team, make it a habit to ask for feedback during your weekly check-ins. The check-in is already part of your routine; now it has an added layer of intentionality. #3 Focus on Systems, Not Outcomes Instead of obsessing over results, concentrate on creating systems that support your desired behavior. For example, if you want to encourage innovation within your team, implement a habit of dedicating 10 minutes at the end of each meeting for brainstorming new ideas. #4 Track Progress and Celebrate Small Wins While habits don’t rely on external validation like goals do, tracking your progress can still be motivating. Use apps or simple checklists to monitor consistency and celebrate milestones along the way. #5 Be Patient and Consistent Habits take time to form: research suggests anywhere from 21 days to several months depending on the complexity of the behavior. Don’t be discouraged by setbacks. Focus on consistency over perfection. The Ripple Effect of Habits in Leadership When you embrace habits as a leader, the benefits extend far beyond your personal growth: they ripple out to your entire team and organization. Here are some examples: Improved Team Engagement. By modeling habits like regular recognition or transparent communication, you create an environment where team members feel valued and motivated. Greater Innovation. Small habits like encouraging questions or dedicating time for creative thinking can spark breakthroughs that drive your projects forward. Stronger Relationships. Consistent habits like active listening or showing empathy build trust and strengthen connections with both colleagues and stakeholders. Most importantly, focusing on habits helps you lead by example. It shows your team that growth isn’t about chasing lofty goals but about showing up every day with intention and purpose. A Challenge for You! As you reflect on this article, I want to leave you with a simple challenge: choose one habit that aligns with your leadership vision and commit to practicing it consistently for the next 30 days. It could be as simple as starting each day with five minutes of mindfulness or ending each meeting

Czytaj dalej

24 December 2024 No Comments