Module 1: Becoming a Leader

Manager vs Leader: Both Matter

You will often hear that managers and leaders are different people: managers handle the boring admin while leaders inspire. That idea sounds attractive, but it causes real damage. A team with inspiration and no organisation misses deadlines and burns out. A team with perfect processes and no sense of direction does the minimum and leaves. If you lead a team, you are paid to do both. This lesson helps you see the two sides of the role clearly so you can check which side you are neglecting.

What management is

Management is about making work predictable. It answers the question "How do we get this done reliably?" Typical management tasks include:

• Planning work, setting deadlines and allocating people to tasks
• Tracking progress and spotting problems early
• Managing budgets, schedules, stock or other resources
• Making sure policies, quality standards and legal requirements are followed
• Handling hiring, leave, performance records and other people processes

When management is weak, you see missed deadlines, duplicated work, confusion about who owns what and constant firefighting.

What leadership is

Leadership is about direction and commitment. It answers the questions "Where are we going, why does it matter and why should people put in their best effort?" Typical leadership tasks include:

• Explaining the purpose of the team and how its work matters to customers or the business
• Setting a direction and helping people see their part in it
• Building trust so people tell you the truth
• Developing people so they grow in skill and confidence
• Leading change and keeping morale steady during difficult periods

When leadership is weak, you see people doing exactly what they are told and nothing more, good staff leaving, and a team that falls apart when plans change.

Why you need both

Think of management as the engine and leadership as the steering. An engine without steering goes fast in the wrong direction. Steering without an engine points the right way but goes nowhere. Most new team leaders have a natural strength on one side. People promoted because they were excellent at the technical work often lean towards management: they love plans and checklists but find conversations about purpose awkward. People promoted because they are well liked often lean towards leadership: they are good at motivating but let follow-up slide.

Your goal is not to become equally brilliant at both on day one. It is to know your default and deliberately build habits on the weaker side.

A worked example

Grace supervises a team of six customer service agents for an internet provider in Nairobi. Complaints about slow responses are rising. Her first reaction is pure management: she introduces a target of answering every ticket within four hours and a daily report of overdue tickets. Within two weeks response times improve, but agents start closing tickets without solving the problem just to meet the target, and two agents complain that nobody asked them what was causing delays.

Grace steps back and adds the leadership side. She holds a meeting where she explains why response time matters: customers who wait feel ignored and cancel their contracts. She asks the team what slows them down. They point out that one common fault needs approval from the technical team, which takes a day. Grace negotiates a faster route with the technical lead (leadership through influence), then updates the target to measure tickets solved, not just closed (better management). Results improve and the team feels heard.

Notice that neither side alone solved the problem. The management fix created a new problem, and a purely inspirational speech would not have removed the technical bottleneck.

Common mistakes to avoid

• Calling yourself "a leader, not a manager" to avoid admin. Your team still needs schedules, clear priorities and fair processes.
• Hiding behind process when people need you to explain the why. Rules without reasons feel like control.
• Measuring only what is easy to count. Targets shape behaviour, so check they encourage the result you actually want.
• Doing the technical work yourself because it feels productive. Your job is now the team's results, not your personal output.

Over the rest of this course you will build practical skills on both sides: expectation setting and delegation (management), and trust, feedback and coaching (leadership).