How Do I Develop Someone Who Is Technically Brilliant but Weak at Managing People?

The best violinist is not automatically the best conductor

I have used this analogy for years. It is a very different skill to play an instrument from the skill required to conduct an orchestra. Yet businesses regularly take their best violinist, hand them the conductor's baton and wonder why they struggle. Nobody taught them how to conduct. That is often exactly what happens with new managers.

Their old strengths can become part of the problem

Technical excellence probably helped them get promoted. They are fast. Capable. Experienced. They know the answer. They can spot mistakes immediately. All useful. But as a manager, those strengths can produce new traps. They do everything themselves. Correct everybody constantly.

Take difficult work back. Become the answer to every problem. Lose patience when others are slower. And gradually become an enormous bottleneck.

They may still be doing the old job plus management

This happens constantly. Before promotion they had a full-time technical role. After promotion they still have most of that role. Plus: one-on-ones; performance management; team meetings; planning; recruitment; coaching; delegation; problem-solving; reporting; conflict; and decision-making.

So what happens? They work longer. Become frustrated. Management gets fitted around “the real work.” And everybody wonders why the promotion is not going particularly well. The business has not really redesigned the role. It has simply added management on top.

Explain that management is now part of the real work

This mindset has to change. A manager may say:

“I haven't got anything done today. I've spent the whole day dealing with people.”

But if you manage people, dealing with people may have been the work. Developing someone. Clarifying priorities. Removing a blockage. Having the difficult conversation. Reviewing performance. Helping somebody make a better decision. Those are not interruptions from management. They are management.

Make the role transition explicit

Do not assume they understand how success has changed. Ask: What did success look like in the old role? What does success look like now? Before: Personally produce excellent work. Now perhaps: Build a team capable of consistently producing excellent work. That is a major shift.

Their output is no longer only their own output

A technically brilliant individual contributor can be measured largely through their own performance. A manager has a multiplier effect. What happens through the people around them? Is the team improving? Are standards clear? Are people developing? Are problems being solved lower down? Is work getting done without the manager personally touching everything? That is a different scorecard.

Stop rewarding them only for doing

If every piece of recognition still comes from their technical output, what will they keep doing? Technical work. If management matters, recognise management. Someone they trained becomes capable. Notice it. Their team improves. Notice it. They delegate something successfully. Notice it. A difficult conversation is handled well. Notice it. The rewards need to support the new job.

Teach them to ask questions instead of supplying answers

This is often one of the biggest changes. Technical experts are used to knowing. Someone asks:

“What should I do?”

They answer. Efficient. But management requires another option.

“What do you think?”

Then:

“What have you tried?”

“What are your options?”

“What do you recommend?”

The manager is no longer only solving the problem. They are developing the person.

Stop them catching every problem ball

Technical experts often find problem-ball catching irresistible. They can solve it faster. So they do. Customer problem? They take over. Quality issue? They fix it. Employee unsure? They tell them. Deadline in trouble? They jump in. The business gets through today. But the team learns very little. The fastest way to solve today's problem can create tomorrow's dependency.

Help them distinguish support from rescue

Support says:

“Let's think this through together.”

Rescue says:

“Give it to me.”

Support leaves the other person thinking and carrying the next action. Rescue transfers the work back to the manager. New managers need to learn that helping somebody does not require taking the problem away.

Teach them to tolerate somebody else's method

This can be very hard for experts. They watch someone perform a task and think:

“That's not how I would do it.”

Fine. But is it wrong? Does the result meet the required standard? If yes, perhaps the manager needs to let it go. There may be several perfectly sensible ways to achieve the result. A manager who insists on cloning their own method will find delegation exhausting.

Teach them the difference between standard and preference

This distinction is enormously useful. A standard matters. Safety. Quality. Customer requirement. Legal requirement. Deadline. Agreed process. A preference may simply be:

“I like doing it this way.”

Managers need to stop turning every personal preference into a compulsory standard. That creates micromanagement.

Give them something real to delegate

Do not merely tell someone:

“You need to delegate more.”

Choose specific responsibilities. What are they currently doing that somebody else could reasonably learn? Who could learn it? What does success look like? What authority will that person need? What checkpoints make sense? Then practise. Delegation is a behaviour, not an aspiration.

Expect delegation to be slower at first

