|
Hello Reader, There is a quiet instinct many people develop as they get more competent. Once you know your work is solid, you try to remove anything that might undermine it. You ensure that small slips that might make you look less capable are gone. The goal becomes clear. Do not give anyone a reason to doubt you. What is interesting is that this instinct often backfires. You have probably seen it happen. Two people demonstrate roughly the same level of skill. One is flawless. The other makes a small, harmless mistake. The room gravitates toward the second person. Not because they are better. The assumption most of us grow up withWe tend to believe that mistakes reduce credibility. If you mess up, you look careless. So we aim for perfection, especially once we are already seen as competent. We treat mistakes as liabilities to eliminate rather than signals to understand. But psychology noticed something different. What researchers discoveredIn the 1960s, psychologists began studying how people judge competence and likability together. What they found was counterintuitive. When someone is already perceived as capable, a small and non-threatening mistake can make them more likable. The competence remains intact, but the person feels more human. The mistake does not cancel out ability, it adds warmth. Instead of feeling distant or intimidating, the person becomes relatable. Someone others feel comfortable engaging with rather than measuring themselves against. Why this works in real lifePeople are not only assessing whether you are good at what you do. They are also assessing whether interacting with you feels safe. Perfect performance can create distance. It signals control, but it can also signal judgment. A minor imperfection changes the emotional tone of the interaction. It tells others that you are human, not untouchable. This is why competence paired with warmth is so powerful. Competence alone impresses. Where people misapply this ideaSome people hear this and swing too far. They overshare and self-deprecate. They lead with flaws before establishing credibility. That rarely works because imperfection only helps when it sits on top of real competence. The mistake has to be small and the capability has to be clear. A crack in the armor works because there is armor underneath. A more useful way to think about mistakesYou do not need to manufacture errors or perform vulnerability. You just need to stop erasing every sign of being human. In a design review, this might sound like: I chose eventual consistency here because it simplified our deployment model, but I know we're trading off some read accuracy. Happy to revisit if that becomes a problem. Or when presenting a new tool: 'I'm still getting up to speed with this automation framework, but here's what I've learned so far that could help our deployment pipeline.' These moments do not make you look sloppy. They make you feel real. What changes when you allow thisWhen people sense both capability and humanity, trust forms faster. Conversations open up. Others feel more comfortable asking questions, offering ideas, and pushing back. The interaction becomes collaborative instead of performative. You stop trying to appear impressive. You become easier to work with. Perfection can command respect. But it rarely builds connection. If you are already good at what you do, the small imperfections you are trying to eliminate may be the very things that help others lean in. Sometimes, the moment people trust you most is the moment you stop trying to look flawless. That is all for this week. |
Join 1k+ other forward-thinking professionals who receive the weekly newsletter, where I provide actionable strategies, insights and tools to escape the grind and build influential, future-proof careers. Sign up to get a FREE copy of my 5-Stage playbook to multiply your impact and build a career that AI can't replace.
Hello Reader, It's Kayode A few years ago, I sat in a planning meeting that had been running for 45 minutes without a single decision made. Everyone had an opinion and nobody had ownership, and the same three options kept cycling through the conversation like luggage on a carousel that nobody wanted to claim. Then one engineer said: “We’ve been here long enough. Based on what we’ve heard, we’re going with option two. Here’s who owns what next.” The room went quiet in the way rooms do when...
Hello Reader, Three years ago, I watched a senior engineer named Sarah coordinate a critical infrastructure migration. Network automation, data platform, and application services were moving to a new orchestration layer simultaneously. In week one, Sarah noticed something: The network team was designing their API for synchronous responses. The data platform team was building for eventual consistency. By week three, these systems would be incompatible. She spent two weeks facilitating...
Hello Reader, A few years ago, I was working with an engineer who had spent eight years building network automation tools. He was exceptional at it. His systems were elegant, his code was clean, and his team respected him. But when I asked him what he wanted to be doing in five years, he went quiet. "Honestly? Not this. But I've invested so much time. It would be wasteful to walk away now." He was protecting the past at the cost of the future. Six months later, he was still there. Not because...