Leadership for Technical Experts: Expert to Leader [EN]

This course contains the use of artificial intelligence.

You were promoted for being the best at the work. Then you were asked to stop doing it. Nobody explained that those were the same conversation.

What actually breaks

It is never the technical judgement. It is that a task takes your engineer four days and would take you six hours, so you take it back, and now you are the bottleneck and they have learned nothing. It is the one-to-one you keep rescheduling because it feels like a meeting with no output. It is the brilliant difficult person on your team who everyone routes around, including you. It is discovering that the skill that got you here — being right, fast — is close to useless in a conversation where the point is that someone else works it out.

What this course covers

Thirty-eight lessons. The technical leadership frame first: what the role owns, technology strategy and architecture, organising engineering teams, prioritising against legacy, metrics, scaling, and innovation. Then the thing that breaks first — delegation: why experts specifically do not do it, SMART and the Eisenhower matrix, RACI, feedback that does not demotivate, delegation used deliberately as development through GROW, and buying back your own time. Then the management spine across twelve lessons: who to hire and where, training experienced people and inexperienced ones, one-to-ones that produce something, choosing and growing a deputy, motivating someone who has stopped caring, handling the difficult expert, pay and market rates, bonuses, retention and counter-offers, strategy and selling it to the team, OKR, conflict, and control that does not become surveillance. Then the mode switch: coaching instead of answering, with GROW, nine principles, powerful questions, listening, the language of the person opposite you, and building the culture. Finally mentoring: matching a pair, preparing the mentor, the first meeting, closing it, and the scenarios you will actually hit.

A note on what is and is not technical here

Six of the thirty-eight lessons are technical — the leadership block at the start. The other thirty-two are about people. That is not an oversight, it is the finding. Nothing about managing people is technical, which is exactly why strong engineers struggle with it: there is no correct answer to derive. The coaching block was recorded with a people-function framing and one lesson refers to employee engagement, but GROW, the balance wheel, powerful questions and active listening are not specific to any department.

Who is teaching this

I am Mike Pritula. I built the people system at Preply as it became a unicorn, and I have worked at Wargaming, iDeals and Alfa-Bank. More than 1.6 million students have enrolled in my courses across 185 countries, and over 150,000 specialists have gone through my programmes. I hold PHRi and SHRM-CP certifications and represent HRCI in more than ten countries.

What is included

• Lifetime access to all 38 lessons

• Active instructor support in the Q&A section

• A Udemy Certificate of Completion

• Working models: GROW, RACI, SMART, the Eisenhower matrix, OKR, the balance wheel, the one-to-one outline, the mentoring agreement

• Direct treatment of the situations experts actually get stuck on

Where to start

Name one task you took back from someone this month because it was faster to do it yourself. That decision cost more than the hours it saved, and lesson seven is about why. Enrol now and start today.