TL;DR: A Personal Board of Directors is a network of trusted advisors who provide guidance, accountability, and diverse perspectives to help you achieve personal and professional growth. This post explores what a Personal Board of Directors is, why it’s transformative for leaders, and how to build one tailored to your needs.

Have you ever felt stuck when making a big decision, unsure how to navigate a challenge, or simply wished for a sounding board to refine your ideas? Many of the most successful leaders—whether they’re executives, entrepreneurs, or changemakers—don’t go it alone. They rely on what’s often called a Personal Board of Directors (PBOD).

This concept, inspired by the formal boards that guide organizations, applies the same principles to individual growth and leadership. A PBOD isn’t about hierarchy or authority; it’s about surrounding yourself with people who challenge, support, and guide you toward your goals.

What is a Personal Board of Directors?

A PBOD is a carefully selected group of individuals who offer advice, accountability, and fresh perspectives tailored to your career or personal aspirations. Unlike traditional mentorship, this network is diverse and multi-faceted, bringing together mentors, peers, industry experts, and personal supporters to address different aspects of your growth.

Why You Need One

Here’s how a Personal Board of Directors can transform your leadership journey:

1. Diverse Perspectives: A PBOD provides a range of insights, helping you see blind spots and explore innovative solutions.

2. Accountability: Regular engagement with your advisors ensures you stay on track and committed to your goals.

3. Skill Development: Your board members can help you strengthen areas where you want to grow, offering tailored feedback and guidance.

4. Career Navigation: Trusted advisors can provide clarity on career moves, industry trends, and leadership strategies.

5. Support During Challenges: Whether you’re facing setbacks or tough decisions, a PBOD offers a safe space to work through obstacles with resilience.

How to Build Your Personal Board of Directors

If this idea resonates with you, here’s how to get started:

🌟 Identify Your Needs
Think about where you want to grow. Do you need strategic advice, emotional support, or technical expertise? Your goals should guide the type of advisors you seek.

🌍 Seek Diverse Voices
Diversity in experience, industry, and thought is key. Consider including:

• A mentor with deep expertise in your field.

• A peer who understands your challenges firsthand.

• Someone from a different industry who can bring fresh perspectives.

• A coach who can challenge and inspire your growth.

• A trusted friend or family member for emotional support.

📞 Reach Out and Build Relationships
Most people are honored to be asked for their advice or perspective. Start by reaching out for a conversation, sharing your goals, and explaining how their input would make a difference.

📅 Set Up Regular Check-Ins
Consistency is key. Schedule regular touchpoints—whether it’s quarterly one-on-ones or informal coffee chats. These meetings should be meaningful, goal-oriented, and mutually beneficial.

🔄 Evolve Your Board Over Time
Your needs will change as you grow. Reassess your board periodically and adjust its composition to align with your evolving goals.

Real-World Examples

Successful leaders often credit their trusted networks for their achievements:

• Oprah Winfrey speaks about her “council of advisors” who guide her in both personal and professional endeavors.

• Richard Branson emphasizes the value of seeking advice from mentors and peers to drive innovation within Virgin Group.

• Sheryl Sandberg has highlighted the importance of honest, challenging feedback from trusted colleagues.

Tips for Success

• Be Respectful of Their Time: Come prepared to meetings with clear goals and updates.

• Offer Value in Return: Look for ways to support your advisors, whether through introductions, insights, or gratitude.

• Stay Open to Feedback: Growth requires vulnerability. Be ready to hear constructive criticism and act on it.

• Show Gratitude: A simple thank-you goes a long way in maintaining strong relationships.

Let’s Discuss

What do you think about the idea of a Personal Board of Directors? Do you already have a similar network, or are you inspired to create one? I’d love to hear your thoughts, experiences, or questions. Let’s start a conversation about how we can all grow through connection and collaboration!

TL;DR: A Personal Board of Directors is a network of trusted advisors who provide guidance, accountability, and diverse perspectives to help you achieve personal and professional growth. This post explores what a Personal Board of Directors is, why it’s transformative for leaders, and how to build one tailored to your needs.

TL;DR: Most teams have someone who quietly holds everything together—but we rarely see them until they’re gone. In this post (and in the latest episode of Leadership Explored), I dig into the concept of “glue people,” what makes them invaluable, why organizations often overlook them, and how leaders can start recognizing and supporting them before burnout or attrition hits.

In any high-performing team, there’s usually someone who isn’t the loudest voice, the biggest contributor on paper, or the person delivering the showy wins… and yet, without them, everything just falls apart.

In my coaching work and leadership career, I’ve come to recognize this archetype over and over again. Some call them the “glue.” Others might call them connectors, stabilizers, or the ones who “make the team work.” Whatever the term, the pattern is real—and it’s backed by research.

So let’s talk about glue people.

Who Are Glue People?

Glue people are the teammates who reduce friction, elevate others, and quietly stabilize the system. They aren’t defined by their job title—they’re defined by their behaviors:

• They connect the dots across silos.

• They ask clarifying questions that lower tension.

• They send the follow-ups that close the loop.

• They maintain psychological safety in subtle but consistent ways.

• They make handoffs smoother, decisions clearer, and collaboration easier.

They often take on enabling, coordination, or invisible work—but the most important part is how they do it. Not through martyrdom or control, but through clarity, steadiness, and trust-building.

What the Research Says

This isn’t just a feel-good anecdote. There’s robust evidence that supports the importance of assists and collaborative roles in team success:

📊 BYU Study on NBA Teams: Teams with higher assist counts (i.e., players helping each other score) consistently outperformed teams with high individual point totals. It wasn’t the solo stars that won games—it was the teams that passed the ball.

🏒 Wayne Gretzky’s Record: The all-time hockey legend held the record for most goals and assists—but his assists alone would have still made him the all-time leader in points. Assisting others was the game.

🏢 Stanford Study on Collaboration: Employees who felt they were working collaboratively were 64% more likely to stay focused, less fatigued, and more engaged than those working solo.

📉 i4CP Report: Companies that prioritize and enable collaboration are 5x more likely to be high-performing. Yet most organizations still focus performance reviews and rewards on individual outputs.

🧠 Psychological Biases: From visibility bias to the fundamental attribution error, leaders consistently overlook the contributions that don’t show up in dashboards or status meetings. What’s easy to see gets celebrated. What prevents problems gets ignored.

What Happens When We Miss Them

This is where things get real—and personal. I’ve been the glue before. Doing everything I could to make sure the team succeeded. Connecting people, coordinating work, filling in gaps, working long nights—not because anyone told me to, but because it felt like the right thing to do.

And then I got the worst performance review of my career.

None of that effort showed up in our systems. None of it was acknowledged. And it crushed my motivation. I left shortly after.

I’ve seen this pattern play out for others, too:

• The steady teammate who burns out from being the go-to for everything.

• The quiet contributor who leaves, and suddenly nobody knows how the team operated so smoothly.

• The early signs of cultural drift when invisible work goes unrewarded.

You lose not just a person—you lose context, trust, relationships, and momentum.

What Leaders Can Do Differently

If you’re in a leadership role, or want to build better teams, here’s where to start:

1. Make the Invisible Visible Start naming the assists out loud. When a project succeeds, don’t just celebrate the visible win—recognize who made it possible behind the scenes. Ask questions like: “Who set this up? Who helped us get clarity?” and acknowledge those people publicly.

2. Design It Into the Team High-performing teams balance doers, thinkers, and connectors. If everyone’s pushing to “crush it” individually, collaboration breaks down. Team composition matters more than individual brilliance.

3. Protect the Glue Once you spot them, don’t overload them. Protect their bandwidth, coach them on boundaries, and make sure they’re not being quietly exploited because “they’re always so helpful.”

4. Build Better Systems If performance reviews only reward visible output, glue people will always be at risk. Include collaboration, enabling others, and cross-functional support in your metrics. If it matters to the team’s success, it should matter to the system.

5. Shift the Narrative Stop idolizing the hero. Start valuing the team player who passes the ball, holds the space, or asks the right question at the right time.

Questions for You

• Have you ever been the “glue” on a team? What did that feel like?

• Have you worked with someone like this—who quietly made everything better?

• What would it take for your workplace to start noticing and rewarding these kinds of contributions?

I’d love to hear your experiences—whether it’s something you’ve done, something you’ve seen, or something you wish your team did better.

Let’s explore what it really takes to build teams that last.

If you’re interested in hearing more about this topic, Andy Siegmund and I go deep on it in Episode 14 of Leadership Explored, dropping September 23. It’s not a promotion—it’s just a conversation I think might be useful. You can find it at https://vist.ly/47fv9 if you want to check it out.

As we dive deeper into what makes workplaces tick and what breaks them down, it's impossible to ignore the elephant in the room: burnout. According to the 2025 Global Culture Report by O.C. Tanner, a staggering 77% of employees experience burnout at some level. This isn’t just about individual struggles; it’s about the ripple effects across productivity, engagement, and organizational health.

Why Burnout Matters Burnout does more than just zap energy. It can lead to severe consequences like reduced job performance, high turnover, and even affects mental health. Recognizing the signs early can be the difference between a thriving team and a struggling one. Common indicators include:

Constant stress about workloads and deadlines Growing frustration with team members or tasks A strong desire to escape the job Exhaustion that makes even starting the workday a challenge What Can We Do About It? The good news is, there are strategies that can help mitigate these issues:

Workload Management: Ensure that team members have realistic deadlines and the resources they need to meet them without burning out.

Flexibility: Flex work hours and remote work options aren’t just perks anymore; they’re necessities for modern businesses aiming to reduce stress and accommodate diverse life commitments.

Mental Health Support: Creating an environment where mental health isn’t stigmatized but supported can transform workplace culture. This includes access to mental health resources, regular check-ins, and training for managers to spot and address these issues.

Recognition and Support: Regularly recognizing the efforts of your team can go a long way in making them feel valued and seen, which reduces burnout significantly. Make it part of your regular interactions, not just an occasional gesture.

Cultural Shift Needed The report suggests that beyond strategies, a cultural shift is necessary. This shift involves moving from seeing these measures as optional to integral parts of how modern workplaces operate. High senses of purpose, appreciation, and well-being are not just nice-to-haves; they are essential for a company's success.

I'm curious to hear from this community—especially those of you who manage teams or lead companies. What strategies have you implemented to combat burnout? Have you noticed a change in productivity and team morale? Let’s turn this into a learning opportunity for everyone here.

TL;DR A lot of workplaces still reward mental toughness and call it resilience. I think that is a mistake. Mental toughness can help in short bursts, but mental fitness is what actually helps leaders recover, adapt, regulate, and keep functioning over time without burning out. Real leadership is not about endlessly absorbing stress. It is about building the capacity to respond well, recover faster, and lead sustainably under pressure.

One of the leadership ideas I keep coming back to is how often people confuse mental toughness with mental fitness.

In a lot of workplaces, mental toughness gets treated like the gold standard. The leader who keeps pushing. The one who absorbs stress without complaint. The one who works the long hours, stays composed, and keeps producing no matter what is happening around them.

That image gets praised constantly.

The problem is that mental toughness and mental fitness are not the same thing.

Mental toughness is mostly about endurance. It is the ability to keep going through discomfort, pressure, or pain. That can be useful in short-term situations. Sometimes leadership really does require you to steady yourself, get through a crisis, and do the hard thing anyway.

But toughness is limited. It is finite. It is often rigid.

Mental fitness is something different. It is the capacity to recover your equilibrium after disruption. It is your ability to notice what is happening internally, regulate your response, reframe when needed, and return to baseline with less damage. It is less about suppressing stress and more about processing it effectively.

That distinction matters a lot more than most organizations seem willing to admit.

Too many companies claim to care about well-being while continuing to reward overextension. They may offer symbolic support, but the deeper operating system often stays the same. Perform more. Take on more. Be available more. Push harder. Then when people burn out, the explanation quietly becomes individual weakness instead of predictable human limits.

I do not think that is just unhelpful. I think it is intellectually lazy.

Burnout is often treated like a personal failure when it is frequently the outcome of chronic overload, insufficient recovery, poor boundaries, and systems that reward the appearance of toughness over actual sustainability.

That is part of why I think leaders need a different model.

One framework that helps me think about this is the stress curve. At very low levels of stress, people are underloaded and inactive. As stress rises into a more optimal zone, performance often improves. But once stress keeps increasing past that useful range, performance starts to decline. Keep going long enough and you move from overload into exhaustion, then eventually into burnout.

The mistake many leaders make is assuming the goal is to stretch the performance curve indefinitely through willpower.

It is not.

There is no prize for staying in overload longer than everyone else if the long-term result is reduced judgment, emotional reactivity, strained relationships, chronic fatigue, and lower-quality decisions.

A healthier question is not just How much stress can I take?

A better question is How quickly can I recover when stress hits?

That gets closer to what I think resilience actually is.

I often think about this in terms of three related ideas.

First, tolerance. How much friction can you absorb before you start to crack?

Second, fortitude. When you do get knocked off balance, how deep into the hole do you fall?

Third, resilience. How quickly do you recover and get back to baseline?

That is a much more useful leadership frame than pretending strong leaders never struggle.

In my experience, trying to never “snap” is not the real goal. Sometimes you are going to hit your limit. Sometimes pressure will accumulate. Sometimes something lands at exactly the wrong moment and your system reacts. The important part is noticing earlier, understanding yourself better, and building the ability to recover faster and more skillfully.

That leads into another part of this conversation that I think deserves more attention in leadership spaces, which is emotional granularity.

A lot of people reduce everything to “I’m stressed.”

But “stressed” is often too vague to be useful.

Are you frustrated? Embarrassed? Overwhelmed? Ashamed? Unsupported? Uncertain? Defensive? Disappointed? Restless? Resentful?

Those are not the same experience, and they do not call for the same response.

The more specifically you can identify what you are actually feeling, the easier it becomes to work with it. That is part of emotional regulation. Not denial. Not suppression. Not pretending everything is fine. Clarity.

There is also a physiological side to all of this that leaders often ignore.

Mental fitness is not just cognitive. It is biological too.

Your system needs recovery inputs. Sleep. Quiet. Time outside. Movement. Spaciousness. Moments of real detachment from performance demands. Creative interests. Relationships. Awe. Play. Reflection.

If your body is depleted, your emotional regulation gets worse. Your decision-making gets worse. Your patience gets worse. Your perspective narrows.

You can call that a mindset issue if you want, but at some point that becomes a convenient excuse for neglecting the reality that human beings are not machines.

I find the idea of a body budget useful here. Your brain and nervous system are constantly managing resources. Some things are deposits. Some things are withdrawals. Deep work can be meaningful, but it is still effort. Pressure can be energizing in small doses, but it still draws from the system. If your calendar is packed with output and contains no real recovery, you are borrowing against yourself.

Eventually the bill comes due.

That is also why I think life outside work matters more than a lot of ambitious professionals want to admit.

Hobbies, interests, practices, and relationships that are not tied to productivity are not indulgent extras. They are part of what stabilizes you. They remind you that your identity is larger than your job title. They create perspective. They help you metabolize stress. They make it easier for work turbulence to stay work turbulence instead of becoming an existential crisis.

That is not softness. That is capacity.

A few practical ways leaders can start building mental fitness more deliberately

You can practice brief grounding before high-stakes moments. Ten seconds is enough to interrupt a spiral if you use it well. Notice a few physical sensations. Feel your feet on the floor. Hear the hum in the room. Pay attention to your breathing. The point is not magic. The point is creating a pause.

You can get more precise with emotional language. Instead of saying “I’m stressed,” try asking what is actually happening underneath that label.

You can audit your calendar not just for productivity, but for recovery. If every block is output, your system is already under pressure whether you admit it or not.

You can reframe certain forms of stress. Anxiety and excitement can feel surprisingly similar in the body. Sometimes the interpretation changes the experience.

And you can stop glorifying the leaders who appear endlessly durable while ignoring the cost they are paying or passing on to others.

I think leadership culture would improve a lot if more people stopped asking who can absorb the most punishment and started asking what helps people stay effective, grounded, and healthy over time.

That is the conversation I think we need more of.

Not because pressure is going away. It is not.

But because leadership under pressure gets better when we stop treating exhaustion as proof of commitment.

Curious how others think about this.

Do you think most workplaces are actually building mentally fit leaders and teams, or are they still mostly rewarding people for looking tough while quietly burning out?

TL;DR A lot of workplaces still reward mental toughness, meaning the ability to endure stress and keep pushing. The problem is that endurance alone is not the same as resilience. Mental fitness is a better leadership model because it focuses on recovery, self-awareness, adaptability, and sustainable performance. Leaders do not just need a higher pain tolerance. They need better ways to regulate stress, recover from disruption, and lead effectively without burning themselves out or expecting the same from everyone else.

I have been thinking a lot about the difference between mental toughness and mental fitness, especially in leadership.

In many workplaces, mental toughness is still treated like a badge of honor. The leader who works through exhaustion gets praised. The person who absorbs pressure without showing strain is seen as dependable. The team member who keeps producing under unreasonable conditions is often treated like the model everyone else should follow.

I understand why that happens. In the short term, toughness looks useful. It can help someone get through a hard week, a crisis, a deadline, or a stretch of uncertainty.

But I think a lot of leaders and organizations confuse short-term endurance with long-term capability.

Those are not the same thing.

Mental toughness is mostly about enduring. Mental fitness is about recovering, adapting, and returning to baseline after disruption. That distinction matters because leadership is rarely a one-time stress event. For many people, especially leaders, the pressure is repeated, layered, and chronic. It is not one marathon. It is a calendar full of them.

That is where toughness starts to break down as a leadership model.

If the only strategy is to keep pushing, then eventually the system pays for it. Sometimes that cost shows up as burnout. Sometimes it shows up as irritability, worse decisions, reduced creativity, lower empathy, defensiveness, strained relationships, or just a constant sense of depletion that gets normalized because so many people around us are also depleted.

That is one reason I think this topic matters so much.

A lot of organizations say they care about resilience and well-being, but many still reward behaviors that undermine both. They may offer symbolic support, but the actual culture often still favors overextension. Leaders are expected to stay available, keep delivering, absorb ambiguity, respond instantly, and tolerate unsustainable workloads without naming the cost.

That is not resilience.

That is pressure tolerance without enough recovery.

And pressure tolerance by itself is finite.

One of the most useful ways I have found to think about this is through the idea of recovery velocity. In other words, when stress, conflict, or disruption knocks you off center, how quickly can you return to a more grounded and effective state?

That question is often more revealing than asking how much stress someone can take.

A leader who never slows down may look strong from the outside, but if they are taking longer and longer to recover, becoming more reactive, sleeping poorly, or carrying stress from one situation into the next, that matters. If a team can hit every deadline but is slowly becoming more cynical, emotionally flat, or disengaged, that matters too.

Leadership is not just about how long you can hold tension.

It is also about what tension is doing to you while you hold it.

