How to Develop a Manager Past Their First Year

Leadership development has a middle child problem. The firstborn gets the fuss. New managers arrive to a transition program, a buddy, a workshop and a check-in. The baby gets the indulgence. Executives get coaching, offsites and a facilitator with a nice pen. The manager in between, the one running most of the business day to day, gets a quiet year and a calendar invite to the compliance refresher. Every Brady Bunch viewer knows how this ends. Marcia got the attention. Jan got a catchphrase.

Nobody decides this. It happens by default, and we watch it happen in almost every organisation we meet. This piece is about those middle years, because they are where your future senior leaders either get built or quietly plateau.

We have written about setting up first-time managers for success. This is the sequel, written for the same person. The one who owns the promoting, the developing and the budget. The transition worked. The team is stable. The manager is competent. Now comes the harder, less urgent job nobody schedules.

Why does manager development stop after the first year?

Development follows urgency, and after the first year the urgency disappears. A new manager carries visible risk. Deadlines slip, good people resign, the failure shows up fast, so organisations invest. A second-year manager carries no visible risk at all. The team is steady, the numbers arrive on time, and the development budget moves to the next fire.

Mid-market organisations feel this hardest. A large corporate has a leadership academy and a talent team to catch the middle years, at least on paper. In an organisation of two hundred to two thousand people, there is usually one L&D leader, a full change agenda, and no program between the new-manager workshop and whatever the executive team does for itself. The middle years default to nothing because nothing owns them.

The cost stays invisible for years, which is exactly why it compounds. Three things happen when the middle years go undeveloped.

Your steadiest managers plateau. A manager develops in year one because the role forces it. Every week brings a first. Somewhere in year two the firsts run out, and without deliberate stretch the growth stops where the novelty did. Gallup's research puts the manager at the centre of team performance, accounting for around 70 per cent of the variance in team engagement. A plateaued manager is not a neutral outcome. They set the ceiling for everyone underneath them.

Your best ones leave. Capable people read silence as a message. When the organisation stops investing, the ambitious conclude their growth lives somewhere else, and the manager you most want to keep is the one most likely to act on the conclusion. Exit interviews rarely record it honestly. Development gaps get filed under salary or opportunity, because those are easier to say on the way out.

Your bench thins without anyone noticing. The gap surfaces years later, when a senior role opens and no internal candidate is ready. The default fix is an external hire, and the research on external hires is unflattering. Matthew Bidwell's Wharton study found external hires were paid significantly more than internal promotions, received worse performance reviews for their first two years, and exited at higher rates. The cheapest senior leader you will ever appoint is the manager you develop now.

What should a manager develop in years two and three?

Five things, none of which fit in the first year. The transition builds the people skills. Delegation, feedback, coaching, the one-to-one worth having. Those skills keep deepening through practice, and our guide to coaching your team covers where they go next. The middle years add what practice alone never provides:

• Commercial acumen
• Strategic line of sight
• Relationships beyond the function
• Stretch with real stakes
• Profile and visibility

Each one is buildable with rooms and work you already run. None of them build themselves.

One caveat before the detail. Not every steady manager wants the executive track, and a career middle manager who runs a team well for a decade is an asset, not a problem to solve. The five areas still apply. Commercial fluency, wider relationships and tested judgement make the permanent middle manager better at the job they intend to keep. Development and promotion are related, and they are not the same thing. Organisations conflating the two either push good managers into roles they never wanted or promote them past the point where their competence runs out.

Commercial acumen

A first-year manager runs the team against the plan they are given. A future leader needs to understand the plan itself. Where the targets come from, what the business earns and spends, which numbers the executive team argues about and why. This is a different skill from running a team well, and it rarely arrives on its own.

The buildable version looks like ownership, not observation. Give the manager a budget line and have them run it end to end, from the ask through to the reconciliation. In practice the line starts small, with the costs their team already generates, made real rather than nominal. If finance is tightly held in your organisation, and in founder-led businesses it usually is, start with the presenting rather than the owning. Bring them into the forecast conversation for their area, the room where the plan gets contested rather than announced. Once a quarter, have them present their team's results to the leadership team and take the questions themselves. Defending a number in front of people who know the business teaches more commercial judgement than any finance course. For the underlying capability, our piece on business acumen as a strategic skillset covers what to build in depth.

You will know it is working when the manager starts arguing with the plan intelligently. Pushing back on a target with a commercial case rather than a workload complaint is the sound of a leader forming.

