LibraryPatternsBuild a Healthier Team CultureOn my team, mistakes get hidden, covered, or quietly …
Problem
Toward Craftsmanship

On my team, mistakes get hidden, covered, or quietly fixed rather than surfaced — because admitting one feels dangerous. So small problems grow in the dark until they become big ones, and I find out about things far too late to help.

Part of the pattern: Build a Healthier Team Culture
Aureliusguide
Aurelius
Online
The coach is replying
You might also say it as
  • people hide mistakes on my team
  • errors get covered rather than surfaced
  • I find out about problems too late
How Aurelius might see it
One way to read this — take what fits, leave what doesn’t.
Your team isn't hiding mistakes out of laziness or bad character. They've learned that telling the truth costs more than staying quiet. The real problem is that the team's unspoken rules punish honesty — and until those rules change, no amount of asking will fix it.
The short answer
Your team hides problems because the culture makes honesty feel risky. You can't talk your way out of that. You have to show, through your own reactions, that surfacing a mistake is safer than burying one. Do that consistently, and the hidden problems start coming to light.
You find out about problems too late because your team has quietly decided that silence is the safer bet. Research on team trust shows that psychological safety — feeling okay to speak up without punishment — is what separates teams that catch small fires early from teams that fight big ones later. Trust like that isn't built by saying 'come to me with problems.' It's built by what you do the moment someone actually does. Marcus Aurelius noticed that people contribute to a shared outcome even when they don't fully understand what they're doing. Some work with open eyes, some without. Right now, your team is working to protect themselves — not because they want to undermine you, but because that's what the environment has taught them to do. The environment is the thing to change, not the people. This week, pick a small mistake of your own — something real, not staged — and say it out loud in front of the team. Name what went wrong, what you missed, and what you'll do differently. Keep it short. Don't over-explain it. Then watch what happens over the next few days. When you make honesty visible and low-cost at the top, it slowly becomes possible lower down. One moment of real candor from you is worth ten 'open door' speeches.
The path forward
  1. 1Name why mistakes feel dangerous
  2. 2Respond well to the next one surfaced
  3. 3Reward honesty deliberately
One thing to try this week
Share one of your own mistakes openly this week and what you learned. A leader who admits errors is how a team learns it is safe to.
Related problems
A new hire has altered the team dynamic in ways I did not anticipate. The culture I built is more fragile than I thought and I am not sure how to protect what was working without being rigid.Bad news does not reach me until it is a crisis. The team filters what they share based on how they expect me to respond. I am operating with a systematically positive picture of what is actually happening.Cliques have formed on my team — in-groups and out-groups, people who are in on things and people who are not. The social lines have hardened into something that shapes who gets heard and who gets left out, and it is quietly corrosive.Credit on my team does not land where the work was done — the visible few are recognised while the people who actually carried things go unseen. The unfairness is breeding quiet resentment, and the ones doing the real work are starting to give less.Every change I introduce meets a wall of resistance — we have always done it this way, quiet non-compliance, waiting it out until I give up. The team has become so change-averse that improvement itself feels like a fight, and I am tired of pushing uphill.I am losing or have lost a top performer and I don't fully understand why.
Sources
  1. 1. Antecedents of Team Creativity: An Examination of Team Emotional Intelligence, Team Trust and Collaborative CultureGloria Barczak; Felicia G. Lassk; Jay Prakash Mulki, Creativity and Innovation Management (2010)
  2. 2. Individual Swift Trust and Knowledge-Based Trust in Face-to-Face and Virtual Team MembersLionel Robert; Alan R. Denis; Yu‐Ting Caisy Hung, Journal of Management Information Systems (2009)
  3. 3. Marcus Aurelius, Meditations 6.37Marcus Aurelius, Meditations (180)

Working through this?

Talk it through with Aurelius, and start where it actually helps.