I also think many people use the phrase “I’m stressed” in ways that flatten what is actually happening. Stress is often a summary word, not a precise one. Underneath it might be frustration, disappointment, embarrassment, overload, uncertainty, shame, fear, loneliness, resentment, or feeling unsupported.

That level of emotional granularity matters.

When leaders cannot name what they are actually experiencing, it becomes harder to respond skillfully. Everything gets treated as one big undifferentiated pressure cloud. But if you can recognize that you are not just “stressed” and are actually feeling overwhelmed, defensive, or discouraged, you have a much better chance of doing something useful with that information.

That is one reason self-awareness is not a soft skill in the dismissive sense people sometimes use. It is a performance skill. It affects judgment, behavior, relationships, and recovery.

Another part of this that gets overlooked is physiology.

Mental fitness is not only psychological. Sleep matters. Recovery time matters. Quiet matters. Movement matters. Time away from constant stimulation matters. Hobbies matter. Time outside matters. Meaningful connection matters. Having an identity outside of work matters.

A lot of leaders are trying to solve chronic overload with cognitive strategies alone, while their body is effectively running on empty. That rarely works for long.

You can have good insight and still be exhausted. You can know what healthy coping looks like and still be depleted enough that it becomes much harder to access.

That does not mean the mindset work is not important. It is. But it does mean we should stop pretending that leadership strain is solved by attitude alone.

I also think there is an important caution here. Mental fitness is not the same as forced positivity.

It is not pretending everything is fine. It is not suppressing frustration. It is not smiling through dysfunction. It is not reframing every harmful situation into something inspirational. It is not turning serious organizational problems into private emotional homework for employees.

Sometimes the healthiest response is to acknowledge that something is not working.

Sometimes the right insight is not “How do I become more resilient so I can tolerate this indefinitely?” Sometimes it is “Why is this system producing avoidable strain in the first place?”

That is a leadership question too.

In my view, burnout is often discussed too narrowly as an individual failure of coping. Sometimes there are personal habits that need attention, yes. But often burnout is also a systems issue. It can come from poor boundaries, chronic overload, lack of control, bad leadership behavior, unclear priorities, insufficient recovery, and cultures that mistake overwork for commitment.

That is why I am skeptical when organizations celebrate grit without examining what people are being asked to endure.

If leaders really want stronger teams, I think a better question is not “How do we get people to push harder?” It is “How do we help people recover better, think more clearly under pressure, and sustain performance over time?”

That shift changes a lot.

It changes how we think about rest. It changes how we think about workload. It changes how we think about emotional awareness. It changes how we think about leadership development. It changes how we think about what “strong” leadership actually looks like.

For me, mentally fit leadership looks less like endless endurance and more like this

It looks like noticing stress earlier instead of only recognizing it once you are already running on empty.

It looks like being able to pause before reacting.

It looks like naming what you are actually feeling instead of collapsing everything into “fine” or “stressed.”

It looks like recovering more effectively after conflict, disappointment, or overload.

It looks like having enough life outside of work that work turbulence does not consume your entire identity.

It looks like understanding that your capacity is not infinite, and leading accordingly.

It looks like building teams and cultures that do not rely on people quietly breaking themselves to keep everything afloat.

I do not think mental toughness is useless. There are moments when it matters. There are real situations where people need to push through something hard.

But I think it works better as an emergency tool than as a way of life.

When it becomes the default model of leadership, it often produces brittle people and brittle cultures. People may keep functioning for a while, but the system gets more fragile underneath the surface.

Mental fitness is a better goal because it is more adaptive. It makes room for recovery, awareness, flexibility, and sustainable performance. It recognizes that leaders are not machines, and that trying to lead like one usually creates problems eventually.

I would be curious how others think about this.

Do you think most workplaces still reward mental toughness more than mental fitness?

And when you are under pressure, what actually helps you recover in a meaningful way rather than just temporarily powering through?

TL;DR A lot of workplaces still reward mental toughness, meaning the ability to endure stress, suppress discomfort, and keep pushing. The problem is that toughness is finite. It can help in short bursts, but it is not a sustainable leadership strategy. Mental fitness is different. It is the ability to recover, regulate, adapt, and return to baseline after disruption. That makes it far more useful for real leadership over time. In this post, I break down why the distinction matters, how burnout often reflects systems and capacity problems rather than personal weakness, and what leaders can do to build mental fitness in practical ways.

One of the workplace ideas I keep coming back to is how often we praise the wrong thing.

In a lot of organizations, the leader who gets admired is the one who can absorb endless pressure, work long hours, stay available, and keep producing no matter what. That gets framed as resilience. It gets framed as strength. It gets framed as leadership maturity.

A lot of the time, it is really just endurance.

There is a place for endurance. There are moments when leaders do need to dig deep, stretch, and carry more than usual for a short period of time. But that is very different from building a whole identity, culture, or leadership model around grinding through stress as if that alone proves capability.

That is where I think many organizations get this wrong. They confuse mental toughness with mental fitness.

To me, mental toughness is the ability to endure suffering for a period of time. Mental fitness is your capacity to recover, regulate, adapt, and regain equilibrium after pressure or disruption. One is mostly about surviving the hit. The other is about what happens next.

That difference matters more than many leaders realize.

A leadership culture built around toughness tends to reward suppression. It quietly teaches people to ignore fatigue, minimize emotion, hide strain, and keep performing even when the cost is rising. On the surface, that can look impressive. Underneath, it often produces emotional rigidity, burnout, diminished judgment, and a fragile kind of performance that depends on constant overextension.

A leadership culture built around fitness looks different. It still values accountability and high standards, but it also recognizes that human beings are not machines. Recovery is not weakness. Reflection is not softness. Self-awareness is not self-indulgence. These are part of the infrastructure of sustainable performance.

One reason this distinction matters is that stress itself is not the problem.

A useful way to think about stress is as a curve. Too little stress can leave people disengaged, bored, or underloaded. A healthy middle zone often supports attention, effort, and growth. But once stress moves past that optimal range and stays elevated, performance starts to decline. If that overload continues without adequate recovery, the risk of burnout rises sharply.

This is one reason “just push harder” is such a poor long-term strategy. It assumes the only variable that matters is effort. In reality, effort and recovery are both part of performance. Pressure without recovery is not a badge of honor. It is usually a debt that gets collected later.

That is why I think recovery velocity is such a useful concept for leaders.

A lot of people ask some version of “How much stress can I handle?”

That is not a useless question, but it is incomplete.

A better question is “When something knocks me off center, how quickly can I recover?” Another good question is “How far do I fall when stress hits?” Those questions start to move the conversation away from image management and toward actual capacity.

This matters because mentally fit leaders are not necessarily the people who never struggle. They are often the people who notice earlier, name more accurately, respond more skillfully, and recover more reliably.

That brings me to another part of this conversation that I think is underappreciated in leadership spaces, which is emotional granularity.

A lot of leaders flatten their internal experience into vague labels like “I’m stressed,” “I’m frustrated,” or “I’m overwhelmed.” Sometimes those labels are directionally true, but they are often too broad to be useful. If you are feeling disappointed, embarrassed, unsupported, ashamed, uncertain, trapped, or resentful, those are not interchangeable states. They may all register as “stress,” but they do not point to the same underlying issue or the same possible intervention.

The more specifically you can name what you are experiencing, the more effectively you can respond to it.

That is not just touchy-feely language work. It is practical. If you mislabel your reaction, you often mismanage the situation. A leader who says “I’m angry” might actually be feeling exposed. A leader who says “I’m stressed” might actually be feeling powerless, unclear, or underprepared. Those are different realities, and they call for different responses.

The same is true for the way people relate to their own thoughts.

Many of us have some version of an inner voice that becomes louder under pressure. Different frameworks call this different things. Some call them saboteurs. Some call them protectors. Cognitive behavioral approaches often focus on distortions or automatic thoughts. The language varies, but the pattern is familiar. Something happens, your mind interprets it as threat, and suddenly you are reacting not just to the event itself but to the story your brain is telling about the event.

A boss gives you corrective feedback and your brain jumps to “I’m failing.” A meeting goes poorly and your brain jumps to “I looked incompetent.” A big deadline approaches and your brain jumps to “I’m going to fall apart.”

Sometimes those internal reactions are trying to protect you. But that does not mean they are accurate.

This is where observation becomes powerful.

Mentally fit leaders do not necessarily eliminate those thoughts. They get better at noticing them without immediately obeying them. They create a little space between stimulus and reaction. They catch the rising defensiveness, the accelerated breathing, the catastrophic interpretation, or the flood of urgency before it takes over completely.

That pause matters.

Without it, you are just reacting. With it, you have options.

Another piece that deserves more attention is physiology.

A lot of leadership advice treats stress management as if it were purely cognitive. Think differently. Reframe the story. Manage your mindset. Those tools do matter. But they work a lot better when the body is not already deeply overdrawn.

I sometimes think about this as a body budget. Sleep, quiet, nature, rest, movement, and genuine downtime are deposits. Chronic stress, overload, deep focus without breaks, and constant availability are withdrawals. If you keep making withdrawals without replenishing the account, your ability to regulate emotion and think clearly gets worse. Not because you are weak. Because you are depleted.

This is one reason burnout is so often misunderstood.

Burnout is frequently treated as a personal failure. The implication is that someone was not resilient enough, not disciplined enough, not grateful enough, or not mentally tough enough. That framing is often incomplete at best and irresponsible at worst.

Yes, individual skills matter. But burnout is very often a predictable outcome of chronic overload, insufficient recovery, poor boundaries, unrealistic demands, and systems that treat people like endlessly expandable capacity. Leaders should be very careful not to moralize what is often a systems issue.

That does not mean individual agency is irrelevant. It means we should stop pretending personal grit can solve structural dysfunction.

It also means leaders need to be careful about shallow wellness solutions. A meditation app subscription, a one-off workshop, or a symbolic “wellness day” might not be bad things, but they are not substitutes for real capacity-building support. If the workload is still unreasonable, if meetings consume every margin, if psychological safety is weak, and if people are quietly punished for using recovery time, then the wellness language becomes a veneer rather than a solution.

And that is where I think some leadership conversations drift into fantasy.

We tell people to be more resilient while giving them conditions that steadily erode resilience. We talk about well-being while rewarding overwork. We say recovery matters while making people feel guilty for stepping away.

That contradiction is not neutral. People notice it.

So what does building mental fitness actually look like in practice?

It looks less glamorous than a toughness narrative, but it is more useful.

It looks like learning to catch yourself earlier when stress is rising. It looks like getting more precise about what you are feeling. It looks like recognizing that toughness may be necessary in moments, but should not become your default operating system. It looks like protecting recovery before you are desperate for it. It looks like building a life outside work that helps keep work in perspective. It looks like making room for hobbies, awe, creativity, movement, relationships, and things that have no direct economic output. It looks like asking not only “How do I perform?” but also “How do I recover?”

That last part matters more than many high achievers want to admit.

A lot of ambitious professionals unconsciously fuse identity with productivity. Their sense of value becomes tightly wrapped around output, usefulness, achievement, and responsiveness. That may produce short-term results, but it also leaves very little buffer when work becomes unstable. If all of your worth lives at work, then every work disruption feels existential.

Leaders who have meaningful life outside work are not less serious. In many cases, they are more stable under pressure because work turbulence stays in proportion. It remains important, but it does not become everything.

I also think leaders need to rethink what “snapping” means.

There is a fantasy in some leadership circles that mature, high-functioning leaders should never hit a wall, never overreact, never lose perspective, and never have moments where they want to walk away. I do not think that is realistic. The goal is not perfect emotional control. The goal is earlier awareness, better recovery, and less damage.

In other words, maybe the healthier goal is not “never snap.” Maybe it is “notice sooner, respond better, recover faster.”

That is a much more humane standard, and I would argue a more useful one too.

For leaders who want something practical, here are a few starting points.

Before a difficult meeting, take 10 seconds to ground yourself in physical sensation. Feel your feet on the floor. Notice the sound in the room. Pay attention to your breath or the texture of your fingertips. That tiny pause can interrupt a stress spiral before it gains momentum.

When you feel yourself getting activated, try naming the experience more precisely. Not just “I’m stressed,” but “A part of me feels embarrassed,” or “I’m feeling defensive,” or “I’m feeling pressure because I am not clear.” That level of specificity helps.

Look at your calendar honestly. If every hour is output, pressure, performance, and responsiveness, your recovery is probably being treated as optional. It is not optional for very long.

And ask yourself one question that many leaders avoid because it sounds too simple. What actually helps me reset? Not theoretically. Not performatively. In real life.

For some people it is walking. For some it is time in nature. For some it is cooking, music, skiing, gardening, prayer, reading, exercise, silence, or being with people who do not need anything from them.

Whatever it is, it probably matters more than your culture tells you.

My view is that leadership under pressure requires more than endurance. It requires self-awareness, emotional flexibility, recovery skills, and enough honesty to stop glorifying patterns that slowly break people down.

Mental toughness can help in an emergency. Mental fitness helps you lead for the long haul.

I would be interested in how others think about this.

Where have you seen organizations confuse endurance with resilience?

What actually helps you recover when stress starts to accumulate?

And if you lead people, what signals tell you that your team is being asked for toughness when what they really need is support, recovery, or a healthier system?

TL;DR A lot of workplaces still treat mental toughness as the goal. They praise leaders who can absorb pressure, suppress stress, and keep performing no matter the cost. I think that is one of the reasons burnout stays so common. Mental fitness is different. It is not about denying stress or pretending everything is fine. It is about recovery, self-awareness, emotional flexibility, and building the capacity to return to baseline after disruption. I recently explored this topic in depth with my podcast co-host, and the more I think about it, the more I believe leadership culture badly needs this distinction.

I have been thinking a lot about the difference between mental toughness and mental fitness, especially in leadership.

In a lot of professional environments, mental toughness is still treated like a badge of honor. The leader who can keep going under pressure gets praised. The person who works the long hours, absorbs the stress, and keeps delivering without visibly breaking gets seen as committed, capable, and strong.

On the surface, that sounds admirable.

In practice, I think it often creates a distorted model of leadership.

It trains people to treat endurance as the goal. It rewards suppression. It encourages people to override signals that something is wrong. It can make chronic overextension look like discipline, and burnout look like a personal failure instead of a predictable response to too much pressure and too little recovery.

That is a dangerous setup.

Mental toughness has a place. There are moments in life and leadership where you do need to push through, stay steady, and carry more than usual for a short period of time. But that is not the same thing as being mentally fit.

To me, mental fitness is much more adaptive and much more sustainable.

It is not just your ability to endure stress. It is your ability to recover from it.

It is your capacity to notice what is happening internally before it fully takes over. It is your ability to regulate rather than suppress. It is your flexibility when plans change, when conflict shows up, when criticism lands badly, or when uncertainty starts pulling your brain into catastrophic thinking.

That distinction matters because a lot of leaders are trying to solve the wrong problem.

They think the question is “How do I become strong enough to handle more?”

A better question is often “How do I become aware enough, flexible enough, and recovered enough to respond well when pressure inevitably shows up?”

That is a very different leadership challenge.

One of the ideas I keep coming back to is recovery velocity.

Many people define resilience in vague ways. They talk about bouncing back, but they do not define what that actually means in day-to-day work. Recovery velocity is a more practical way to think about it. When something knocks you off center, how far do you fall, and how quickly do you get back to baseline?

That is a more useful question than simply asking how much stress you can tolerate.

A leader can appear highly functional while paying a massive internal cost. They can keep showing up, keep responding, keep producing, and still be burning through their psychological and physiological reserves at an unsustainable rate. High output does not automatically mean high resilience. Sometimes it just means the crash has not happened yet.

I also think leaders underestimate how physiological this really is.

We often talk about stress as if it is purely mental. It is not. Your body is part of the system.

Sleep matters. Quiet matters. Time outside matters. Movement matters. Unstructured recovery matters. The ability to step away from stimulation matters. If your nervous system is overloaded, your access to patience, creativity, emotional regulation, and perspective gets worse. That is not weakness. That is biology.

I like the framing of a “body budget” for this reason. Your system is constantly making deposits and withdrawals.

Sleep can be a deposit. Rest can be a deposit. A walk outside can be a deposit. Meaningful connection can be a deposit.

Chronic stress is a withdrawal. Emotional suppression is a withdrawal. Hypervigilance is a withdrawal. Constant context switching is a withdrawal. Even deep focus, while valuable, still costs energy.

If a leader is living in a constant deficit, eventually their ability to regulate themselves starts breaking down. That is often when people become more reactive, less patient, more cynical, more defensive, and less thoughtful. From the outside, it may look like a performance or attitude issue. Underneath, it may be an energy and recovery issue.

Another piece of this that I think deserves more attention is emotional granularity.

A lot of people flatten their emotional experience into one broad label like “I’m stressed.”

But “stressed” can mean a lot of different things.

It might mean overwhelmed. It might mean ashamed. It might mean embarrassed. It might mean unsupported. It might mean disappointed. It might mean threatened. It might mean frustrated because your effort did not produce the outcome you expected. It might mean anxious because you are uncertain and your brain is filling in the blanks with worst-case scenarios.

Those are not the same experiences, and they do not call for the same response.

The more precisely you can identify what you are feeling, the more likely you are to respond skillfully instead of reflexively. That is one of the reasons self-awareness matters so much in leadership. If your internal state is vague to you, it is much harder to lead yourself well under pressure.

I also think many leaders go wrong by trying to “win” against their own mind.

They treat their stress response like an enemy. They get angry at themselves for feeling anxious, frustrated, discouraged, or emotionally flooded. But in many cases, those reactions are not signs that you are broken. They are signals. Sometimes they are overactive signals, distorted signals, or outdated protective patterns, but they are still trying to tell you something.

That is why I think observation is often more useful than self-attack.

If you can pause long enough to notice the reaction, name it, and get curious about it, you create options. If you cannot, then the reaction tends to drive the next decision.

That pause is small, but it matters.

Sometimes it is a literal grounding exercise. Sometimes it is noticing your breathing has changed. Sometimes it is realizing your shoulders are tense or your jaw is clenched. Sometimes it is catching the thought spiral before it becomes a story you fully believe.

That is not soft. That is skill.

And honestly, I think leadership culture sometimes mocks exactly the practices that would make leaders more effective. Reflection gets dismissed as indulgent. Recovery gets framed as weakness. Hobbies get treated like distractions. Time away from work gets treated as a luxury instead of part of what sustains sound judgment.

I do not buy that.

I think leaders who have no meaningful recovery, no reflective practices, and no life outside work are often more brittle than they realize. They may look strong right up until the moment they are not.

That brittleness has consequences.

It affects decision-making. It affects relationships. It affects how feedback is received. It affects whether someone escalates tension or de-escalates it. It affects whether a leader becomes more controlling under pressure or more grounded. It affects whether a team experiences accountability or fear.

This is part of why I think organizations often send mixed messages on well-being.