The manager may say:

“It would take me ten minutes. It'll take me an hour to explain it.”

Probably. Today. But if they explain it once, coach it, and the person becomes capable, future work no longer requires the manager. That is the investment. If they keep choosing ten-minute personal efficiency, they may remain the bottleneck forever.

Teach them to build shoulders

If they are moving upwards, they need capable people underneath. I call this building shoulders. Who can carry more? Who is being developed? Who can step up? Who is learning decisions the manager currently makes? Who can handle work that once came only to them? Strong shoulders beneath a manager create room for the manager to grow.

Teach clear expectations

Technically strong managers can become frustrated because:

“Surely they should know.”

Perhaps not. What does good look like? What does completed mean? What standard applies? By when? What authority exists? Make it explicit. The fact that something is obvious to the expert does not mean it is obvious to everyone else.

Teach them What Success Looks Like

A job description tells somebody what their responsibilities are. That is not always enough. The employee also needs to understand: What would being genuinely good at this look like? Start with a few clear development areas. Specific. Observable. Something both employee and manager can recognise. That gives the new manager a much better basis for performance conversations.

Teach them to manage evidence, not irritation

Technical experts can become impatient with weaker performers. They may say:

“They're just not good enough.”

What is the evidence? What was expected? What actually happened? How often? What pattern exists? Specific evidence produces a much stronger management conversation than expert frustration.

Teach them to have difficult conversations early

A new manager may be technically confident and interpersonally avoidant. They can solve a complex operational issue without blinking. But telling an employee: “This isn't meeting the standard” feels deeply uncomfortable. So they wait. Hope. Compensate. Do the work themselves. Then resentment grows. Teach them to address small issues while they are still small.

Prepare, don't rehearse every word

For difficult conversations, help them prepare: What was agreed? What happened? What evidence exists? Why does the gap matter? What do they need to understand? Then have the conversation. They do not need a theatre script. They need clarity.

Teach them to listen

Technical expertise can create a dangerous assumption:

“I already know what the problem is.”

Maybe. But ask. What does the employee think is happening? Is something missing? Did the manager misunderstand? Is the process broken? Good managers remain curious long enough to discover whether their first conclusion was right.

Teach them one-on-ones are not status meetings

A technically oriented manager may turn a one-on-one into:

“Where is Job A?”

“What's happening with Customer B?”

“Have you finished C?”

That is work coordination. Useful perhaps. But development needs more. What are you finding difficult? What are you learning? What do you want help thinking through? What are you working on developing? A strong one-on-one builds capability.

Make the employee do some thinking before the one-on-one

The employee should not arrive waiting for the manager to conduct an examination. Ask them to prepare. What is working? What isn't? What commitments did they make? Where do they need support? What do they want to discuss? That helps the technically brilliant manager learn not to carry the whole conversation.

Teach silence

This can be surprisingly difficult. Ask a question. Then stop talking. Do not answer it for them after three seconds. Let the employee think. Technical experts are used to speed. Development sometimes needs silence.

Teach them not to accept “I don't know” immediately

If an employee says: “I don't know,” the manager may instantly give the answer. Try:

“Humour me. If you did know, what might you say?”

Or:

“What is your best guess?”

Or:

“What options can you see?”

The objective is to exercise the employee's thinking muscle.

Teach them accountability without micromanagement

A new manager may swing between extremes. Either: checking every detail; or:

“I don't want to micromanage, so I'll leave them alone.”

Neither is particularly helpful. Instead: clarify the outcome; agree the owner; agree the date; define done; set sensible checkpoints; then follow up. That is accountability.

Teach them to let people make sensible mistakes

If every error results in the manager grabbing the work back, development stops. Ask: Was the mistake reckless? Or was it a reasonable decision that did not work? If the latter, use it. What happened? What did you learn? What will you do differently next time? Managers need to learn that not every mistake is evidence that delegation failed.

Teach them to recognise progress

Experts can have very high standards. Good. But that can make them notice only the remaining gap. Someone has improved substantially but is not yet as good as the manager. The manager sees:

“Still not good enough.”

The employee experiences:

“Nothing I do is ever enough.”

Recognise progress while still maintaining the standard. Both can be true.

Teach them to give specific feedback

Not:

“You need to communicate better.”

