Hey Subscriber First Name,

A few things in this one. A lesson about what makes someone worth following, a practical look at the next layer of AI for project managers, and a cheatsheet I put together that explains project management in one page.

I once worked with a project director who barely spoke in meetings.

While everyone else was fighting for airtime, throwing opinions around, talking over each other, trying to sound like the smartest person in the room, he just sat there. Listening. Taking it in.

And then, when the noise died down, he'd ask one question.

One question that somehow cut through everything. That reframed the entire conversation. That made everyone pause and think, "Actually, yeah, that's the real issue."

He never raised his voice. Never pulled rank. Never reminded anyone he was the most senior person at the table. But every single person in that room respected him more than any loud, chest-thumping leader I'd ever seen.

That stuck with me. Because it made me realise something I've seen play out hundreds of times since: the leaders worth following aren't the ones demanding attention. They're the ones earning trust.

So what separates those leaders from everyone else?

After years of working with project teams, reading everything I can get my hands on, and reflecting on my own experience, I think it comes down to three things.

1. They Start With WHY, Not WHAT

Simon Sinek tells a story about the race to build the first aeroplane. On one side, you had a well-funded government-backed scientist with every advantage imaginable. On the other, two bicycle mechanics from Ohio with no funding and no formal education.

Langley wanted to be first. The Wright Brothers wanted to give humans the ability to fly.

When the Wright Brothers succeeded, Langley quit. He didn't pivot to making flight better. He just stopped. Because it was never about the mission. It was about the credit.

The same thing plays out in project teams every day. Some leaders hand out tasks: "Do this by Friday." Others connect the work to something bigger: "Here's why this matters, and here's how your piece fits in."

That shift, from WHAT to WHY, is the difference between compliance and commitment. Your team will do what you tell them. But they'll only go the extra mile if they understand why it matters.

2. They Build Belief Through Evidence, Not Speeches

Steven Bartlett talks about something he calls The Belief Law in Diary of a CEO: you cannot choose your beliefs. You can't just decide to believe in something. Beliefs are formed automatically based on the evidence your brain processes.

Think about what that means for leadership.

If your team doesn't believe the project will succeed, it's not because they're negative. It's because they haven't seen enough evidence that it will. No motivational speech fixes that. No "come on team, we've got this" fixes that.

What does fix it? Making progress visible. Sharing small wins. Showing traction. Pointing at real, tangible proof that things are moving forward.

Evidence creates belief automatically. So instead of trying to inspire people with words, show them with results. Even small ones. Especially small ones.

3. They Take Responsibility Without Taking Blame

You've heard the line: "With great power comes great responsibility." I've always thought it's the wrong way round. With great responsibility comes great power. When you take ownership of what happens next, you take control of the outcome.

And here's the bit that matters: fault and responsibility are not the same thing.

It's not your fault the supplier missed the deadline. It's not your fault the requirements changed halfway through. It's not your fault the budget got cut.

But it is your responsibility to figure out what happens next.

Leaders people actually want to follow don't hide from problems. They don't point fingers or wait for someone above them to make the call. They say: "This happened. Here's what we do next."

That single shift, from blame to ownership, builds more trust than any motivational speech ever could.

MAKING IT HAPPEN: Your Weekly Strategy

Pick one person on your team this week and make their progress visible. Not in a status report. To them, directly. Tell them what their work contributed to. Connect the task they finished to the outcome it moved forward. It takes thirty seconds. But when someone sees that their work matters, not just that it's done, something shifts. They stop just completing tasks and start owning outcomes. That's the difference between a team that delivers and a team that cares about what they're delivering. Purpose, evidence, ownership. You don't need all three at once. Start with one this week and see what changes.

AI for PMs: Layer 2, AI Assistants

Last week we covered Layer 1 (LLMs) and the 6-step prompting framework. This week we're stepping up to Layer 2: AI Assistants.

With Layer 1, you go to the AI. You open a tool, type a prompt, get an answer. Layer 2 flips that. The AI comes to you. It's built into the tools you're already using, watching what you're doing, and chipping in. Think of it like a helpful colleague sitting next to you while you work. "Want me to tidy up that email?" "Here's a summary of that hour-long meeting." "This paragraph could be clearer." That's what Microsoft Copilot does inside Outlook, Teams, and Word. Or Google Gemini inside Workspace. You're still doing the work, but someone's got your back.

For project managers, this means less time formatting reports, writing up meeting notes, and polishing communications. The AI handles the grunt work so you can focus on what the communication actually needs to achieve. If your organisation has rolled out Copilot or Gemini, you'll already know what I mean.

Try this week: Next time you come out of a long meeting, use your AI assistant to generate the summary and action items instead of writing them up manually. If your organisation hasn't rolled out Copilot or Gemini yet, tools like Claude Projects and Custom GPTs give you a taste of what's coming. Upload your project brief and ask it to help draft your next status update. Either way, the shift is the same: stop doing the admin from scratch and let the AI handle the first pass.

Want to go deeper? Read the full guide: Introduction to AI for Project Managers

A Quick Word

I put together a cheatsheet this week that explains project management in one page. What a project actually is. The five core components. The triple constraint. Five styles of PM. The myths. The reality. Everything I wish someone had handed me when I started. Textbooks give you the theory. Experience gives you the truth. This gives you both. You can download it here. Save it, share it with someone starting their PM journey.

If this landed with you, forward it to someone who's trying to lead without the loudest voice. That's how this community grows. One conversation at a time. Explore more insights and interactive experiences at bilaljamil.com.

Got a challenge you're facing or a topic you'd like me to cover? Hit reply and tell me. I read every response and your questions shape future editions.

Missed a previous edition? You can catch up on every issue in the newsletter archive.

Take care and speak soon, 

Bilal