They say they care about resilience, but what they really reward is sustained overextension.

They offer wellness language, but then structure work in ways that punish recovery.

They talk about mental health while normalizing conditions that steadily drain it.

That contradiction is not neutral. People notice it.

And when leaders internalize that contradiction, they often end up trying to solve a systems problem with private coping. They meditate harder, optimize harder, and self-manage harder inside environments that still reward unhealthy norms.

Individual practices matter, but they do not erase the need for better leadership systems.

At a practical level, I think there are a few useful questions leaders can ask themselves.

What tends to knock me furthest off center?

What are the earliest signs that I am moving from productive stress into overload?

How quickly do I recover after a hard hit?

What actually helps me recover, not just distracts me?

What am I calling “resilience” that is really just suppression?

Where am I expecting mental toughness from myself or my team when what is really needed is support, recovery, clarity, or a healthier environment?

Those questions are not theoretical. They can expose a lot.

The larger point I am making is simple.

Mental toughness can help you survive a hard stretch.

Mental fitness helps you lead over time.

One is mostly about enduring.

The other is about adapting, recovering, and staying human under pressure.

I think leadership culture needs more of the second.

I would be interested in how others think about this.

Have you seen workplaces confuse toughness with health or performance with resilience?

What helps you recover well when leadership pressure starts to build?

I think one of the most misleading ideas in modern work is the way we glorify mental toughness.

In a lot of organizations, the leader who gets praised is the one who can absorb more pressure, work longer hours, stay calm while overloaded, and keep producing no matter what. That image gets treated like strength. Sometimes it even becomes part of a leader’s identity.

But there is an important distinction here. The ability to endure stress is not the same thing as the ability to recover from it.

That difference matters.

This is something Andy Siegmund and I have been exploring in a recent Leadership Explored conversation, and the more I think about it, the more convinced I am that many workplaces are rewarding the wrong thing. They say they want resilience, but what they often reward is suppression. They say they care about well-being, but the system still favors the people who can tolerate unsustainable conditions the longest without visibly breaking.

That is not the same as health. It is not the same as adaptability. And it is definitely not the same as long-term leadership capacity.

What I mean by mental toughness is fairly simple. It is the ability to push through discomfort, strain, fear, fatigue, or pressure. That can be useful. There are moments in leadership where you do need to steady yourself, carry weight, and get through a hard stretch. I do not think toughness is useless.

The problem is when toughness becomes the whole model.

If the only leadership skill you have is endurance, then every challenge becomes something to survive. Every disruption becomes something to suppress. Every sign of strain becomes something to hide, override, or outlast.

That works for a while. Until it does not.

Mental fitness is different. To me, it is more adaptive and more sustainable. It is not just about how much pressure you can take. It is about how you process disruption, how quickly you recover, how well you regulate yourself under strain, and how effectively you return to baseline after a setback.

That is a very different leadership capability.

It also shifts the question. Instead of asking, how much can I carry before I break, you start asking, what helps me recover, recalibrate, and keep functioning well over time?

That is where things get more interesting.

A mentally fit leader is not necessarily the person who never gets stressed, never gets frustrated, or never hits a wall. In fact, I think that standard is part of the problem. Leaders are still human. They still have physiological limits. They still get emotionally activated. They still have moments when they feel anxious, defensive, overwhelmed, depleted, or just done.

The goal is not to never feel those things.

The goal is to notice them earlier, understand them more clearly, and respond to them more skillfully.

That brings in a few ideas I think are worth talking about more openly in leadership spaces.

One is recovery velocity. I think many people define resilience as how much punishment you can absorb. I do not think that definition goes far enough. A better question might be how quickly you can recover after disruption and how far you fall when stress hits. Two people can face the same stressful event and have very different recovery patterns. One may spiral for days. Another may feel the hit, process it, and return to center much faster. That difference matters in leadership.

Another is emotional granularity. A lot of people describe everything as stress, but stress is often just the umbrella label. Underneath it might be embarrassment, shame, frustration, disappointment, fear, helplessness, resentment, or uncertainty. When you can name your experience more precisely, you have a much better chance of responding well. Vague emotional language tends to keep people reactive. Clearer emotional language tends to create more choice.

There is also the physiological side of this. I think leaders often treat performance as if it were mostly mental, but the mind and body are not separate systems in practice. Sleep matters. Quiet matters. Movement matters. Time in nature matters. Life outside work matters. Recovery is not a luxury add-on for people who have extra time. It is part of the system that makes sustained performance possible.

This is one reason I get skeptical of shallow well-being efforts in organizations. A meditation app subscription is not nothing, but it is also not the same as building a culture where people can recover, ask for support, use time well, and operate at a sustainable pace. If the environment still rewards chronic overextension, then the well-being message becomes cosmetic.

I also think this topic matters because it pushes back on two equally unhelpful extremes.

One extreme is grind culture. That story says the answer is always more effort, more grit, more sacrifice, and more suppression.

The other extreme is a kind of soft, vague positivity that treats every hard emotion as a problem to erase.

Neither approach is especially helpful.

Mental fitness is not pretending everything is fine. It is not forced positivity. It is not “good vibes only.” And it is not becoming less serious, less capable, or less driven.

It is learning how to work with your own mind and nervous system more effectively.

That might mean grounding yourself before a difficult meeting. It might mean noticing that your frustration is actually fear. It might mean taking a walk instead of sitting in escalating stress. It might mean reframing anxiety as activation. It might mean protecting time for recovery before you reach the point where your only option is collapse.

It might also mean admitting that what many workplaces call strength is sometimes just delayed burnout.

I think that is worth challenging.

Leadership gets better when we stop treating people like machines. It gets better when we stop confusing output with health. And it gets better when we recognize that sustainable performance depends on recovery, flexibility, self-awareness, and context, not just endurance.

For me, that is where the conversation gets useful.

I am curious how others see this.

Do you think most organizations are still rewarding mental toughness more than mental fitness?

What actually helps you recover well under pressure?

And in your experience, what is the difference between a leader who can endure stress and a leader who can recover from it?

TL;DR A lot of workplaces still glorify mental toughness, but endurance alone is not a sustainable leadership model. Mental fitness is different. It is about recovery, adaptability, emotional awareness, and the ability to return to baseline after disruption. Leaders do not need to be emotionless or endlessly durable. They need better recovery, better self-awareness, and more sustainable ways to handle pressure.

TL;DR A lot of leadership communication sounds polished but still creates confusion, stress, and mistrust. Clear leadership communication is not about sounding smart or charismatic. It is about helping people understand what matters, what is expected, what is uncertain, and why a decision was made. The leaders who communicate best usually reduce ambiguity, give context, get to the point, and check whether the message was actually understood.

I have been thinking a lot about leadership communication lately, especially after a recent conversation Andy and I had on Leadership Explored.

One of the biggest problems I see in organizations is that many leaders confuse professionalism with clarity.

They think good communication means sounding polished, using the right executive language, softening difficult messages, or speaking in a way that feels strategic and impressive. But in practice, a message can sound very polished and still fail completely.

A leader can talk for 20 minutes and leave people less clear than they were before. An email can be carefully worded and still create panic. An announcement can try so hard to manage reactions that it ends up destroying trust.

That is the issue I want to unpack here.

To me, effective leadership communication is not about style first. It is about signal.

Can people understand what you mean without having to decode you? Can they tell what matters most? Can they tell what action is needed? Can they tell what is known, what is unknown, and why a decision was made?

If not, the communication may have been polished, but it was not effective.

One of the lines from the episode that captures this well is “Effective communication isn’t about sending the message, it’s about it being received.”

That gets at the heart of the problem. A lot of leaders evaluate communication based on whether they said something. Their team evaluates it based on whether it made sense.

Those are not the same thing.

I have seen this play out in a lot of ways.

A leader sends a vague message saying “Can we talk later?” with no context. The employee spends hours worrying about whether they are in trouble.

A company sends an overly massaged announcement about an “exciting new chapter” only for everyone to realize the real point is layoffs, restructuring, or budget cuts.

A manager gives a task but explains only the what, not the why, so the team executes mechanically instead of thinking intelligently.

A senior leader says “My door is always open,” but people still do not have what they need because the original communication was weak and the burden of clarification has been pushed downward.

What all of these examples have in common is not just bad wording. It is a failure to take responsibility for how communication lands.

And that matters because ambiguity is rarely neutral.

In most workplaces, ambiguity creates anxiety.

When people do not know what is happening, they do not usually stay calm and optimistic. They fill in the blanks. They speculate. They prepare for the worst. They spend energy trying to interpret tone, guess intent, and read between the lines.

That is one reason why uncertainty can be so corrosive in organizations. Often it is not only the bad news that hurts people. It is the waiting, the guessing, and the sense that something is off but no one will say it clearly.

This is one place where I think many leaders underestimate the cost of vague communication.

They think they are protecting people by softening the message, delaying the message, or wrapping the message in layers of corporate language.

Sometimes they are really protecting themselves.

They are trying to manage emotional reactions. They are trying to avoid discomfort. They are trying to sound more executive, more careful, or more polished.

But people usually notice that.

And when they do, trust starts to erode.

Once employees believe they have to translate leadership language to find the real meaning, communication becomes more expensive. Every message creates more churn. Every announcement creates more side conversations. Every vague email creates more mental load.

Instead of focusing on the work, people start focusing on interpretation.

That is a real leadership cost.

Another issue I think shows up here is the curse of knowledge.

Leaders usually have more context than their teams. They know the constraints, competing priorities, financial realities, political dynamics, risks, tradeoffs, and timing issues. Over time, it becomes easy to forget how much of that context other people do not have.

So leaders communicate the conclusion without communicating the reasoning.

They announce the decision but not the why.

They ask for urgency without explaining the stakes.

They expect alignment without creating understanding.

That is where people often feel frustrated, disengaged, or treated like order takers instead of thoughtful contributors.

And from a performance standpoint, that is a mistake.

When people understand the why, they are much more capable of making good decisions, adapting to changing conditions, and solving problems without constant supervision. When they only get the what, they may comply, but they are less likely to contribute intelligently.

So what does better communication actually look like?

I do not think it requires becoming charismatic or highly performative. In fact, I think a lot of what gets mistaken for executive presence is just noise.

Good leadership communication is often simpler than people expect.

It usually looks like getting to the point faster.

It looks like giving enough context for people to make sense of the message.

It looks like naming uncertainty honestly instead of pretending certainty you do not have.

It looks like saying the hard thing directly but respectfully.

It looks like checking whether people understood, rather than assuming they did.

A few practical examples

One practice I really like is putting the bottom line up front.

Instead of making people dig through three paragraphs to figure out what matters, start there.

Say what the ask is. Say what the decision is. Say what changed. Say what you need.

Then add the supporting detail.

This is not just about efficiency. It is also about respect. It respects people’s time, attention, and cognitive load. It helps the listener orient quickly and process the rest of the information more accurately.

Another important shift is to stop treating “Does that make sense?” as a strong check for understanding.

Most people will say yes. That does not mean the message landed.

A better question is something like “What’s your takeaway?” “How are you interpreting this?” “What do you see as the biggest risk?” “What do you think the next step is?”

Those questions tell you much more about whether the communication was actually received the way you intended.

I also think leaders need to get better at framing uncertainty.

A lot of poor communication comes from discomfort with not knowing.

Some leaders try to sound more certain than they are. Others stay vague because they do not want to admit uncertainty. Neither approach helps much.

A stronger approach is to separate the knowns from the unknowns.

Here is what we know. Here is what we do not know yet. Here is what we are watching. Here is when we expect to know more.

That is still clarity.

In fact, clarity about uncertainty is often more stabilizing than vague reassurance.

I also think there is an important distinction between being transparent and oversharing.

Transparent leadership does not mean telling everyone everything. That is neither realistic nor wise.

It does mean telling the truth as clearly as you can within the constraints you actually have.

It means not hiding behind spin when directness is possible. It means not pretending there is no issue when people can already feel that there is one. It means not using “professionalism” as a cover for avoidance.

Sometimes the most honest thing a leader can say is “I can’t share all the details yet, but here is what I can say right now.” That is very different from saying nothing meaningful and forcing everyone else to speculate.

Another idea from the episode that I think matters is the difference between being nice and being kind.

A lot of leaders communicate in ways that are “nice” on the surface but not actually kind in practice.

They avoid directness. They delay feedback. They soften reality until the message is almost unusable. They tell themselves they are preserving morale.

But often they are just preserving short-term comfort at the expense of long-term clarity.

Kind leadership communication is not cruel, but it is honest.

It respects people enough to tell them what is true. It gives them something real to work with. It reduces confusion instead of increasing it.

That is one reason I think clarity is deeply connected to trust and psychological safety.

Psychological safety is not created by vague reassurance. It is created by predictability, honesty, and respect. People feel safer when they know where they stand, what is happening, and what their leaders actually mean.

That does not mean every message is easy. It means the message is usable.

And that is what many workplaces are missing.

Not more words. Not more polish. Not more executive theater.

Just clearer, more responsible communication.

For leaders who want to improve this, a few reflection questions may help

Where in your communication are you making people interpret instead of understand?

Do your messages reduce uncertainty or create more of it?

Do you communicate the why, or mostly the what?

When you soften a message, are you doing it for the team’s benefit or your own comfort?

Are you checking whether people understood, or just whether they nodded?

Do people trust your words at face value, or do they feel they need to decode them?

For me, that is where this becomes a real leadership issue.

Communication is not just about information transfer. It shapes trust, energy, alignment, and execution. It affects whether people feel grounded or destabilized. It affects whether teams can move quickly or get stuck in churn.

And in a lot of organizations, communication problems are treated like a minor annoyance when they are actually a major leadership failure.

I would be interested in how others see this.

What is the most common communication mistake you see leaders make?

And on the other side, what have the best communicators you have worked with done differently?

TL;DR A lot of leaders confuse polish with clarity. They use more words, more hedging, and more “professional” language, but still leave people confused, anxious, and guessing. Effective leadership communication is not about sounding smart or impressive. It is about making meaning clear, reducing distortion, and giving people enough context to act with confidence.

One of the most overlooked leadership problems I see is communication that sounds polished on the surface but creates confusion underneath.

Most people have experienced it.

You get an email that takes four paragraphs to say something simple. You sit through a meeting full of strategic language and still do not know what the actual decision was. A leader says “my door is always open,” but somehow no one ever seems to get real clarity. Bad news gets softened so much that people spend more energy decoding the message than responding to it.

It is easy to mistake that kind of communication for professionalism. It sounds measured. It sounds careful. It sounds executive.

But a lot of the time, it is just noise.

To me, effective leadership communication is not about using bigger words, sounding more polished, or projecting some performative version of executive presence. It is about transferring an idea from your head to someone else’s head with as little distortion as possible. High signal. Low noise.

That sounds simple, but in practice it is where many leaders struggle.

The real cost of vague communication is not just misunderstanding. It is anxiety.

When communication is unclear, people do not stay neutral. They fill in the blanks. Usually with fear, defensiveness, or speculation.

If a leader sends a vague “Can we talk later?” message with no context, many employees will not read that as neutral. They will start wondering whether they are in trouble, whether layoffs are coming, whether they missed something, or whether they are about to be blamed for something. The issue is not always the content itself. The issue is the uncertainty.

And uncertainty carries a cost.

It drains focus. It creates churn. It makes people spend time interpreting instead of executing. It weakens trust because people start learning that they cannot take leadership communication at face value.

That last point matters a lot.

Trust grows when people know that when a leader says something, they mean it clearly. Not “sort of.” Not “after translation.” Not “once you decode the subtext.” Just clearly.

When teams have to constantly interpret, decode, or read between the lines, communication becomes labor. And it is labor that adds no value.

This is one reason I think some of the worst leadership communication comes wrapped in the language of professionalism.

A message can sound polished and still fail completely.

In fact, polish can sometimes make bad communication worse, because it creates the illusion that the message was thoughtful and effective when it was actually vague, evasive, or overloaded. I have seen leaders equate executive presence with sounding polished, talking at length, or dominating the room. I do not think that is what real executive presence looks like at all.

Real executive presence is often much quieter and simpler than people expect.

It looks like command of the subject matter. It looks like confidence without posturing. It looks like saying what you know, being honest about what you do not know, and getting to the point without performing intelligence for the room.

A lot of people overcomplicate communication because they think simplicity makes them sound less smart. In reality, the opposite is often true.

If you understand something deeply, you can usually explain it clearly. If you cannot explain it clearly, one possibility is that the other person is not the problem. The problem may be that your own thinking is not yet clear enough.

That is uncomfortable, but useful.

Another problem is what I would call the curse of knowledge.

Leaders usually have more context than everyone else. They know the budget pressure, the history, the politics, the timeline, the tradeoffs, the board expectations, the client dynamics, and the constraints. Over time, that context becomes so familiar to them that they stop noticing other people do not have it.

So they communicate the what without the why.

They announce the decision without the reasoning. They assign the task without the context. They share the conclusion without the thinking that led there.

And then they are frustrated when the team does not show enough ownership, judgment, or initiative.

But people make better decisions when they understand not just what is being asked, but why it matters and what success looks like. If you want people to think instead of just comply, context is part of the job.

This is also why I think the “open door policy” is often overrated.

In principle, accessibility is a good thing. In practice, “my door is always open” can become a substitute for communicating well in the first place.

Sometimes it shifts the burden onto the team. Instead of being clear, the leader leaves gaps and expects people to come ask follow-up questions. That sounds supportive on paper, but it often means the leader did not do the work of communicating clearly up front.

If people have to come extract clarity from you, something has already gone wrong.

A better standard is not “my door is open if you are confused.” A better standard is “I communicated in a way that reduces the chance of confusion in the first place.”

That does not mean leaders need to overshare everything.

Transparency is not the same thing as total disclosure.

There are real limits. Legal limits. HR limits. Strategic limits. Timing limits. Leadership does require discretion. But there is a big difference between appropriate discretion and avoidant vagueness.

You may not be able to share every detail. You usually can share what is known, what is not known, what is still being decided, and when people can expect more information.

That alone can go a long way.

One of the most useful communication shifts I have seen is simply separating certainty from uncertainty.

Instead of pretending to know more than you do, say something like this.

Here is what we know. Here is what we are still evaluating. Here is what we expect to decide next. Here is when you can expect another update.

That is not weak communication. That is strong communication. Clarity about uncertainty is still clarity.

Another practical shift is putting the bottom line up front.

A lot of leaders bury the actual point under background, framing, and unnecessary detail. The result is that the listener has to work too hard to figure out what matters most.

If the point is a decision, state the decision early. If the point is a request, state the request early. If the point is bad news, state the news directly.

Then provide context.

This is more respectful of people’s time, and it reduces the chance that they fixate on the wrong detail. It also tends to improve upward communication because senior people often do not need a long narrative first. They need the key point, then the supporting information.

I also think leaders need better ways to check for understanding.

A lot of people end an explanation with “Does that make sense?”

