NEW: Learn OnDemand in Arabic, French, Chinese & Spanish – Explore Courses or Book Free Consultation
Speak to an advisor
Learn how project managers can improve stakeholder engagement, manage competing priorities and keep project tasks moving forward.
When you manage a project, it’s easy to get completely absorbed. You know the deadlines, the dependencies, the decisions that are still pending and the things that could become a problem three weeks from now if they’re not resolved today. You probably think about the project during meetings, while answering emails and, occasionally, at times when you’d rather not be thinking about work at all.
But there’s something that’s very easy to forget: while your project might be one of the most important things on your desk, for someone else it might be number twelve on their list.
I think this is one of those lessons that most project managers learn relatively quickly, although accepting it — and learning how to work with it — can take a little longer.
We’ve all experienced some version of the same situation. There’s an important deadline approaching, and you need someone to review a document, answer a question, approve something or make a decision before the project can move forward. You send an email and receive no response. A few days later, you follow up. You mention it during a meeting, and the person tells you they’ll look at it as soon as they can. Then another few days pass, and you find yourself following up again, while your project plan continues to remind you that the task should already have been completed.
It’s frustrating, particularly when you’re the person responsible for keeping everything moving. However, over time I’ve learned that these situations become easier to manage when you stop looking at them only from the perspective of the project and start looking at them from the perspective of the person whose input you need.
As project managers, we spend a huge amount of time thinking about our projects, but many of the people we work with don’t. They have their own roles, teams, customers, deadlines, meetings and responsibilities, and our project may be only one of several initiatives competing for their attention.
The task that’s been sitting in your head since Monday morning might be something they’ve allocated twenty minutes to on Thursday afternoon. The decision that’s blocking your next milestone might be competing with an urgent customer issue, a deadline from their manager or another project that’s equally important to them.
That doesn’t necessarily mean they’re not interested in the project or that they don’t care about its success. Sometimes, your project is simply someone else’s side job.
Understanding this changed the way I approach these situations because it shifted my focus from asking, “Why haven’t they done this yet?” to asking, “What can I do to make it easier for them to contribute?”
That’s a very different question.
When something is delayed, the natural response is to chase it, and sometimes that’s exactly what needs to happen. Every project manager has sent more “Just following up on the below…” emails than they’d probably like to admit.
However, there’s a limit to what another reminder can achieve. If you’ve already asked three times and nothing has happened, sending the same request for a fourth time may not be the most effective solution.
Instead, I’ve found it useful to understand what’s preventing the person from responding. Perhaps they know there’s a deadline but don’t realise what depends on their decision. Perhaps the request is too broad, and they’re not sure exactly what you need from them. Perhaps they’re waiting for information from somebody else. Perhaps what looks like a simple review from your perspective represents two hours of work from theirs. Or perhaps they’re simply overloaded, and your request keeps falling to the bottom of the list.
This is where, for me, project management becomes much more about people than plans. A project plan can tell us that a task is late, but it can’t tell us why the person responsible hasn’t completed it. Understanding that usually requires a conversation.
One of the simplest things we can do is make our requests clearer. Asking somebody to “review this document” can mean almost anything. Do you want them to check every page? Are you asking them to approve the content? Do you need their technical opinion? Are there two specific questions that only they can answer?
The clearer we are about what we need, when we need it and why it matters, the easier it becomes for someone to fit our request into everything else they’re doing.
I’ve also learned not to underestimate the value of a short conversation. Sometimes five minutes of speaking to someone achieves more than five follow-up emails because it gives both people the opportunity to clarify what’s actually needed. In other situations, bringing the right people together for twenty minutes can resolve something that’s been sitting between different inboxes for two weeks.
This isn’t about doing other people’s work for them or removing accountability. It’s about recognising that part of our role as project managers is to remove unnecessary friction. If someone wants to contribute to the project, we shouldn’t make it unnecessarily difficult for them to understand how.
There’s also a big difference between telling someone, “I need this by Friday,” and explaining, “We need to make this decision by Friday because the development team is starting on Monday and they can’t move forward until it’s been agreed.”
The deadline is exactly the same, but the second conversation gives the person context. They can see what happens after their part is completed and, more importantly, what happens if it isn’t.
This is something I think we sometimes underestimate when we’re very close to a project. Because the connections between different pieces of work are obvious to us, we assume they’re equally obvious to everyone else. Usually, they’re not.
People are much more likely to engage when they understand where they fit into the bigger picture. A task stops being something the project manager is chasing and becomes a contribution to something that other people are waiting for.
That doesn’t guarantee that everything will suddenly be delivered on time, of course, but it changes the nature of the conversation.
None of this means that good communication magically eliminates missed deadlines. There’ll still be reminders, delayed responses and meetings where somebody says, “Sorry, I haven’t had a chance to look at that yet.” There’ll also be situations where expectations have been made completely clear, but somebody still doesn’t deliver. In those cases, escalation or a more direct conversation may be necessary.
Understanding other people’s priorities doesn’t mean accepting every delay. Empathy and accountability can exist at the same time.
For me, the important distinction is between repeatedly chasing someone for a task and trying to understand what’s needed to get that task moving. Sometimes the answer genuinely is another reminder. At other times, it might be clarifying the request, explaining the impact of the delay, changing the approach, bringing two people together or escalating an issue that can’t be resolved at the project level.
The objective isn’t to become better at chasing people. It’s to become better at creating the conditions in which people can contribute.
Project managers are often responsible for delivering outcomes that depend heavily on people over whom they have no direct authority. We can’t make our project everybody else’s number-one priority and, realistically, it shouldn’t always be.
What we can do is understand the world that exists outside our project plan. We can communicate clearly, provide context, listen to what’s happening on the other side of the conversation and make it easier for people to understand what we need from them and why their contribution matters.
Successful projects rarely happen because one project manager kept sending reminders until everybody eventually completed their tasks. They happen because a group of people with different roles, different priorities and different pressures somehow managed to move in the same direction.
For me, learning to recognise that has been an important part of becoming a better project manager. The project may occupy a large part of my working day, but I can’t expect it to occupy the same space in everybody else’s.
Sometimes your project really is someone else’s side job.
And once you understand that, the challenge is no longer simply how to get people to complete tasks. It’s how to help them become part of what you’re trying to achieve.
Highly in-demand across roles, industries, and experience levels
Book Your Free ConsultationJoin IPM Hub, the free community where Project Managers share real challenges and learn from each other.
10% Off your first On-Demand course when you join.
Please activate your account by clicking the verification link we’ve sent to your email.
Once verified, your 10% code will arrive by email.
If the email doesn’t appear soon, please check your spam or junk folder.
We use cookies to ensure you get the best experience of our website. By clicking “Accept”, you consent to our use of cookies.