Instead:

“Yesterday you changed the production plan but didn't tell Sales, which meant the customer received the old date. Next time I need Sales informed before the plan changes.”

Specific feedback teaches. Vague feedback frustrates.

Teach them that people are not machines

Technical systems are often predictable. People are less so. Two people can receive the same instruction and respond differently. One needs challenge. One needs confidence. One needs more context. One needs clearer boundaries. Management requires judgement about people, not simply process. That can feel messy to someone who prefers technical certainty.

Do not make them amateur psychologists

They do not need to diagnose everybody. They need to observe behaviour. Ask good questions. Listen. Set expectations. Use evidence. Have conversations. Follow through. Practical management beats endless speculation about people's personalities.

Teach them to handle poor performance rather than compensate for it A technically brilliant manager often hides poor performance by doing the missing work. The customer still gets served. The job still gets finished. Senior leadership sees no problem. Meanwhile the manager is exhausted. Ask:

“Whose performance gap are you currently compensating for?”

Then manage the gap.

Teach them to protect good people

When poor performance is tolerated, stronger employees often pick up the work. A new manager needs to understand that managing poor performance is not merely about the weaker employee. It is also about fairness to the reliable people.

Teach them that management standards apply even to top performers This can be another difficult transition. A technically strong manager may excuse another high performer because:

“They're brilliant at the job.”

But if that person damages the team, ignores processes or behaves badly, the manager has to address it. Results do not buy exemption from behavioural standards.

Teach them consistency

If one employee is challenged and another gets away with the same behaviour, people notice. New managers need to become predictable. Not rigid. Consistent. What does the standard require? Apply it fairly.

Teach them to think beyond today's problem

Technical experts are often excellent troubleshooters. That is useful. Now develop the next question:

“Why does this keep happening?”

And then:

“What system would make it less likely?”

That is the move from technical problem-solver towards organisational leader.

Teach them to conduct the orchestra

This is the real transition. The conductor does not prove their value by grabbing every instrument. Their job is to help the whole orchestra perform. Timing. Standards. Coordination. Development. Direction. Listening. Adjusting. That is management. The fact that the conductor might also be an excellent violinist is almost beside the point.

Redesign their workload

Sometimes development will fail unless the business changes the role. If the manager remains responsible for 100% of their old technical workload, where exactly is management supposed to fit? Decide what they should stop doing. What can be delegated? What should move elsewhere? What should remain because the business genuinely still needs their expertise? Make room for the new job.

Keep some technical involvement where it adds value

The answer is not necessarily to strip away everything technical overnight. Some managers should remain close to the work. Their expertise may be commercially important. But be deliberate. Which technical work should they personally retain? Which should they progressively transfer? Do not let habit decide.

Give them management tools, not just a title

Teach them a practical rhythm. One-on-ones. Weekly meetings. Clear actions. Scoreboards. Progress tracking. What Success Looks Like. Decision boundaries. Those structures give a new manager somewhere to practise management. Without them, the title may change while the working habits remain exactly the same.

Coach the manager themselves

Ask regularly: What are you finding hardest about managing? Which conversation are you avoiding? What are you still doing that somebody else should learn? What keeps being escalated to you? Who are you developing? Where are you rescuing? What evidence shows your team is becoming stronger? Those are development questions for the manager.

Measure managerial progress over time

Do not simply ask:

“How do you think they're going?”

Look for evidence. Are they delegating more successfully? Are fewer problems reaching them? Are their employees becoming more capable? Are one-on-ones happening? Are commitments followed up? Are difficult issues addressed earlier? Is the manager spending less time firefighting? That is progress.

Give them a small number of management-development priorities

Do not tell a new manager to improve fifteen things at once. Choose perhaps three. For example:

Stop rescuing

Ask for employee thinking before answering.

Delegate one significant responsibility

Develop someone else to carry it.

Hold difficult conversations earlier

Address the evidence when the gap first becomes clear. Then review. Once those become stronger, move to the next areas.

A practical development plan for a technically brilliant manager

1. Redefine the job

What does success look like as a manager?

2. Reduce the old workload

Create genuine room to manage.

3. Identify the hero habits

What do they keep taking back?

4. Teach questioning

What do you think? What do you recommend?

5. Build delegation

Give others meaningful responsibility.