Choosing the Number Over Your Team Works This Quarter and Costs You Next Year
Why exhausted managers put the number first, what it gets them this quarter, the loop that makes them more tired by next year, and where a team decides what to tell you.
Think back over last week. Did you move a one-on-one for the third time because the board deck was due? When someone told you about a mistake, did you answer more sharply than you meant to? Did you rewrite a piece of work at six in the evening because that was quicker than explaining what you wanted? In Monday’s meeting, did you tell someone the date wasn’t up for discussion?
None of that makes you a bad manager. With more time, you’d have handled all four differently, and you know it. You sat through the psychological safety training and agreed with every word of it. Then the instruction to build psychological safety landed on you the same way the number did: with a deadline, no room for questions, and from leaders who mostly haven’t built it for you. So you’re carrying both, and most days you’re carrying them tired.
That bind is what Dr. Timothy R. Clark and Junior work through in the latest episode of The Leader Factor, How to Build Psychological Safety When Your Managers Are Exhausted. This piece covers what choosing the number gets you now and costs you later, why nobody builds psychological safety for managers, where your team decides what to tell you, and the first of four stories from the companion guide.
The number wins most weeks, and for a while that works
An hour spent on the number shows up in this week’s report. An hour spent on your team shows up months later as a launch that didn’t slip or a good person who didn’t quit, and nobody reports on things that didn’t go wrong.
In the short term, pressure works, and you may as well admit that to yourself. Each of those four choices saved you time on the day you made it. The number comes in, your boss is satisfied, and nothing visibly breaks.
Meanwhile, your team quietly starts telling you less. Nobody on the team complains, and the work still gets done, so from where you sit the team looks fine. For a while, a team that has stopped telling you things is easier to manage than a team that still does.
Then, a few months on, you start getting surprised. A project is on track in every update until the week it’s late. A customer problem turns out to have been common knowledge on your team for a month. Each surprise takes more of your time than the conversation you skipped would have taken, and the surprise arrives when you have the least time to give. You get more tired, your patience gets shorter, and people tell you less. A good share of the exhaustion you feel now comes out of that loop. And when the number does finally slip, the cause is months old, so nobody, including you, traces the slip back to a skipped one-on-one.
| This quarter | By next year |
|---|---|
| Your meetings end on time | The real discussion happens after the meeting, without you |
| Mistakes get fixed fast | Mistakes get hidden until they’re too big to hide |
| The work gets done your way | Every decision waits for you |
| The plan goes unchallenged | Problems reach you late |
| The number comes in | The number gets harder to repeat, and the people with the most options have left |
Nobody builds it for managers, and you should go first anyway
It’s fair to ask why you should give your team something nobody gives you.
And you’re right that nobody gives it to you. In a survey of 1,160 managers published in Harvard Business Review in 2025, middle managers scored 68 out of 100 on psychological safety, lower than the executives above them at 72.7 and lower than their own teams by 4.2 points.
Why does nobody build it for managers? The likeliest reason is that nobody was asked to. When a company decides to work on psychological safety, it trains managers to give it and surveys employees about whether they got it. Nobody is assigned to give it to the manager.
The leaders above you are also in the same position you are. They answer for a number, they have a boss who doesn’t want surprises, and they tidy up bad news before they carry it upstairs. The pressure that made you tell someone on Monday that the date wasn’t up for discussion is the same pressure that makes your boss short with you. That’s why waiting for your boss to go first doesn’t work: your boss is waiting too.
The practical reason to go first is that nothing else makes your own job lighter for as long. A new hire helps for a quarter, and so does a better tool or a deadline that moves. How your team works together stays with you. And if your own boss is someone you can’t afford to surprise, a team that warns you early is the best protection you have. You end up less stretched, less reactive, and better prepared.
Your team decides what to tell you in small moments you barely notice
The damage to your team doesn’t come from anything you’d recognize as a decision. It comes from small moments that are over almost before you notice them. Someone brings you a problem while you’re in the middle of something else. Someone asks a question you’ve already answered twice. Someone pushes back in a meeting that’s running late. In each of those moments the other person is working out whether coming to you was worth it, and they mostly go by how you react in the first few seconds. People will forgive you for being tired and brief, and even for saying no, as long as those first few seconds told them you were glad they came.
Dr. Clark, who wrote The 4 Stages of Psychological Safety, defines psychological safety as a culture of rewarded vulnerability. Asking a question, admitting a mistake, and disagreeing with the boss are all small risks, and what happens to a person right after they take one decides whether they take the next. Psychological safety develops in four stages, and each stage depends on the stage before it.
- Inclusion Safety. People know they’re accepted on the team as they are.
- Learner Safety. People can ask questions and get things wrong while they learn.
- Contributor Safety. People are trusted to do real work with real autonomy.
- Challenger Safety. People can challenge how things are done, including your decisions, without retaliation.
Pressure tests all four stages. The guide takes one stage at a time and follows one person on your team through three moments when the number came first. Here is the first of them.
Inclusion Safety: when the quarter gets tight, you spend your time on the people who deliver fastest
Inclusion Safety is the first stage of psychological safety, and Dr. Clark’s point about it is that people are owed it before they’ve proven anything. That’s why Inclusion Safety slips first under pressure: when you’re short on time you hand out your attention according to output, and the newest person gets the least of it.
Dana joined your team eight weeks before the end of the quarter.
Week three. The board deck is due, and you move your one-on-one with Dana for the third time. You tell yourself, “I’ll catch up with her properly once this deck is out the door.” Dana concludes, “Third time. I guess I’m not a priority.”
Month two. In every team meeting you go to the same two people for answers. Dana has a concern about the vendor you’re considering and keeps it to herself, because nobody has asked her anything in a meeting since her second week. You tell yourself, “I just need an answer. I don’t have time to go round the table.” Dana concludes, “Nobody asked me. It’s probably nothing anyway.”
Month five. You choose the vendor on a call Dana isn’t on. Dana worked with that vendor at her last company. You tell yourself, “If I add one more person, we’ll never get this on the calendar.” Dana concludes, “They went with that vendor? I could have told them. Not my call, I guess.”
By next year. Dana does exactly the work she’s given and nothing more. The vendor misses its first two deliveries. In Dana’s exit conversation you learn that she could have told you why.
Under each of those moments, the guide gives three things that would have changed how Dana’s story ends. In week three: cut the one-on-one to fifteen minutes before you cancel it; if you have to move it, give the reason and the new time in the same message; start the meeting with a question about Dana’s work before you get to yours. The other six take a few seconds each, and none of them requires more time than you have.
The other three stories, and what to do with them
Luis is two years into the job and tells you, two days before the forecast, that he sent a client last month’s pricing by mistake. Priya is the most senior person on your team, and at six o’clock on Wednesday you open her deck to fix two slides and rewrite most of it. Omar is your most experienced engineer, and in Monday planning he says the launch date can’t be met unless the team cuts testing. The guide follows each of them through three moments, what you tell yourself, what they conclude, and the three things to say instead, with the version of next year that follows if you don’t.
Then it collects the four habits that run through every story onto one card, each with the sentence to use, and closes with where to start when your own boss hasn’t gone first: pick the person whose story sounded most like someone on your team, and send two people the one question that tells you what you do when you’re stretched.
Ready to bring it to your team? Talk with us →