Strategic line of sight

A manager usually meets strategy at the end of the process, as a cascade to pass along. A developing leader needs to meet it earlier, while it is still being argued. The difference matters. A manager who hears the summary learns what was decided. A manager who hears the reasoning learns how the organisation decides, and where their team fits inside the thinking.

Three moves put this within reach. Bring them into one slice of the annual planning cycle with a genuine contribution to make, not a seat to fill. Brief them on strategy before the company-wide rollout, so they hear the trade-offs behind it rather than the polished version. Then ask them to translate one strategic priority into a plan for their own team and present the translation back up. Translation is the test. A manager who converts strategy into their team's work has understood it. A manager who forwards the slide deck has not.

Relationships beyond the function

In year one, a manager's world is their team and their own boss. By year three, a leader needs working relationships across the organisation. Peers in other functions, the people who own the systems and budgets their work depends on, the leaders they will one day work beside.

These relationships do not form on their own, especially in mid-sized organisations where every function runs lean and heads stay down. Opening doors is the organisation's job. Put the manager on a cross-functional project with a named counterpart in another function. Rotate them into another function's leadership meeting for a quarter, as a contributor rather than an observer. Build a peer cohort of managers across functions who meet without an agenda handed down from above. The introductions cost you nothing. Their absence costs the manager years.

Stretch with real stakes

Stretch grows judgement. Load grows hours. Organisations confuse the two constantly, and the confusion burns out good managers while teaching them nothing.

A genuine stretch assignment has three features:

• A real decision the manager owns, with the authority to make it
• Stakes visible beyond their own team
• A sponsor senior enough to open doors and absorb some of the risk

In a mid-market organisation, the candidates are usually already on the change agenda. Leading a system implementation, owning the integration work after an acquisition, running a pricing review, standing up a new service line. Work the executive team was going to assign anyway, redirected into development by who gets it and how it is sponsored.

More volume of familiar work has none of these. Neither does a project where the manager gathers input for a decision someone else makes. One well-designed stretch assignment a year, followed by a proper review of the judgement calls inside it, develops more leadership capability than a dozen extra responsibilities. The review matters as much as the assignment. Ask what they weighed, what they missed, and what they would decide differently. Judgement improves when it gets examined, and almost nobody examines it.

Profile and visibility

Being known for the right things is a leadership requirement, and it does not happen by accident. Promotion decisions, succession lists and stretch opportunities all flow toward the people senior leaders know and trust. A manager doing excellent work invisibly will be passed over for someone doing good work visibly, and the organisation loses twice. Once in the decision, once in the message it sends.

The organisation controls most of the levers here. Have managers present their own work to senior audiences instead of having it presented on their behalf. Give them airtime in the rooms where reputations form. Name them in talent conversations and say why. None of this is performative visibility or self-promotion coaching. It is making sure the record matches the work. It matters most for the managers least inclined to promote themselves, who are often the ones whose work deserves it. Left to individual initiative, profile flows to the confident. Designed deliberately, it flows to the capable. We have written in depth about how professional reputation gets built at work, and the same mechanics apply inside your leadership pipeline.

Whose responsibility is manager development after the first year?

Shared at first, then handed over. The first year sits mostly with the organisation, because a new manager is consumed by the transition and has nothing spare to direct their own growth with. The middle years work differently. The organisation provides the openings. The budget line, the planning seat, the project, the room. The manager takes them up and owns what comes of it.

Both failure modes are common. Some organisations keep driving everything and produce managers who wait to be developed. Others hand over too early, call it self-directed learning, and leave people mid-arc with a content-library licence nobody has opened since the welcome email. The design job for you as the L&D leader is to make ownership possible, then expect it. Open the door and watch who walks through. The walking tells you as much about leadership readiness as any assessment.

The manager above them carries the development week to week. The regular conversations, the sponsorship into rooms, the honest signal about readiness. Your program design should equip the manager of managers rather than route around them, because no framework survives a boss who treats development as an HR process happening somewhere else.

The manager owns their half of this arc too, and it helps when they know it. We have written a companion piece addressed to the manager directly, covering what they need to build in themselves. Sharing it with your managers sets the expectation from both sides.

How do you build the middle years into a development program?

Treat them the way you treat the transition. Named, scheduled and sponsored, rather than left to goodwill. The design does not need an academy. It needs four decisions.

