Four Reasons Your Team Tells You Bad News Late
Hello Learners,
This is Learn Leadership. Every issue takes one thing that quietly goes wrong between managers and their teams, shows it happening through a real story, and leaves you with something to try this week.
Today it's the bad news that reaches you on Thursday when your team knew on Monday. You'll leave with a one-line threshold rule, a message that invites half-diagnosed problems, and a standing ten-minute slot for early warnings.
Monday's problem, Thursday's news
Maya found out at 4 pm on Thursday that the data migration would slip by two weeks. She runs a platform engineering team of seven, and that morning she'd told the sales director everything was on track.
Dan, the engineer leading the migration, had known since Monday lunchtime. When Maya asked why she was hearing it now, he gave her four reasons, and none of them was fear of her.
Maya's first thought was that Dan should have been braver. After she'd gone through his four reasons, she dropped it. Every one of them came back to something she'd set up, or never set up.
Each reason is a gap in how the team is set up. You can close all four without changing anyone's personality.
Nobody said how bad counts as bad
On Monday, Dan's test run showed a two-day slip. He didn't know whether two days was worth interrupting Maya for, so he decided to watch it. By Wednesday it was nine days, and by Thursday it was two weeks.
Hospitals stopped leaving this call to judgment years ago. The UK's National Early Warning Score, updated by the Royal College of Physicians in 2017, turns a patient's vital signs into a single number. An aggregate score of 5 or 6 calls for an urgent response, and 7 or more calls for an urgent or emergency response from a team with critical care skills. A junior nurse at 3 am can call for help on the number alone, and nobody asks her whether she was sure it was bad enough.
Give your team the same thing in one line: "Tell me the same day if anything slips more than two days, costs more than $2,000, or involves a client asking something you can't answer." Pick your own numbers and write them down, because an unwritten threshold is only a guess about your mood.
The last messenger got shot
In April, a colleague of Dan's flagged a vendor delay in the team meeting. The first thing anyone said back to her was "How did we not catch this sooner?" Nobody meant it as blame, the whole team heard it as blame, and she kept things to herself for the rest of the quarter.
This reflex runs deep. Leslie John and colleagues at Harvard Business School ran eleven experiments on shooting the messenger, published in 2019. People rated whoever delivered bad news as less likeable, even when the news came from a random draw the messenger had no part in.
The researchers linked it to our need to make sense of bad luck. When something goes wrong, we look for someone to pin it on, and the person standing in front of us is the easiest choice.
Your team remembers the first sentence you said to the last person who brought bad news. Make that sentence the same every time: "Thanks for telling me early." Ask your questions after it, and ask about the problem before you ask about the person.
They wanted the fix first
Dan spent Tuesday and Wednesday trying to solve the slip before raising it. He wanted to walk in with the problem and the answer together, because he thought that's what a good engineer does.
James Detert, then at Cornell, and Amy Edmondson of Harvard found this belief across the organisations they studied. In their paper on implicit voice theories, published in 2011, one of five unwritten rules people use to censor themselves at work is that you need solid data or a solution before you speak up. It feels like diligence, and it costs you days.
If you've ever asked people to bring solutions along with their problems, you've taught your team this rule. Undo it in writing. Send one message this week: "Bring me half-diagnosed problems. Tell me what you know, what you don't know yet, and when you'll know more."
You're always in a meeting
Dan did try, on Tuesday. He messaged Maya at 10:15, and she replied from a planning session: "Can it wait for our one-on-one?" Their one-on-one was Thursday at 3.
Maya had 31 hours of meetings that week. In the same hospital study of nurses, Anita Tucker and Amy Edmondson found that a manager's physical presence on the unit made it more likely problems reached them. Seven in ten nurses they interviewed believed their manager expected them to work through disruptions alone. One said, "My manager is not interested in hearing about things if they are small."
Book a standing ten-minute slot, twice a week, and call it "early warnings." Nothing else goes in it, and you only move it for a real emergency. If nobody has anything, you get ten minutes back.
What to do with all four
Here's the setup for Monday morning, in order:
- Write your threshold line and pin it in the team channel.
- Send the half-diagnosed message.
- Book the twice-weekly early-warnings slot for the next six weeks.
- Put "Thanks for telling me early" on a sticky note next to wherever you take calls.
None of this needs anyone's sign-off, and all four take under an hour.
You'll know it's working when problems start reaching you smaller and less finished. The first few will feel like noise. That's the point: a two-day slip that reaches you while it's still two days is one you can still fix.
Maya did all four that week. Three weeks later, Dan used the Tuesday slot to flag a vendor API that had started responding slowly. It was still a two-day problem when she heard it, and it stayed one.
