First time manager training is the clearest response to the untrained manager wave: capable engineers receive people authority before they have practiced the conversations, decisions, and habits that management demands. The wave is not a complaint about inexperienced people. It is an operating risk created when organizations treat promotion as preparation and expect teams to fund a manager's learning through avoidable confusion.
Why is there an untrained manager wave now?
Engineering organizations often promote the person who knows the system, rescues releases, and earns peer trust. Those strengths matter, but management changes the work. The new manager must create clarity through other people, address behavior without hiding behind code review, balance individual needs with team commitments, and explain decisions that will disappoint someone. Technical credibility does not automatically produce those skills.
Growth also makes the problem repeat quickly. A company adds teams, needs several managers at once, and fills the roles from its strongest individual contributors. Each promotion looks reasonable in isolation. Together they create a layer of leaders learning in public with uneven guidance. Senior leaders then spend time repairing escalation paths, unclear ownership, and preventable departures instead of building the next leadership layer.
According to iSilta's 2026 survey of 146 organizations, 61% train after promotion and 44% provide no formal training before someone begins managing. That sequence explains the wave. Authority arrives on day one, while practice arrives weeks or months later. By then, the manager has already established what a 1 on 1 feels like, whether feedback is safe, and how priorities really get decided.
What does an untrained manager cost an engineering team?
The first cost is rarely a dramatic failure. It is friction. A senior developer leaves a 1 on 1 without knowing whether a promotion is realistic. A quiet engineer receives less useful work because the manager delegates to the loudest person. A project slips because risk stayed implicit. Every event seems small, yet the pattern teaches the team to route around the manager.
That workaround is expensive. Tech leads become unofficial people managers. Product partners seek decisions from skip level leaders. Engineers save concerns until they become resignation conversations. The manager feels excluded and responds with more status checks or tighter control. What began as a skill gap becomes a trust gap, then a delivery problem.
| Early signal | Likely gap | Useful response |
|---|---|---|
| 1 on 1s become status reports | Listening and coaching | Practice an agenda built around the employee |
| Work stays with the manager | Delegation and trust | Define outcomes, boundaries, and review points |
| Feedback arrives late | Courage and specificity | Rehearse prompt examples tied to impact |
| Priorities change silently | Decision communication | Record what changed, why, and what stops |
| Strong people disengage | Growth conversations | Create evidence based development plans |
Why doesn't experience alone solve the problem?
Experience only teaches well when the learner can see cause and effect. Management feedback is delayed and ambiguous. An engineer may agree politely, then transfer months later. A project may ship despite poor leadership because a staff engineer quietly carried it. Without observation and reflection, the manager can interpret survival as proof that the approach worked.
Late training must also compete with identity. Once someone has been called a manager for six months, admitting uncertainty can feel risky. They may defend habits that helped them survive, even when those habits limit the team. Early practice makes curiosity normal before status turns every correction into a perceived judgment.
According to iSilta's 2026 survey of 146 organizations, 78% report weak 1 on 1s when training arrives late. The finding matters because 1 on 1 quality is a useful window into broader management behavior. Managers who cannot create a candid, useful conversation often struggle with coaching, expectation setting, and early conflict as well.
What should organizations do before the next promotion?
- Define the role. Show candidates the real calendar, decisions, and emotional demands instead of presenting management as the default reward for technical excellence.
- Offer practice. Let candidates facilitate planning, coach a volunteer, give feedback in a simulation, and lead a small coordination problem with support.
- Assess motivation. Ask whether the person wants to improve systems through people or mainly wants title, pay, and influence. Fix career paths so management is not the only route to recognition.
- Train core conversations. Build skill in 1 on 1s, delegation, feedback, conflict, growth, and fair performance decisions before the person owns them.
- Plan the transition. Name the new manager's coach, reduce individual contributor load, set thirty day expectations, and schedule observation before the announcement.
How should first time manager training work?
Good training resembles engineering practice more than a lecture. Learners need a clear model, a realistic scenario, a chance to respond, precise feedback, and another attempt. A manager can understand a feedback framework on a slide and still freeze when a respected senior engineer dismisses a teammate in design review. Practice closes that gap.
Use situations drawn from actual work: an incident review turns personal, an engineer wants promotion without enough evidence, roadmap pressure encourages hidden quality debt, or two teams disagree about service ownership. These examples force managers to combine empathy with standards. Generic inspiration does not prepare them for that tension.
Training should continue after promotion, but the purpose changes. Before promotion, it tests fit and establishes safe basics. During onboarding, it connects those basics to the team's goals and people. Later coaching helps the manager interpret patterns, prepare difficult conversations, and improve judgment. One workshop cannot serve all three purposes.
What are the five parts of this series?
- Should you train managers before promotion? explains why practice before authority reduces risk and how to design a fair readiness process.
- How to onboard a new manager gives a practical transition plan for the first ninety days.
- What is an accidental manager? shows how informal responsibility grows without clear choice or support.
- How to coach untrained managers offers a respectful way to replace harmful habits with observable skills.
- How to measure leadership training connects learning to behavior, team experience, and operating results.
Who owns the solution?
Senior leadership owns the conditions. People teams can provide curriculum and tools, but executives decide whether candidates get time to practice, whether expert careers remain credible, and whether managers are rewarded for developing people. A leadership program cannot compensate for a promotion system that values emergency heroics above healthy team performance.
The new manager's manager owns transfer into daily work. They should observe selected conversations, review decisions, ask what the manager is trying differently, and give feedback soon enough to help. A monthly question such as “How is the team?” is too broad. Ask for evidence: whose expectations became clearer, what was delegated, which concern surfaced early, and what conversation still feels difficult?
The learner owns preparation and reflection. They can request context, rehearse wording, document decisions, and notice outcomes. Ownership does not mean learning alone. It means using the support deliberately rather than waiting for confidence to appear.
How do you prevent training from becoming theater?
Start with behaviors leaders can observe. “Communicates well” is vague. “Explains the decision, names the tradeoff, checks understanding, and records the next step” can be practiced and reviewed. Tie each module to one or two behaviors, then create opportunities to use them in normal work.
Measure more than completion. According to iSilta's 2026 survey of 146 organizations, 81% do not measure behavior change. Attendance can prove that a session happened, not that management improved. Ask team members focused questions, sample 1 on 1 preparation, review delegation agreements, and watch whether difficult feedback happens earlier.
Do not turn every signal into a scorecard. Teams need psychological safety, and managers need room to learn. Combine private coaching evidence with broad trend data. The goal is better leadership, not surveillance. When measures reveal a gap, respond with practice and support before punishment unless the behavior is clearly harmful.
What does progress look like?
Progress appears in ordinary moments. Engineers know what good performance means. Risks reach planning meetings while options still exist. A manager can disagree without becoming defensive. Delegated work includes authority as well as accountability. 1 on 1s surface growth, motivation, and friction instead of repeating project updates.
The untrained manager wave will not end with a perfect course. It ends when organizations treat management as a profession that deserves selection, practice, onboarding, coaching, and evidence. That system gives first time managers a fair chance to succeed and protects teams from becoming the training environment by default.
Frequently asked questions
What is the untrained manager wave?
The untrained manager wave is the growing number of people promoted into management before they learn the core behaviors the role requires. They gain authority first, then try to learn feedback, coaching, planning, and conflict work while their teams absorb the mistakes.
Why is first time manager training urgent?
A first time manager shapes workload, trust, growth, and retention from the first week. Delayed support lets weak habits become normal and makes later training harder to apply.
Should training happen before promotion?
Yes, whenever possible. A short practice period before promotion helps candidates understand the job, demonstrate basic skills, and decide whether management fits them before authority raises the cost of learning.
What should first time manager training include?
It should include 1 on 1s, feedback, delegation, coaching, fair decisions, conflict handling, delivery planning, and practice with realistic engineering situations.
How can leaders know whether training worked?
Measure observable behavior at several points after training. Use team feedback, manager observation, conversation quality, decision records, and delivery signals rather than attendance or satisfaction alone.
Related: training managers before promotion, new manager onboarding, the accidental manager.
Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.