Why ‘don’t come to me with problems—come to me with solutions’ is bad advice

0 6 minutes read

“Don’t come to me with problems. Come to me with solutions.”

You’ve almost certainly heard this line. You may have even said it yourself. It sounds both tough-minded and empowering. But of all the things managers say with good intentions, this is my least favorite. It inadvertently sends two unhelpful messages: First, that problems aren’t welcome, and second, that solving them is something you should do on your own. Both are exactly wrong in today’s complex, uncertain world.

As a management aphorism, it’s in direct tension with what the best leaders tend to say and do. Colin Powell once said: “Leadership is solving problems. The day soldiers stop bringing you their problems is the day you have stopped leading them. They have either lost confidence that you can help or concluded that you do not care. Either case is a failure of leadership.”

Having spent much of my research career studying why people fail to speak up with their concerns, questions, and even ideas at work, Powell’s words seem refreshingly wise to me. And they remind me of something Fujio Cho, then the Toyota plant manager in Georgetown, Kentucky (and later chairman of Toyota worldwide) said in a senior leadership meeting to a subordinate named Jim Wiseman, as reported in Fast Company years ago: “Please talk to us about your problems so we can work on them together.”

{“blockType”:”mv-promo-block”,”data”:{“imageDesktopUrl”:”https:\/\/images.fastcompany.com\/image\/upload\/f_webp,q_auto,c_fit\/wp-cms-2\/2026\/08\/SHRM-Executive-Council-Amy-Edmondson.png”,”imageMobileUrl”:”https:\/\/images.fastcompany.com\/image\/upload\/f_webp,q_auto,c_fit\/wp-cms-2\/2026\/08\/i-3-91584173-Design-Levain-X-CB-2.jpg”,”eyebrow”:””,”headline”:”Amy Edmondson”,”dek”:”Amy Edmondson thinks about and studies leadership, teams, and organizational learning at Harvard Business School. She\u0027s convinced that failures are essential for learning, innovation and growth. To learn more, find her on \u003Ca href=\u0022https:\/\/urldefense.proofpoint.com\/v2\/url?u=https-3A__www.linkedin.com_in_amycedmondson_\u0026amp;d=DwMGaQ\u0026amp;c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM\u0026amp;r=xHenyQfyc6YcuCNMBsOvfYGQILM1d1ruredVZikn4HE\u0026amp;m=eaUb4Si3nur_3az00AUZVOkk7wIYIzvhT-t3NAOsvwjPFxLTT1ct_dF9N-C4SQGY\u0026amp;s=8rhfWXM1gL0MM-c51iFZ_xO_5s7u7iKCVllq1g0t2Ww\u0026amp;e=\u0022 target=\u0022_blank\u0022 rel=\u0022noreferrer noopener\u0022\u003ELinkedIn\u003C\/a\u003E or visit \u003Ca href=\u0022https:\/\/urldefense.proofpoint.com\/v2\/url?u=https-3A__amycedmondson.com_\u0026amp;d=DwMGaQ\u0026amp;c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM\u0026amp;r=xHenyQfyc6YcuCNMBsOvfYGQILM1d1ruredVZikn4HE\u0026amp;m=eaUb4Si3nur_3az00AUZVOkk7wIYIzvhT-t3NAOsvwjPFxLTT1ct_dF9N-C4SQGY\u0026amp;s=ryDarq9utAKGUSYbOyRG7rc2iNWAejtYozBi0kPZmsI\u0026amp;e=\u0022 target=\u0022_blank\u0022 rel=\u0022noreferrer noopener\u0022\u003Ehttps:\/\/amycedmondson.com\u003C\/a\u003E.”,”subhed”:””,”description”:””,”ctaText”:”Learn More”,”ctaUrl”:”https:\/\/amycedmondson.com”,”theme”:{“bg”:”#2b2d30″,”text”:”#ffffff”,”eyebrow”:”#9aa2aa”,”subhed”:”#ffffff”,”buttonBg”:”#3b3f46″,”buttonHoverBg”:”#3b3f46″,”buttonText”:”#ffffff”},”imageDesktopId”:91584472,”imageMobileId”:91584306,”shareable”:false,”slug”:””,”wpCssClasses”:””}}

Unpacking impact

Let’s start with what “don’t come to me with problems—come to me with solutions” actually conveys to subordinates. Although its intent may be to ask people to take initiative, to think critically about options rather than just dropping problems in the boss’s lap, or to discourage passive complaining, its impact is something else entirely. It is not brilliant solutions. It’s silence. It’s rework. Ultimately, it gives rise to, “How did this get so bad without anyone telling me?”

When people are told, “Don’t come to me with problems,” they hear, “Problems make you look weak, negative, or difficult.” They hear, “I don’t want to hear bad news.” Employees—especially those early in their careers or far from the center of power—are exquisitely attuned to what might get them labeled as a poor performer, or worse, a troublemaker. As a result, they naturally hold back half-formed concerns. They delay sharing early warning signs until the problem has grown so large that it can no longer be hidden.

To be fair, there might have been a time and a context where this admonition made sense. In contexts characterized by relatively high levels of consistency and predictability, and especially when interdependence and complexity were relatively low, problem-detecting and -solving often paired together neatly. Expert work that’s neatly siloed—think of a brilliant diagnostician in a narrow field of medical expertise—also allows this to occur.

We see versions of this pattern in postmortems of crises and major corporate failures. In inquiry after inquiry—from NASA shuttle failures to VW “Dieselgate” and Theranos—investigators discovered that warning signs were present long before failures hit the headlines. Employees may have raised safety concerns, questioned aggressive targets, or flagged vulnerabilities—only to be ignored or discouraged. Months before Equifax’s massive data breach, for example, a security researcher warned the company that it was vulnerable to a large-scale attack.

Research across industries finds that people routinely stay silent about problems because they fear retaliation, doubt anything will change, or simply don’t believe their concerns are welcome. A crisp aphorism about not bringing problems to the boss only reinforces that reluctance. It tells people, in so many words, that their job is to cope, not to name the underlying issue.

Problem-solving in today’s organizations

The second issue with “Don’t come to me with problems” is just as important but less obvious: It misunderstands how problem-solving actually works in modern organizations. Spotting problems is something individuals are good at. The customer service representative hears the same complaint five times in a week. A nurse notices that a piece of equipment is confusing and easy to misuse. A junior engineer keeps tripping over the same bottleneck in the code review process. We are excellent problem-spotters, especially when we’re close to where the work happens.

But individuals rarely have all the information, resources, or authority required to design and implement a solution on their own. In real organizations, consequential problems almost always cut across functional, geographic, or hierarchical lines. Fixing a recurring customer issue might involve product and operations, legal and finance, headquarters and the field. Improving a safety process might require coordination between frontline staff, supervisors, training, and compliance.

In this context, “Come to me with solutions” lands as: “Unless you can single-handedly architect the cross-functional remedy, keep quiet.” It tells the people best positioned to notice emerging issues that their observations are incomplete and therefore unwelcome. That’s how organizations sleepwalk into preventable failures. The lone-hero model of problem-solving is a poor fit for complex, interdependent systems. It encourages a subtler form of waste as well: Teams invest energy in work-arounds that not only don’t solve the problem, but also give rise to dynamics that worsen the problem over time.

High-performing teams are not defined by the absence of problems; they’re defined by the speed and candor with which problems surface. The faster people in an organization can make sense of a shared reality, the faster the organization can respond.

An alternative

What should leaders say instead? I recognize that the phrase captures a legitimate sentiment—a desire for initiative instead of passive complaining. The question is how to cultivate that without shutting down the flow of vital information.

One option is: “Bring problems early, so we can approach them productively.” This shifts the emphasis from expecting ready-made solutions to the important work of understanding the problem as clearly as possible so as to develop possible solutions. Good questions in this conversation might include: What are you seeing? How often? What examples or data points do you have? What makes this concerning? Framing a problem clearly is itself a contribution. The goal is to bring the right people together to ask good questions and generate options.

Another might be: “You don’t have to have the solution, but come ready to think with me.” This preserves the expectation of engagement and ownership. It’s not permission to dump vague discomfort on someone else’s desk but rather an invitation to collaborate.

Relatedly, a powerful reframing is: “Escalating a problem is an act of leadership, not disloyalty.” In many organizations, people worry that surfacing problems will make their team, their unit, or their boss look bad. They stay quiet out of a misguided sense of loyalty. As Netflix cofounder Reed Hastings wrote in his book, No Rules Rules: “It is tantamount to being disloyal to the company if you fail to speak up when you disagree with a colleague or have feedback that could be helpful. After all, you could help the business—but you are choosing not to.”

The same is true for problems. Explicitly reframing problem-raising as a contribution to the collective helps create psychological safety for speaking up. When people know they can raise concerns without having everything figured out, and that they will be expected to participate in the thinking, they’re far more likely to speak up early and energetically. The contrasting cultures that leaders’ approaches to problem-finding create are captured in the table below.

Contrasting cultures

Leadership message	“Don’t bring me problems; bring me solutions”	“Bring problems early; let’s solve them together”
Message people hear	Problems are unwelcome. Bad news is risky and makes you look negative or incompetent.	Problems are information. Early warning signs are valued, and raising them is responsible.
When people will speak up	Only when they’re certain and have a full solution, or when the problem is too big to hide.	As soon as they see a meaningful risk or pattern, even if they’re unsure and the solution is unclear.
Beliefs about problem-solving	Lone hero expected to fix things alone.	Cross-functional and collaborative; a mix of people is needed to design and test solutions.
What gets rewarded	Smooth status reports, few visible problems, heroic last-minute saves.	Early escalation, clear problem-framing, and contributions to team-based solutions.
Performance implications	Silence, surprise crises, recurring failures	Fewer surprises, faster learning, more resilient performance.

Going forward

Words alone are not enough, of course. Leadership is more than simply swapping out slogans. If people bring messy problems forward early and are met with irritation or blame, they will learn the lesson quickly. To make these norms real, leaders must respond to problem-raising with curiosity, appreciation, and a genuine invitation to think together. That is how you teach people that their problems are, in Gen. Powell’s sense, your work.

The impulse behind “Don’t come to me with problems” is understandable. Most leaders don’t want to become complaint departments. But if you want a resilient, innovative organization, you need people to be expert problem-spotters and collaborative problem-solvers.

It’s time to retire that well-worn aphorism. Take Powell’s reminder seriously—when people stop bringing you problems, you have stopped leading them. Saying “Bring me problems early and be ready to think together” is less catchy—but far more effective.

Sarah Walker 49 minutes ago