Part of the Pressure Intelligence™ framework
guide
Member
Member
Member

The Last to Know

A field guide for a leader who hears about problems too late: bad news often travels slowly, and you can learn to hear it while the fixes are still cheap.

The Last to Know
96
the-last-to-know

Why bad news travels slowly through a team, and how to hear about problems while the fixes are still cheap.

Between people and teams

The challenge: Problems surface after they’re expensive to fix

Most trouble starts small, noticed by someone close to the work, and grows more expensive with each week it takes to reach someone who can act. Carrying bad news has a cost for the person who carries it, pressure raises that cost, and whether people speak up depends on what happened the last time someone did. Telling a team the door is open rarely undoes that lesson. The guide helps you make early news cheaper to bring than late news, so risks reach you while the fixes are still small.

Who it’s for: Leaders who hear about problems after they are expensive: a manager, a program lead, a function head, anyone whose team sees trouble weeks before it reaches them. Read it on your own first, then take the conversation in part three to your team.

How it shows up

Part 1 of 3 · Notice the effect. The scene, where it lands, and the questions that often sit with you before you fix anything.

The scene

A project review goes smoothly. The status is green, the questions are easy, and the meeting ends early. Three weeks later the same project is in trouble, and the fix that would have taken one conversation in the first week now takes a re-plan, a later launch and a difficult conversation with a customer. In the debrief it becomes clear that several people saw it coming. They mentioned it to each other. They padded their estimates. They did not bring it to the room, and when the leader asks why, the answers are vague, because the true one is uncomfortable to say out loud: the last time someone raised a risk like this, it did not go well for them.

Where it lands

  • In you: problems tend to reach you when they are already expensive, and you are often the last to learn something the people closest to the work saw weeks earlier.
  • In your team: concerns typically come up in the hallway after the meeting, estimates carry extra padding, and quick agreement in the meeting turns into resistance afterward.
  • In your organization: customers, auditors or partners often find issues before anyone inside reports them, and each layer of the hierarchy softens the picture a little on its way up.

Questions to ponder

Think of the last piece of bad news that reached us late, and ask:

  • Who saw it first, and how long before it reached us?
  • Did they say anything, to anyone?
  • If they did, where did it go, and why didn’t it change anything?
  • Is there a regular moment in our team’s week where someone would naturally mention a risk?
  • How did we tend to react the last time someone brought bad news early?

Questions to discuss

With what filled the last minute of the meeting on the table, the answers to “What did we not get to that we should have?”:

  • Which views have we heard least in our last several conversations, and what might that be telling us? The missing voice is often the one holding the risk.
  • What pressure are we under that we haven’t said out loud, and why? Pressure that can’t be spoken tends to compound. Naming it, even partly, often frees enough room for the team to start working with it.
  • How could we change the way we work together so that each of us helps the others bring bad news early, and the first person to see a problem has a good reason to say so? Name what you will each do in the first thirty seconds after someone raises a risk, and who goes back to the person whose warning proved right.

Try this week

In your next team meeting, change the last minute. Close with one question: “What did we not get to that we should have?” Then wait. The pause after that question is often the most informative minute of the meeting, and what fills it is often the concern that would otherwise have come up in the hallway. Thank the first person who answers, whatever they say.

Keep reading with a free account

  • How to read what is missing from a room: the voice that didn’t speak, the disagreement that arrived as a clarifying question, the agreement that came too fast
  • What one overruled truth-teller teaches everyone else, and how to undo it
  • Two habits for the first and last minute of the meetings you already run
  • The first thirty seconds after bad news arrives, and the question to ask in place of a reaction
  • The research behind it, and books to read next
  • The toolkit: questions to ponder, questions to discuss, things to subtract, actions to take
  • The kit, as downloads: the full Field Guide, a Leader’s Guide, and slides for the team conversation
Create a free account

Free, no card.

Open the field guide >>

About the author

Mark D. Benson
Mark D. Benson
Founder of Resonant Vector™
Resonant Vector
Full profile →

Mark D. Benson is the founder and principal writer of Resonant Vector, the home of Pressure Intelligence, and the host of Pressure Rising™. He is a product and systems leader who has spent his career running global teams, complex platforms, and consequential decisions under real constraint.

His career sits where strategy, technology and large human systems meet, in places where high stakes are the norm.

Resonant Vector is his commitment to learning in public and sharing what helps leaders and teams perform under pressure.

More about Mark can be found at markdbenson.com.