A promotion can put you in a role you are not ready to do well yet. That does not automatically mean the promotion was a mistake. The trouble starts when you treat the gap as something to conceal instead of something to close.
Imagine a senior developer who becomes a team lead, then an engineering manager, and then takes over a division after a reorganization. The new role brings decisions about forecasting, compensation, performance processes, budgets, and work far beyond the person’s technical expertise.
The title changes faster than the skills do. That is a real problem. But it is not a personal failing to need help learning a different job.
Organizations can mistake strong individual performance for readiness to lead. A person who delivers excellent work may be promoted because of that success, even though managing people and making broader business decisions require different capabilities. A reorganization or urgent need can also put someone in the role before there has been time to prepare them.
The organization has responsibility for the transition. The new leader has responsibility for what happens next.
And this is where the pressure changes. Once people look to you for answers, asking a basic question can feel like risking the authority you just gained. You may worry that admitting what you do not know will make others question whether you belong in the role.
So you bluff, or postpone the decision. You keep approvals close because you are not sure what to delegate. You tell yourself you are being careful. Sometimes you are. But when uncertainty becomes a reason to delay everything or hold every decision, the team ends up working around your need to look certain.
That is how a skills gap becomes a leadership problem.
Leaders cannot know everything. Learning on the job is normal. Being open about a gap is not the same as handing someone else your responsibility. You still have to make the decision, but you may need to bring the right people into the process before you can make it well.
Start with the work in front of you. If you do not understand the assumptions in a headcount forecast, ask finance to walk you through them. If you are about to approve compensation changes and do not understand the company’s process, ask HR to explain it. If a decision depends on technical context you no longer have, say so and involve people who do.
Be specific about what you know, what you do not know, and what you need in order to decide. Then follow through. Asking for help does not remove your obligation to learn the work or make a call. It gives you a better chance of doing both.
You may not get a warm response. Some workplaces punish uncertainty, and support is not guaranteed. That is a real risk. But hiding the gap has a cost too: decisions stall, approvals collect around you, and your team is left guessing whether the delay is thoughtful judgment or a lack of context.
The answer is not to perform confidence more convincingly. It is to make your learning visible enough that people can help you build competence—and to stop making your team pay for the version of you that never needs help.
