Leadership & CommunicationLeading teams · Lesson 1 of 21

Leadership foundations and adaptive styles

Article · 14 min · 9 min lecture

Video lecture

Leadership foundations and adaptive styles

12 chapters · about 9 min · full transcript

Coming soon

Chapter 1 of 12

Leadership foundations

  • Behaviours, not a title
  • Adapt your style
  • Build trust deliberately
  • Set direction on one page

The narrated lecture is in production

Every chapter is scripted and ready. Browse the chapters and read the full transcript now — the video will appear here when it’s published.

Chapters

Leadership is a set of behaviours, not a title

Leadership is the ability to help a group of people achieve a shared goal. Formal authority helps, but many of the most effective leaders in organisations have no direct reports: project leads, senior specialists, account managers, founders of small teams. What they share is a set of learnable behaviours: setting direction, building trust, enabling people to do their best work and taking responsibility for results.

Management and leadership

The two overlap, and every team needs both.

Management focuses onLeadership focuses on
Planning and budgetingSetting direction and purpose
Organising and staffingAligning people behind the direction
Controlling and problem-solvingMotivating and inspiring
Predictability and orderChange and improvement

A team with management but no leadership runs efficiently in the wrong direction. A team with leadership but no management has energy but misses deadlines.

Adapting your style

No single style works in every situation. A useful way to think about style is to consider two dimensions: how much direction you give (what, how, when) and how much support you give (encouragement, listening, involvement in decisions). Situational leadership models suggest matching these to the person's competence and commitment for the specific task.

SituationPerson's stateHelpful style
New task, enthusiastic but inexperiencedLow competence, high commitmentDirecting: clear instructions, close follow-up
Learning, some frustrationSome competence, lower commitmentCoaching: direction plus encouragement and explanation
Capable but unsureHigh competence, variable confidenceSupporting: listen, encourage, share decisions
Expert and motivatedHigh competence, high commitmentDelegating: agree outcomes, step back

The same person may need directing on one task and delegating on another. A common mistake is to use one style for everyone, usually the style you personally prefer.

Trust: the foundation

People follow leaders they trust. A practical way to think about trust is that it grows from three things:

  1. Competence: you know what you are doing, or you know how to find out.
  2. Reliability: you do what you say, consistently.
  3. Care: you have people's interests at heart, not only your own.

Trust is built slowly through many small actions and can be lost quickly. Admitting mistakes, giving credit generously and keeping confidences build it; blaming others, overpromising and inconsistency destroy it.

Setting direction

A team needs to know where it is going and why it matters. Create a short, clear statement of purpose and a few priorities:

Team purpose: Help small retailers in our region sell online with less effort.
This quarter's priorities:
1. Launch the new onboarding flow (target: 80% of new sellers complete setup in one day)
2. Reduce support response time to under 4 working hours
3. Hire and onboard two engineers
Not a priority this quarter: new marketplace integrations

The "not a priority" line is as important as the priorities. It gives people permission to say no.

Worked example

Illustrative. Amina, a newly promoted team lead at a fictional software company in Lahore, managed five former peers. At first she tried to be "one of the team" and avoided giving direction, then swung to micromanaging when a deadline slipped. With coaching, she adopted a situational approach: close direction for a junior developer on a new payments feature, coaching for a mid-level developer learning to lead code reviews, and delegation for a senior engineer on the architecture. She also wrote a one-page team purpose and priorities. Within two months, the team reported greater clarity, and Amina spent less time firefighting.

Leadership in different cultural contexts

Expectations of leaders vary. In some workplaces, including many in Pakistan and the Gulf, people may expect leaders to be more directive and to show respect for hierarchy; in others, such as many UK and US workplaces, a more participative style may be expected. Neither is universally better. Effective leaders learn the local norms, explain their approach, and adapt while staying consistent in their values.

Hands-on: write your team charter and style map

Spend 30 minutes producing two short artefacts you can share with your team this week.

1. A one-page team charter

Team purpose (one sentence):  Why do we exist, and for whom?
Top 3 priorities this quarter:  1. ...  2. ...  3. ...
Explicitly NOT a priority:      (things we will say no to or pause)
How we measure success:         2-4 measures we review monthly
How we work together:           response times, meeting rhythm, decision rules
What you can expect from me:    e.g. weekly 1:1s, decisions within 48 hours, credit in public

2. A situational style map (private, for you)

PersonTaskCompetence (L/M/H)Commitment (L/M/H)Style I will useNext check-in
AishaClient reportingHHDelegatingMonthly
AishaBudget forecastingLHDirectingTwice a week
TomSupplier onboardingMLCoachingWeekly

Review the map monthly. The goal is to move each person-task pair towards delegating.

Optional AI prompt (anonymise names first):

Act as an experienced leadership coach. Here is my draft team charter: [paste].
1) Point out anything vague or unmeasurable.
2) Suggest what might be missing from "NOT a priority".
3) Ask me three questions a sceptical team member might ask.
Do not rewrite it for me; give feedback I can act on.

Common mistakes

  • Using one style for everyone.
  • Confusing being liked with being trusted.
  • Setting too many priorities, so none are priorities.
  • Avoiding decisions to keep everyone happy.
  • Doing the team's work instead of leading it.

Quick self-check

For each person in your team, write down one task they are working on and the style that fits their competence and commitment for that task. Compare it with the style you actually use. Where they differ, plan to adjust this week.

Key takeaways

  • Leadership is a learnable set of behaviours: setting direction, building trust, enabling people and owning results.
  • Match direction and support to each person's competence and commitment for the specific task.
  • Trust grows from competence, reliability and care.
  • State the team's purpose, a few priorities and what is not a priority.

Check your understanding

Quick questions to lock in the lesson. They don’t count towards your certificate.

  1. A motivated new hire is starting a task they have never done. Which style fits best?
  2. Which action most directly builds trust?
  3. Why include a 'not a priority' line in team priorities?

Put it into practice

Write a one-page purpose and priorities statement for your team (or a team you work with), including at least one explicit non-priority, and share it for feedback.

Enrol for free to save your progress

Reading is always free. Enrol to keep your place, take the final assessment and earn a verifiable certificate.