An expert becomes a leader: the old work does not disappear
Define the new leader’s workload, delegation boundaries and support for the team.
Article language: English

In this article
On Monday the new leader received congratulations. On Tuesday came the team's questions. On Wednesday they still had every assignment from the previous role. The company treated the promotion as increased capacity, although for now it had mainly increased the number of people waiting at the desk.
Imagine an experienced editor at a company preparing Polish product materials who takes charge of a small team. Previously they owned their texts and helped with difficult passages. Now they must also coordinate workloads, support new contributors and clarify dependencies with customer service. They still want to be the person who fixes a difficult paragraph fastest.
The expertise has not vanished and may still be needed. But the work for which the leader is responsible has changed. Unless the organisation decides what they should stop doing personally, the new role will be squeezed into the time left by the old one, usually when everyone is already waiting for an answer.
An expert's result does not describe all a leader's work
A personal result is easy to recognise: a text corrected, an analysis completed, a problem solved. Leading a team also includes work whose effect appears in someone else's execution. A colleague understands a task, can choose a next step or has obtained an agreement. It need not look like another finished document bearing the leader's name.
Benson, Li and Shue's study of sales staff at 131 firms distinguished results in the previous role from factors predicting managerial performance. It used data from particular US companies; the cited version was accepted for publication in 2019. It does not prove good experts become bad leaders. It shows why the kinds of work matter.
For our fictional company, ask what should now happen through the leader's work. It might be editors independently resolving ordinary feedback, a clear division of work and appropriate escalation of exceptions. “Take care of people” is too vague. Name the added tasks and what a useful result looks like.
Nor is every conversation automatically valuable. If a meeting merely repeats information already in the task, examine its purpose. The new role does not require a calendar full of contacts. It requires recognising dependencies an individual contributor cannot resolve and creating conditions for others to work.
A week does not grow after a promotion
Trace a fictional week. On Monday the editor takes a large assignment because they know the client. On Tuesday two people ask about different pieces of feedback. On Wednesday customer service needs an agreement on priorities. The leader postpones every conversation to finish their own text. By Thursday the team is waiting for several interdependent answers.
The problem need not be a lack of diligence. The leader retained contributor commitments while accepting new dependencies. If the plan lists only texts to edit, the time needed to prepare others' work is invisible. It can falsely appear that team questions interrupt the only legitimate work.
The Center for Creative Leadership describes first-time managers' challenges using its own research on development-programme participants, including balancing workload, developing others and delegation. These are the experiences of a defined group, not a measure of the prevalence of those problems in every Polish company.
The organisation should review the leader's previous commitments: which will they finish personally, which can transfer, and which new tasks will they stop accepting until available time is established? Without that conversation, “delegate more” may merely add the work of handing over tasks, for which no time was allocated either.
Name the transition period. The leader may finish an old case while preparing the team to take the next one. Define what ends that period. If every new assignment is called the last exception, the old role can continue indefinitely under a new title.
Help does not always mean fixing everything yourself
A junior editor brings unclear client feedback. The leader immediately rewrites the paragraph. The assignment moves on, but it is unclear whether the editor understood why it changed. A similar comment may return the same way next time. Speed of individual execution does not by itself reveal what happened to team independence.
It may be enough to identify together what the client is comparing and what material is missing. Sometimes a hint is needed, sometimes an explained example, and sometimes a genuine takeover. Asking for help on a team (in Polish) should make these needs distinguishable. A leader need not give every question the same kind of answer.
But refusing help must not become a rule for developing people. If the editor lacks access to a source, or a decision exceeds their role, sending them away to think independently supplies nothing. The leader may need to obtain the source or identify someone with authority. Independence requires conditions, not expectation alone.
When giving feedback on an expert's work (in Polish), ask why an option was chosen. A leader who can quickly correct a text may unconsciously replace the needed explanation with their own version. The employee should understand what required change and how to recognise a similar problem later, without adopting every personal stylistic preference of their manager.

The new leader may need help too. Editing expertise does not imply knowledge of every organisational dependency. Consulting an experienced person about a difficult conversation or the scope of a decision is different from language consultation. The company should show where to get that support rather than assuming promotion supplied it.
Transfer the task with the means to do it
Delegation should not merely move a deadline to someone else's list. The recipient needs the expected result, materials and boundary of their own choices. If the leader retains every minor decision, they still return to every case. The formal contributor changed, but dependence on the leader's attention remains.
In the editing example, distinguish ordinary description corrections from a change to a product promise. The employee handles the former within the agreed scope; the latter may need the person responsible for the client's material. This is a working division for that company to agree. Explain the boundary before judging whether someone asks too often.
When onboarding an employee to company knowledge (in Polish), also check access to a current source. A leader's absence should not block information that can circulate normally. Access to a file does not itself authorise every change. Knowledge and decision authority need separate consideration.
Agree how the work returns. One case needs a result checked before delivery; another needs a short closure note. If the leader repeats the entire task every time, ask exactly what they verify and why. A check needs an object; otherwise the work is done twice and the team still waits for the same person.
Expertise alone will not settle every cross-team dispute
Customer service may want a short answer today while editors need clarification first. Writing another text personally will not resolve the entire difference. The company may need to decide what it promises at that stage and which data makes that promise achievable.
A shared description of the cross-team problem (in Polish) helps. Do the parties differ in knowledge, objective or available time? Each answer calls for a different discussion. The leader's personal speed may temporarily hide the lack of agreement without removing the condition that will recur on the next assignment.
Distinguish team leadership from being the process owner (in Polish). A new leader need not have authority to change the whole customer-service path. They should know what they can agree within the team and what must go elsewhere. A title does not answer every boundary question.
The leader can still do a difficult task requiring their expertise. Name the effect on other work: who takes current questions, what moves, and is this an exception or a recurring assignment needing a different division? Leadership does not prohibit expert work; it requires a deliberate place for it.
The team and the rest of the company must learn about the change
Suppose the leader agreed to transfer ordinary corrections, but the account handler still sends them directly to them. The reason is understandable: until now that person did them well. The internal decision has not yet changed the route. The leader and manager should explain the new division to people who actually direct work to the team.
Communication should show the practical result. Who receives ordinary material? Where does an unclear comment go? Which exception requires the leader? Announcing a job title does not answer those questions. If customer service must still expect all previous responses from the leader, include that duty in the new role instead of simultaneously assuming the work was fully transferred.
The leader also needs agreement with their own manager on when they may decline another task from the old role. That allows a conflict to be raised and priorities decided without abandoning prior commitments unilaterally. Otherwise the company expects changed behaviour towards the team while rewarding rapid personal takeover of every difficult case.
Check what the team can do without the leader taking over
A weekly review should not count only the leader's completed texts. Examine whether people obtained agreements, resolved ordinary cases and routed exceptions correctly. These are concrete leadership results; they need not immediately become an elaborate system for rating individual employees.
If every hard case still ends with the leader correcting it personally, revisit dependence on one person (in Polish). Is the cause knowledge, access, authority or an unclear task boundary? Do not assume the team refuses to learn. The company may never have made it possible to take over the necessary work.
With AI, the distinction is concrete. A leader may review every draft because sources and evaluation rules were never agreed. Alternatively, they may check defined exceptions while a trained team recognises ordinary cases. The choice depends on the tool, data and task. Promotion alone creates neither rules nor time to prepare them.
At Aeneia Audit, start with one workflow that regularly returns to the new leader. Examine the roles of AI, sources and the person in that task. The company separately determines workload and the role's scope. A useful first step may sound ordinary: decide which old commitment stops landing on the leader's desk so there is time for the new work.









