
In this lecture you take one task you still do yourself and plan the first four weeks of handing it over: the week of writing your own work down, the week of giving one task away with a written result, the week of reviewing the result instead of the steps, and the week of spending the freed hours on the work only you can do.
This course is built from five disciplines: technical leadership, delegation, people management, coaching and mentoring.
The map of the course
A dictionary for reading lectures from other fields as work with your own engineers
Three questions to ask after every lecture
A short self-diagnostic that shows which sections to watch first
Download the Four Week Handover Plan and fill in one line after each lecture.
The technical leader as a strategist rather than the strongest engineer
How the role differs from the neighbouring ones
Balancing what the business wants against what the technology needs
The competencies that actually matter in the job
Building a technology strategy around business goals
The stack, and the criteria for choosing it
Architecture: monolith, service-oriented, microservices
The current directions: cloud, AI, data-driven, security by design
Organising engineering teams: structures and roles
Agile, Lean and DevOps as the working basis
Hiring and keeping strong engineers
Building an engineering culture, and mentorship inside it
Working with the chief executive, product and the business units
Prioritising technology initiatives when everything is urgent
Balancing new work against maintaining what exists
Performance metrics, and treating security and risk as part of the job
Supporting company growth with technology
Architecture built for scale
Cost management and infrastructure optimisation
Supporting acquisitions and entry into new markets
The technology directions worth watching
Creating competitive advantage through innovation rather than announcements
Building a partner ecosystem
Driving a transformation rather than being handed one
What delegation does to team output and to your own effectiveness
The psychological barriers and the myths behind them
Formulating a task with SMART so it can actually be handed over
The Eisenhower matrix, and what not delegating costs you in stress
The stages from choosing a task to checking it is done
RACI for assigning responsibility unambiguously
Managing delegated work in Trello, Asana or Jira
Giving feedback without demotivating, and the standard mistakes
Using delegation as a development tool rather than offloading
The GROW model for setting and reaching a goal
Matching task difficulty to skill so it motivates rather than crushes
Delegating strategic goals through OKR, and adding engagement elements
Freeing up time for the work only you can do
Pomodoro applied in a delegation context
Automating routine with Zapier and IFTTT
Agile and Scrum principles, and dashboards for tracking progress
A portrait of the person the role requires
Where to look: recruiters, sites, agencies
Assembling a strong team rather than a group of strong individuals
Experienced and settled against young and hungry
Retraining people who already know a lot
Developing people early in their career
Creating an atmosphere where development is normal
How these meetings affect actual results
The format and the outline
Recording what was decided
What to do with many people and little time
Bringing out capability people have not shown yet
Choosing who can stand in for you
Developing that person deliberately
Dealing with someone who has stopped caring
The brilliant expert who is impossible to work with
Why money does not motivate the way people assume
What non-financial motivation actually consists of
Why you pay what you pay
How much, and how to find out what the market does
How often to raise
Pay during a downturn
The relationship between a bonus and motivation
What to actually pay a bonus for
The types available to you
Making sure your best engineer is not poached
Why the strongest people leave, and what to do about it
Negotiating when someone asks for more
Whether and how to beat another company's offer
What separates a good strategy from a list of intentions
Building one
Selling it to the team so they act on it
Implementing it
What the method requires before it works
Five differences from management by objectives
Starting it for the first time without the usual pain
Requirements for a key result, and linking it to performance review
Why not everyone wants to be a team
Getting people who dislike each other to work together
Managing conflict inside the team
Building a team that does not need you present
Whether you need to see every step
What to do when mistakes keep repeating
Automating the checking
Keeping control from becoming surveillance
The definition, and the research behind it
The core competencies of a coaching approach
How it differs from every other form of development
The GROW model and the wheel of balance
People have more in common than they appear to
People are curious and want to contribute
People grow inside relationships and act in their own interest
People live inside their own perception, have choices, and define their own integrity
The balance wheel in practice
Questionnaires
The one-to-ten scale
Checklists
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. 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.