An engineer gets promoted into management. They know the systems, understand the technical challenges, and have earned the respect of their team.
Then, a few weeks into the new role, they begin wondering what they've gotten themselves into. Meanwhile, the person who promoted them may be having doubts of their own. Both are looking at the same transition, but they're seeing two very different problems.
As an engineer, success was often straightforward. A problem needed solving, and you knew how to approach it. You could see the results of your work.
Management is different. Now there are competing priorities, employee concerns, deadlines, and decisions that don't have obvious answers. You may spend an entire day in meetings and wonder what you actually accomplished.
Then a technical problem comes along. Finally, something familiar. Something you know how to fix. So you jump in.
It feels productive, the team appreciates the help, and for a moment, you feel like you're contributing again. But the responsibilities you were hired to manage are still waiting.
The engineering leader who made the promotion may see things differently. They already know the new manager is technically capable. That's not what they're worried about.
They need someone who can recognize when a project is drifting off course, address performance concerns, develop employees, and make decisions that consider the entire team's needs.
Instead, they see their new manager spending hours troubleshooting code or personally resolving problems that team members could handle.
From their perspective, the new manager isn't stepping into the role. But what looks like an unwillingness to let go of technical work may actually be uncertainty about how to contribute in a position where success is measured differently.
The first 90 days can expose behaviors that weren't particularly noticeable when someone was an individual contributor.
An engineer who was always quick to take ownership may struggle to leave decisions with others. Someone who excelled at solving immediate problems may find it difficult to focus on longer-term team priorities.
These aren't necessarily signs that the promotion was a mistake. They may be behaviors that need to be recognized and developed.
For the new manager, understanding those tendencies can make the unfamiliar parts of the role easier to approach. For their supervisor, recognizing them provides an opportunity to offer more specific guidance rather than simply expecting the engineer to start thinking like a manager.
Ideally, that understanding begins before the promotion, when there is still time to practice new responsibilities without the full pressure of managing a team.
The first 90 days aren't just about learning new responsibilities. They're also about changing how success is understood.
The new manager may think they're proving their value by solving problems. Their supervisor may be waiting for them to stop solving everything themselves.
Neither may realize they're measuring success differently.