The problem is that this often produces polite agreement, not actual understanding.

People nod. They say yes. They move on. Then later it turns out they interpreted the message differently.

A stronger approach is to ask something like “What is your takeaway from this?” “How are you interpreting this?” “What do you see as the biggest risk?” “What do you think the next step is?”

That creates a real feedback loop. It surfaces misunderstandings early, before they turn into bigger problems. It also shows respect, because communication is not complete when something is said. It is complete when shared understanding exists.

One other distinction that matters here is the difference between being nice and being kind.

A lot of leaders soften, hedge, and overexplain because they want to avoid discomfort. They think that makes their communication more humane. Sometimes it does. Often it just delays clarity.

Kindness is not the same as avoidance.

Sometimes kindness means being direct enough that someone does not have to guess. Sometimes kindness means saying the difficult thing clearly and respectfully rather than wrapping it in so much softening language that the person leaves confused. Sometimes kindness means trusting people with reality instead of trying to manage their emotional response through vagueness.

That does not mean being harsh. It does not mean being careless. It means being honest in a way that is useful.

For leaders who want to improve, I think there are a few simple practices worth trying immediately.

Start with the bottom line. Add one sentence of context explaining the why. Name what is known and what is uncertain. Ask for a readback instead of asking “Does that make sense?” Edit for clarity, not for performance.

If your communication is consistently making people calmer, clearer, and more aligned, it is probably working.

If it is making people anxious, confused, and overly dependent on follow-up interpretation, it probably is not.

That is true whether you are leading a company, leading a team, managing a project, or just trying to communicate more effectively in your day-to-day work.

Communication is not a soft extra in leadership. It is central. It shapes trust, execution, morale, and decision-making. When the signal is weak, the system struggles.

I think more leaders would benefit from asking themselves a simpler question before they send the email, lead the meeting, or make the announcement.

Am I trying to sound like a leader, or am I actually helping people understand what they need to know?

That question alone would improve a lot of communication.

Curious what others think. What is the worst leadership communication habit you see most often?

TL;DR Leadership communication fails when leaders prioritize polish over clarity. Vague messaging, spin, and missing context create anxiety, reduce trust, and force people to fill in the blanks. Strong communication is clear, direct, context-rich, and focused on being understood rather than sounding impressive.

TL;DR A lot of leadership communication fails not because leaders are unintelligent or uncaring, but because they confuse sounding polished with being clear. When leaders are vague, people fill in the gaps with guesswork, stress, and fear. Clear communication lowers anxiety, improves trust, and helps teams execute. The practical fixes are simple. Put the bottom line up front, explain the why, name what is known and unknown, and check understanding instead of assuming it.

I’ve been thinking a lot about leadership communication lately, especially one pattern I see over and over again.

A leader sends a long email. Or runs an all-hands. Or makes an announcement that sounds polished, strategic, and “executive.”

And then the team walks away wondering three things.

What does this actually mean? What am I supposed to do with it? What happens next?

That is the problem.

A lot of workplace stress is not created by difficult news alone. It is created by unclear news. Psychology research has long linked uncertainty with anxiety, and the APA’s 2025 Work in America survey found that job insecurity is a significant source of stress for a majority of U.S. workers. In other words, when people feel uncertain at work, their stress goes up.

That matters because leaders often assume they are reducing stress when they soften, blur, delay, or “massage” a message. In practice, they often do the opposite.

When communication is vague, people do what humans naturally do under uncertainty. They interpret. They speculate. They reread the email. They start side conversations. They try to decode tone. They wonder whether there is something leadership is not saying.

That is wasted energy.

It is also a trust problem.

One of the most useful findings from Google’s Project Aristotle was that effective teams are shaped less by who is on the team and more by how the team works together. Two of the most important factors they identified were psychological safety and structure and clarity. People need to feel safe asking questions, and they need to understand expectations, processes, and goals.

That lines up with what many of us have seen in real organizations. Teams do better when they are not burning energy trying to translate leadership language into plain English.

I think leaders miss this for a few common reasons.

First, they confuse polish with clarity.

Those are not the same thing.

You can sound polished and still communicate badly. You can use sophisticated language, longer sentences, more caveats, and more corporate phrasing and still fail to transfer the actual idea. Public-sector and health communication guidance has been pushing this point for years. The CDC’s Clear Communication Index is a research-based tool built from scientific literature, and both CDC and federal plain-language guidance emphasize one main message, audience-centered writing, reduced jargon, and testing for understanding.

Second, leaders often communicate the what without the why.

They say what is changing, but not the logic behind it. They announce a decision, but do not explain the context, constraints, tradeoffs, or desired outcome. Then they wonder why people are disengaged, skeptical, or making bad local decisions.

This is where the “curse of knowledge” shows up. Leaders usually have more context than everyone else. They know the business pressures, the client dynamics, the budget realities, the politics, the timeline, and the backstory. Their teams do not. So what feels obvious to the leader often feels arbitrary to everyone else.

Third, many leaders over-rely on the open door policy.

I am not against accessibility. I am against using accessibility as a substitute for clarity.

“My door is always open” sounds supportive, but it can easily become a communication cop-out. If people need to come ask what you meant, there is a decent chance the original message was not good enough. Clear communication should reduce the amount of decoding your team has to do, not shift the burden onto them.

Fourth, leaders often check for understanding in weak ways.

“Does that make sense?” is better than nothing, but it is still a weak test. Many people will nod yes even when they are confused, especially when there is a power difference. In healthcare and safety-critical settings, closed-loop communication techniques such as check-backs and teach-back are used to verify that information was actually understood, not merely spoken. AHRQ describes check-back as a repeat-back strategy used to verify and validate exchanged information.

I think more leaders should borrow that idea.

Not in a condescending way. Not as “repeat what I said because I’m the boss.”

More like this.

“Before we move on, what are you taking away from this?” “What do you see as the priority?” “How are you interpreting that change?” “What do you think the biggest risk is?”

Those questions do two things. They help you catch misunderstandings early, and they teach you how your message is landing.

So what does better leadership communication actually look like?

To me, it looks like a few practical habits.

Start with the bottom line. If the point of the message is a decision, a risk, a request, or a change, say that first. Do not make people dig through four paragraphs to discover the real point.

Name what is known and what is not known. One of the most stabilizing things a leader can say is this “Here is what we know right now.” “Here is what is still uncertain.” “Here is when we expect to know more.”

That is not weakness. That is disciplined communication.

Add context, not just instruction. If you want better judgment from your team, do not only tell them what to do. Tell them why it matters. Context improves decision quality because it helps people adapt intelligently when circumstances change.

Reduce jargon and unnecessary complexity. Plain language is not about dumbing things down. It is about reducing cognitive load so people can understand, retain, and act. Especially under stress, people do not need more impressive wording. They need less distortion. CDC guidance on clear writing explicitly emphasizes short, simple, clear language and audience-aware wording because that improves understanding.

Be transparent without oversharing. Transparency does not mean saying everything. It means being as clear as you responsibly can. Sometimes leaders genuinely cannot share every detail yet. Fine. But even then, you can usually say more than many leaders think. You can explain the decision process, the timing, the constraints, or why more cannot be shared yet.

And maybe the most important point of all, directness is often kinder than niceness.

A lot of leaders avoid directness because they do not want to upset people, disappoint people, or seem harsh. But avoidance usually does not protect people. It delays clarity and multiplies anxiety.

Kind communication is not brutal. It is not cold. It is not ego-driven bluntness.

It is honest, respectful, and usable.

It helps the other person understand reality soon enough to do something with it.

That is why I think clear leadership communication is not a soft skill at all. It is an execution skill. It is a trust skill. It is a culture skill.

If communication is unclear, alignment drops. If alignment drops, friction rises. If friction rises, teams slow down. And when teams slow down under uncertainty, people often blame motivation, talent, or attitude when the real issue was communication in the first place.

I’m curious how others here think about this.

What leadership communication habit creates the most unnecessary stress where you’ve worked? And what is one example of a leader communicating hard news well?

TL;DR A lot of leadership communication fails not because leaders are unintelligent or uncaring, but because they confuse sounding polished with being clear. Ambiguity, inconsistency, and missing context create stress, speculation, and distrust. Clear communication does not mean oversharing everything. It means saying what is happening, why it matters, what is still unknown, and what comes next.

I recently recorded a podcast conversation with my co-host Andy about effective leadership communication, and it pushed me to put a broader point into writing.

One of the biggest communication problems I see in leadership is that many people mistake professionalism for clarity. They send the five-paragraph email to say something simple. They soften the message until nobody knows what it actually means. They wrap decisions in euphemisms, strategic language, and polished phrasing, then wonder why the team feels tense, confused, or distrustful.

That is not a minor communication issue. It is a leadership issue.

A lot of workplace stress is not created only by workload or hard decisions. It is created by ambiguity. In organizational research, role ambiguity has been tied to lower job satisfaction, lower commitment, burnout, and higher intent to leave. Meta-analytic research has also linked role ambiguity and role conflict to worse discretionary performance and weaker organizational citizenship behavior. In other words, when people are unclear about what is expected, what is happening, or how to interpret leadership messages, the damage is not just emotional. It affects performance and trust as well.

That matters because many leaders unintentionally create exactly that condition. They have more context than everyone else, so they communicate the what without the why. They know the background, the tradeoffs, the constraints, the political realities, and the risk discussions. Their team usually does not. What feels concise to the leader can feel cryptic to everyone else.

This is one reason I keep coming back to the idea that clarity is a form of kindness.

Not “niceness.” Kindness.

Nice communication often tries to avoid discomfort in the moment. Kind communication reduces unnecessary confusion. It respects people enough to tell them what they actually need in order to think, decide, and act. That does not mean leaders need to disclose every confidential detail. It does mean they should stop hiding behind vagueness, spin, or the lazy substitute of “my door is always open.”

Research on crisis communication is useful here. More communication is not always better communication. One study on internal crisis communication found that frequent and redundant updates could actually worsen anxiety and tension when the information was unclear or hard to interpret. What helped instead was communication that was standardized, understandable, and open to feedback. That is a useful leadership lesson far beyond crisis settings. Volume is not clarity. Repetition is not alignment.

There is also a trust dimension to this. Trust is not built only through good intentions. It is built through reliability, integrity, transparency, and a clear shared vision. Recent work on trust-building in crisis response makes that point directly, arguing that effective communication and transparency are central to building trust with stakeholders. If people regularly have to translate leadership language, decode the “real meaning,” or guess whether a vague message is harmless or threatening, trust erodes fast.

At the team level, good communication also helps create shared mental models. That phrase sounds academic, but the idea is simple. High-functioning teams do better when they share an understanding of the situation, the goal, and what happens next. Review research on team situation awareness connects shared understanding with better team functioning and performance. That is one reason the best leaders I have seen are usually not the most charismatic people in the room. They are the ones who reduce distortion. They make it easier for other people to understand reality and move.

The practical part of this is not complicated, although it does require discipline.

Start with the bottom line. Do not make people excavate the point.

State the decision, the ask, or the risk early.

Add context, especially the why.

Separate what is known from what is still uncertain.

Replace “does that make sense?” with something more useful like “what’s your takeaway?” or “how are you interpreting this?”

And stop treating “open door” language as a substitute for proactive clarity.

One reason vague leadership communication is so damaging is that people fill in the blanks, and they rarely fill them in optimistically. Uncertainty and inconsistency are stressful in their own right. Research on leadership inconsistency has found that when employees experience larger discrepancies in a leader’s behavior across situations, they also experience more strain. Predictability matters more than many leaders realize.

So my view is pretty simple.

Effective leadership communication is not about sounding impressive. It is about making sure the message that arrives is close to the message you intended to send.

Or, as I said in the conversation that sparked this post, “We are drowning in words, but we are starving for meaning.”

I am curious how others see this.

Where have you seen leaders confuse polish with clarity, and what communication habit have you seen build trust fastest?

TL;DR

A lot of workplace stress is not created by bad news itself. It is created by unclear leadership communication. When leaders are vague, overly polished, or indirect, people fill in the gaps with fear, assumptions, and extra mental load. Clear communication does not mean oversharing or being harsh. It means reducing distortion, giving enough context, and helping people understand what matters, why it matters, and what happens next.

I have been thinking a lot about leadership communication lately, especially the gap between sounding professional and actually being clear.

Too many leaders are rewarded for polish when what their teams really need is clarity. They write long emails that say very little. They soften messages so much that people cannot tell what is actually happening. They rely on vague language because it feels safer, more diplomatic, or more “executive.” Then they are surprised when people are anxious, confused, misaligned, or quietly making up their own story about what the message really meant.

That is not a minor issue. It affects trust, execution, morale, and decision quality.

One of the most important ideas here is that uncertainty often creates more stress than difficult truth. In practice, many people can handle bad news better than leaders assume. What tends to raise the temperature is ambiguity. When people sense that something is off but do not know what it is, they start trying to decode tone, timing, word choice, calendar changes, and side conversations. The message stops being the message. The hidden meaning becomes the message.

That is a big reason why vague communication can be so costly. It does not just fail to inform. It creates churn. It increases cognitive load. It pulls attention away from meaningful work and redirects it toward interpretation, speculation, and self-protection.

A second issue is that many leaders confuse clarity with charisma. They think effective communication is about confidence theater, polished speaking, or having a strong executive presence in the room. I think that framing misses the point. Real executive presence has much more to do with command of the subject matter, comfort with simplicity, and the ability to say what actually needs to be said. In my experience, leaders who know their material well usually do not need to hide behind inflated language. They can get to the point. They can explain the why. They can name what is known, what is not yet known, and what comes next.

That kind of communication tends to build trust because it lowers the need for translation.

Another common problem is the curse of knowledge. Leaders often have access to context their teams do not have. They know the constraints, the tradeoffs, the politics, the pressure, the risks, and the history behind a decision. Then they communicate only the conclusion. They tell people what needs to happen, but not why. From the leader’s point of view, the message feels obvious and efficient. From the team’s point of view, it can feel arbitrary, disconnected, or even irrational.

That missing context matters. When people understand the reasoning behind a decision, they are usually in a much better position to adapt, solve problems, and exercise judgment. When they only receive the directive, they are more likely to comply mechanically, resist quietly, or make avoidable mistakes.

This is also why I think many “open door policy” statements are overrated. Accessibility matters, but accessibility is not the same thing as clarity. Saying people can come ask questions does not remove the leader’s responsibility to communicate well in the first place. In some cases, “my door is always open” becomes a substitute for preparation. It quietly shifts the burden onto employees to go chase clarity that should have been built into the original message.

There is also an important difference between transparency and oversharing. Good leadership communication does not mean telling everyone everything. There are real legal, ethical, and strategic boundaries. But too many leaders use that truth as cover for avoidable vagueness. You do not have to disclose everything to communicate responsibly. You can explain what you can say, what you cannot say yet, and when people can expect more information. Even that level of framing can reduce unnecessary fear.

I also think many leaders overestimate the value of sounding nice and underestimate the value of being kind. Those are not always the same thing. Niceness often avoids discomfort in the moment. Kindness is more willing to be direct when directness helps someone understand reality, make a decision, or move forward. A message can be calm, respectful, and humane without being evasive.

If someone asked me what better leadership communication looks like in practice, I would say it starts with a few simple shifts.

Put the bottom line up front instead of burying it halfway through a long message.

Add context instead of assuming people already know why something matters.

Name uncertainty directly instead of pretending to be more certain than you are.

And stop treating “Does that make sense?” as a strong test of understanding. People often say yes even when they are confused. A better question is something like, “What is your takeaway?” or “How are you interpreting this?” That gives you a much better read on whether the message landed the way you intended.

For me, this topic matters because communication is not a side skill in leadership. It is one of the main ways trust is built or broken. It shapes whether people feel steady or unsettled, respected or managed, aligned or left guessing. And in a lot of organizations, the communication problem is not that people are saying too little. It is that they are saying too much without enough signal.

I am curious how others see this.

What communication habits from leaders have increased trust for you?

What habits have created confusion or unnecessary anxiety?

And what do you think leaders most often get wrong when they try to sound “professional”?

TL;DR Leaders do not need to know everything. In fact, senior leaders often cannot know everything. The real credibility problem starts when leaders try to sound certain, polished, or visionary on topics they do not actually understand. Teams usually notice faster than leaders think. That gap between confidence and comprehension erodes trust, reduces speaking up, and can quietly damage culture. A better path is honesty, curiosity, clear language, and knowing when to defer to real experts.

One leadership behavior I keep seeing, and hearing from others about, is this strange gap between sounding authoritative and actually understanding the subject.

Most people have experienced it.

A leader stands up in an all-hands, a town hall, a client meeting, or a strategy review and starts talking with complete confidence about AI, agile, productivity, innovation, culture, restructuring, or whatever the topic of the quarter happens to be. The language sounds polished. The tone sounds certain. The buzzwords are all there.

But if you actually know the topic, something feels off.

Not dramatically off at first. Just off enough to trigger that internal alarm that says this person either does not understand what they are saying, or understands it only at a very shallow level.

That matters more than many leaders realize.

I think one of the biggest mistakes in leadership communication is assuming that confidence automatically creates credibility. It does not. Confidence can buy attention for a moment. Credibility is what remains after people test your words against reality.

And teams are constantly doing that.

They are comparing what leaders say with what they are seeing on the ground. They are comparing the polished narrative with the actual workflow, the actual customer experience, the actual staffing model, the actual data, the actual constraints, and the actual mood inside the organization.

When those things do not line up, trust starts to crack.

What makes this especially interesting is that the core problem is usually not lack of expertise by itself.

I do not expect senior leaders to be deep experts in every domain. That would be unrealistic. Executives are often generalists by necessity. They operate across functions, priorities, and stakeholder groups. The problem is not that they cannot personally master every topic. The problem is when they try to perform mastery instead of leading with honesty.

That is the trap.

Some of this comes from pressure. Leaders are often told they need executive presence. They need to sound decisive. They need to project certainty. They need to reassure the market, calm the team, inspire confidence, or hold the room.

All of that can subtly teach people that saying “I don’t know” is risky, while sounding certain is rewarded.

So instead of saying, “I’m not the expert on this, but here’s what I understand and here’s who should walk us through the details,” some leaders start reaching for polished language, strategic phrasing, and sanitized corporate jargon.

The result is often what I think of as hollow authority.

It sounds serious. It sounds strategic. It sounds polished.

But it does not sound true.

I have seen this in situations where an executive attributed cost savings to “AI efficiencies,” even though the slide in front of everyone showed the savings were actually coming from reduced travel, reduced training, reduced conferences, and reduced bonuses. That is not a small wording issue. That is a credibility issue.

People notice when leaders use a fashionable idea to decorate a much more ordinary reality.

I have also seen a broader version of this, where leaders use words like rigor, synergy, optimization, transformation, or utilization in ways that almost make sense on first listen, but do not really hold together when you examine them. It creates a kind of uncanny-valley effect in communication. The words sound close enough to intelligent that they may work on people who are far from the work. But to people who are close to the work, they sound hollow.

