The Problem With Being the Person Who Always Has the Answer

Image created with AI using ChatGPT

In many organizations, the people who advance into leadership positions are those who have consistently demonstrated an ability to solve problems, make decisions, and provide answers when others are uncertain. Their expertise earns them credibility, and their willingness to step in often becomes one of the qualities for which they are most valued.

But as their responsibilities evolve, the very behaviors that contributed to their success can begin to limit the development of those around them.

I frequently work with leaders who are exceptionally capable, deeply invested in their teams, and genuinely committed to helping others succeed. Yet when someone approaches them with a challenge, their instinct is to offer a solution. They see the problem, recognize a path forward, and provide direction, often before the other person has had an opportunity to fully consider the situation themselves.

In the moment, this approach feels efficient. The problem gets resolved, the employee receives guidance, and everyone moves forward. What is less immediately apparent is the pattern that can develop over time.

When a leader consistently provides the answers, employees may become increasingly reliant on that leader's judgment rather than developing confidence in their own. Questions that could have been resolved independently are escalated, decisions are deferred, and the leader becomes an unnecessary point of dependency within the organization.

Ironically, the same leader may eventually express frustration that their team lacks initiative or struggles to make decisions without them.

The challenge is that developing others requires a different kind of contribution. Rather than demonstrating expertise at every opportunity, effective leaders must become intentional about creating opportunities for others to exercise their own judgment.

This does not mean withholding guidance or allowing employees to struggle unnecessarily. There are certainly situations where experience, urgency, or risk warrants a direct answer. The distinction lies in recognizing when immediate intervention is necessary and when a conversation could serve a more valuable developmental purpose.

Something as simple as asking, "How have you thought about approaching this?" or "What would you recommend?" can shift the responsibility for problem-solving back to the individual. From there, a leader can offer perspective, challenge assumptions, and help refine the proposed approach without taking ownership of the decision entirely.

Over time, these interactions do more than resolve individual challenges. They build confidence, strengthen critical thinking, and establish an expectation that employees should arrive prepared to contribute their own perspective.

For leaders accustomed to being the person everyone turns to, this adjustment can be uncomfortable. It requires patience, a willingness to tolerate approaches that differ from their own, and an understanding that developing capability sometimes takes longer than simply providing the answer.

But leadership effectiveness cannot be measured solely by how many problems a leader can solve personally. It must also be reflected in the organization's ability to function, make sound decisions, and continue progressing without that leader's constant involvement.

Perhaps one of the more important transitions in leadership is recognizing that your value is no longer defined primarily by the answers you provide, but by the judgment and capability you develop in others.

When Feedback Feels Personal: Staying Curious Long Enough to Learn

Feedback is relatively easy to receive when we agree with it. The harder—and often more useful—work begins when someone offers an observation that feels inaccurate, unfair, or inconsistent with how we understand ourselves.

Illustration created with AI

Our natural response in those moments is often to evaluate the feedback before we have really considered it. We explain the context, identify what the other person may not understand, or begin building the case for why their assessment isn’t quite right. Sometimes, of course, it isn’t. Feedback is inherently subjective, and not every observation deserves the same weight.

But feedback does not have to be entirely accurate to contain useful information.

I often encourage leaders to separate intent from impact when they are trying to make sense of difficult feedback. We tend to evaluate our own behavior with the benefit of knowing our intentions, while everyone around us experiences that behavior primarily through its impact. A leader may know that she is thoughtful and collaborative, for example, while others experience her reluctance to speak early in a meeting as a lack of confidence. Another may believe he is being direct and decisive while his team experiences the same behavior as dismissive.

The question, then, is not simply, “Is this feedback true?” A more productive question is, “What might someone be experiencing that caused them to reach this conclusion?”

That subtle shift matters because it replaces defensiveness with curiosity without requiring us to accept every piece of feedback as fact. Ask for examples. Look for patterns rather than isolated comments. Consider whether the perception changes depending on the audience or environment. Most importantly, resist the urge to explain your intention before you fully understand the impact.

This is particularly important as leaders become more senior. Leadership is not only about what we intend to communicate; it is also about our ability to recognize how our behavior is being interpreted by the people around us. Perception should not dictate every decision, but neither can it simply be dismissed because it does not match our own assessment.

