Do New Managers Understand the Difference Between the Expert Role and the Manager Role?
May 18, 2026
New managers often get stuck in the expert role. What distinguishes it from the manager role, how to recognise the symptoms, and how to make the switch.
New managers often get stuck in the expert role. What distinguishes it from the manager role, how to recognise the symptoms, and how to make the switch.
Most new managers do not understand the difference between the expert role and the manager role in the first six to twelve months after their appointment — and this is the main reason their teams stall and they themselves burn out. An expert is promoted because they do the work better than anyone else. A manager is evaluated on the results the team delivers, not on what they do themselves. These are two different professions with different currencies, different success metrics, and a different structure to the working day. In my consultations with managers between 2024 and 2026, I keep seeing the same picture: someone receives a promotion, formally becomes a boss, but in their behaviour remains a senior specialist. This article is about how to recognise the symptoms, understand the mechanism, and switch into the new role without losing confidence.
Why the "Expert or Manager?" Question Matters More Than It Seems
When a specialist is promoted, they are rarely told that this is a change of profession. In corporate culture, moving into a management position is perceived as "career growth in the same field." You were a senior engineer — now you are a team lead. You were a strong salesperson — now you run the sales department. It seems as though a few management tasks have been added while the substance of the work remains the same.
In reality, the currency of the work has changed. An expert is paid for an hour of their own labour: they analyse, write, sell, design, negotiate. A manager is paid for an hour of other people's labour, multiplied by the number of team members and the quality of their output. These are mathematically different models. And if someone continues to earn only for themselves, their team does not grow, the hiring budget is wasted, and they themselves work themselves into the ground.
Why Experts Are Promoted in the First Place
The company's logic is understandable: promote the person who understands the work from the inside. I agree that you cannot manage without expertise — someone who does not know the specifics cannot evaluate quality or make strong decisions. The problem is not the promotion of an expert per se. The problem is that after the promotion, nobody shows them what their job now consists of.
One CTO at a company of 60 people told me in a consultation: in his first six months in the role, he wrote more code than he had in the entire previous year as a senior developer. Meanwhile, the team was complaining that there was no architectural vision and no clarity on where the product was going. He was still earning as an expert — in hours of code — instead of earning as a manager: through clarity of direction, team velocity, and quality of hiring.
What a New Manager Sees in the First Weeks
In the first weeks of a new role, a stream of things that look like "real work" lands in the inbox: approvals, escalations, operational questions. This creates an illusion of being busy. The new manager closes tasks, answers emails, fights fires — and at the end of the week cannot say whether they did anything important for the team or the business.
This is the first signal that the person is looking at work through the eyes of an expert. An expert measures themselves by the number of tasks closed. A manager measures themselves by team growth and predictability of outcome. If this switch has not been made, the typical symptoms below begin to appear.
How the Expert Role Differs from the Manager Role
The key difference lies in the source of the result. An expert creates value themselves. A manager creates conditions in which the team creates value. All other differences follow from this: how time is spent, what counts as success, which skills matter, how decisions are made.
An Expert Sells the Results of Their Own Hands
An expert is strong because they know the subject deeply. Their working day is built around tasks they close personally: design, calculate, write, run a meeting, close a deal. Effectiveness is measured in hours, throughput, and the quality of a specific result. An expert's career grows through deepening expertise and expanding the range of tasks they can close independently.
In this role, team skills help but are not primary. An expert can be reserved, uncommunicative, difficult — and still valuable. They are kept for results, not for communication.
A Manager Sells the Results of the Team
A manager does not close tasks with their own hands. They are responsible for the team closing tasks predictably, on time, at the right quality, and without burning out. Their working day consists of conversations, decisions, retrospectives, hiring, letting people go, setting tasks, and negotiating with adjacent departments. Effectiveness is not measured in hours but in team results: was the quarterly goal met, did the metrics improve, did the strong people stay, did a new strong person join the team?
A manager cannot be closed off. If they do not talk to the team, nothing works. Communication is not a pleasant bonus to expertise — it is the primary instrument.
Comparison Table: Where the Difference Is Felt in Practice
| Parameter | Expert Role | Manager Role | |---|---|---| | Source of result | I did it myself | The team did it with my help | | Key metric | My throughput and task quality | Team results, retention, velocity | | How the working day is spent | Focused on a task | In conversations, retrospectives, decisions | | What "I was useful" means | Closed a complex task myself | Helped someone else close a task better | | Response to an employee's problem | Do it for them | Help them figure it out and do it themselves | | Main fear | Doing something poorly | Not letting the team grow | | What is developed | Own expertise | Other people and the system | | How career grows | More complex tasks, higher expertise level | Wider area of responsibility, more teams | | Source of tiredness | Volume of tasks | Emotional load from people | | Success signal | Praise for a result | The team works without me for a week |
Understanding this table is the first step toward transition. When someone sees that the manager's key metric is "the team works without me for a week," their idea of what a good working day looks like begins to change.
Seven Symptoms That You Are Stuck in the Expert Role
In consultations I have assembled a list of recurring patterns. If you recognise three or more — the transition to the manager role has not happened yet.
1. You are the strongest specialist on the team for the content of the tasks. Employees come to you with questions not because you are their manager, but because you know the subject better than anyone. You answer, explain, sometimes show on your screen how to do it. The team gets used to the idea that the final knowledge lives with you, and does not grow its own. 2. You regularly "finish off" employees' work in the evenings or at weekends. You tell yourself it is "faster to do it myself than to teach." As a result, the employee does not learn, your working week becomes 60–70 hours, and the quality of your management decisions drops from exhaustion. 3. You are afraid to hire people who are stronger than you in their specialty. There is a fear that they will see gaps in your expertise. In reality, a strong manager builds a team of people who are stronger than them in their own domain. If you cannot hire such a person, you have stayed in the expert role. 4. Your calendar is full of tasks, not conversations. Management work happens primarily in communication: one-on-ones, syncs, retrospectives, hiring, negotiations. If your calendar is dominated by slots for "working on a document," "finishing a report," or "closing a ticket" — you are still working as an expert. 5. You do not know what your employees care about outside work or what their plans are for the next 6–12 months. Not in terms of gossip, but in terms of professional intentions. What is the next step your strong analyst sees for themselves? Is your key engineer about to leave in three months? If you do not know, you are not managing the team — you are using it as a tool. 6. Employees do not come to you with bad news first. If you find out about a problem from an adjacent department, a client complaint, or metrics — that is a sign there is no psychological safety in the team. A manager does not make bad news frightening; they help deal with it. An expert often reacts with "how did this happen" and unconsciously teaches the team not to be honest. 7. When you go on holiday for two weeks, the team stops or saves up decisions for your return. This is the most honest test. If nothing moves without you, you are a bottleneck, not a manager.
I have worked through these symptoms with dozens of managers between 2024 and 2026. For most people who are stuck, three or four symptoms coincide at the same time. The good news is that the transition to the manager role is not a question of talent. It is a question of changing habits and priorities.
Three Real Cases: What Being Stuck Looks Like in Practice
Case 1. A Head of Sales Who Still Attends Meetings Himself
A strong salesperson became head of a team of six managers. After eight months, the team has missed the plan for two quarters in a row. The manager himself is closing more deals than three of his managers combined. On review, it emerged that 70% of his working time was going on personal client meetings and reworking commercial proposals that he found it "easier to rewrite than to explain." The team had grown used to him running the difficult deals and was not learning to run them itself. His decision: stop taking on new deals, hand over current ones to two strong managers, and spend three months working exclusively on process and coaching. Two quarters later, the team hit its plan for the first time in a year.
Case 2. A CTO Who Keeps Writing Code
A CTO at a company of 60 people complains of exhaustion and a feeling that the team never finishes projects. When reviewing the calendar, it turned out that four days out of five he was working on release code, and strategy, hiring, and architectural reviews got one meeting per week. The team perceived him as a senior developer, not a technical director. After the audit, he set a rule: no more than four hours of coding per week, and only on demos or prototypes, never on production. Six months later, two strong architects he had finally found time to hire rebuilt the release process, and deadline failures stopped.
Case 3. A Marketing Director Who Reviews Every Publication
A marketing director at a large B2B company read every piece of copy before it was published — and often rewrote it. A team of five editors and copywriters felt that their work had no value. Two people left in a single quarter. The solution was to introduce editorial standards, train the senior editor to be responsible for quality, and move the control point from every individual text to a quarterly audit. Four months later the team stabilised, and the director had time for strategic work for the first time.
The common thread across all three cases: the manager did not consider their expert work a problem for a long time. Understanding the difference between roles only comes when a person sees the price of being stuck — not in personal feelings, but in team results.
The Myth That the Best Specialist Makes a Bad Manager
The phrase "the best salesperson becomes the worst sales manager" or "the best engineer makes a bad team lead" is often repeated. This is an oversimplification, and it causes harm. In practice, expertise helps in several key situations. A manager with strong expertise makes decisions faster, evaluates quality more accurately, hires better, and moderates technical disputes more effectively.
The problem is not expertise itself. The problem is that the new manager uses expertise in the wrong place: they apply it to do a task themselves, rather than to help the team do it better. Expertise should work toward scaling the team, not toward remaining the best individual performer.
A simple test: take a task you recently closed yourself instead of handing it to a direct report. Answer honestly — what would have happened if the employee had closed it? Probably slower and sometimes worse. But after three or four iterations they would have learned. Meanwhile, you could have done something that only you can do: hire a new strong person, negotiate with an adjacent department, change a process that is blocking the whole team.
When a Manager Does Need to Step In as an Expert
Refusing all expert work is just as much of a mistake as being stuck in it. I identify four situations where stepping in is appropriate.
1. A crisis where the cost of a mistake is higher than the cost of learning. A major client failure, a release disaster before investors, a public incident. The team needs a fast solution. After two or three weeks, the manager returns to normal mode. 2. A hiring or letting-go decision where the cost of a mistake is too high. Key interviews and final conversations are the manager's expertise in the domain of people. 3. Strategic decisions that will affect the team for a year ahead. Product architecture, choosing a major partner, moving to a new methodology. 4. Training. Showing how to do something once or twice is fine. The key is not to turn this into a permanent shortcut that sends the task back to you.
The boundary is simple: stepping in as an expert is appropriate if it is time-limited and does not replace the regular work of employees.
A 90-Day Plan for Transitioning to the Manager Role
Weeks 1–2. Audit Your Calendar and Tasks
Extract everything your working time went toward over two weeks. Divide tasks into three groups: "only I could do this as a manager," "an employee could have done this but I did it," and "nobody should have done this — it is noise." If the first group is less than 30%, you have a skew toward expert work.
Weeks 3–4. One-on-Ones with Every Person on the Team
Schedule 45-minute meetings with each employee — recurring, not one-off. At the first meeting, ask three questions: what is going well for you right now, what is getting in the way of your work, what do you want in a year. Do not offer solutions at the first meeting. Your job is to listen, not to fix. An expert immediately jumps to solving. A manager first builds the picture.
Weeks 5–6. Delegation with Full Ownership Transfer
Take three tasks from the second audit group and hand them over with full accountability, not as "help me." Agree on result criteria in advance: what done looks like, by when, how we will check. Do not step in to the process. If the intermediate result is worse than what you would have done, hold back from redoing it. Instead, debrief in a retrospective.
Weeks 7–8. Team Metrics Instead of Personal Metrics
Formulate two or three metrics by which the team will be evaluated this quarter. Once a week, answer in writing (even if only for yourself): "What did I do this week that helped the team get stronger?" If you have no answer three weeks in a row, the approach needs to change.
Weeks 9–12. Reassess Your Own Role
Write down how the team has changed over 12 weeks. Find one task that used to require your involvement every day and now runs without you. That is the first objective signal that the transition has happened.
What to Do When the Pressure to Do Everything Yourself Weighs on You
Part of the pressure comes not from the company but from within. Many new managers grew up in environments where they were praised for personal results. In consultations I regularly hear: "I feel like I am not working when I spend the whole day in conversations." This is normal for the first few months.
Three things that help:
- An honest conversation with your own manager about what counts as a result in the new role.
- A management decision journal. Once a week, write down three decisions you made as a manager. After two months, the personal feeling of "I am not doing anything" gradually fades.
- A mentor who has already made this role change. One hour per month with someone who went through the same transition three to five years ago gives more than a dozen management books.
FAQ
How do I know if I am ready for the manager role if I am a strong expert?
The most honest test is the question: "Do I feel pleased when someone else does my former work well?" If yes, you are ready. If it triggers irritation or envy, it is worth sorting out your own identity first.
How long does the transition from expert to manager take?
In my observation, a conscious transition takes 6–12 months of active work on yourself and your habits. The first 90 days are the most intensive period, when the calendar and task set change. A fully formed new identity takes a year to a year and a half.
Can you combine the expert and manager roles?
In the first 3–6 months in a team lead role with a team of up to five people — partially, yes, to maintain context. Beyond that, combining the roles becomes a brake on the team. With eight or more people, combining is physically almost impossible.
What should I do if the company expects me to produce expert output alongside the team?
This is a signal that the company does not understand why it hires managers. You need to work on it through a direct conversation with your own manager, through reformulating KPIs, and sometimes through changing jobs. It is not possible to work in such a system for long — either you will burn out, or the team will not grow.
What is the difference between a manager and a leader?
A manager is responsible for predictability, processes, and operational results. A leader sets direction and brings people together around an idea. At the early stage of the transition, it is more important to master the management set: delegation, one-on-ones, metrics. Leadership comes later as a layer on top.
What should I read about transitioning to a management role?
The essential minimum: Andy Grove's High Output Management and Camille Fournier's The Manager's Path. It is also useful to keep your own observation journal — your own cases will be more accurate than any book.
The difference between the expert role and the manager role is not in the salary or the nameplate on the door. These are different professions with different result currencies. An expert earns for themselves; a manager earns through the team. New managers get stuck in the expert role because nobody tells them the profession has changed. If you recognised yourself in the symptoms in this article, start with a calendar audit and one-on-ones. After that, the team will start showing you that the transition has happened.
