When is it time for a job change?

Self-Development

We often ask ourselves questions like: “is it a good time to end this relationship?”, “is it a good time to start a new one?”, “is it a good time to change my haircut?”, “is it a good time to start saving money?”. “Is it a good time to change my job?” is on that list too. We wonder “what if”.

What if I… had another job?

… had another manager?

… moved to another city/country?

… changed my job entirely and start doing something completely new?

All of those “what ifs” are with us when we think about our perfect lives, perfect jobs or perfect managers. But “perfect” doesn’t exist – there will always be something that destroys the “perfect” view of a job we have. Too much work/too less work, too many people/too few people to do everything, too many restrictions/bureaucracies or no structure at all/total mess.

But when we think about the current situation we are in, we instinctively feel when it’s time to start looking for something new. How to know for sure? Here are some signals you can look for to answer to this important question and make a decision for yourself.

1. “OMG it’s Monday again”

When we live from weekend to weekend it’s like living from paycheck to paycheck. Or from vacation to vacation. Never happy about what it is, always dreaming about a perspective of next thing that should ease our pain somehow. When you are sick to your stomach every Sunday afternoon and at the very beginning of Monday you cannot wait until it’s Friday again, it probably means that you don’t like your job very much. Or your life in overall, it’s another angle to take a look on the situation.

All the gifs, memes and stories that are all over the internet convince us that hating Mondays is normal, all people on the planet has the same thing, right? And those who are happy and can’t wait for the new week are either crazy or workaholics.

Do you know somebody who loves Mondays? Who are they? What do they do? What decisions do they make? Are they crazy?

Source: https://boldomatic.com/p/bZUEfg/i-know-one-person-who-loves-monday

If you hate Mondays, it is the first sign that maybe it’s not about the Monday itself – it’s more about what you do everyday from Monday to Friday. How you spend your weeks? Do you do something that you’re passionate about?

2. I can’t stand people in this company

Sometimes we work in a company that has a high level of maturity. Mature, experienced people, mature organization, leadership, working processes. People don’t waste time on things that don’t matter, they focus on their job and the value that they want and should bring to the table. There are some new people, sometimes young, sometimes students that want to start their career somewhere. But in overall, people understand what we say to them.

And pretty often we work in a mess. Messy environment, processes, structures, communication flow. People are running around in circles, wasting time on things they shouldn’t even think about. They do tasks that are not even theirs.

And when you are a smart person and you work in that kind of environment, you just can’t stand some people. Their never-ending questions, over and over again about the same things. Their lack of independence, taking responsibility for what they do or finding solutions to the problems that occur. And it’s not like you don’t want to help – it’s just exhausting for you to work in that kind of organization.

When you feel that way, it might mean that you need a change of a scenery and a new place. Of course a new firm doesn’t mean that there won’t be questions. It means that you can do a fresh start, with better contracting that will prevent this feeling of frustration to happen again, at least in that scale.

3. Why it’s such a mess?

This one is kind of connected to the previous one.

If you have a strong need for structure, you will die in the organization that is messy. Literally. You’ll be frustrated all the time that you waste all of your energy on things that should be structured by a simple policy for instance.

I wrote about this several times now, but from my experience there is not a not worse things then wasted time. And wasted potential. I am personally attached to this one since I’m a really structured person and a mess in the work environment drives me crazy. I cannot work when I need to waste time on looking for the right piece of information or the right person. Or taking part in meaningless meetings where there is no takeaway, and people just meet because they suppose to be busy or something.

If you have a strong need for structure and the organization that you work within at the moment is super messy, you are on the straight path to the burnout zone. When a basic hunger is not fed, we procrastinate, looking for excuses, not acting our best selves. We self-sabotage a lot, sometimes it’s not even a conscious act, we just do it because of the helplessness of the situation. Especially when we don’t have any, or we have a little influence on what’s happening every day.

4. Why it’s so hard to make a change here?

The most common scenario: the bigger the organization, the harder is to make any change. There are more layers of approvals, more bureaucracy, more complex set of systems where the change needs to go through.

For some of us it’s fine, we are not in a rush, we can wait.

But for some, it’s infuriating. When we see that something isn’t working, and there is a way to change that, we want to act on it and fix the thing. It can be anything: a process, way of communication, product, way of working – you name it. There is always space for improvement, anything can work better. So if you are frustrated that you waste time and there is no way that it can change, that’s another signal for you that maybe this organization is not the place where you’re supposed to be.

5. Nobody sees me

A while ago I wrote an article about hungers. One of three of those is a recognition hunger. The idea about this one is built around a need of being seen, important – as a person, and as an employee. The hunger can be fed by providing recognition signs – they can be positive or negative. Regardless of their type, all people on the planet tend to get any of it, because there is not many things worse than being invisible.

If you are not seen in the organization, what is the difference between the situation where you are there and you are not? When you don’t get any feedback (positive or constructive), you are not recognized for what you do really well, nobody even says “thank you” for your work – it is not a place where you can unleash your full potential.

6. I can’t change anything I do (same task list all over again)

Regarding Transactional Analysis the goal of every human being is to live in autonomy. Autonomy is a combination of an ability to be:

aware of who you are, what you do and when,
spontaneous and make your own decisions,
in a relation with other people to fully live your life.

The decision-making part is strictly connected with your ability to decide on your scope of tasks and responsibilities. Of course when you get the job connected to the certain position, you agree on a certain set of things you are going to cover on a daily basis. But if this is fixed, finite set of tasks, it never changes and you are bored to death, it’s not a good place for your mind and body.

The main question here is: do you have any influence on that? Can you change the current situation, take on new tasks or exchange some tasks with other people in a team? Maybe you can take another part of the job, like being a buddy for new joiners or a mentor?

If yes – great, talk to your manager, see what you can do and do it.

If no – you are on a straight path to the bored or to the burnout zone. Either way, it’s not a space where you want to be – there is no growth, no passion there. Do you really want to spend your life like that?

7. I don’t care

Last but not least – when you just don’t care about the job anymore, it means that it’s time. Sometimes it’s just it – you achieved everything you could’ve in a certain organization, you’ve learned everything what was possible and there is no space for more for you. And that’s okay – like we outgrow from some relationships when we grow up, we can outgrow from the organization as well.

It’s a natural process of change – it can be sad, but it is life.

The bottom line

The goal of this article is not to encourage anybody to quit their job right away. I just wanted to say that it’s important to be aware where we are in our careers, what works and what doesn’t. Based on that we can make better decisions – better not only for ourselves, but also for other people (do you like being surrounded by the burned-out people?) and for the organization too (do you like working in a firm where there are demotivated and whiny people all over the place)?

It is always a tough decision to make a change. But to move on, to grow and to be better every single day, we need to make those uncomfortable actions. We need to have courage. It’s better to be scared about not trying to change something.

Because life is too short to spend it in a job that we don’t even like anymore.

Udostępnij

Komentarze

0 0 votes

Article Rating

1 Komentarz

Oldest

Newest Most Voted

Inline Feedbacks

View all comments

ceek gate.io

1 year ago

I agree with your point of view, your article has given me a lot of help and benefited me a lot. Thanks. Hope you continue to write such excellent articles.

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

8 February 2025 No Comments

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