Read time: 5 minutes

Hey Friend,

Early in my career, I watched one of my project plans get shredded by the board in a review meeting. I had walked in with good intentions: a clean plan, sensible priorities, and a story about progress that looked solid enough to hold up. An hour later the plan was in pieces, pulled apart by a question I had not prepared for, a priority the board cared about more than I did, and a decision that suddenly had to be reopened.

I remember thinking, there goes the work. Then I looked again at what had actually happened. The question killed an assumption I had carried for weeks. The reopened decision finally found an owner. The awkward priority forced a conversation that should have happened a fortnight earlier. The plan had been interrupted, but the project had moved.

That meeting stayed with me, because I have watched the same thing happen every week since. Most of us build our weeks around an imaginary clean line. Monday to Friday, planned tasks, neat blocks, steady progress. Then the week arrives and behaves like a redirect.

Something pings. Someone appears. A decision slips sideways. A risk moves from the corner of your eye into the middle of the room.

It is tempting to treat all of that as interference. The real work is over here, neatly listed. The interruptions are over there, getting in the way. So we spend the week quietly irritated at the very things trying to tell us something about the project.

I recently reflected on something James Clear, the author of Atomic Habits, once wrote, and it landed differently because of that meeting. He put it simply: "The interruption is not standing between you and your life. It is your life." His point was broader than work, but I could not stop seeing it through the lens of delivery.

A good plan still matters. It gives you direction and something to test reality against. But a plan is only a map drawn before the weather changed, and interruptions are the road signs telling you the route has moved.

I lost a lot of energy in those early years protecting a version of the week that had already disappeared. I kept returning to the original plan as if the interruption was a temporary inconvenience, something to clear before the proper work could resume. The strange thing is that the proper work was usually inside the disruption.

The awkward call clarified the decision. The urgent message exposed the gap. The wobble from a stakeholder showed me where trust was thinner than I thought. None of it looked tidy on a plan, which is exactly why it is so easy to undervalue. Interruption work leaves something quiet behind: a misunderstanding removed, a risk named early, a decision made before it hardened into delay.

It can feel like you spent the day being dragged away from the project, when you actually spent it keeping the project honest. There is a difference between reactive and responsive. Reactive has no judgement in it, everything gets the same attention because everything feels urgent. Responsive notices the redirect and asks whether it is telling you something useful.

Because not every interruption is a signal. Some messages are noise. Some meetings are habit dressed up as urgency. Some people are just trying to outsource their thinking. The craft is telling the difference without becoming hard or dismissive, and the best PMs I have worked with do exactly that. They do not treat every interruption as a crisis, but they do not wave it away because the plan said today was meant to be quiet.

Is this a genuine blocker, or a passing anxiety? Is the week messy because people lack discipline, or because the project has moved into a phase where coordination is the work?

That last question changed how I see busy weeks. Some phases of delivery are meant to be noisy. Decisions are being shaped, and people are working out what a change means for their corner of the world. Expecting quiet in that kind of week is like expecting a station concourse to feel like a library.

The movement is the point.

A good project manager does not only protect the clean line. They help the team move through the redirects without losing the destination. So when a day keeps getting interrupted, I have learned to stop asking how do I get back to the real work, and start asking what this interruption is trying to show me.

Sometimes the answer is nothing. Close the tab, decline the meeting, protect the hour. Other times it is uncomfortable. The thing I wanted to treat as a distraction is the thing I have been avoiding. The message I resent answering is pointing at a weak handover.

The redirect is annoying because it changes the route. It is useful because it stops you driving confidently in the wrong direction. The quiet week is a myth, or at least too rare to build your whole system around. The job is less about defending the plan from reality and more about building a week that can absorb it without falling apart.

The interruption is not always the enemy of progress. Sometimes it is the project asking to be managed.

MAKING IT HAPPEN: Your Weekly Strategy

This week, keep two lists. Each morning, write down what you planned to do. Each evening, write down what actually took your attention: messages, calls, decisions, requests, issues.

On Friday, compare the lists. Pick one interruption that kept repeating and ask: what would have to change so this stops arriving as a surprise? Keep the fix small. You are learning which redirects deserve a better road sign.

CHEAT SHEETS

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

If this one landed, forward it to a PM who keeps waiting for the quiet week to begin.

bilaljamil.com | Newsletter archive | Hit reply and tell me what interrupted your best work this week. I read every one.

Have a great week and speak soon,

Bilal