Read time: 5 minutes

Hey Subscriber First Name,

A senior sponsor said something to me a few years ago that I've never forgotten.

We were six weeks into a delivery that had been, let's say, politely difficult at the start. I walked into his office to update him and he looked up, grinned, and said: "You know what, I haven't seen you in weeks. That's a really good sign."

I laughed. But on the walk back to my desk, it hit me. He was right. And what he was saying was much bigger than a compliment.

Because when I started out, I thought my job was to do everything. I'd work excessively. I'd be in every room, copied into every email, chasing every update. I thought that's what running a project looked like. And I'd burn out and stress over why things still weren't moving forward, despite the fact I was pouring everything into it.

It took me a long time to realise I had it completely backwards. And if that sounds familiar, you're not alone.

Here's the truth that took me years of delivery to see clearly: if you're still the bottleneck, the project isn't running. You are.

Let me say that again in a different way. If nothing moves unless you reply to the message, answer the question, sign the form, attend the meeting, or chase the update, then the project is held together by your personal presence. And the moment you step away, it stops. That's not a project. That's everything resting on one person.

The best PMs and leaders I've ever worked with don't look busy. They look suspiciously calm. They're not in every meeting. They don't reply to every Teams message within four minutes. They're not the hero who saves every crisis at 10pm. And yet, somehow, their projects move faster, land cleaner, and feel lighter to be on than the ones run by the PM who's drowning in visible effort.

Why?

Because they've built something underneath the project that doesn't need them in the room.

Think about the people running the best-run companies in the world. The ones you've actually heard of. The CEOs whose businesses scale to thousands of people across dozens of countries. They're not reviewing every invoice. They're not sitting in every hiring panel. They're not signing off every decision. They can't. It would burn them out inside a week. What they've done instead is build systems, teams, rituals, and decision rules that run without them. That's the whole job. When a CEO has to be in the room for something to happen, the company has hit its ceiling. When they don't, the company has room to grow.

PMs should think about their projects the exact same way, just at a smaller scale.

This is inspired by James Clear, who shared the idea in Atomic Habits that your results are never really determined by how good your plan is. They're determined by what systems you've put in place underneath it. The plan gets you started. The system is what keeps things moving when you're not standing over it. And that's exactly what great PMs build.

So here are three super simple things you can do to start turning your work into a system:

1. Document it. If you answer the same question three times, it's not a question anymore. It's a missing rule. Write it down. Share it somewhere the team can find it. The next time someone would have come to you, the answer is already there. Decision criteria, escalation paths, "what does done look like". Write it once, and it works forever.

2. Delegate it. Pick a recurring task you still own. The status update, the weekly meeting, the progress chase. Hand it to someone on the team. Not as a favour. As genuine ownership. Give them the authority and the trust to run it. You'll be surprised how quickly people step up when you actually let them.

3. Automate it. Set up the thing that removes you from the loop entirely. A shared tracker the team updates themselves. A template that answers the question before it gets asked. A standing agenda that runs whether you're in the room or not. The goal is to make the right thing happen by default, without anyone needing to chase it.

Now, before you read that and think "this sounds like avoiding responsibility". It's the exact opposite. This is how you build a culture of trust, ownership, and accountability within your projects. You're not stepping back because you don't care. You're delegating and automating responsibly so that the project runs properly and you can monitor, control, and focus your energy where it's genuinely needed. The hard problems, the strategic decisions, the things only you can do. And honestly, that's one of the hardest parts of the job to get right.

Here's the question that will tell you, in about thirty seconds, how much of a bottleneck you actually are:

If you took a two-week holiday tomorrow, with no phone and no laptop, what would break?

Write that list. Be honest. Every item on it is something you haven't designed yourself out of yet. That list is your actual job for the next six months. Everything else is just busy.

The goal of a great PM isn't to be needed. It's to build something that doesn't need you. That sounds counterintuitive when your whole career has taught you that value comes from being in the middle of everything. But stop and think about the PMs you actually respect. The ones whose names come up years after a project. They're never the people who worked themselves into the ground. They're the people who made a project look easy because they'd thought about it properly before it started.

Good PMs deliver. Great PMs disappear. And when your sponsor says, "I haven't seen you in weeks, that's a really good sign," that's when you know you're finally doing the job properly.

MAKING IT HAPPEN: Your Weekly Strategy

Pick one thing this week that everyone still comes to you for. Just one. Then decide: do you need to document it, delegate it, or automate it? If it's a question you keep answering, document it. If it's a task you still own out of habit, delegate it. If it's a process that shouldn't need a person at all, automate it. One thing this week. One thing next week. One thing the week after. In six months you will look up and realise your project runs without you leaning on it. That is what "making it happen" looks like when it scales.

TREND I'M WATCHING: Your Own AI, On Your Phone

Last time I talked about local AI and how the ground is shifting away from renting someone else's chatbot. Recently, Google made it real.

They've just released an app called Google AI Edge Gallery. It's free. It's on iPhone and Android. And here's the thing. It runs AI models directly on your phone. No internet needed. No data leaving your device. Nothing going to the cloud. It's completely offline.

The app actually walks you through what you can do with it. You can chat with a model like you would with ChatGPT. Point your camera at something and ask it to tell you what it's looking at. Record a voice note and have it transcribed into text. There's even a Prompt Lab where you can experiment with different ways of asking things and see how the results change.

The best part is it guides you through all of it. You don't need to be technical. You just download a model, pick a use case, and try it. No setup, no account, no subscription. Just your phone.

I've been exploring the use cases for both work and personal life, and it's surprisingly useful for both. Give it a go and let me know what you think. I'm genuinely curious how people find it.

CHEAT SHEETS

The free cheat sheet library lives here. I'll keep adding to it. Save the link and grab whatever helps.

If this landed with you, forward it to a PM who's drowning in the noise. They'll quietly thank you for it. That is how this community grows, one honest conversation at a time.

bilaljamil.com | Newsletter archive | Hit reply and tell me what one thing on your list you're going to design yourself out of this week. I read every reply.

Take care and speak soon, 

Bilal