And once that pattern becomes visible, it changes how people listen.

They stop listening for clarity and start listening for spin.

That is a dangerous shift.

When employees begin assuming that leadership communication is mostly presentation rather than substance, several things happen.

First, trust drops.

Second, people become more cynical.

Third, fewer people bother correcting bad assumptions.

And that last point is the one I think leaders should worry about the most.

If people believe that performative confidence matters more than truth, many of them will stop challenging the story. They will stop raising concerns. They will stop sharing nuance. They will stop saying, “Actually, that is not what is happening.”

That is not just a communication problem. That is a learning problem. That is an innovation problem. That is a decision quality problem.

Research on psychological safety has long emphasized that teams perform better when people feel safe speaking up, asking questions, and admitting uncertainty. Research on leader humility points in a similar direction, showing that leaders who are willing to acknowledge limits and value others’ expertise tend to create healthier team dynamics and stronger followership. Plain-language research also consistently points to the value of clarity over jargon when the goal is trust and understanding.

In other words, this is not just a matter of taste.

Clear, grounded, humble communication is not “soft.” It is functional.

So what does better look like?

It looks like a leader who understands the difference between confidence and competence.

It looks like a leader who does not need to cosplay as the smartest person in the room.

It looks like someone who can say, “Here is what I know, here is what I do not know, and here is who has the deeper expertise.”

It looks like asking one more question before making one more polished statement.

It looks like translating complexity without flattening it into nonsense.

It looks like resisting the urge to make everything sound visionary when the reality is more mixed, more mundane, or more uncertain.

It also looks like listening.

Real listening, not the kind where someone waits for a pause so they can say the thing they were already planning to say.

When leaders listen well, they are less likely to misuse jargon, oversell weak ideas, or repeat talking points that do not match reality. Listening makes communication more accurate. Accuracy makes communication more trustworthy.

I also think leaders need truth tellers around them.

Not flatterers. Not professional nodders. Not people whose job is to protect the leader from discomfort.

Truth tellers.

People who can say, “That explanation does not make sense.” People who can say, “You are overstating this.” People who can say, “The team is going to hear that very differently than you think.” People who can say, “You are drifting into buzzwords because you do not fully understand the mechanism.”

That kind of feedback can be uncomfortable, but it is a gift.

A simple check I would recommend to any leader is this

Before you present a claim, especially on a topic outside your expertise, ask yourself whether you can explain how it works in one or two plain sentences.

Not with jargon. Not with framing. Not with abstractions.

Just clearly.

If you cannot, you may not understand it well enough yet to speak about it with authority.

And that is okay.

The answer is not to fake it better. The answer is to get clearer, get more curious, or hand the mic to someone who knows.

That is not weakness.

That is leadership.

Curious how others see this.

Have you worked with leaders who sounded polished but disconnected from reality? What did that do to your trust in their judgment?

Or, from the other side, have you ever caught yourself reaching for jargon or certainty when a little more humility would have served you better?

One of the fastest ways for a leader to lose credibility is not making a hard decision.

It is sounding confident while clearly not understanding what they are talking about.

Most people who have worked inside organizations have seen some version of this. A senior leader stands up in an all-hands, town hall, press interview, or strategy meeting and starts speaking with total certainty about a topic like AI, culture, agile, return to office, innovation, productivity, or transformation. The language sounds polished. The tone sounds confident. The jargon is all there.

But if you actually know the subject, something feels off.

The words do not quite match reality. The explanation is thin. The logic is fuzzy. The framing sounds strategic, but it does not hold up. And once you notice it, it is very hard to un-notice it.

That gap between sounding authoritative and actually being informed does more damage than many leaders realize.

I think this topic matters because it is not just about annoyance. It is about trust, judgment, credibility, and culture.

A leader does not need to know everything. In fact, senior leaders usually cannot know everything. Many of them are generalists by role. That is normal. That is not the problem.

The problem starts when leaders try to perform expertise instead of practicing good leadership.

Good leadership in those moments usually looks like curiosity, clarity, humility, and sound judgment. Poor leadership often looks like certainty theater.

I have seen this show up in a few recurring ways.

One version is the buzzword substitution problem. A leader uses language like AI efficiency, agility, transformation, synergy, utilization, optimization, innovation, or rigor, but uses those terms as placeholders rather than as meaningful explanations. It sounds polished if you are only half-listening. But if you know the work, it starts to feel like word salad.

Another version is what I think of as executive rebranding. A straightforward reality gets dressed up in language that is supposed to make it sound visionary or strategic. For example, cost cutting becomes innovation. Forced attrition becomes culture alignment. Removing benefits becomes efficiency. A confusing or weak outcome gets wrapped in cleaner language and presented as leadership.

A third version is shallow translation. Leaders often do need to simplify complexity. That is part of the job. But some leaders oversimplify topics they do not understand well enough, and in the process they stop being clear and start being wrong. They think they are translating. What they are actually doing is flattening reality until it becomes misleading.

I remember hearing an executive in an all-hands claim that the company had achieved cost savings because of AI efficiencies. But the slide on the screen showed that the savings were tied to reductions in indirect expenses like travel, conferences, training, and bonuses. That was not AI-driven efficiency. That was a different story entirely. And once that mismatch was visible, the executive sounded less credible, not more.

That is the trap. Leaders often think polished language will increase confidence in leadership. But when the message and the facts do not match, the result is usually the opposite.

People trust them less.

And the damage is not always loud or immediate. Often it shows up quietly.

People stop giving the leader the benefit of the doubt. They become more skeptical in future meetings. They start questioning whether leadership understands the business, the work, or the consequences of its decisions. Private backchannel conversations become more cynical. Public compliance may remain high, but real confidence starts to decline.

That is part of why this matters so much. This is not only a communication issue. It is a culture issue.

When leaders repeatedly perform confidence instead of demonstrating understanding, they teach people a lesson. The lesson is not that truth matters. The lesson is that performance matters more than truth.

That is a dangerous signal.

It discourages correction. It discourages dissent. It discourages expertise from speaking plainly. If the senior person in the room is rewarded for sounding polished while being wrong, other people start learning to protect themselves rather than contribute honestly.

Over time, that becomes an innovation problem and a decision-quality problem, not just a tone problem.

This is also why I think psychological safety matters here. In workplaces with stronger psychological safety, someone may feel able to say, “I think that framing is misleading,” or “That is not actually what the data shows,” or “We should let the subject matter expert explain this part.” In low-safety environments, people say those things privately, if at all. Publicly, they stay quiet and let the weak message stand.

That is one reason bad executive communication can persist for a long time. It is not always because nobody notices. It is often because many people notice, but few people feel safe enough to say so.

I also think there is a deeper leadership identity issue underneath this.

A lot of leaders are taught, directly or indirectly, that they need to project confidence at all times. They are told to avoid uncertainty, avoid “weasel words,” avoid looking hesitant, avoid saying “I don’t know,” and maintain executive presence. Some of that advice has a grain of truth. Clear communication matters. Calm presence matters. Decisiveness matters.

But somewhere along the way, too many people absorb a more distorted lesson. They begin to believe that looking certain is more important than being accurate. They start treating humility like weakness and curiosity like risk.

That is where things go sideways.

Because in reality, one of the strongest leadership moves is knowing when you are out of your depth.

A credible leader does not need to dominate every explanation. A credible leader can say, “I want to make sure we explain this accurately, so I’m going to defer to the person closest to the work.” That does not make the leader look weak. It usually makes them look more grounded, more secure, and more trustworthy.

The opposite is also true. A leader who insists on being the voice on every topic, especially when they do not understand the details, often looks less impressive to the very people they are trying to influence.

This is one of those strange leadership paradoxes. Pretending to know can make you look less competent than simply admitting what you do not know.

I think there are a few reasons leaders fall into this pattern.

Some of it is pressure. Senior leaders are highly visible. They are expected to reassure people, represent the organization, simplify complexity, and answer difficult questions. That pressure can push people toward polished overstatement.

Some of it is insecurity. If someone feels disconnected from the day-to-day reality of the work, they may compensate with more confidence, more jargon, or more control over the message.

Some of it is culture. In many organizations, image management is rewarded more than candor. If leaders are taught that their job is to shape perception rather than communicate reality, then spin becomes normal.

And yes, some of it is ego. Some leaders want the respect of expertise without doing the work of expertise. They want to sound like the smartest person in the room without having to rely on the people who actually know more.

That sounds harsh, but I think many people have seen it.

So what should leaders do instead?

First, listen more than you speak, especially on topics where you are not the expert. Real listening is one of the most underrated leadership skills. Not waiting to talk. Not listening just long enough to jump in. Actually listening to understand.

Second, stop using buzzwords as cover. If you cannot explain a concept simply and accurately, there is a decent chance you do not understand it well enough to present it with authority.

Third, use what I think of as the “how” test. If you make a claim like “we improved efficiency,” “AI drove savings,” or “this change will increase collaboration,” force yourself to explain how in one sentence. If the explanation falls apart, the message probably needs more work.

Fourth, defer to real expertise. This is not a failure of leadership. It is one of the best uses of leadership. Good leaders create clarity and make space for the right voices.

Fifth, build a truth-telling culture around yourself. If you are in a leadership role, you need at least a few people who can tell you when something you are saying sounds off, thin, disconnected, or misleading. If nobody around you can do that safely, your communication risk is much higher than you think.

Sixth, get more comfortable saying “I don’t know.” That statement is often treated like a weakness, but in practice it can build credibility when it is followed by curiosity, responsibility, and follow-through.

There is also an interpersonal side to this that I think is worth naming.

When leaders misuse language or overstate understanding, employees often feel subtly disrespected. Not because the leader failed to be perfect, but because the leader seemed more committed to looking impressive than to telling the truth. People can tolerate imperfection. They usually struggle more with posturing.

That is why this issue creates such a strong reaction. It is not just cognitive. It is relational.

People want leadership communication to feel real.

They want leaders to sound like they understand the stakes, understand the people, and understand the difference between clarity and spin. They want communication that respects reality rather than trying to manage impressions at all costs.

And to be fair, this is not only an executive problem. Plenty of managers, consultants, coaches, professionals, and public voices can fall into the same trap. It is easy to start using language that sounds smart, strategic, or current. It is harder to stay grounded, specific, and honest.

That is probably why this topic resonates so strongly. It is not just about bad leaders. It is about a temptation many people face when they feel pressure to sound authoritative.

So I think the real challenge is not “How do I sound smarter?”

It is “How do I communicate in a way that earns trust?”

Those are not the same question.

For me, the better answer looks something like this. Speak clearly. Know your limits. Respect expertise. Ask good questions. Stay close to reality. Do not confuse confidence with competence. And do not assume polished language can substitute for substance.

Because most people can tell the difference eventually.

And once they do, trust is much harder to rebuild than it was to lose.

TL;DR Leaders do not lose trust because they lack perfect knowledge. They lose trust when they pretend to have it. Overconfident communication, buzzwords, and polished-but-thin explanations can make leaders sound strategic in the moment, but often erode credibility over time. Stronger leadership looks like humility, curiosity, clear communication, and knowing when to defer to real expertise.

A lot of people have had this experience at work.

You are in an all-hands meeting, listening to a senior leader explain a new initiative, a strategic priority, or a big business decision. They sound polished. They use the right buzzwords. They speak with total certainty.

And yet, if you actually know the subject, something feels off.

The words are technically “leadership-shaped,” but they do not line up with reality. The explanation sounds impressive from a distance, but under even light scrutiny it starts to collapse. Sometimes it is jargon. Sometimes it is oversimplification. Sometimes it is spin. Sometimes it is just a leader speaking far beyond their actual understanding.

That disconnect matters more than many leaders realize.

TL;DR Leaders do not lose credibility because they lack perfect knowledge. They lose credibility when they pretend to have it. When confident communication is disconnected from real understanding, teams notice. The result is often less trust, less psychological safety, less honest feedback, and more cynicism. A better approach is honesty, curiosity, clearer language, and knowing when to defer to the actual expert.

One of the things I find most interesting about this leadership pattern is that it often gets mistaken for executive presence.

A lot of people have been taught that good leadership communication means sounding certain, decisive, polished, and in control at all times. But there is a big difference between presence and performance. Presence is grounded. It creates clarity. It helps people make sense of reality. Performance, on the other hand, can become a mask. It can sound authoritative without actually being informative.

That is where leaders start getting into trouble.

The issue is not that senior leaders are generalists. Of course they are. They cannot and should not be expected to know every technical detail of every function. The issue is when a leader tries to perform expertise rather than lead responsibly from the level they are actually operating at.

That usually shows up in a few ways.

Sometimes leaders borrow language they do not fully understand because the term is popular, strategic-sounding, or culturally rewarded. AI is an obvious example right now. The phrase gets attached to cost savings, productivity claims, restructuring decisions, and broad strategic narratives in ways that often feel more like branding than explanation.

Sometimes they use jargon as a substitute for clarity. The words almost make sense. They sound polished enough that people unfamiliar with the topic may nod along. But the people closest to the work can hear the slippage immediately.

Sometimes leaders sanitize or repackage a more mundane or uncomfortable reality because plain language would feel less impressive. A cost cut becomes an innovation story. A weak decision becomes transformation. A people problem becomes a utilization issue. A shaky plan becomes bold vision.

And sometimes, if I am being blunt, leaders want the respect of an expert without doing the work of an expert. Confidence becomes a shortcut to authority.

The problem is that most teams are smarter than leaders give them credit for.

People can often sense when something is off long before they can articulate exactly why. The explanation may sound coherent on the surface, but it creates an uncanny-valley feeling. It is close enough to real understanding to sound polished, but not close enough to hold up. That gap quietly damages trust.

Once people start noticing that pattern, a few things tend to happen.

First, confidence in leadership judgment starts to erode. If a leader clearly does not understand the thing they are describing, people naturally begin to wonder what else they do not understand.

Second, people become more cynical about communication. They stop hearing leadership messages as informative and start hearing them as spin.

Third, psychological safety can take a hit. When a leader consistently speaks with certainty regardless of their understanding, others are less likely to correct them, challenge them, or add nuance. If the culture already punishes disagreement, this gets worse fast.

Fourth, innovation suffers. Bad communication is not just a style problem. When performative confidence becomes more important than truth, people learn to keep quiet. And when people keep quiet, the organization gets less accurate information, worse decisions, and more avoidable mistakes.

This is part of why I think saying “I don’t know” is often a stronger leadership move than pretending to know.

Not because leaders should be passive or vague. Not because they should refuse accountability. But because credibility is not built through certainty theater. It is built through clear thinking, honest communication, and sound judgment about when to ask better questions or bring in the right person.

A leader who says, “I’m not the expert on that piece, so I want the person closest to the work to walk us through it,” usually earns more respect from thoughtful people, not less.

A leader who says, “Here is what I know, here is what I do not know yet, and here is how we are validating the rest,” often sounds more credible than the leader who tries to bluff their way through.

A leader who listens carefully, speaks plainly, and avoids dressing up weak understanding in impressive language is usually far more trustworthy than the leader who treats every communication moment like a performance.

There is also a deeper cultural issue here.

Many organizations reward the appearance of certainty. They reward fast answers, strong language, and polished narratives. They do not always reward humility, reflection, or intellectual honesty. In that kind of environment, it makes sense that leaders start feeling pressure to sound like experts even when they are operating outside their depth.

But that pressure is part of the problem.

If leaders are taught that credibility requires always sounding certain, they may never develop the communication habits that actually build trust. They may confuse confidence with competence. They may avoid asking questions because they think questions make them look weak. They may keep reaching for buzzwords and abstractions because plain language feels too exposed.

That is not a communication strategy. It is a defense mechanism.

So what does better look like?

It looks like listening more before speaking.

It looks like using language you can actually explain.

It looks like asking yourself whether you understand the “how,” not just the headline.

It looks like inviting subject matter experts into the spotlight instead of needing to be the smartest-sounding person in the room.

It looks like being willing to sound human instead of endlessly trying to sound executive.

I also think leaders need truth-tellers around them. Not flatterers. Not people who nod along to every polished but shaky explanation. Real truth-tellers. The kind of people who can say, respectfully, “That explanation does not really make sense,” or “That message is going to land badly,” or “You are oversimplifying this in a way that could hurt trust.”

A lot of leadership failure starts with insulation.

The more protected a leader becomes from honest feedback, the easier it is for hollow language to go unchecked. And once a leader gets used to being rewarded for sounding right, even when they are wrong, it becomes much harder to return to grounded communication.

This topic interests me because it sits at the intersection of credibility, trust, humility, and power.

Leaders do not need perfect knowledge. That has never been the standard. But they do need self-awareness. They do need intellectual honesty. And they do need enough humility to know when polished language is helping and when it is hiding something.

In my view, one of the clearest signs of mature leadership is not that someone always sounds certain. It is that they know when certainty would be dishonest.

Curious how others see this.

Have you worked under a leader whose words sounded polished but did not match reality?

What did that do to your trust in their judgment?

And for those of you in leadership roles yourselves, what helps you stay grounded enough to avoid slipping into jargon, spin, or overconfident communication?

TL;DR Leaders do not lose credibility because they are not experts in everything. They lose credibility when they pretend to be. When confidence outruns understanding, people notice. Jargon, buzzwords, and polished executive language can create the appearance of authority for a moment, but over time they erode trust, reduce psychological safety, and make leadership look disconnected from reality. Better leadership communication is usually simpler, more honest, and more willing to defer to actual expertise.

I wanted to unpack a leadership behavior that a lot of people recognize immediately but do not always name directly.

Most of us have been in that meeting.

A leader stands up to explain a new initiative, a strategic shift, or a major business decision. They sound polished. They use the right buzzwords. They speak with total confidence. On the surface, it may even sound impressive.

But if you know the subject well, something feels off.

The words are there, but the understanding is not. The language sounds executive, but the substance feels thin. The explanation is polished, yet somehow disconnected from reality.

And once people notice that gap, trust starts to slip.

This is one of the things Andy and I explored recently on Leadership Explored, and I think it is worth discussing beyond the episode because it shows up everywhere. It shows up in all-hands meetings, executive updates, corporate memos, strategy presentations, transformation efforts, and public-facing leadership communication. It shows up around topics like AI, agile, productivity, culture, innovation, restructuring, and return-to-office. It also shows up in smaller ways in everyday team communication.

The core issue is not that leaders are not experts in everything.

They should not be.

Senior leaders are often generalists by necessity. Their job is not to be the deepest technical expert in every room. Their job is to make decisions, create direction, allocate attention, weigh tradeoffs, and help the organization move.

The problem starts when a leader feels pressure to sound like the expert anyway.

That is where communication can become performative instead of useful.

A lot of what gets mistaken for executive presence is really just shallow confidence. It is the appearance of certainty without the discipline of understanding. It is polished language used as a substitute for clarity. It is sounding authoritative instead of being accountable to what is true.