The goal of feedback is not to construct a perfectly accurate description of who you are. It is to give you information about how your leadership is being experienced.

You can disagree with some of that information and still learn from it. In fact, sometimes the feedback we are most inclined to reject is precisely the feedback worth examining a little longer.

The Art of the Follow-Up: How to Push Without Being Pushy

Photo by Mariia Berezovsky on Unsplash

In my last post, I wrote about what happens when communication breaks down: decisions stall, priorities become unclear, and small gaps in accountability can eventually create very real operational consequences.

But recognizing the need for clarity is one thing. Asking for it—particularly when you are waiting on a peer, senior leader, or another department—is another.

Many leaders struggle with the follow-up. They don’t want to appear impatient, overstep, or create unnecessary tension. So they wait. Or they send a vague “just checking in” message that is easy to overlook and does little to move the work forward.

There is a better approach.

Effective follow-up is not about applying more pressure. It is about providing more context. Instead of simply asking someone for an answer, explain what depends on that answer. “I need your decision by Wednesday” can feel like a demand. “We need a decision by Wednesday in order to keep production on schedule” communicates the same urgency while also explaining why it matters.

That distinction is important. When people understand the impact of their response—or lack of one—they are better equipped to prioritize. You are no longer asking them to respond simply because you need something. You are giving them information they need to make a decision about the work.

The same principle applies when priorities compete. Rather than repeatedly pushing for your request to move to the top of someone’s list, ask for clarity about where it belongs. “If this needs to move behind the other priorities this week, that’s fine. I just need to understand the timing so we can plan accordingly.”

That is not passive, and it is not aggressive. It is clear.

Strong leaders learn how to create urgency without creating unnecessary friction. They communicate the need, connect it to the broader impact, and give the other person an opportunity to respond or reprioritize.

Sometimes leadership means making the decision. Other times, it means making it easier for someone else to make one.

Either way, the goal is the same: less ambiguity, better alignment, and work that keeps moving forward.

The Hidden Cost of Waiting: When "Polite" Communication Breaks Your Team

Photo by Nathan Dumlao on Unsplash

Most teams don’t fail because people are incapable. More often, communication breaks down—and over time, that breakdown creates confusion, misalignment, and loss.

It rarely happens all at once. Instead, it shows up in small, seemingly reasonable moments: waiting for a response, holding back on a follow-up, assuming someone else will clarify what matters most.

On the surface, this can look like professionalism. Phrases like “I’ll get back to you,” or “Let me check,” signal thoughtfulness and collaboration. But in practice, they can introduce something far more costly: ambiguity.

Ambiguity slows decisions, obscures ownership, and quietly shifts accountability into the space between teams.

I was working with a leader recently whose team was consistently throwing away product. Not because of a lack of capability, but because sales had confirmed demand without fully aligning on timing, storage, or next steps. Operations, in turn, waited for clarification. Sales assumed the details were being managed. No one pushed directly, and no one made the priorities explicit.

The issue wasn’t effort. It was visibility.

This is where many organizations get stuck. There is an unspoken belief that being easy to work with means being flexible, accommodating, and patient. But over time, that interpretation erodes effectiveness. When urgency is not clearly defined, when expectations are implied rather than stated, and when follow-up is softened to preserve comfort, communication begins to fragment. And when communication fragments, performance follows.

Strong teams operate differently. They make priorities visible and are explicit about the implications of delay. They do not rely on assumptions to carry critical work forward. Instead, they communicate in a way that connects timelines, decisions, and outcomes in a shared and consistent way.

This is not about being forceful. It is about being clear.

Clarity is what creates alignment. And alignment is what prevents the quiet breakdowns that organizations often normalize: missed handoffs, duplicated effort, and preventable losses that are absorbed rather than addressed.

If a team feels consistently busy but not effective, or aligned in intent but not in execution, it is worth asking a simple question: where is communication breaking down?

Because the cost of that breakdown is rarely visible in the moment. Over time, however, it becomes embedded in how the organization operates—subtly, consistently, and expensively.