Motivating and developing people

0:00 Motivating and developing people

Think about the best manager you've ever had. Now think about what they actually did. It's rarely a big speech. More often it was small things: they trusted you with something important, they noticed when you'd improved, they had your back in a difficult meeting, and they helped you see where you could go next. In this lecture you'll learn what research suggests motivates people at work, how to run one-to-ones that people value, how to coach with the GROW model, and how to plan development so people actually grow.

0:39 Why it matters

Why does this matter? Because motivated, growing people do better work, stay longer, and help others grow too. And disengagement is expensive. It shows up as quiet quitting, missed ideas and good people leaving. You can't install motivation in someone like software. But you can create the conditions where it's much more likely. And you can do that with habits that take an hour or two a week, not a big programme. That's what we'll build today.

1:12 What motivates

First, the concept. Pay and security matter a great deal. If people feel unfairly paid or insecure, motivation suffers. But beyond a fair baseline, research on motivation, for example self-determination theory, points to three psychological needs. Autonomy: some control over how, when and with whom I work. Competence, or mastery: the sense that I'm getting better and doing good work. And relatedness: belonging, and a connection to something that matters. Here's the key idea. Your job is to design work and conversations that feed those three needs.

1:50 The game designer

Here's an analogy. Think of a video game that people can't put down. It gives you choices about how to play: autonomy. It gets steadily harder at just the right pace, and shows you your progress: mastery. And often you play with friends, towards a goal in the story: belonging and purpose. Nobody has to bribe players to keep going. Good work can have the same design. Clear goals, room to choose the route, visible progress, and people you enjoy working with. You're the level designer.

2:27 One-to-ones

So how do you do that in practice? The single most effective habit is a regular one-to-one. Thirty minutes every week or two. And here's the rule: it's their meeting, not your status update. Their topics first. Then blockers: what can I unblock for you? Then feedback both ways, including asking, what's one thing I could do differently to help you? Then, at least monthly, growth: skills, career goals and stretch opportunities. Finish with clear actions. And keep brief notes. Nothing destroys trust faster than a promise you forgot.

3:06 Coaching with GROW

Now coaching. When someone brings you a problem, the fastest thing is to tell them the answer. But people remember what they discover, and they build capability. So use GROW. Goal: what would a good outcome look like? Reality: what's happening now, and what have you tried? Options: what are three possible approaches, and what else? Will, or way forward: which will you take, what's the first step, and when? A useful personal rule is to ask at least three questions before you offer a suggestion. It feels slow. It saves enormous time later.

3:47 Worked example 1: Maria and Kamran (illustrative)

A simple worked example. Maria, a developer in a small software team in Lahore, tells her lead, Kamran, I'm stuck, the client keeps changing the requirements. Kamran's instinct is to call the client himself. Instead, he coaches. Goal? A stable scope for the next sprint. Reality? Changes arrive by chat, from three different people. Options? Maria suggests a single change log, one named contact, and a weekly change review. Will? She'll propose it to the client on Thursday. It works, and next time she handles it without asking.

4:25 Worked example 2: Claire in London (illustrative)

Now a realistic business scenario, illustrative. Claire leads a fifteen-person customer success team at a software company in London. In the annual survey, growth scores are low and two strong people have left for bigger roles elsewhere. Claire introduces three things. Fortnightly one-to-ones with a growth slot every month. A one-line development plan for everyone: career goal, skill, stretch task, mentor, and one piece of learning. And specific, public recognition in the weekly team call. Six months later, two people have moved into internal team-lead roles, and the growth score has risen noticeably. The investment: about three hours of Claire's week.

5:09 Development and recognition

A word on development and recognition. Most learning happens on the job. A widely used rule of thumb says it comes mainly from challenging experiences, then from people, like coaching and mentoring, and least from formal courses. Treat the exact proportions as a rough guide, not a law. So when you plan development, lead with a stretch assignment. And recognition should be specific, timely and sincere. Not great job everyone. Instead: the way you restructured the onboarding email cut our support tickets this week. Thank you. That tells the person exactly what to do more of.

5:51 Watch me: preparing a 1:1

Watch me do it. I'm preparing for a one-to-one with an illustrative team member, Tom. I open his shared one-to-one doc. Under their topics, he's added: unsure about the new pricing process. I note one piece of feedback in situation, behaviour, impact form. Under growth, I check his plan: goal, account management; stretch task, lead the renewal call with a mid-sized client. I also ask an AI assistant, using no personal details, for five coaching questions on building confidence in client calls. I pick two that fit, and write my rule at the top: three questions before advice.

6:34 Common mistakes

Common mistakes. Cancelling one-to-ones when you're busy, which tells people exactly where they rank. Turning them into status updates. Giving answers instead of coaching. Assuming everyone is motivated by what motivates you. Development plans that list courses and nothing else. Generic praise, or praise only for the loudest people. And letting an AI write recognition or performance feedback you don't genuinely mean. People can tell, and it corrodes trust. Use AI for preparation, never as a substitute for your own attention.

7:09 Measuring success

How do you know it's working? Measure it, gently. Track whether one-to-ones actually happen: aim for well over nine in ten kept, not moved. Watch your team's engagement or pulse survey, especially the questions about growth and recognition. Count internal moves and promotions, not just exits. And ask directly, every quarter: on a scale of one to ten, how much are you learning here, and what would make it a ten? Write the answers down. If the same theme appears from three people, that's not a personal issue. That's a system issue, and it's yours to fix.

7:51 Recap and try this now

Let's recap. Beyond fair pay, people are motivated by autonomy, mastery and belonging with purpose. One-to-ones are their meeting. Coach with GROW, and ask before you tell. Plan development around stretch experiences, and recognise specific contributions sincerely. Your try this now: set up a shared one-to-one doc for each person using the lesson template, book the next meeting, and write one development line for each person on your team. Next module, we move to feedback, difficult conversations and conflict, starting with how to give feedback people can actually use.