The management mantra «Don’t come to me with problems—come to me with solutions» is widely repeated as a call for initiative and critical thinking. But according to leadership researchers, the phrase backfires in today’s complex workplace, discouraging employees from speaking up and hiding early warning signs until they become full-blown crises.
The advice inadvertently tells subordinates that problems are unwelcome and that solving them is a solo endeavor. Both messages are wrong in interdependent organizations, where consequential issues almost always cut across functional, geographic, or hierarchical lines. Employees hear that raising concerns makes them look weak, negative, or difficult, and that bad news is not wanted. As a result, they hold back half-formed concerns and delay sharing early signals until problems grow too large to hide.
Former Secretary of State Colin Powell captured the opposite view: «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.» Similarly, Fujio Cho, then Toyota plant manager in Georgetown, Kentucky, and later worldwide chairman, told a subordinate in a senior leadership meeting: «Please talk to us about your problems so we can work on them together.»
The phrase may have made sense in an era of predictable, siloed work where a single expert could both detect and fix issues. But that model is a poor fit for modern systems. Postmortems of major corporate failures—from NASA shuttle disasters to Volkswagen’s Dieselgate and Theranos—repeatedly find that warning signs were present long before failures hit headlines. Employees raised safety concerns, questioned aggressive targets, or flagged vulnerabilities, only to be ignored or discouraged. Months before Equifax’s massive data breach, a security researcher warned the company it was vulnerable to a large-scale attack.
Research across industries shows people routinely stay silent about problems because they fear retaliation, doubt anything will change, or believe their concerns are not welcome. A crisp aphorism about not bringing problems to the boss reinforces that reluctance. It tells people their job is to cope, not to name the underlying issue.
The second flaw is subtler: it misunderstands how problem-solving actually works. Spotting problems is something individuals are good at—a customer service representative hears the same complaint five times in a week, a nurse notices confusing equipment, a junior engineer trips over the same bottleneck in code review. But individuals rarely have all the information, resources, or authority to design and implement a solution alone. Fixing a recurring customer issue may involve product, operations, legal, finance, headquarters, and the field. Improving a safety process requires coordination between frontline staff, supervisors, training, and compliance.
«Come to me with solutions» lands as: unless you can single-handedly architect the cross-functional remedy, keep quiet. That tells the people best positioned to notice emerging issues that their observations are incomplete and therefore unwelcome. Teams then invest energy in work-arounds that not only fail to solve the problem but worsen it over time.
High-performing teams are not defined by the absence of problems; they are defined by the speed and candor with which problems surface. The faster people can make sense of a shared reality, the faster the organization can respond. Leaders who want early warnings and honest feedback should invite problems, not shut them down.