A strong specialist can finish a difficult day having solved the most urgent technical problems and still find that the team is waiting for them on almost everything else. That is a recognisable difficulty in a first management role. The expertise that earned promotion remains valuable, yet the job now includes making other people's work possible, reliable and progressively more independent.
For a senior specialist moving into management, the change is deeper than having more people to help. Your own output is no longer an adequate measure of the whole contribution. You may still need to make difficult technical judgements, but you also have to set direction, make decisions at the right level, coordinate resources and help colleagues develop the capability to handle work you once did yourself. Understanding that shift makes it easier to decide where your expertise belongs and where it is becoming a bottleneck.
Your work is no longer the whole result
Specialist performance is often visible in the work you personally complete: a problem diagnosed, a process improved, a record assessed or a customer issue resolved. In management, those contributions still count. The result also depends on whether other people know what matters, have the information and support to act, and can bring a developing problem to the right decision maker in time.
That wider result changes how a working day should be judged. A manager who personally clears a queue of difficult tasks may have protected today's output. If priorities remain unclear to the team, the queue may rebuild as soon as the manager is unavailable. Conversely, time spent clarifying responsibilities or helping a colleague understand a recurring issue may produce little personal output that afternoon while improving the team's next attempt. Neither kind of contribution can be judged by activity alone. The relevant test is what work the team can deliver, with appropriate control, over time.
This does not mean that a manager becomes detached from the substance. Technical judgement helps identify which problem deserves attention, what good work looks like and when a proposed solution carries unacceptable risk. A new manager may also retain direct responsibilities or be the only suitably competent person for a particular decision. The change is in how that expertise is used across the role. If the most capable person takes every difficult task back, the team has fewer chances to learn and the manager has less time to coordinate what only the manager can coordinate.
The boundaries of the role matter as much as its ambition. A title does not automatically grant every approval, resource or decision right. A first-line manager may supervise work while another person controls a technical release, expenditure or a change to an established process. Recognising those boundaries is part of the transition: the manager must enable action within them and carry unresolved decisions to the person authorised to make them.
When every difficult problem returns to you
Personal problem-solving is an attractive default after promotion. You know the work, can often reach a defensible answer quickly, and may feel responsible for preventing a delay. Taking over can be the right response when time, risk or competence makes immediate intervention necessary. It becomes a problem when colleagues learn that routine uncertainty is best resolved by waiting for you.
Imagine a newly promoted production specialist who handles every recurring handover difficulty between shifts. Each intervention restores the immediate flow. Yet if the manager does not identify what information was missing, who should supply it and how the receiving shift can raise an exception, the next handover returns to the same person. The help has kept work moving, but the team still has only one route through the manager for the next difficulty.
The same pattern can appear in less visible work. A manager may settle every ordinary scheduling conflict, rewrite each report or make every call that sits just beyond a colleague's confidence. The quality of the immediate answer can conceal the cost: colleagues do not practise the judgement they will need next time, and the manager's attention is consumed by decisions that could have been prepared or made elsewhere. An occasional rescue is a response to circumstances. Repeated rescue is useful evidence that the way work is framed, supported or authorised needs attention.
The response is not to refuse help or transfer risk to someone unprepared. Begin by distinguishing the difficulty itself. Does the colleague lack information, time, competence, permission or a clear standard? Those causes call for different support. Explaining a decision once may be enough when the standard was unfamiliar. A repeated conflict of priorities may require the manager to clarify direction or secure a decision from above. Asking someone to take responsibility without the authority or resources to act would reproduce the bottleneck in another place.
Use expertise to frame work others can do
The manager's technical knowledge becomes especially valuable when it helps someone else understand the work well enough to carry it forward. That starts with the intended outcome. A colleague needs to know what must be achieved and what constraints cannot be crossed, not only which steps the manager would personally take. Where the work is unfamiliar or consequential, they also need a way to test their reasoning before a mistake becomes hard to correct.
Consider the handover example. The manager could explain what information the next shift needs in order to continue the work safely and accurately, ask a colleague to examine where recent handovers lost that information, and agree when the findings will be reviewed. The colleague can investigate and propose a practical improvement. The manager remains available to test assumptions and to involve the appropriate technical or operational authority if a proposed change affects a controlled process. Expertise has shifted from personally repairing each handover to making the problem, its boundaries and the next decision clearer to others.
Delegating in this way is more than passing over a task. The person needs enough decision room to do useful work, together with clarity about what must be checked, documented or escalated. A review point can protect both performance and learning: the manager sees whether the work is on course, while the colleague gets feedback before the final result is fixed. The review should fit the person's competence and the work's significance. Constant checking can turn delegation into remote control; no checking can leave avoidable uncertainty undiscovered.
Expertise also helps a manager notice when apparently similar problems are materially different. A colleague may handle a familiar variation within an agreed boundary, while an unusual result calls for a specialist assessment. A production manager might be able to arrange an investigation and protect the schedule but lack authority to approve a technical release. The manager's contribution is to make that distinction visible early, so the right person receives the necessary information before pressure to keep work moving narrows the options.
Make decision rights and escalation visible
Work often passes through several people before an outcome is settled. One person performs an activity, another reviews the evidence, a third provides time or equipment, and an authorised person makes a decision that changes what can happen next. In a food manufacturing setting these roles can sit in different functions, and their allocation depends on the site. A new manager needs to understand the actual arrangement rather than infer it from job titles.
When a team member brings a problem, the manager can first establish what decision is needed. Can the colleague decide within an agreed boundary? Is this a judgement the manager has authority and competence to make? Does another function own a technical decision, while the manager can coordinate the work needed to support it? If the issue requires resources the manager cannot provide, the relevant resource holder needs a clear account of the consequence of delay. These distinctions prevent a manager from either absorbing every decision or promising an outcome they cannot authorise.
Escalation works best when it carries useful information. A manager approaching a more senior decision maker can state what happened, what is known and uncertain, which options remain, what each option would require and by when a decision is needed. That is different from forwarding a vague problem upwards or silently making a choice outside the manager's remit. It also gives the team a model for raising concerns early rather than waiting until a preferred solution is the only one left.
This is a practical conversation to have early in a first management role. Clarify with your own manager which decisions are yours, which require consultation, what expenditure or staffing you can commit, and how urgent exceptions should be handled. Speak with adjacent functions about the information they need before they can decide. The answers may vary by site and circumstance, but uncertainty about them should not be left to surface only during a difficult event.
Develop capability while delivering today's work
A manager cannot make development an entirely separate activity if the team is already delivering demanding work. Capability grows when real assignments include enough explanation, support and feedback for people to improve their next attempt. That requires judgement about which tasks are suitable for practice and which currently need closer supervision or a more experienced performer.
Giving someone a stretch assignment may be useful when its boundaries are understood and help is available. More work alone is not development. If the colleague receives an unfamiliar task without a standard, authority or review point, the resulting pressure may teach them mainly to seek rescue at the last moment. A smaller part of a complex task, with a clear outcome and timely feedback, can provide a better learning opportunity while keeping delivery under control.
Feedback is most useful when it refers to actual work. Telling a colleague to be more independent gives little guidance if they do not know which decisions they may make. A manager could instead explain that the colleague identified the missing handover information accurately, but waited for the manager to choose an ordinary follow-up that fell within an agreed boundary. The next comparable handover then offers a chance to test whether that boundary is clearer and whether the colleague can act within it. The manager can increase or adjust responsibility based on observed work, not on confidence alone.
There will still be work the manager should do directly. Urgent exposure, unresolved technical significance, limited competence or an authority reserved to the role may justify taking the lead. Even then, there may be a later opportunity to explain the reasoning, review what information was needed and decide whether the team can handle a similar situation differently in future. Development does not require pretending that every decision is safe to delegate.
Measure the transition by what the team can now handle
The shift from specialist to manager is easier to recognise in the team's work than in the manager's calendar. Over time, are priorities understood without constant restatement? Can colleagues make ordinary decisions within their agreed limits and raise exceptions early? Do handovers give the receiving person information they can use? When a difficulty returns, has the team learned anything that changes its next response? These observations are more informative than counting how many tasks the manager has handed over.
They also reveal constraints outside the manager's personal technique. A team may depend on one expert because staffing is thin, a key process is unclear or necessary decisions sit elsewhere. The manager should distinguish a development gap from a resource or authority gap, explain the effect on delivery and seek support where their own remit ends. Taking on every problem personally can temporarily hide the constraint; making the work visible gives others a chance to address it.
A useful personal review is to compare where your technical effort goes now with where it genuinely improves the team's work. Direct intervention remains valuable for significant or reserved issues. For recurring ordinary issues, the greater contribution may be a clearer standard, a better decision boundary, a coached colleague or a more reliable route to the right authority. Promotion has changed neither the value of expertise nor the need for judgement. It has changed the result that expertise is expected to help produce: a team increasingly able to deliver sound work without every hard step depending on one person.