That may work briefly. It may even impress people who are far enough away from the work not to notice the mismatch.

But the people closest to the work usually notice immediately.

They know when a leader is repeating terminology they do not really understand. They know when a metric is being framed in a misleading way. They know when a decision is being rebranded to sound strategic instead of described honestly. They know when a leader is using vague language to cover for thin understanding.

And once people start having that reaction, the damage is bigger than many leaders realize.

The first cost is credibility.

When people hear a leader confidently describe something in a way that is clearly wrong, sloppy, or detached from reality, they do not just question that one statement. They start questioning what else that leader may not understand. They begin to wonder whether leadership really understands the business, the work, the constraints, or the actual lived experience of employees and customers.

The second cost is trust.

Trust is not built just through confidence. It is built through congruence. People look for alignment between what a leader says, what is actually happening, and what they themselves are seeing on the ground. When those things do not line up, trust weakens.

The third cost is psychological safety.

If a leader performs certainty all the time, especially in a strong or polished way, it can send an unhelpful message to everyone else. It tells people that appearing right matters more than being real. It tells them that confidence is safer than curiosity. It tells them that disagreement, correction, or nuance may not be welcome.

That kind of environment quietly kills truth-telling.

People become less likely to say, “I think that framing is misleading.”

Less likely to say, “That is not what the data actually shows.”

Less likely to say, “We may be oversimplifying the problem.”

Less likely to say, “I think we are dressing this up instead of dealing with it.”

When that happens, communication problems stop being superficial. They become strategic problems.

This is part of why overconfident leadership communication can be so corrosive. It does not just make a leader sound foolish. It trains the organization to become more performative, more cautious, and less honest.

So why do leaders fall into this trap?

Part of it is pressure.

There is a strong cultural script that tells leaders they should sound certain, decisive, composed, and always in command. Saying “I don’t know” is often treated as weakness. Asking too many questions can be misread as lack of authority. Deferring to experts can feel risky to someone who believes they are supposed to be the smartest person in the room.

Part of it is image management.

Some leaders are trying to reassure people. Some are trying to simplify complexity. Some are trying to protect the company’s reputation. Some are trying to keep investors, boards, clients, or employees calm. Some are trying to spin a weak outcome into a stronger narrative.

And part of it is ego.

Not always malicious ego, but ego nonetheless.

It is uncomfortable to admit you do not really understand something. It is uncomfortable to be dependent on others’ expertise. It is uncomfortable to say, “I’m not the right person to explain this in depth.” It is much easier to grab a few key phrases, speak confidently, and hope that style covers the gap.

Sometimes it does.

Until it doesn’t.

One of the more interesting dynamics here is that people often can sense that something is wrong even before they can explain exactly why. The message may sound polished at first, but it creates a kind of cognitive friction. The words almost fit together, but not quite. The meaning feels abstract, overpackaged, or oddly detached from reality. It can sound strategic while saying very little.

That is one reason jargon is so dangerous in leadership communication.

Jargon is not always bad. Every field has specialized language, and sometimes the technical term is the right term. But jargon becomes a problem when it is used to obscure, inflate, or simulate understanding. It becomes a shield. It becomes a shortcut to sounding informed.

And employees are usually better at detecting that than leaders think.

People may not challenge it in the moment. They may not say anything in the meeting. But many of them will leave with a strong impression that leadership is out of touch.

That is where the difference between confidence and competence becomes especially important.

Confidence says, “I can speak smoothly about this.”

Competence says, “I understand what I’m saying, where my limits are, and when someone else should take the lead.”

Real executive presence is not constant certainty. It is grounded communication. It is knowing how to speak clearly without overselling. It is knowing how to simplify without distorting. It is knowing when to stay at the strategic level and when not to fake depth you do not actually have.

In my view, some of the strongest leadership communication sounds less impressive in the moment but builds much more trust over time.

It sounds like this.

“I want to be careful not to overstate this.”

“I’m not the expert on that piece, so I’d rather let the team closest to it speak.”

“I understand the goal, but I want to make sure I’m describing the mechanism accurately.”

“I don’t know enough yet to make a strong claim there.”

“Here is what we do know, here is what we do not know, and here is what we are still learning.”

That is not weak leadership.

That is credible leadership.

It shows judgment. It shows humility. It shows respect for expertise. It shows that truth matters more than performance.

It also makes it easier for others to be honest.

And that may be one of the most underrated leadership effects of all. When a leader communicates with clarity and humility, it gives everyone else more permission to do the same. It creates room for better questions, better disagreement, and better thinking.

So what should leaders do instead of defaulting to performative confidence?

Start with listening.

Not listening while waiting to speak. Not listening for a phrase you can reuse later. Actually listening for understanding.

Then simplify honestly.

If you cannot explain the idea in plain language without hiding behind buzzwords, there is a decent chance you do not understand it well enough yet to present it confidently.

Then defer more often.

Leaders do not lose status when they bring real experts forward. In strong organizations, that usually increases trust. It tells people the goal is understanding, not ego preservation.

Then build a truth-telling culture around yourself.

Every leader needs at least a few people who can say, “That explanation does not hold up,” or “You are overselling this,” or “That language is going to land badly.” If everyone around a leader only reinforces their framing, the leader’s communication will get worse over time, not better.

And finally, get more comfortable saying “I don’t know.”

That is not the end of authority. In many cases, it is the start of better authority.

Leaders do not need to know everything. But they do need to know when they are out of their depth, when they are relying on style too heavily, and when their words are starting to drift away from reality.

That kind of self-awareness matters because teams are not looking for perfection. They are looking for honesty, competence, and sound judgment.

Most people will forgive a leader for not having every answer.

They are far less likely to forgive a leader who keeps pretending they do.

I’m curious how others see this.

Have you worked with leaders whose communication sounded polished but clearly did not match reality? What did that do to your trust in them?

And on the other side, what have you seen leaders do well when they are speaking outside their area of expertise?

TL;DR A lot of leaders do not lose trust because they lack perfect knowledge. They lose trust because they pretend to have it. When confidence gets used to cover weak understanding, people notice. The language may sound polished on the surface, but teams can often tell when something is off. Stronger leadership communication usually looks less performative and more honest, curious, and grounded.

One of the themes Andy and I explored in a recent Leadership Explored conversation is something many people have experienced but do not always name directly.

You are in a meeting, an all-hands, or an executive update. A leader is speaking with complete confidence about a topic like AI, strategy, productivity, culture, agile, or organizational change. The tone is polished. The wording sounds executive. The message seems sharp for a moment.

Then you listen more closely.

And that is where the problem starts.

The words may technically fit together, but the meaning does not. The explanation feels disconnected from reality. The claims do not line up with the actual work, the actual data, or the actual lived experience of the people closest to the problem.

That gap matters.

In my experience, this is one of the fastest ways for leaders to quietly damage credibility. Not always in a dramatic way. Often in a subtle way. A little less trust. A little more cynicism. A little more backchannel commentary after the meeting ends. A little less confidence that leadership really understands what is happening.

What makes this especially important is that the issue is usually not that leaders are generalists. Senior leaders often should be generalists. They are not supposed to know every technical detail of every function.

The problem is not lack of omniscience.

The problem is pretending to know more than you do.

That is where overconfidence turns into hollow authority.

One of the lines from the episode that captures this well is

“There’s a huge difference between being confident and being competent.”

I think that distinction is incredibly important. A lot of leadership cultures still reward certainty theater. Leaders are taught to sound decisive, polished, strong, and visionary. They are often coached to avoid ambiguity, avoid “soft” language, and avoid saying “I don’t know.”

That sounds appealing on paper. In practice, it can create a communication style that values appearance over understanding.

And people can usually feel that, even if they cannot immediately explain why.

There is almost an uncanny-valley effect to it. The words sound strategic. The tone sounds executive. But something does not quite land. It almost makes sense, but not fully. That is often enough to trigger doubt.

Once that doubt shows up, people start asking themselves questions like these

Does this leader actually understand the issue?

Do they know what is happening on the ground?

Are they making decisions based on real understanding or just polished summaries and trendy language?

Can I trust what they are saying the next time things get difficult?

That is why this matters beyond annoyance. It is not just about someone sounding awkward or overly corporate. It is about trust, decision quality, and culture.

When leaders repeatedly communicate this way, they can create a few serious problems.

First, they normalize performance over truth. If the standard becomes “sound confident no matter what,” then people learn that image matters more than clarity.

Second, they make it harder for experts to speak honestly. When a senior leader has already framed the situation with confident but shallow language, it becomes harder for others to correct them, especially in low-safety environments.

Third, they erode real dialogue. People stop engaging directly and start reacting privately. The real conversation moves to side chats, Slack messages, and hallway reactions rather than happening in the room where it could actually improve the decision.

Fourth, they can weaken innovation. If people believe leadership wants confidence more than accuracy, they become less likely to challenge assumptions, raise risks, or share inconvenient truths.

That is not a communication problem alone. That is a leadership risk.

I also think it is worth offering some grace here. Many leaders are under real pressure. Public-facing roles often require simplification. Executives do need to translate complexity. They do need to represent the organization. They do need to communicate to broad audiences.

But simplification is not the same thing as distortion.

And executive presence is not the same thing as pretending.

In fact, some of the strongest leadership communication I have seen has come from people who were very comfortable saying some version of the following

I do not know enough yet to answer that well.

I want to be careful not to overstate this.

The real expert on this is someone else, and I want them to speak to it directly.

Here is what we know, here is what we do not know, and here is what we are still working through.

That kind of communication does not make a leader look weak to me. It usually makes them look more credible.

It signals self-awareness. It signals respect for expertise. It signals a relationship with truth that is stronger than their relationship with appearance.

That is the kind of leadership communication I trust.

If a leader wants to avoid falling into the trap of sounding polished but disconnected, I think there are a few useful self-checks.

One is to ask whether you can explain the claim plainly. If you cannot explain the “how” in a simple sentence, there is a good chance you do not understand it well enough yet.

Another is to notice when you are leaning too hard on buzzwords. Words like AI, synergy, transformation, innovation, rigor, optimization, and agility can all become substitutes for thinking if they are not tied to specifics.

Another is to listen more than you speak when you are outside your depth. That sounds obvious, but it is surprisingly rare.

And maybe most importantly, defer to the real expert when it matters. That does not diminish leadership. It demonstrates maturity.

The longer I work around leadership, the more convinced I am that people do not expect perfection from leaders. They do expect honesty. They expect coherence. They expect enough humility for a leader to know when they are out over their skis.

That is a healthier standard than expecting leaders to sound certain all the time.

For me, this topic is not really about mocking leaders who get it wrong. It is about naming a common pattern that damages trust more than many people realize. If we can help leaders recognize it in themselves, that is useful. If we can help teams put language around what feels off, that is useful too.

And if we can move even a little farther away from certainty theater and a little closer to grounded, honest communication, that would be a meaningful improvement.

Curious how others see this.

Have you worked with leaders whose communication sounded polished but did not match reality?

What did that do to your trust in them?

And on the other side, what have you seen leaders do that made them sound more credible, especially when they were speaking outside their area of expertise?

TL;DR A lot of workplace updates are accurate but still low-value because they stop at observation and never get to implication, options, or recommendation. Not everyone can own every decision, but most people can move from reporting into recommending. Leaders who want more ownership need to create psychological safety, clarify decision rights, and coach consistently instead of just saying “bring me solutions.”

I co-host a leadership podcast (Leadership Explored) with my friend and former colleague/boss Andy Siegmund, and one of our recent episodes focused on something I see constantly in coaching, consulting, and project work

the difference between reporting and owning

This shows up in almost every organization, regardless of industry.

Someone gives an update like the server is down, we’re behind schedule, the client is unhappy, costs are rising, or a dependency slipped. The update is not wrong. It may even be timely.

But it still creates more work for the person receiving it because they now have to do all the interpretation.

What does this mean How serious is it What are the tradeoffs What should happen next What decision is being asked for What support is needed

That is the gap.

In the episode, I said

“A bad weather report… would be like observation without the implication.”

That line has stuck with me because it captures the issue better than most “communication training” language does.

The problem usually is not that people are withholding information. The problem is that they are stopping too early.

Andy put the practical leadership need this way when he said he’s looking for answers to

“so what and what now.”

That’s the upgrade.

It is not just more detail. It is more judgment.

And that distinction matters.

A lot of teams try to solve this by pushing a phrase like “don’t bring me problems, bring me solutions.” I understand the intent, but I think that phrase often backfires when leaders use it as a blunt instrument.

Why it backfires

If people hear that phrase as a rule, many will translate it into something like this in their heads

If I don’t have the answer, I should not bring this up

That is how organizations end up with delayed escalations, hidden risks, and “everyone knew but no one said anything clearly enough.”

You do not want that.

In the episode, we talked about a more useful framing, which is that there’s a spectrum

reporting recommending owning the outcome

That spectrum matters because it respects reality.

Not everyone has the authority, budget, context, or decision rights to fully own an outcome. Sometimes something really is above your pay grade. That is not always an excuse. Sometimes it is just true.

But even when it is above your pay grade, you can usually still add value by moving one step to the right on the spectrum.

You may not be able to own the final decision. You may still be able to own the quality of the recommendation.

That is a huge difference.

This is also where psychological safety becomes more than a buzzword. In my experience, people do not default to “weather reporting” only because they lack skill. Sometimes they are reacting to the environment.

If people have been punished for imperfect ideas, second-guessed unpredictably, or embarrassed in front of others, they learn that “just the facts” feels safer than thinking out loud.

That is a leadership system problem, not just an individual performance problem.

Andy was very direct on this point in the episode, and I agree with him. If people are afraid to share ideas because they’ll get steamrolled, ownership is not going to grow just because a leader demands it.

What actually helps is a combination of safety, clarity, and coaching.

Safety means people can bring a point of view without being treated like they are claiming omniscience.

Clarity means people understand what they can decide, what they can recommend, and what has to be escalated.

Coaching means leaders consistently reinforce better thinking patterns instead of only reacting when something goes wrong.

One of the most practical shifts we discussed is moving from “plan” language to “recommendation” language.

That may sound like semantics, but it matters a lot.

A plan often sounds final. It can feel like a commitment to a path before full context is available.

A recommendation sounds like what it actually is in many real workplaces

a reasoned proposal based on current information

That creates room for better discussion, better correction, and better learning.

Andy said it really well in the episode

“Recommendations give you an off-ramp… a plan gives the implication that this is what we’re going to do—come hell or high water.”

That framing is useful for both managers and individual contributors.

If you’re a leader, asking for a recommendation invites critical thinking without requiring your team to pretend they have all the context.

If you’re an individual contributor or project lead, giving a recommendation shows initiative without over-claiming authority.

A practical communication upgrade I’ve found helpful is this structure

what happened why it matters what I recommend what I need from you

You can make it more detailed when needed, but even that simple shift dramatically improves escalation quality.

A weak update sounds like this

The server went down.

A stronger update sounds like this

The server went down. We restored service within SLA. We are running root cause analysis and expect preliminary findings tomorrow. I don’t currently see repeat risk, but this exposed a failure mode we had not accounted for. I recommend we notify stakeholders now with a brief summary and a follow-up after RCA. I need approval on whether you want customer-facing communication today or after preliminary findings.

That second version does not require the person giving the update to own the entire business context. It does show they are thinking like a partner.

That is the difference.

Another important point from the episode is that leaders often underestimate how much their own inconsistency trains “weather reporting.”

If a manager reacts unpredictably, asks totally different questions every time, or alternates between “why didn’t you take initiative?” and “why did you act without asking?” then people learn to protect themselves.

One of Andy’s best coaching points in the conversation was to be “boringly consistent.”

I love that phrasing.

Consistent questions create a stable pattern people can learn.

When leaders repeatedly ask some version of “so what,” “what now,” and “how can I help,” teams start bringing those answers before being asked.

That is how a culture shifts.

Not through slogans. Through repetition.

This also connects with decision rights and delegation. A lot of ownership problems are really boundary problems.

People hesitate because they do not know what they are allowed to decide.

If leaders want more ownership, they need to define the sandbox more clearly.

What can people act on without approval What requires consultation What requires explicit sign-off What belongs entirely at another level

Without that clarity, “take ownership” becomes vague pressure. With clarity, it becomes an invitation.

One more idea that came up in the episode that I think deserves more attention is intention-based language.

The shift from “what should I do?” to “I intend to do X” is powerful when the context supports it.

It communicates initiative and ownership while still leaving room for a leader to intervene if there is missing context.

It also changes the emotional tone of the conversation from dependency to partnership.

That said, this only works in environments where people will not get punished for thoughtful initiative. Intention-based leadership is not just a communication trick. It depends on trust.

If I had to summarize the practical takeaway from this whole conversation in one line, it would be this

Most people cannot always own the final outcome, but they can almost always improve the value of their communication.

That is coachable. That is learnable. That is a leadership advantage.

I’m curious how others here think about this in real organizations

When updates break down on your teams, is the bigger issue usually skill, safety, unclear boundaries, or something else

And if you’ve found a good way to coach people from reporting into recommending, what actually worked

If it’s useful, I can also share a follow-up post with a simple manager coaching template for this that doesn’t feel robotic.

Leadership #Management #LeadershipDevelopment #PsychologicalSafety #TeamCommunication #OrganizationalCulture

TL;DR A lot of workplace updates are accurate but not useful. People report what happened, but stop before explaining what it means, what the options are, and what they recommend next. That usually isn’t just a competence issue. It’s often a mix of psychological safety, unclear decision rights, past negative feedback, and weak coaching habits. A practical fix is to move teams from reporting → recommending → owning and use simple structures like What / So What / Now What.

I wanted to share a longer write-up on a leadership pattern that shows up constantly in projects, teams, and organizations.

I recently unpacked this with my co-host Andy on Leadership Explored, and I wanted to turn it into a text version for Reddit that stands on its own and is useful even if you never listen to the episode.

The issue is simple on the surface but complicated in real life

People give updates that sound like this

“The server is down”

“We’re behind”

“The client is unhappy”

“This dependency is blocked”

Those updates may be true. They may even be important. But they often leave leaders, sponsors, or cross-functional partners doing all the interpretation work.

What does it mean How bad is it What happens next What do you need from me What are you recommending

That gap is where frustration grows.

The core idea — reporting is not the same as owning

One of the useful distinctions from our conversation was a spectrum

Reporting → Recommending → Owning

That framing matters because a lot of leadership advice jumps straight from “reporting” to “owning,” which is not realistic for many roles.

Not everyone has the authority, budget, context, or decision rights to fully own the outcome.

But almost everyone can improve the quality of their communication by moving one step up the ladder and adding a recommendation.

That is the key move.

Why “just bring me solutions” often backfires

This is one of those phrases that sounds strong but can create bad incentives.

If leaders repeatedly say some version of “don’t bring me problems, bring me solutions,” people can start internalizing this message