A second-stage plan for every manager past year one. Map each manager against the five areas above and write down where the gaps sit. The plan fits on a page. Its existence is the point, because a written plan survives busy quarters and unwritten intentions do not.

A sponsor above the direct manager. The direct manager carries the weekly development. The sponsor opens the rooms the direct manager has no access to, and keeps the manager's name alive in senior conversations. In a mid-market organisation the sponsor is often an executive, which is precisely what gives the sponsorship its weight. Busy executives hear sponsorship as another load, so cost it out for them. An hour a quarter with the manager, plus saying the manager's name in rooms the sponsor already sits in. It is the cheapest development work an executive will ever do.

A quarterly cadence. Annual development conversations leave eleven months of drift between check-ins. Review the plan every quarter, in the same rhythm as your business reviews, and the development stays attached to real work instead of drifting into a parallel HR process.

A different measure of progress. Year-one success is a stable, performing team. Middle-year success is contribution beyond the team. Cross-functional impact, the quality of judgement on stretch work, readiness signals from people outside their own function. Measure managers on what they are becoming, not only on what their team produced.

Sequence matters too, loosely. The five areas do not arrive at once, and a plan attempting all of them in parallel produces exposure without depth. Commercial acumen and cross-functional relationships tend to come first, because they grow out of the manager's existing work. Strategic involvement and stretch assignments build on them. Profile builds throughout, as a by-product of the rest done visibly. Hold the sequence lightly and let the manager's readiness set the pace rather than a fixed timetable.

For a mid-market organisation, all four decisions run through rooms and rhythms you already have. Planning cycles, forecast meetings, business reviews, live projects. The cost is design and discipline, not budget. None of it requires an office either. A forecast meeting works the same on a screen and a peer cohort meets wherever it meets. If anything, hybrid raises the stakes on the design, because the accidental versions of visibility and cross-functional contact disappeared with the office corridor. What gets designed happens. What gets left to chance does not.

A last word on authority, because most L&D leaders hold less of it than this design assumes. You do not need a mandate to start. You need one executive willing to sponsor two or three managers for a pilot year. Bring the one-page plan, the external-hire research and the cost of your last senior recruitment, and ask for the smallest version. Results win over the rest of the executive team better than a policy ever will.

What do you get back from developing managers past year one?

A leadership bench you grew instead of bought. Every organisation eventually needs senior leaders, and the ones who promote from within share a habit. They kept developing managers after the point where it stopped feeling urgent. The manager who steadied a team last year is your fastest and most reliable source of future senior leadership, and what they become over the next two years depends far more on the doors you open than on anything you put in a course catalogue. Your middle child has been ready for attention this whole time.

We are openly biased here. Developing the manager already in the building is the best value in leadership development, and watching a steady manager turn into a leader the business trusts is the best part of our job.

Catalyst works with ANZ organisations to design leadership development across this whole arc, from the first-time transition through to the leaders who carry your strategy. If your managers are steady but your bench is thin, talk to us about what the middle years should look like.

Frequently asked questions

What is the difference between developing a new manager and an experienced manager? New-manager development is about the transition. Letting go of the old job, learning delegation, feedback and coaching, and getting a team stable. Development past the first year builds breadth. Commercial understanding, strategic contribution, cross-functional relationships, tested judgement and a deliberate profile. The first stage is about the team. The second is about the business.

How do you decide which managers to develop past the first year? Watch behaviour rather than labels. The managers worth the investment have steadied their team and started asking questions beyond it. About the numbers, the strategy, the other functions. A high-potential list drawn up too early tends to reward visibility instead of capability, and visibility is partly a product of the opportunities you have already handed out.

What makes a project a genuine stretch assignment? A real decision the manager owns, stakes visible beyond their own team, and a senior sponsor. Extra volume of familiar work is load rather than stretch, and a project where someone else makes the final call develops coordination rather than judgement.

How long does it take to develop a manager into a senior leader? Years rather than months, and the pace depends less on the manager's talent than on the exposure the organisation provides. A manager given real commercial ownership, strategic involvement and stretch work develops in a fraction of the time of an equally capable manager left to grow through team management alone.

Sources

• Gallup, State of the American Manager (managers account for around 70 per cent of the variance in team engagement)
• Bidwell, M., "Paying More to Get Less: The Effects of External Hiring versus Internal Mobility", Administrative Science Quarterly (external hires earn more and underperform internal promotions in their first two years)