It's not luck. It's not personality. It's design.
There's a manager type everyone knows.
You've either worked for them or you've heard someone describe them with a specific kind of reverence; the kind that sounds less like admiration and more like relief. Things just get to them early. Problems surface before they become disasters. Someone always seems to say something before it's too late. And when you ask how they run their team, they usually shrug and say something vague about keeping the door open.
The door has nothing to do with it.
To boot, we asked founders, operators, and people managers a single question: when did you last hear genuinely bad news from your team before it became a crisis? 60% of respondents said they either usually find out late or honestly weren't sure. Another thirty-six percent said it happens, but not consistently. Only one in four said their team tells them things early.
The easy read on those numbers is that most teams have a communication problem. The accurate read is different: most managers have an experience design problem, and they don't know it.
The calculation your team is running

Every time someone on your team almost tells you something uncomfortable, they are running a fast and largely unconscious calculation. The variables change person to person, but the logic is always the same: is bringing this to you worth it?
Now, they know it's important. The question is what happens next. Will you listen, or will you defend? Will you act on it, or will it disappear into the noise of your schedule? Will bringing this make you see them as a problem-solver or as a problem? And most critically, will what you do in the next ten minutes make them more or less likely to come back next time?
The managers who find out early have answered those questions well, repeatedly, over time. Not through policy. Not through a stated commitment to transparency. Through what actually happened in the moments that counted.
What "designing for honesty" actually looks like
Marcus Buckingham, whose new book Design Love In is built around decades of research on what makes people perform at their best, makes a point that applies well beyond its original context: human behaviour doesn't shift in response to mildly positive experiences. It shifts when experiences cross what he calls an emotional threshold; when someone doesn't just think that was fine but registers something more like I want more of that.
The same logic applies to your team's relationship with honesty. A single good conversation where you received bad news well will not rewire anything. But five of them, stacked across months? That starts to move the needle. People start to carry information to you differently. The calculation changes.
Buckingham's research identifies five conditions that, when built into an experience in sequence, make people most likely to genuinely love it: control, harmony, significance, warmth, and growth. Harvard Business Review He was writing about customer and employee experience broadly. But map those five to the specific moment when someone is deciding whether to bring you a problem, and something sharpens.
Control is whether your team member feels like they have agency in the conversation: like they're bringing you information, not submitting to an audit. If your first instinct when bad news arrives is to take over, investigate, and assign blame, you've removed their sense of control. They will not be back soon.
Harmony is whether the experience is emotionally coherent. Buckingham gives a precise example: nurses who administer injections with the least pain are those who, before starting, tell their patients clearly that there will be a bit of pain. Blogternator The warning doesn't make it hurt more. It makes the experience feel honest, which makes it tolerable. When you tell your team that you prefer hard news early and then visibly panic when it arrives, the dissonance is deafening. They heard what you said. They learned what you meant.