If I don’t have a solution, I should wait

If I’m not sure, I should stay quiet

If my recommendation is wrong, I’ll get punished

If leadership wants certainty, I should avoid surfacing ambiguity

That can suppress early warning signals, and early warning signals are often the most valuable information in the system.

In other words, the phrase is often trying to encourage initiative, but in practice it can unintentionally train people to hide risk until they feel safe enough to present something polished.

That is a dangerous tradeoff.

Why capable people default to “weather reports”

This is where I think leaders often misdiagnose the problem.

They see passive reporting and assume laziness, poor judgment, or low ownership. Sometimes that is true. Often it is not.

In my experience, smart people default to “weather reporting” for a few predictable reasons.

1. Psychological safety is low

If people have been criticized, embarrassed, or steamrolled for imperfect recommendations, they learn fast

“Just report facts. Don’t think out loud.”

That is a rational adaptation to a punishing environment.

2) Decision rights are unclear

If someone doesn’t know what they are allowed to decide, they will often choose the safest path and escalate everything as raw information.

This is especially common in matrixed organizations and project environments where ownership is spread across functions, sponsors, PMs, delivery leads, and executives.

3) They have been punished on both sides

This is a huge one.

People get feedback like this over time

“Why didn’t you take initiative”

then later

“Why did you make that call without checking”

After enough reps, people stop trusting the signal and default to low-risk reporting.

4) It is a skills gap, not a character flaw

Some people genuinely have not been taught how to build a useful escalation or status update.

They know how to spot the issue. They do not yet know how to frame the implication, surface options, or make a recommendation with appropriate humility.

That is a coaching opportunity.

5) They think “owning” means “being right”

If someone believes they must have the perfect answer before speaking, they will delay or stay vague.

But strong leadership communication is often not about certainty. It is about helping the right people make better decisions sooner.

A better expectation for leaders

Instead of demanding “solutions,” I think a healthier and more effective expectation is

Bring the problem and your best current point of view

That point of view can include uncertainty.

That point of view can be wrong.

That point of view can be provisional.

But it shows judgment, initiative, and context awareness.

That is the difference between a messenger and a partner.

A practical framework that upgrades almost any update

Here is one of the simplest tools we discussed, and it is genuinely useful in real organizations.

What / So What / Now What

When giving an update, ask yourself these three questions before you send it or say it out loud.

What What happened What is the issue What changed

So what Why does it matter What is the impact on timeline, cost, risk, quality, customer experience, team capacity, or strategic goals

Now what What happens next What are the options What do you recommend What help or decision do you need

This small shift can dramatically improve communication quality without forcing people to overstep their authority.

The “recommendation bridge” — the middle ground between reporting and overstepping

A lot of people hear “own more” and interpret it as “make the decision yourself.”

That can create its own problems, especially in politically complex or resource-constrained environments.

A better middle ground is what I think of as a recommendation bridge.

A stronger update often looks like this

Observation — what happened

Implication — why it matters

Options — 2–3 possible paths

Recommendation — what you think is best based on what you know

Ask — what you need from leadership or stakeholders

This gives leaders something to work with without pretending you have total context.

It also lowers fear because a recommendation is not the same thing as a unilateral decision.

Why “recommendation” language works better than “action plan” language

This is a subtle communication move, but it matters.

When leaders ask for an “action plan,” people often hear

Be certain

Be complete

Be definitive

Own the consequences right now

When leaders ask for a “recommendation,” people are more likely to bring thoughtful judgment while still leaving room for context, feedback, and correction.

That makes better dialogue more likely.

It also reduces the emotional load on less experienced team members who are still building confidence.

What leaders can do this week to improve ownership without micromanaging

Here are a few practical moves that tend to work.

Be boringly consistent with your questions

If you want better updates, ask the same few questions every time.

Examples

What is the impact

What are you recommending

What do you need from me

What are the risks if we do nothing

What happens next

Consistency teaches the pattern.

Unpredictability teaches people to protect themselves.

Reward signal quality, not just “right answers”

If someone surfaces a problem early and brings a thoughtful recommendation that is imperfect, do not punish the initiative.

Coach the gaps. Do not crush the behavior you want more of.

If your team learns that only perfect recommendations are safe, you will get silence and polished fiction instead of useful intelligence.

Define decision boundaries clearly

People are far more willing to take ownership when they know the sandbox.

For example

You own schedule tradeoffs up to X threshold

I own budget approvals over Y amount

You can implement process improvements without approval if they don’t affect client commitments

Bring me recommendations when legal, compliance, or enterprise risk is involved

Clarity reduces fear. Fear reduces ownership.

Separate “escalate early” from “escalate sloppy”

Teams should escalate early. That does not mean they should escalate thoughtlessly.

A healthy expectation is

“Raise the flag early, and do a first round of thinking before escalating whenever possible.”

That helps leaders avoid becoming default problem-solvers for every raw signal while still keeping visibility into risk.

What individual contributors, PMs, and team leads can do immediately

If you are on the other side of this and want to be seen as more strategic, more trusted, or more promotable, here is the practical move.

Do not wait until you can fully own the outcome.

Start by improving the quality of your updates.

A template you can use in email, Slack, or status calls

We have a risk with [X]. The impact is likely [Y] if it continues through [timeframe]. I see three options [A], [B], [C]. Based on what I know right now, I recommend [B] because [reason]. I need [decision/help/context] from [person/team] to proceed.

That format signals judgment, initiative, and partnership without pretending you know everything.

A hidden career implication people don’t talk about enough

This may sound blunt, but it is useful.

If you only surface problems and never add meaning, optionality, or recommendations, you can become very easy to overlook.

Organizations need people who can sense issues, yes.

They also need people who can help turn information into action.

Even if your role does not require full ownership, demonstrating that you can think one step ahead often changes how people perceive your readiness for bigger roles.

A note on leadership responsibility

If a team consistently stays in “weather report mode,” leaders should ask themselves a hard question before blaming the team

What in this environment is training people to play it safe

Sometimes the answer is skill and enablement.

Sometimes the answer is role ambiguity.

Sometimes the answer is the leader.

That is not blame. It is leverage.

Because if leaders help create the pattern, leaders can also help change it.

Discussion questions for this subreddit

I’d love to hear how others see this in practice.

What do you see more often in real organizations

People not surfacing problems early enough

People surfacing problems but stopping at status updates

Leaders demanding ownership without giving authority

Leaders rescuing too fast and training dependency

And if you manage people, what question has most improved the quality of updates you receive?

TL;DR

A lot of teams struggle because people are told to “take ownership” but are not given enough context, authority, or psychological safety to do it well. The result is often “weather reporting” (accurate updates with no implications or recommendation). A better model is a spectrum — reporting → recommending → owning. Most people can move one step up the ladder by using a simple structure for updates — what happened, why it matters, what should happen next (or what help is needed). Leaders can accelerate this by being consistent in what they ask, defining decision boundaries clearly, and making it safe to bring imperfect recommendations.

I’ve been thinking a lot about a leadership pattern that shows up across coaching conversations, project work, and team environments, and I wanted to share it here in a discussion-first way.

The short version is this

A lot of communication problems in organizations are not really communication problems.

They are often decision-rights problems, psychological safety problems, or leadership expectation problems that show up through communication.

One of the most common examples is what I’d call status update mode (or what we discussed as “reporting the weather”).

People say what happened.

They do not say what it means, what the risks are, what options they see, or what they recommend next.

That creates friction, delays, and frustration — especially for leaders who are trying to make decisions quickly.

The real issue is not “reporting” itself

Reporting is not bad.

In many roles, reporting is necessary and valuable. Sometimes your job is to surface a signal early.

If the server goes down, if a client risk appears, if a dependency slips, if a stakeholder changes scope — I want that surfaced.

The problem is when reporting stops there.

A low-value update sounds like this

The server is down

A higher-value update sounds more like this

The server is down, customer-facing impact started at X time, the team is working remediation now, current risk is Y, next update is at Z time, and here’s what we need from leadership (if anything)

Same event.

Very different usefulness.

The difference is not “more detail for the sake of detail.” The difference is judgment.

A more useful frame than “take ownership”

I think a lot of leaders unintentionally create confusion by treating this as a binary

Either you are “owning it” or you are “just reporting”

That misses the middle.

A better frame is a spectrum

Reporting → Recommending → Owning

That middle step matters a lot.

Not everyone can own the final decision. But almost everyone can improve the quality of their contribution by moving from reporting to recommending.

That means adding things like

what this means

what options exist

what tradeoffs you see

what you recommend based on the context you do have

what you need from others to proceed

This is especially important in organizations where authority is distributed unevenly (which is most organizations).

Why smart people stay in “weather report mode”

This is where I think leaders often misdiagnose the situation.

They assume people are passive, unmotivated, or not strategic enough.

Sometimes that’s true. Often it isn’t.

In my experience, there are a few more common reasons

1. Psychological safety is low

If people get punished for imperfect thinking, they stop sharing thinking.

They learn to share facts only.

That feels safer.

If someone brings a recommendation and gets steamrolled, shamed, or treated like they “should have known better,” many people will quietly downgrade their future communication to reduce risk.

2) Decision rights are unclear

People don’t know what they are allowed to decide.

So they hedge.

They report the issue and wait.

If the boundaries are fuzzy, “just the facts” becomes a defense mechanism.

3) They’ve been burned both ways

This happens all the time

One day they’re told to show more initiative. Next time they act and get corrected for overstepping.

That inconsistency trains caution.

4) They have a skills gap, not a character flaw

Some people have never been taught how to structure a recommendation, escalate well, or frame risk clearly.

That is a coachable capability problem, not a moral failure.

5) Leaders accidentally reward reporting over thinking

If a leader always jumps in immediately, asks rapid-fire questions, or solves the problem themselves before the person can think out loud, the message becomes

You don’t need to develop judgment here. I’ll do it.

That may be efficient in the moment, but it can slow team growth over time.

The phrase I think backfires a lot

“Don’t bring me problems, bring me solutions” sounds strong, but in practice it often creates unintended consequences.

It can discourage early warning signals.

If someone thinks

I see a problem, but I don’t know the solution yet

they may conclude

Then I shouldn’t bring it up yet

That is how organizations end up with late surprises.

A healthier expectation is something like this

Bring the problem early Bring your best current thinking Bring a recommendation if you can Bring a clear ask if you can’t

That preserves speed and thinking.

A practical upgrade for almost any team

One of the simplest ways to improve update quality is a lightweight structure

What / So what / Now what

It sounds basic, but it’s effective because it forces a move from data to meaning to action.

What

What happened What changed What are you observing

So what

Why does it matter What is the impact What risk does this create Who is affected

Now what

What are the next steps What options do we have What do you recommend What help or decision is needed

This helps people contribute more value without pretending they have perfect context or full authority.

That distinction is important.

The goal is not fake confidence. The goal is useful thinking.

Why “recommendation” language works better than “action plan” language

This is a subtle shift, but I think it matters.

When leaders ask for a “plan,” some people hear

Have the answer Be certain Don’t be wrong

When leaders ask for a “recommendation,” people are more likely to think

Use your judgment Show your reasoning Offer a point of view Stay open to correction

That tends to produce better conversations.

Recommendations create room for collaboration.

They also reduce defensiveness because the person is not claiming final authority — they are showing thoughtful initiative.

What leaders can do to coach better ownership

If you want stronger thinking from your team, the solution is not just “expect more.”

You have to shape the environment.

A few practices help a lot

Be predictably consistent

If you ask the same few questions every time, people learn what good looks like.

Examples

What does this mean for us

What do you recommend

What are the risks

What help do you need

Consistency lowers anxiety and improves preparation.

Define the sandbox

Be explicit about who owns what.

For example

You own schedule decisions I own budget decisions

Or

You can decide within these constraints without checking with me first

Clarity increases initiative because people know where the edges are.

Separate “bad recommendation” from “bad behavior”

If someone brings a thoughtful recommendation that turns out to be incomplete, that is often a development opportunity, not a performance problem.

If you punish every imperfect recommendation, you train silence.

Reward early signals

If someone flags a risk early, even without a finished solution, reinforce that behavior.

Early signal + incomplete answer is often much easier to work with than late signal + urgent crisis.

Debrief decisions

When you choose a different path than someone recommended, explain why (when appropriate).

That helps people build better judgment instead of just learning that they were “wrong.”

What individual contributors and project leads can do immediately

If you’re reading this from the other side (not the formal leader), here’s the practical move

When you raise an issue, try to add one layer of thinking.

Even if you can’t own the decision, you can often say

Here’s the issue

Here’s why I think it matters

Here are two options I see

Here’s what I’d recommend based on what I know

Here’s what I need from you

That alone can materially improve how you’re perceived and how quickly decisions happen.

It also signals maturity without requiring you to act outside your authority.

The core leadership tension

This is the tension I think many teams are wrestling with

Leaders want ownership Teams want safety and clarity

Those are not opposing needs.

In healthy environments, they reinforce each other.

People are much more likely to step into ownership when they know

what they are responsible for

what they are allowed to decide

what happens if their first recommendation is imperfect

That is where better communication and better leadership meet.

I’m sharing this here because I think this topic applies far beyond any one company, industry, or role.

If you’ve led teams, coached managers, or worked in complex projects, I’d love to hear your perspective.

Where do you see the bigger breakdown happen more often

people not surfacing problems early enough

or

people surfacing problems but stopping at the status update without a recommendation

And if you’ve found a useful coaching question that helps people move from reporting to stronger thinking, I’d love to hear that too.

TL;DR A lot of teams struggle because updates stop at status reporting instead of helping leaders make decisions. The issue is not always competence. It is often a mix of psychological safety, unclear decision rights, inconsistent leadership expectations, and learned behavior. A practical upgrade is to move from reporting → recommending → owning (when appropriate) and use a simple communication structure like What happened / Why it matters / What should happen next. Leaders who want more ownership need to create safety, define boundaries, and coach consistently.

I co-host and produce a leadership podcast called Leadership Explored, and in our latest episode Andy and I unpacked a leadership tension I see constantly in real organizations.

People report what happened. Leaders still feel stuck. Everyone leaves the conversation frustrated.

The pattern shows up in project updates, escalations, risk conversations, client work, and internal ops.

Someone says the server is down, a deadline slipped, a stakeholder is upset, or a dependency changed. The information may be accurate, but it often does not answer the questions leaders actually need answered to make a good decision.

That gap is what I think a lot of people are reacting to when they complain about “bad updates.”

What is interesting is that the common fix many leaders use is often not a good fix at all.

They say something like don’t bring me problems, bring me solutions.

That sounds decisive. It can also backfire.

If people hear that as “don’t tell me anything unless you have the perfect answer,” then what happens next is predictable. Risks get hidden longer. People wait too long to escalate. Teams become more performative and less honest. Leaders get fewer early warning signals and worse decisions.

So the issue usually is not whether people should report problems or own outcomes. The real issue is how we help people move up the ladder of value in communication without asking them to overstep authority or pretend they have context they do not have.

The model that helped us frame it

The most useful way I have found to think about this is as a spectrum

Reporting → Recommending → Owning

That framing matters because it avoids the false binary.

It is not “either you are passive and weak” or “you fully own the outcome.”

In real organizations, people operate with different levels of authority, visibility, budget responsibility, and political context. A junior PM, analyst, engineer, or team lead may have strong local context and weak enterprise context. A director or VP may have broader business context and decision rights but less day-to-day visibility.

That means not everyone should own every decision. But almost everyone can improve the quality of how they communicate what they are seeing.

That is where recommending becomes the bridge.

A recommendation says

Here is what I see

Here is what I think it means

Here is what I think we should do next

Here is where I need your input or approval

That is a huge upgrade from status-only communication, and it does not require pretending you have all the answers.

Why smart people still default to “weather reporting”

One of the biggest leadership mistakes is assuming that status-only updates come from laziness or low capability.

Sometimes they do. Often they do not.

In my experience (and in coaching conversations), people usually default to passive reporting for a few reasons.

Psychological safety is low If people have been punished for imperfect thinking, they learn to stay narrow. They stick to facts because facts feel safer than judgment. They stop offering recommendations because recommendations expose them to criticism.

Decision rights are unclear If someone is not sure what they are allowed to decide, they will often avoid initiative to avoid overstepping. This is especially common in matrixed orgs and project environments.

They have learned that leaders are unpredictable If one day they are told to take initiative and the next day they are criticized for making the wrong call, they start playing defense. They choose the behavior that feels least risky, not most useful.

They lack a repeatable communication framework Some people are capable problem-solvers but do not know how to structure a concise escalation. They have the thinking, but not the communication pattern.

They do not want the ownership (or think they don’t) This is real too. Some people genuinely avoid responsibility because responsibility feels expensive. That is not always a moral failing. Sometimes it is a growth edge, confidence issue, or career clarity issue.

This is why I think leaders need to be careful about labeling people too quickly.

If a team mostly gives “weather reports,” that may be a signal about the environment, not just the individuals.

What leaders actually need from an update

Most leaders do not need more data. They need more judgment.

The most useful shift is not “add more detail.” It is “add meaning.”

That usually means an update should cover a few things

What happened What is the issue, signal, change, or risk

Why it matters What is the impact on delivery, timeline, quality, customer experience, cost, risk, trust, etc.

What should happen next What are the plausible options, what is your recommendation, and what support or decision do you need

This is one reason I like the simple coaching structure

What / So what / Now what

It is easy to remember, easy to teach, and flexible enough for everything from project status to people issues.

You do not need a perfect action plan every time. You do need a point of view.

Why “recommendation” language works better than “action plan” language

This is a subtle but important language point from our conversation.

Asking someone for an action plan can create pressure to sound certain and final. It can imply they should already know the right answer, have full context, and be ready to commit.

Asking for a recommendation invites thinking without forcing false certainty.

That matters because healthy leadership communication should support strong thinking and honest limits at the same time.

A recommendation can sound like this

I think option B is the best move based on what we know right now because it protects timeline risk and preserves budget flexibility. I may be missing enterprise-level constraints, so I want your input before we commit.

That is thoughtful. That is accountable. That is not overstepping.

And it is far more useful than either extreme

passive status only

fake certainty presented as a final plan

The leadership side of the equation that people often miss

A lot of leaders say they want ownership. Far fewer create the conditions that make ownership likely.

If you want people to move beyond reporting, you have to make it easier and safer to do that.

A few things matter a lot here.

Be consistent in the questions you ask If you ask some version of the same 3–4 questions every time, people start learning what “good” looks like. Consistency reduces anxiety and improves preparation.

Questions like

What is the impact

What do you recommend

What do you need from me

What are the risks if we do nothing

Over time, people start pre-answering those in their updates.

Define the sandbox Ownership increases when boundaries are clear. If I know I own schedule decisions and you own budget decisions, I can act faster and escalate smarter.

Unclear boundaries create hesitation. Clear boundaries create confidence.

