When I was an Individual Contributor, I followed a path many of us know well. In the early days, I sought permission for everything. I looked for constant approval and felt the need to validate every minor decision with my seniors.
Over time, I hit a turning point. I started worrying that my constant questions were becoming a distraction—that I was interrupting the team’s flow or, worse, that it might negatively impact my performance reviews. I decided to change my approach. I began taking the time to debug on my own, growing into my role, and finding my own solutions before speaking up. I took pride in my independence.
Years passed, and naturally, when I moved into leadership, I brought this mental model with me. I would do everything myself as much as possible, rarely seeking help, and I would spend a good amount of time helping others. I didn’t see this as a weakness in anyone; I saw it as a way to collaborate and share my knowledge.
“62% of critical project delays are not caused by technical failures, but by ‘known issues’ that were never communicated until they became crises.” — 2025 State of Engineering Management Report
We Trapped Ourselves
Those were the “good ol’ days” of being a Dev Lead. But eventually, I became an Engineering Manager, and I brought those same principles with me.
I set a clear KPI for my direct reports: “If you need me to step in, it means I have not enabled you properly.”
I thought I was giving them the ultimate gift: total autonomy. “Do as you please!” I wanted them to feel the same pride in ownership and independence that I had felt.
The reality was far more chaotic.
While the team still brought me problems from time to time, this direction created a subconscious barrier. People became terrified of appearing incompetent or “interrupting” the manager who usually remained on the sidelines. Instead of a high-trust environment, I had inadvertently built a culture of concealment.
It took me a long time to see this because, at the end of the day, my people were high performers, and so was I. The concealment was masked by great relationships and frequent 1-on-1s.
However, sometimes small fires—the kind that could have been doused with a five-minute chat—were left to smolder in the dark. I only became involved when the smoke was too thick to ignore. By the time I stepped in, I wasn’t there to mentor or advise; I was there to manage a crisis. I was solving “big messes” that had evolved from simple bugs that a bit of early guidance could have easily fixed.
This optimization for apparent independence was created at the expense of the team’s safety.
To be fair, we were all suffering from Imposter Syndrome. Leads weren’t bringing me their concerns in a timely manner to avoid appearing like they couldn’t handle them, and I believed that those “boots on the ground” were better prepared to manage immediate issues. Not only had I created a problematic target, but I had also stopped leveraging my own experience effectively.
Debunking the Famous Motto
“If you bring me a problem, bring me a solution.”
We’ve all heard it. Many of us have said it. On the surface, this motto has excellent intentions. It aims to foster proactivity and ownership. It’s designed to push people to take the reins of their own work.
And let’s be honest: feeling in control of our work is essential. We spend 8, 9, or 10 hours a day at our desks or home offices. Autonomy isn’t just a “management style”; it’s a requirement for human happiness. When we feel like cogs without agency, mental health issues and burnout aren’t far behind.
But here is where the system breaks.
To understand why, we have to talk about Competence. Brian Tracy defines competence as the ability to get results through the efficient use of your skills and resources. It’s a journey, not a destination.
However, there is a missing link in that definition: Intentionality. As leadership experts often point out, talent is a natural gift, but it only becomes a true asset when combined with the intentionality to apply it correctly. Talent is the potential; Intentionality is the vector.
When we demand a solution from someone who hasn’t yet developed the specific competence to solve that problem, we don’t get proactivity. We get friction.
This “bring me a solution” requirement creates a physical and psychological gap between the leader and the team. It makes conversations harder. Instead of a collaborative “debugging” session, the employee feels they are being tested.
If they don’t have the solution, they don’t bring the problem. The smoke from those “small fires” I mentioned earlier starts to expand. By enforcing this motto blindly, we are recreating the exact same culture of concealment—just with a more professional-sounding excuse.
This doesn’t just apply to problem solving; it bleeds into our daily micro-interactions.
Imagine a report shares an article or a video in a Slack channel. If your immediate response is, “What were your key insights?” or “Can you summarize the takeaways for the team?”, your intention might be genuine curiosity, engagement, to help the person further express themselves. You want to learn from them and enable them to be more valuable.
But the employee often hears something else: “I am being tested. I need to sound smart, right now.”
Suddenly, the simple act of sharing—the lifeblood of a learning culture—feels like a high-stakes exam. When every interaction is perceived as a judgment of competence, people stop sharing, they stop questioning, and the system becomes opaque.
Let’s Make it Safe to Fail
Recent data from Deloitte (2025) shows that 48% of senior leaders are suffering from burnout, citing “the anxiety of managing complex problems without a clear support system” as their primary stressor.
We have built a management culture that prioritizes the appearance of autonomy over the reality of performance. We tell our teams: “Don’t bring me problems, bring me solutions.” We think we are empowering them. In reality, we are creating a dangerous culture of concealment that is burning out leaders and stalling projects.
To fix this, we need to provide Clarity.
Clarity is the antidote to the anxiety and paralysis that “forced autonomy” creates. Instead of the binary wall of “Problem vs. Solution,” a more effective mental model is to categorize tasks based on Situational Competence.
A Senior Engineer might be a Level 3 in technical architecture but a Level 1 when managing a cross-departmental conflict. Competence isn’t a rank; it’s the ability to handle a specific challenge.
By using Dave Ramsey’s framework of the 3 Levels of Initiative, you can calibrate your leadership to meet the person where they actually are:
Level 1: “I will tell you what to do.”
This level is for situations where competence is low or the risk is too high for a “trial and error” approach.
At Level 1, there is a clear, unspoken contract: The leader provides the solution, and the report follows. It isn’t about micromanagement; it’s about safety. If you demand a solution here, you are leaving the person to drown. Instead, you take the wheel, explaining your “why” as you go. You are building their foundation so they can eventually move to the next level.
Level 2: “Bring me two or three options, and we will decide together.”
This is the calibration phase. The person has enough competence to identify the paths, but perhaps not enough context or confidence to choose the right one alone.
Here, your job is to Guide.
You aren’t picking the winner; you are looking at the trade-offs together. This removes the high-stakes of being wrong. By debating the options, you are sharpening their judgment. You are moving from “giving the answer” to “teaching how to find the answer.”
Level 3: “You handle it and keep me posted.”
This is where true ownership lives. At this level, the person has proven competence and understands the intentionality required for the task.
At Level 3, your job is to Trust.
You stay out of the way, but remain accountable. This is the destination, but it only works if you’ve put in the work at Levels 1 and 2 first.
Implementation: The Leader’s Internal Compass
You don’t need to announce a “new framework” to your team or hand out a manual. This is a tool for your internal decision-making.
When a report brings you a problem without a solution, don’t react with frustration. Instead, ask yourself: “Is this person at Level 1, 2, or 3 for this specific task?”
If they are at Level 1, give them the solution and use it as a teaching moment. If they are at Level 2, ask for their perspective.
Success isn’t measured by the absence of problems, but by the transparency and speed of their detection. When you stop demanding premature solutions, you tear down the invisible walls. You stop the forest fires before they start because you’ve made it safe for the smoke to be visible.
Conclusion
Our job as leaders is to design a system where people can grow without burning out.
The next time you hear “Don’t bring me problems, bring me solutions,” remember that you might be looking at a system bug in disguise. Listen to the signal, identify the level of initiative needed, and build the clarity your team—and your own peace of mind—desperately needs.
