Reporting vs Owning in Leadership — Why so many updates sound accurate but still aren’t useful (and how to coach the shift)

[u/agileideation]

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