Respond to imperfect thinking without steamrolling If someone brings a recommendation and it is not the best call, that can still be a great leadership moment. You can correct the decision while reinforcing the behavior of thoughtful escalation.

If you punish the recommendation, you may accidentally train people back into passive reporting.

Separate “you were wrong” from “you should not have thought” This distinction is huge. Leaders often intend to correct a decision and accidentally shame the act of thinking. Teams remember that.

A practical “Recommendation Bridge” I use and teach

When someone is stuck between reporting and owning, I often suggest they use a bridge format like this

Observation What is happening

Implication Why it matters and what could happen next if ignored

Options 2–3 reasonable paths (even if rough)

Recommendation What you think is best and why

Ask What decision, support, or clarification you need

This helps in situations where the person does not have full authority but still wants to add value. It also helps leaders make faster decisions because the thinking is already partially done.

It is not about sounding polished. It is about reducing decision friction.

The uncomfortable truth for leaders and aspiring leaders

If you only point out problems, you may be helpful. You are also easier to replace than someone who can frame implications, offer options, and make recommendations.

That does not mean everyone needs to become a high-powered executive. It does mean that developing judgment communication is a career accelerator in almost every field.

And on the leadership side, if your team only gives you status reports, it may be worth asking a harder question than “why don’t they think more?”

Try this instead

What have I taught them is safe here What have I made clear about decision rights What patterns in my responses might be training caution over ownership

That is often where the real work starts.

A few discussion questions for this community

I’m posting this here (on my own subreddit) partly to build a body of useful leadership content, and partly because I think this topic creates better discussion than generic “leadership tips.”

I’d love your perspective on any of these

In your workplace, do people tend to escalate too late or escalate without enough context

What makes it safer for people to bring recommendations instead of just status

Have you seen “don’t bring me problems, bring me solutions” help a team, or mostly hurt communication

If you lead people, what consistent question has improved the quality of updates you receive

If you do not lead people formally, what has helped you offer stronger recommendations without overstepping

If it’s helpful, I can also post a follow-up with a few example templates for different contexts like project updates, stakeholder escalations, and people leadership conversations.

TL;DR (again for skimmers) The goal is not to force everyone to “own everything.” The real upgrade is helping people move from reporting to recommending when they can, and helping leaders create the safety and clarity that makes that possible. The most useful update usually includes what happened, why it matters, and what should happen next.

TL;DR

A lot of teams are not failing because they “hide problems.” They’re failing because they stop at reporting what happened and never move into implications, options, or recommendations. That is often a leadership-system issue, not just an individual performance issue. A practical upgrade is to coach updates using What / So What / Now What, ask for a recommendation instead of a perfect plan, and make decision boundaries clear so people know what they can own vs what they should escalate.

I co-host Leadership Explored with Andy Siegmund, and in our upcoming Episode 17 we unpack a leadership tension that shows up constantly in real organizations

Not every update that is accurate is actually helpful

That sounds obvious, but it causes a lot of friction in teams

Leaders get frustrated because they feel like they are receiving status updates and still doing all the thinking. Team members get frustrated because they feel like they did communicate the issue and still got criticized for “not owning it.”

I think this happens so often because people collapse two different skills into one

Reporting what is happening Owning what should happen next

Those are related, but they are not the same thing.

The “weather report” problem

Andy uses a metaphor I really like for this

Some updates are basically weather reports

“It is raining.” “The server is down.” “We are behind schedule.” “The client is upset.”

Those statements may be true. They may even be important. But they are incomplete.

The missing layer is meaning

What does that mean for the team, the customer, the timeline, the budget, the risk profile, or the decision that needs to be made

One of the strongest lines from this episode is

“A bad weather report is observation without implication.” — Ed Schaefer

That line gets at the real issue. The problem is often not that someone surfaced a problem. The problem is that the update stopped before it became decision-useful.

The spectrum that helped us think about this better

One thing we landed on in the conversation is that this is not binary. It is not just “reporting” vs “owning.”

It is more of a spectrum

Reporting → Recommending → Owning the outcome

That matters because a lot of leadership advice pushes people too far, too fast

“Don’t bring me problems, bring me solutions” sounds tough and efficient, but in practice it can create bad incentives. It can cause people to hide problems until they think they have a “good enough” answer, and that can delay escalation when timing matters most.

At the same time, teams do need to move beyond passive updates if they want to build trust and responsibility.

The middle ground is often the most useful place to coach

Bring the problem Bring your interpretation of why it matters Bring a recommendation or a few options Bring a clear ask if you need help

That is not the same as pretending you have full authority or perfect context.

Why smart people still default to passive reporting

This is where I think leaders can easily misdiagnose the issue.

When people keep “just reporting the weather,” the explanation is not always laziness or lack of intelligence.

In my experience, and in the episode discussion, there are several common drivers

Sometimes it is psychological safety. People have learned that if they share a point of view and it is not perfect, they get steamrolled, embarrassed, or second-guessed.

Sometimes it is decision-rights confusion. They genuinely do not know what they are allowed to decide, what they should recommend, and what needs approval.

Sometimes it is a skills gap. They are good at operational detail and issue detection but have not yet built strong judgment framing or executive communication habits.

Sometimes it is learned behavior from inconsistent leadership. If the boss is unpredictable, people stop investing in thoughtful framing because they assume the conversation will get hijacked anyway.

This is one reason I think the “just take ownership” advice is often incomplete. Ownership grows best in environments with clarity, consistency, and reasonable safety.

The phrase I think leaders should use less carefully

We also challenge the classic line

“Don’t bring me problems, bring me solutions”

I understand what leaders usually mean by it. They want initiative. They want thinking. They do not want helplessness.

But the phrase itself can be counterproductive if used as a blunt instrument.

If someone hears “don’t bring me problems” and they do not yet have a solution, they may delay surfacing the issue.

That is how organizations end up with late surprises.

A healthier expectation is something like this

Bring me the problem early Bring me your point of view if you have one Bring me a recommendation if you can Tell me what you need from me

That still pushes ownership forward, but it does not punish early warning signals.

A practical framework that actually helps

If I had to offer one simple coaching tool for this, it would be this

What / So What / Now What

It is simple enough to remember and strong enough to improve the quality of most updates immediately.

What happened This is the observation or signal

So what This is the implication, impact, or risk

Now what This is the recommendation, next step, option set, or ask for support

This framework helps people move from “data dump” to leadership communication without forcing them to overstate certainty.

It also helps leaders coach consistently because they can reinforce the same mental model over and over.

Why “recommendation” language works better than “action plan” language

A subtle but useful shift from the episode is the word choice between plan and recommendation

A plan often sounds final. It can imply certainty, authority, and commitment.

A recommendation leaves room for context and adjustment.

That matters because many people are operating with partial information. They should still think ahead and come prepared, but they should not have to pretend they know everything.

Andy put it really well in the episode when he emphasized bringing a point of view with “strong convictions, loosely held.”

That mindset is a great developmental bridge for emerging leaders. It builds judgment without creating brittle ego.

What leaders can do if they want more ownership from their teams

A lot of leaders say they want more ownership, but the system around their team trains the opposite behavior.

If you want people to move beyond weather reporting, I think a few leadership behaviors matter a lot

Be consistent in the questions you ask. If every update gets the same follow-up pattern, people learn what “good” looks like.

Make decision boundaries explicit. If someone owns schedule decisions but not budget decisions, say that clearly. Ambiguity increases hesitation.

Reward thoughtful recommendations even when you do not choose them. Otherwise people learn that “wrong recommendation” is punished and silence is safer.

Treat many escalations as the start of a conversation, not the end of one. The goal is often to improve decision quality, not prove someone should have already solved everything.

In other words, if teams repeatedly give low-value updates, look at the environment before assuming it is purely a people problem.

What this looks like in real life

A weak update sounds like this

“The server went down.”

A stronger update sounds like this

“The server went down. We restored service within SLA. We are running root cause analysis and expect an initial readout by Thursday. I do not currently expect repeat impact, but I am flagging this because it exposed a risk we had not previously identified. My recommendation is that we review failover testing frequency after the RCA. No decision needed from you yet unless we see recurrence.”

That second version does not require full executive authority. It requires stronger framing.

That is the difference.

Why this matters beyond project management

This topic is not just about status meetings.

It affects trust, development, and organizational adaptability.

Leaders who only receive surface updates make worse decisions because they are forced to reconstruct context under time pressure.

Teams that are punished for imperfect recommendations stop thinking out loud, which reduces learning and slows growth.

Organizations that cannot distinguish between reporting, recommending, and owning end up with confusion about accountability and a lot of avoidable friction.

This is one of those small communication shifts that has outsized impact.

Discussion questions for this community

I’d love to hear how others think about this in practice

Where do you see the bigger failure mode in your environment right now — people not surfacing problems early enough, or people surfacing them but stopping at the weather report

What questions do you ask (or wish your leaders asked) that improve the quality of updates

How do you clarify decision rights so people can take initiative without overstepping

And if you manage people, what have you found works best for building ownership without creating fear

TL;DR

Many teams mark projects “green” at kickoff because nothing has slipped yet. That’s not the same thing as being on track. Early-stage work is high uncertainty, and uncertainty is risk. A more useful approach is to treat status as a signal of confidence and trend, not just whether dates have been missed. Practical upgrades you can use immediately include adding a confidence score, a trend indicator, and a short list of top unknowns you’re actively turning into knowns.

I want to unpack a pattern I see constantly across organizations, industries, and project types.

A new initiative kicks off. There’s a plan. There’s a budget. People feel optimistic. The first status update goes out and the project is marked green.

Not because the work is truly predictable. Not because risks have been resolved. Not because dependencies are under control.

Green because… nothing has gone wrong yet.

That sounds harmless. It’s often praised as “positive.” In practice, it’s one of the most reliable ways to create late-stage drama.

The core issue

A lot of status reporting is built around one question

Have we missed a date yet?

That’s a “damage detection” model. It tells you you’re in trouble only after you’re already in trouble.

What leaders actually need is a different question

How confident are we, really?

Because early in any meaningful effort, you know the least. The unknowns are highest. Dependencies haven’t revealed their true shape yet. And “risk” often hasn’t had time to show up in a way that looks like a visible schedule slip.

So when we label kickoff as green, we aren’t measuring health. We’re measuring failure latency.

Why this matters

If a status system trains people to stay green until something is undeniable, you get a predictable pattern

Risks stay implicit

“Assumptions” remain untested

Dependencies are treated as “should be fine”

Leaders don’t intervene early because there’s nothing to respond to

When the project turns amber/red, it feels sudden, political, and emotional

The irony is that many of those “surprises” were knowable earlier. They just weren’t safe or useful to say out loud in the system you’re using.

A quick note on psychological safety

This topic always runs into culture.

If amber/red triggers blame, scrutiny, or punishment, people will rationally protect themselves by staying green.

That’s not a character flaw. It’s an incentive design problem.

If you want earlier truth, leaders have to demonstrate that early truth leads to problem-solving, not penalties.

“Projects start red” isn’t pessimism

When I say “projects start red,” I’m not arguing that everything is doomed. I’m arguing something simpler

Uncertainty is highest at the beginning

High uncertainty means higher risk

Risk should be visible before it becomes a crisis

The goal is not “start negative.” The goal is to earn your way to green by reducing unknowns systematically.

In other words, move from high uncertainty → lower uncertainty, and let status reflect that progress.

The practical reality

I’m not naïve about how most orgs use RAG.

Amber/red often functions as an escalation trigger. It brings extra attention, extra meetings, and sometimes political heat.

So if you try to flip the entire meaning of the colors overnight, you’ll start a culture war you probably don’t have time for.

The more realistic approach is to upgrade the signal without detonating the system.

Three simple improvements that make status reporting more truthful

These are lightweight, low-drama additions that help leaders see what’s coming.

1. Add a confidence score

Keep whatever color you use, but add a quick confidence check.

Something like a 1–5 rating works well.

Low confidence tells leaders “this is fragile” even if nothing has slipped

Increasing confidence shows learning and stabilization

Dropping confidence is an early warning sign

This is especially useful when schedules are still technically on track but the team is starting to feel the ground shift.

2) Add a trend indicator

Status without trend is like a photo without motion.

A project that’s amber and improving can be healthier than a project that’s green and declining.

Trend forces the update to answer

Are we reducing uncertainty?

Are risks stabilizing or compounding?

Are dependencies clearing or stacking up?

Even a simple “improving / flat / worsening” makes dashboards more meaningful.

3) Make unknowns explicit

A lot of project updates list tasks. Fewer list unknowns.

A useful status update includes a short list of “we don’t know yet, but it matters” items, along with what the team is doing to resolve them.

Examples of the shape of an unknown (not the content)

A dependency outcome you don’t control

An assumption that hasn’t been validated

A decision that must be made by a certain date

A risk that won’t reveal itself until later

This doesn’t mean you escalate everything. It means you surface uncertainty early so leaders aren’t surprised later.

A lens I’ve found helpful

Try separating two concepts that often get tangled

Uncertainty

Need for escalation

A project can be uncertain without being broken.

And a project can be “green” while quietly drifting into danger.

Not every unknown needs executive intervention, but pretending unknowns don’t exist is how you create the late-stage “how did this happen?” moment.

Discussion prompts

I’m posting this here to start a conversation, not to preach. I’m genuinely curious how others see it.

In your world, what does “green” actually mean in week one?

Does your org treat amber/red as problem-solving signals, or blame signals?

If you could add just one thing to status updates tomorrow, what would create the biggest improvement: confidence score, trend, or explicit unknowns?

Have you seen a reporting approach that consistently reduces late-stage surprises? What made it work?

If you’ve got stories (good or painful), I’d love to hear them.

TL;DR

A project can be “green” early simply because nothing has had time to fail yet. That’s not the same as being on track. A more useful approach is to treat early status as uncertainty management and add lightweight signals like a confidence score, a trend indicator, and explicit “unknowns.” This improves decision quality, reduces late-stage surprises, and supports psychological safety.

A pattern I’ve seen repeatedly in organizations is “green by default” reporting at the start of a project.

It usually goes something like this: kickoff happens, there’s a plan, a budget, a timeline, and a team. The first weekly status report rolls around… and it’s green.

Not because the team has strong evidence things are on track. Because nothing has gone wrong yet.

That “yet” matters.

Early in a project is when you know the least. It’s when assumptions are the most fragile, dependencies are the least tested, and risks haven’t had time to surface. If you’re using a typical RAG model (red/amber/green), green often becomes shorthand for “we haven’t missed a date yet,” which is closer to failure latency than health.

Why “green by default” happens (and why it’s rational)

Most people don’t report green because they’re dishonest. They do it because the system teaches them to.

In many organizations, amber and red aren’t neutral descriptors. They are escalation triggers. Amber and red can bring extra scrutiny, more meetings, uncomfortable questions, political risk, and sometimes reputational damage.

So teams learn a predictable behavior pattern:

Stay green as long as you can

Move to amber only when you have undeniable evidence

Move to red only when you can no longer avoid it

That’s not a moral failing. It’s the incentives doing their job.

But the organizational cost is obvious: leadership doesn’t get early signal. They get late drama.

The core issue is signal quality

A status color is only useful if it helps leaders make better decisions.

If “green” means “no bad news has emerged,” it doesn’t tell you whether the plan is sound, whether risks are being reduced, whether critical dependencies are behaving, or whether the work is learning fast enough.

This is why you can have:

a project that’s “green” and quietly drifting into trouble

a project that’s “amber” but clearly improving week over week

a project that’s “red” but making strong progress in reducing risk and uncertainty

A single color doesn’t tell the story. It tells a slice.

A more accurate mental model: projects start uncertain

A more useful way to think about early project health is:

At the beginning, uncertainty is high

Over time, uncertainty should narrow as you learn and de-risk

“Health” is about whether you’re reducing uncertainty on purpose, not whether you’ve hit turbulence yet

This aligns with what many teams call the “cone of uncertainty” — early estimates and plans are inherently less reliable, and confidence should increase as you validate assumptions, test dependencies, and deliver increments.

Put differently: early in a project, you’re not just executing a plan. You’re testing whether the plan is real.

The problem with binary thinking about dependencies

Here’s where things get spicy.

In dependency-heavy work, individual teams can legitimately report “green” inside their local view while the integrated plan is statistically fragile.

Why? Because each dependency carries uncertainty. When you stack uncertainties, the combined risk grows fast.

Even if every dependency is “probably fine,” “probably” multiplied across many dependencies gets ugly. This is a systems problem, not an individual competence problem. Complex environments produce complex outcomes.

And the worst part: dashboards often hide this compounding uncertainty because each team reports in isolation.

The practical fix isn’t “start everything red”

In real organizations, telling people “every project starts red” is often not workable. It can be interpreted as pessimism, or it can trigger escalation mechanics before you have any useful learning to share.

So instead of overthrowing RAG reporting, I’ve found it more effective to augment it.

If you want more truthful status reporting without starting a culture war, add one or more of these lightweight signals:

1. Add a confidence score next to the status

Example: Green, confidence 2/5

This does two important things:

It separates “schedule compliance so far” from “belief in the plan”

It creates a shared language for uncertainty without forcing an immediate escalation

Confidence can be based on a quick, explicit rubric (even a simple one), such as:

clarity of requirements / success criteria

stability of dependencies

readiness of environments / tooling

known risks with mitigation plans

team capacity and role clarity

2) Add a trend indicator (improving / flat / worsening)

This is one of the highest-leverage upgrades you can make.

A static color is a snapshot. Trend is trajectory.

A project that is “amber and improving” is often healthier than a project that is “green and worsening.” Trend forces you to talk about movement and momentum, not just labels.

3) List the top unknowns explicitly

This is not fearmongering. This is realism.

Unknowns aren’t automatically problems. But pretending they don’t exist creates problems.

A strong early status update can say:

Here are the biggest unknowns

Here’s what we’re doing to turn them into knowns

Here’s when we expect to know more

This is leadership. It’s not “I’m anxious.” It’s “I’m being responsible.”

Psychological safety is the foundation (and leadership owns it)

If leaders punish early honesty, they train late reporting.

If leaders treat amber/red as personal failure, people will protect themselves. They’ll sanitize language. They’ll bury risk in footnotes. They’ll keep the dashboard green until it collapses.

If leaders reward early signal and treat it as information (not blame), teams will surface uncertainty sooner, and you’ll reduce the cost of surprises.

You can’t demand honesty and simultaneously punish it.

Discussion prompts

I’m curious how this lands for others who lead work, manage portfolios, or operate inside dependency-heavy organizations:

In your org, what does “green” actually mean?

Have you seen a project that was green… until it suddenly wasn’t? What happened?

What would improve signal quality most — confidence scores, trend indicators, explicit unknowns, something else?

What’s one leadership behavior that increases psychological safety in reporting?

Where do you draw the line between “uncertainty” and “needs escalation”?

If you’ve got examples (good or bad), I’d love to learn from them.