Why ‘Don’t Bring Me Problems, Bring Me Solutions’ Is Bad Leadership

141
10

It's a bit of a modern management cliché to say, “Don't bring problems! Bring me solutions!”

I think what it's meant to mean is, “Don't just complain! Think about improving things!”

It often means, sadly, “Be quiet and stop being a troublemaker!”

It's good to think about improvement, but sometimes (if not often!) that improvement process starts by identifying problems.

In a “Kaizen” process in a team, I encourage people to bring problems forward even if they do NOT have a solution or “countermeasure” in mind. When someone points out a problem, it can prompt discussion or brainstorming (with the manager and colleagues) about potential solutions to test.


Hear Mark read this post (Subscribe to the podcast):


Here's an article from Harvard Business Review that delves into this same topic:

Don't Bring Me Problems–Bring Me Solutions!”

The interview with Professor Frances X. Frei starts like this:

CBD: I thought that encouraging employees to solve problems was a good thing–?

FF: It is, of course. But sending out this message doesn't do it. Instead of promoting accountability, it actually encourages employees to turn a blind eye to problems they see but cannot figure out how to fix. When you say “Don't bring me problems–bring me solutions,” what you're saying, in effect, is “Of all the problems you find, I only want to know about the ones you can solve.”

I'd add that even when people have solutions in mind, we have to be careful that we're not jumping to solutions. Making sure we define (and understand) the problem first is a very helpful and necessary first step.

Frei adds:

Identifying problems can be a solo sport, but finding solutions rarely is. This is especially true when the problems have any degree of complexity. If you're giving people permission to tell you about just those problems they can solve, you're missing out on many opportunities for improvement. You're leaving performance boosters on the table simply because the problem and the solution aren't collocated.

Frei also says, “that managers use [the phrase] to quiet chronic complainers.” Does this make it “dangerous” for people to speak up and point out problems? We need to make it safe for people to talk about problems to create an environment where improvement can happen. She, not surprisingly, points to Toyota as an example of a company that has a healthy improvement culture.

At the heart of this discussion isn't semantics or debating a catchy phrase. It's about psychological safety. When leaders say, “Don't bring me problems–bring me solutions,” people quickly learn that it's safer to stay quiet than to speak up. Problems don't disappear in those environments; they just go underground.

If we want real continuous improvement, we need people to surface problems early, openly, and without fear of blame. That requires leaders who respond with curiosity instead of judgment and who see problems as information–not personal failures. In Lean terms, problems are signals that help us understand the system better.

Toyota and other learning organizations understand this well. They don't expect individuals to solve complex problems on their own before speaking up. Instead, leaders create space for dialogue, shared problem-solving, and experimentation. Identifying problems can be done by one person, but improving systems is almost always a team sport.

If you want people to think, learn, and improve, make it clear–through your words and your reactions–that bringing problems is not only acceptable, it's expected. Psychological safety isn't a “nice to have.” It's a precondition for improvement.

Read the rest of the interview. I'd be happy to hear your thoughts or any reflections on this expression and what it means to your team and your organization.


If you’re working to build a culture where people feel safe to speak up, solve problems, and improve every day, I’d be glad to help. Let’s talk about how to strengthen Psychological Safety and Continuous Improvement in your organization.

Get New Posts Sent To You

Select list(s):
Previous articleScheduling Time for Breaks, Lunch, and Kaizen
Next articleVideo: The Culture is Staff Input; Info About a Class on Kaizen at Franciscan St. Francis Health
Mark Graban
Mark Graban is an internationally-recognized consultant, author, and professional speaker, and podcaster with experience in healthcare, manufacturing, and startups. Mark's latest book is The Mistakes That Make Us: Cultivating a Culture of Learning and Innovation, a recipient of the Shingo Publication Award. He is also the author of Measures of Success: React Less, Lead Better, Improve More, Lean Hospitals and Healthcare Kaizen, and the anthology Practicing Lean, previous Shingo recipients. Mark is also a Senior Advisor to the technology company KaiNexus.

10 COMMENTS

  1. The approach I used with my kids back in the day was more like “what’s your plan to do something about it” rather than having them bring a specific solution. I did it to keep them from whining about something without thinking through how to deal with the situation. In some cases, I would help them through the analysis of the problem; in others, they worked out solutions on their own. At work, I’ve used a similar approach and used it as a teaching moment, frequently with the use of a new tool they hadn’t used before.

  2. Great comment from LinkedIn:

    From Ladislav Zastresek:

    To cite Colin Powell “The day the soldiers stop bringing you their problems is the day you stopped leading them. They have either lost confidence that you can help them or concluded that you do not care. Either case is a failure of leadership.

  3. In the offices we have a saying that for every patient that complains, there are 10 more that say nothing and just transfer to another practice. When you discourage or ignore the voicing of problems that may not have an obvious solution, those problems may indeed go away… but not in the way you want them to.

  4. I like this Mark and I agree – the phrase “don’t bring me problems, bring me solutions” has become yet another vacuous management ejaculation that sounds impressive but is completely stupid.

    I don’t understand why we treat problem identification as a negative activity. In fact, it is one of the most useful skills in business. Illustrating a situation for the benefit of others is exactly how an environment in which solutions can be found is created.

    A better phrase might be “I see what you mean. What ideas do you have for how this situation can be resolved?” Usually, the problem-bringer WILL have some idea of what the solution might be. A good manager would validate and appreciate their identification of the problem and then encourage them to contribute their ideas as to the solution.

    Hope a few of these buzz-phrase toting management types read your blog, Mark!

    • Great comment, John. I think the negativity about problems maybe comes from people being BLAMED for those problems. Therefore, problems are a bad thing because I suffer when I’m blamed. So, it’s better to ignore the problems or actively cover them up.

      But, when problems are just fact — a realistic understanding of what reality is — we can work together without blame to actually solve the problem. Then, things get better, nobody loses, problems are a positive thing.

      “We need to hold people accountable” is another example of a vacuous phrase that sounds good — but it’s blaming and it’s harmful.

  5. I completely agree, Mark. Platitudes like, “Don’t bring me problems. Bring me solutions” may look great on a mug. But, they do nothing to encourage employee engagement or creativity.

    On the contrary, they often have the effect of scaring employees to death. Employees are afraid that if they bring up a problem without a solution they will be blamed for causing it. It’s a no-win situation for them. If they bring up a problem without a solution, they may get punished. If they don’t bring up a problem or delay bringing up a problem and the problem escalates, they may get punished. The only safe course of action is to never bring up a problem you can’t solve and to cover your tracks lest anyone find out you have identified a problem and are keeping quiet about it.

    It reminds me of a former coworker who was going through the motions, but she was really hiding work in her desk. I’m not sure why she behaved that way. But, I wouldn’t be surprised if part of the reason had to do with getting confused at some point or making a mistake and being afraid to ask for help or admit fault.

    Scared employees go into “fight-flight” mode where all they can do is survive. Fear shuts down executive reasoning, which is needed for creativity and innovation. Ironically, scaring employees with ultimatums about solutions may prevent them from exercising the very type of critical thinking that is necessary to come up with the solutions you are demanding.

    Psst. Scaring employees never ends well. Pass it on.

LEAVE A REPLY

Please enter your comment!
Please enter your name here