I once attended a project review meeting with my team to review the status of a high-visibility project.
A few minutes into the meeting, the temperature in the room started rising. It was obvious that the project was falling apart with slipping deadlines, and tempers started to run short. I noticed that my team leads were looking at me to “jump in” and “fix” the issues being discussed.
Instead, I stayed quiet for almost twenty minutes. I just listened, asked one question, and then let the team work it out.
I know this may seem strange and counterintuitive, and you may think I was being plain rude or ignorant of my team’s challenges.
Let me explain.
I was not being rude or ignorant. In fact, I believe I did the hardest thing a manager can do, which is: do nothing, on purpose.
Let’s face it: the corporate world has built a picture of what “good leadership” looks like: quick answers, fast decisions, visible hustle, and so on.
But having led teams for 20+ years, here’s my honest take: some of the most valuable things you do as a manager are invisible.
They don’t look like “leadership”. In fact, they look like doing nothing at all.
Here are six of them.
1. You let silence sit in a meeting
Let’s say you’re hosting a product review meeting with your team, and a stakeholder from another division asks a hard question.
Your instinct as the manager is usually to “fill the gap”.
Maybe you throw in a quick suggestion, or name a team member to “chime in”, or even throw in a quick joke.
Anything to fill the gap.
Here’s what you should do: resist that temptation.
Wait for ten seconds, maybe twenty.
I know it will feel like forever, but more often than not, someone who was working through the problem will eventually speak up. Maybe it’s your team lead, maybe it’s the more junior person on your team.
But when they do speak up unprompted by you, they will likely have the sharpest, most authentic answer.
👉🏻 Takeaway: Silence isn’t empty air. It’s actually thinking time, and every time you fill it, you’re robbing your team of the thinking time that they deserve.
Suggested frameworks:
2. You don’t answer the question you’re asked
Let’s say your team lead catches you in the hallway on a busy Wednesday afternoon, and asks: “Should we push the release or keep the date?”
How would you respond?
Most managers would make the obvious move - to just give them the answer.
Here’s what you should do.
Instead of just making the decision for them, throw it back at him: “What would you do, and why?”
I can bet that more likely than not, he already knows the answer. He just wants the assurance, or the permission, or maybe just the “cover”.
👉🏻 Takeaway: As leaders, answering every question makes us feel useful. But it also makes your team worse at answering on their own.
Suggested frameworks:
3. You let a mistake finish happening
Let’s say you observe one of your engineers build a solution that you know won’t work. You’ve seen it fail a few times when you were an engineer.
So, you’re tempted to “jump in” and rescue him, rigth?
Don’t do that.
Instead, let him build it, ship it, and fail exactly the way you know he will.
You may think I’m crazy to say that, but hear me out.
When you do that, you’re not “neglecting” him. On the contrary, you’re teaching him how to fish, not just handing him the fish.
👉🏻 Takeaway: If you don’t let your team fail and learn the lessons on their own, they will never learn the lessons at all.
Suggested frameworks:
4. You skip the meeting you were invited to
You probably get invited to a gazillion meetings by your team members, by default, because “you’re the manager”.
Maybe as “optional”, if that’s a culture in your team.
And once you have your calendar fills up with all those meetings, you feel the obligation to show up in those meetings.
Again, you’re the “manager”, so your team must need you in the meeting, right?
Wrong.
Here’s what you should do: show up to a fraction of them. And you don’t do this because you’re “too busy”, but because, let’s face it, your mere presence changes what happens in the meeting.
When you’re in the meeting, your team tends to defer to you. They look at you after any big question.
They wait to see what you think before they say what they think.
👉🏻 Takeaway: Skipping a meeting isn’t just a scheduling choice. It’s a decision about who gets to own the outcome.
Suggested frameworks:
5. You don’t touch the document
Let’s say you have a new manager on your team, and he puts together a deck that he’ll be presenting to the stakeholders next week.
As you review the deck, you find three things that you would have written differently. So, what do you do?
Most managers would get tempted to “fix the deck” themselves. After all, they know exactly what to fix and how to fix it.
Resist the temptation to do that.
Instead, just leave a single comment for the new manager to review and update in his terms.
When you rewrite someone else’s work in your own voice, it may feel like “helping”. But in reality, it mostly just teaches them to stop trying, since whatever they produce gets overwritten anyway.
👉🏻 When you let others learn and adapt, you may get a slightly worse document now, but you’re teaching them to write better ones in the future.
Suggested frameworks:
6. You don’t have a take on everything
Let’s say you’re in a leadership team discussion about a reorg.
The most logical thing for you to do is to “jump into the debate”. Right?
But you decide to stay out of it. You do this not once, but twice.
And you don’t do that because “you don’t care”, but because you can see that the other two managers arguing actually have it covered.
You know that inserting a third opinion into the mix would just give everyone an excuse to continue the argument, instead of converging on a decision.
👉🏻 Having an opinion on every topic may look like “engagement”. But it’s usually just noise that’s delaying the real outcome.
Suggested frameworks:
Conclusion
The six things we looked at may feel like it’s about being “passive”.
But they’re the exact opposite.
They’re really about restraint, and we all know that restraint takes more discipline than action does.
It’s easy to “jump in”, to fill the silence or rewrite a paragraph. That’s what most managers do.
But it takes discipline and, frankly, trust in your team to sit on your hands instead.
The best leadership I’ve ever seen through my 20+ years as a manager didn’t look like what we have come to expect of leadership.
Instead, it looked like a manager doing nothing, at exactly the right moment, on purpose.
If this resonated with you, hit the ❤️ and consider a restack, it helps this reach more managers who need it. And if you want the frameworks behind posts like this one, check out The Ultimate Leadership Toolkit.
💬 Join the conversations
Join The Good Boss community if you’re tired of leadership content that sounds good but doesn’t work when you’re actually in the room.
No performative LinkedIn BS. Just real stuff.
