The move to management changes the job from producing primarily through personal expertise to setting direction, supporting people, making decisions, coordinating the system, and being accountable for team conditions. New managers need explicit authority, training, coaching, and space to learn. Continuing to do the old job at full scale usually crowds out the new one.
Who this is for: New managers promoted from specialist roles who now lead former peers or a team doing work they previously performed themselves.
- Rewrite the role around managerial responsibilities and remove enough former work to make those responsibilities possible.
- Establish clear relationships, decision rights, confidentiality boundaries, and expectations, especially when managing former peers.
- Build skill through supported practice in feedback, delegation, planning, hiring, conflict, and organizational process.
Accept that the job changed
Clarify what the organization now expects: direction, priority decisions, employee support, performance conversations, resource planning, coordination, risk, and communication. Identify which specialist duties will stop, transfer, or shrink. A new title without changed workload asks the manager to perform two substantial jobs and makes people work the first casualty.
Success now includes conditions and outcomes created with others, not being the fastest person to solve every technical problem. Expertise remains valuable for context and judgment, but it can become a bottleneck when the manager reviews every detail or takes the hardest work automatically. Discuss with your manager how individual contribution will be bounded.
Reset relationships and authority
Meet team members to discuss the role change, what remains stable, how decisions and feedback will work, and what they need from a manager. With former peers, acknowledge the changed responsibility without demanding immediate emotional adjustment. Do not continue sharing confidential information or participating in old social dynamics as though authority has not changed.
Learn the boundaries of your authority and the organization's processes for performance, leave, accommodations, hiring, pay, complaints, safety, and other consequential matters. Seek qualified partners rather than improvising. Being supportive does not require having every answer; it requires knowing when a decision belongs elsewhere and following through on the route.
Build a management operating rhythm
Establish a manageable rhythm for one-on-ones, team coordination, planning, feedback, stakeholder communication, and your own manager check-in. Each forum needs a purpose. Avoid filling the calendar to prove accessibility. Leave room for preparation, difficult conversations, decision work, and the unexpected responsibilities that management brings.
Delegate coherent outcomes with clear authority and checkpoints. Ask questions before offering the specialist answer. When you do contribute expertise, label whether it is context, a suggestion, or a decision. This helps employees exercise judgment and prevents the manager's casual idea from becoming an unchallengeable instruction.
Learn with support and reflection
Identify immediate skill needs from real responsibilities, such as giving feedback, setting expectations, interviewing, planning capacity, or handling conflict. Combine formal learning with rehearsal, observation, coaching, and debriefing. Do not practice unfamiliar employment procedures on employees without guidance; use the organization's process and experienced support.
Review decisions and interactions regularly: what outcome you sought, what evidence you used, how authority affected the conversation, and what you would change. Ask your own manager for specific feedback and organizational context. Management skill develops over time, but employees still deserve clear standards, reliable support, and timely correction while you learn.
Stop being the team's default expert
A newly promoted engineering manager answers every technical question, while experienced engineers wait for approval and employee conversations keep slipping.
- Review the new role with the manager's supervisor and transfer or bound former coding ownership so people work has protected capacity.
- Clarify technical decision rights with the team and identify experienced engineers who can own coherent areas with appropriate review.
- When questions arrive, ask for the owner's recommendation and offer context without automatically taking the decision back.
- Use regular reflection and supervisor feedback to review delegation, team access, decisions, and delayed management responsibilities.
New manager transition map
Complete this map with your manager and revisit it as responsibilities, team needs, and organizational context become clearer.
- Role shift: new outcomes, people responsibilities, retained specialist work, transferred work, authority, and policy boundaries.
- Relationships: team conversations, former-peer changes, stakeholders, confidentiality, decision rights, and support expectations.
- Operating rhythm: one-on-ones, team forums, planning, feedback, manager support, preparation, and protected judgment time.
- Learning plan: immediate situations, methods, qualified partners, practice, observation, feedback, reflection, and review.
Common mistakes
- Keeping the previous individual workload while adding full management responsibility on top.
- Solving every difficult specialist problem and unintentionally teaching the team to wait for permission.
- Improvising consequential people decisions instead of learning policy and involving qualified organizational partners.
Try one
A new manager now supervises close former peers who expect the same access to confidential discussions. How should the manager respond?
A strong answer acknowledges that the relationship and responsibilities changed, explains that employee and organizational information now has confidentiality boundaries, and applies those boundaries consistently. The manager can remain respectful and connected without sharing protected details or discussing one colleague with another. They should seek qualified guidance for uncertain cases and create transparent team decision practices where confidentiality is not required.
Sources
- CIPD line management factsheetProfessional guidance on the people-management responsibilities and support needs of line managers.
- Atlassian one-on-one playA practical format for recurring conversations between managers and team members.