Skip to main content
  1. Posts/

Red flags

··1380 words·7 mins·

As I advance in my career, there’s one activity I consistently enjoy: mentoring.

I love helping other people discover their hidden potential and work through obstacles. Mentoring involves lots of listening and asking questions. My mentees ask some great questions as well, and some of them are difficult to answer.

One that I’ve had a lot recently is:

When do I know it’s time to move on from my current project or even my company?

Take a quick look at any news source and you’ll find news about big layoffs and a hot labor market. Moving on from one project to another is one thing, but moving to another company is something different entirely.

This becomes more even complicated in the United States since, for most of us, our health insurance and disability benefits are tied to our current employer. 😰

I’ve answered this question many times for many different people but I never covered it on the blog. This post will explain how I built my system of red flags and I’ll explain some of the red flags that have been useful to me along the way.

Think gradients, not binary values #

I worked for a great leader in a previous job who had a talent for giving very direct feedback that I could put to good use quickly. He introduced me to impostor syndrome, the theory of constraints1, and empathy in a business setting.

Our company was going through quite a few challenges at the time. I asked him about how to know when to stay on a project, dig in, and improve it or when it’s time to go. He sat down with me and explained his system of red flags. 🚩

He suggested making a list of two to three changes within the company that would reduce my faith in the company. These things would sew doubt about company leadership, products, or the approach to the customer experience. He explained that every change should be looked at with full context of the situation and that no single item should cause someone to make a rash decision.

There was one rule he was clear about: You must come up with your list of red flags when you aren’t under duress.

These red flags must be in place before the ship starts to sink. Why? All kinds of cognitive bias set in when you’re under frustrated or frightened. Once the body’s fight or flight system kicks in, all bets are off. It’s difficult to make sound judgments at that point.

I asked him if he could give me one of his red flags as an example. He said he keeps a list of people in the company who he respects and watches for them to change roles or leave the company. Earning his respect at the company meant:

  1. You are committed to quality work
  2. You are committed to the customer experience
  3. You bring your best each day

His list changed over time and usually had five to ten people on the list at any one time. I asked him if he could give me another example and he immediately gave me that look and said:

Only you know what your red flags really are.

My red flags #

Once I explain this concept to someone, they immediately want to know what I use. Here’s a brief overview of what I use.

Great people leave #

I’ve watched incredibly talented people come and go during my career. However, much like my previous leader, I keep a list of five to ten people that I genuinely respect. The people on my list meet my criteria:

  1. You bring your best effort to work consistently
  2. You admit when you don’t know something
  3. You’ve been in a tough spot and doubled down on making an improvement
  4. You take time to help others through tough situations
  5. You realize that success at work means more than writing code or managing infrastructure

When people on my list leave the company, it starts raising red flags.

Am I going to leave because one talented person left? Likely not.

Am I going to leave because half of my list has left the company? Likely not. However, this will make me stop to think about my current situation and evaluate some other red flags.

Reduced belief #

Survival in almost any company requires you to believe that your contributions create value for someone somewhere. You also need a belief that your chance for further opportunities in the company should improve as the product improves.

A previous CEO once talked to us about “wobbles”. A wobble happens when your belief in your leadership and overall company direction is shaken. He argued that these wobbles are totally helpful and we must work to understand them. Simply shutting down a wobble only makes it worse.

This is one of those red flags where you must ask yourself how you could potentially change the outcome.

You might be the catalyst for a movement that changes the way your company thinks about your product and its customers! 🎉

You also might become a pariah for an effort that was doomed before it even started. 😥

This is where a great relationship with your manager comes in handy. If you have a relationship where you can talk about these big ideas and your manager supports you, then you have a good chance of success.

If not, then your best choice might be to walk away.

Degraded quality #

Quality means something different to everyone. When I talk about quality here, I am talking about delivering a high quality product and talking to customers about it honestly. Every product in the world has bugs and shortcomings that everyone wishes were better.

If a product needs to ship with ten features, but only eight are ready, then it might make sense to ship what you have. The key is that you’re honest with customers and say “Okay, we have 80% of what you wanted and we wanted to get it to you now so you can get started sooner.”

That’s not a quality issue. You did your best to hit the deadline, gave customers the largest amount of features you could, and then explained honestly that there’s work left to be done. That’s an honest job and it maintains customer trust.

I look for situations where teams choose to release products without certain pieces and then find ways to hide it from the industry or from customers. An even bigger red flag goes up for me when those teams are confronted about it and they don’t see a problem.

A lack of honesty with customers is a step down a very dark path for any company.

What now? #

Start small! 🤏

Make a list of items, that if they changed, would frustrate you or make you nervous about your job. If it’s something that increases your stress, write it down.

When red flags start to appear, talk to your manager about them as soon as possible!

Don’t let them fester and get worse while you’re silently becoming more and more upset and stressed. Try to bring them up with your manager in the context of your experience with them.

Why focus on experiences? They are unique to you. They cannot be taken away. If someone on your list leaves the company and you are nervous about the future of the company after that, then that’s your experience. Start with something like:

When he/she left the company, I became very nervous about the future of our product and I’m stressed about meeting our deadlines to customers.

Great managers will usually want to know more about your feelings and the impact that person had on the project. It’s entirely possible that your leaders had no idea how integral that person was to the project over time.

I hope you can use this red flag framework as a method for reducing your stress and taking some of the emotion out of your decision to stay or leave. In the end, only you can make that decision. 🫂


  1. This concept seriously changed my career. If you’d like to learn more, your first stop should be to read The Phoenix Project. Want to dig deeper? Read The Goal for a much more detailed and manufacturing-centric approach. ↩︎