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.

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.
Part 1 of 3 · Notice the effect. The scene, where it lands, and the questions that often sit with you before you fix anything.
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.
Think of the last piece of bad news that reached us late, and ask:
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?”:
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.
Free, no card.
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.