You know that feeling when your manager rolls out a shiny new “framework” for how the team should think? They stand in front of the whiteboard, smile warmly, and say, “I want us to be better at admitting our mistakes.” It sounds beautiful. It feels like a trap.
Saying “I am often wrong” is just a humble-brag if you punish people who don’t follow your process.
Recently, a tech leader wrote an article titled “I am often wrong.” It was meant to be a reflection on intellectual humility. The premise? He built a strict, multi-step decision-making framework for his team. If team members skip a step, he gives them “feedback.” The tension is glaring. The author claims fallibility while enforcing a rigid, mandatory process for discovering it.
We’ve all been there. You’re forced to adopt a manager’s personal pet system, and if you deviate, it shows up on your performance review. It’s the ultimate irony: the boss claims to be humble, but their humility is entirely conditional on you doing exactly what they say.
True intellectual humility looks like changing your mind. False humility looks like mandating a flowchart for how others must change theirs.
The commenters on the article proved the thesis better than the author did. They called out the exact arrogance the author was trying to deny. One reader nailed it: “Nothing more annoying than a manager with a personal know-it-all framework requiring people to follow it or else they get ‘feedback’.” The commenters were actually correcting the author for being wrong about how to be wrong. The author was meta-wrong.
When you reach a certain level of influence, you don’t get to declare yourself humble and then build an enforcement mechanism around your personal operating system. That’s not vulnerability. That’s dogma dressed up in a cardigan.
You cannot institutionalize vulnerability. The moment you make it a mandate, it becomes a weapon.
For managers and decision-makers, the lesson is simple. If you want a team that admits mistakes, you have to practice it, not mandate it. You have to let people push back, use their own methods, and sometimes, fail. Forcing your team to adopt your framework of fallibility doesn’t make you a humble leader. It makes you a hypocrite with a flowchart.
FAQ
Q: But don't teams need standardized frameworks to avoid chaos?
A: Standardized processes are fine. But enforcing a manager's personal 'humility framework' under threat of feedback isn't process—it's ego. There's a difference between a shared operational standard and a mandated thought-process.
Q: How do you actually practice intellectual humility as a leader?
A: By letting your team use their own methods to solve problems and accepting outcomes that differ from your own. Humility is giving up control, not building a tighter leash.
Q: Is claiming 'I am often wrong' just a manipulation tactic?
A: Often, yes. It's the ultimate shield against criticism. By declaring yourself fallible upfront, you disarm critics while simultaneously enforcing your own rules. It's arrogance wearing a disguise.