Somewhere in your first few weeks as a new sales manager, you'll sit in a meeting where a report, a metric, or a dashboard comes up that everyone else seems to understand instantly — and you don't. Maybe you never fully did, even in your old role. The pressure in that moment is to nod, say nothing, and quietly go figure it out later.
Resist that instinct. One of the more counterintuitive lessons of becoming a leader is that admitting you don't understand something, clearly and without embarrassment, tends to build credibility rather than damage it.
Why This Feels So Risky
You were promoted because you were excellent at selling — a job with its own specific expertise, but not necessarily the operational, financial, or systems knowledge that leadership now expects you to have. Suddenly you're in rooms discussing forecasting methodology, pipeline reporting conventions, or metrics that were someone else's job to understand before. The gap between "I was clearly excellent at my old job" and "I don't fully understand this new terminology" feels like exposure, especially in front of people who used to see you as the most capable person in the room.
So the instinct is to fake fluency. Nod along, use the right words without full understanding, hope nobody asks a follow-up question you can't answer. This rarely works for long, and it costs more than it saves.
Why Admitting It Actually Builds Trust
Teams can tell the difference between a leader who understands something and one who's performing understanding. A leader who asks a clear, direct question — "I want to make sure I'm following this correctly, can you walk me through why we measure it this way?" — signals something valuable: that they care more about actually understanding the business than about appearing competent in the moment.
This also gives your team permission to do the same. If you can admit a gap openly, they'll feel safer admitting theirs, rather than everyone quietly nodding along to things nobody in the room fully understands.
How to Do This Without Looking Incompetent
- Ask with confidence, not apology. "Walk me through why we track it this way" lands very differently than "sorry, I don't really get this." The first sounds like genuine leadership curiosity. The second sounds like an apology for existing in the room.
- Ask it once, properly, rather than faking it repeatedly. One direct question that actually resolves your understanding is far less costly to your credibility than months of nodding along and hoping it never comes up.
- Pick your moments. You don't need to announce every gap the instant it appears. A quick note to follow up privately afterward is sometimes the better call — the goal is genuine understanding, not maximum visible transparency in every single meeting.
- Follow through. Asking the question is only half of it. Actually learning the answer well enough to use it competently afterward is what turns the moment into credibility rather than just an admission.
The Deeper Point
Nobody actually expects a brand new manager to already understand every system, report, and metric on day one — except, often, the new manager themselves. The pressure to already know everything is almost entirely self-imposed, and it's one of the more unnecessary burdens people carry into a new role.
Every promotion requires a new version of you. Part of that version is comfortable enough in their own competence to say "I don't know that yet" out loud, without treating it as a confession.