How do I handle constant requests to add more to an active project?
This is probably one of the most essential topics to discuss, especially for first-time managers. I can’t tell you how much I wanted something like this when I first started out, because the reality of additional work just “creeping” into your process is almost a certainty.
It always starts with a small request – never in big batches or as a permanent addition. Sometimes it’s framed as “a big favor,” a “one-time exception,” or a “let’s test it out and see how it goes.” But the end result is always the same: you get stuck with extra workload and no extra people or money. Many first-time managers, in an effort to be polite and friendly, approach this “one-time request” with a yes, thinking it’s a small ask – and then they get stuck with it. With so many intricacies, political dynamics, and complex rules in the corporate environment, what should a first-time manager do to better handle scope creep?
To handle scope creep without burning out your team or alienating stakeholders, lean on change control and transparent trade-offs. Establish clear review procedures, define what “done” truly looks like, and swap flat refusals for constructive “Yes, and…” pushbacks. By framing every extra request around impact, quality, and bandwidth, you protect your team’s focus while maintaining stakeholder trust.
In this article:
- The Iron Triangle: Understand that every process relies on balancing efficiency, quality, and cost, meaning you cannot add new scope without adjusting at least one of these trade-offs.
- The Change Control That All First-Time Managers Need: Protect your process from chaos by setting up simple review procedures for all extra requests and establishing a crystal-clear definition of what “done” looks like.
- Pushback and Communication Techniques: Frame refusals around objective business impacts rather than personal feelings, using constructive “Yes, and…” trade-offs to protect your team while keeping relationships intact.
- Team Protection and Stakeholder Trust: Maintain full transparency with stakeholders and your team to prevent burnout, build lasting trust, and continually refine your boundaries through post-project reviews.
The Iron Triangle
Mostly known as the Operational Triangle, this very interesting concept is a combination of three elements essential for any leader: efficiency, quality, and cost. The better you are at balancing these three elements, the better your process will be, because in the end, everything you do will always come back to them. I have an extensive overview of this in the article Balancing Efficiency, Quality, and Cost Metrics, so feel free to check it out for more details.
What most first-timers need to understand about this triangle is this: you can’t change one thing without changing at least one other. Balance is very tricky, and whatever you try to do with one element will definitely impact the others:
- You want lower costs? You should probably expect lower quality.
- You want higher quality? You should expect higher costs.
- You want better efficiency? You should expect higher costs.
And so it goes, on and on. Just like the saying “nothing in life is free,” balance in this triangle is about trade-offs: you cannot change one variable without adjusting another.
A common block we hit with this topic is stakeholders and how most of them tend to forget that operations come with a clear structure – meaning a set of baseline expectations. You can’t expect scope to creep in left and right if it’s not part of that baseline. Truth be told, this is probably one of the biggest factors responsible for faulty processes: people just keep taking on new stuff without a proper structure, plan, or sometimes even thinking it through.
The Change Control That All First-Time Managers Need
When it comes to something valuable above all else for a first-time manager dealing with scope creep, it’s change control.
Change Management is a broad concept, and while it is part of a leader’s job, not every detail of it needs to be fully mastered right away. The core concept is simple: changes in your process don’t just happen out of nowhere. You need a proper structure – a mechanism for these changes – so that nothing is negatively impacted, and even when there’s a risk, you take every possible action to mitigate it.
From the entire change management concept, a first-time manager dealing with scope creep really needs to understand the change control aspect. Each time new scope gets pushed your way, control mechanisms should stop it before it gets any further. You don’t have to make this a complicated or bureaucratic process; with just a few simple steps, you can stop unnecessary or unrequested work from landing on your plate.
To help you out, here is what I normally do when extra scope comes up:
- Procedure 1: Nothing outside normal work is done by my team without my review and approval.
- Procedure 2: Any new scope of work must be sent to me before anyone starts working on it.
- Procedure 3: All new scope is reviewed by me and my subject matter experts. We assess the effort needed, the impact on our current work, the impact on other projects/activities, and any potential side effects we can foresee.
Once we review the new scope, we look at the core points of the Operational Triangle and ask: Do I have the resources to perform this activity as requested and as efficiently as possible?
Sometimes, new scope is not something we can say no to; we have to do it regardless of our findings or feedback. Because of this, we must always document all requirements as early as possible. Don’t let your process descend into chaos because of requests sent in a disorganized manner: document, ask questions, and put everything in writing as soon as you can.
On the topic of documentation, remember the most essential question: What does “done” look like? This is the point where your team’s intervention on a task is officially completed. Without a proper definition of “DONE,” tasks will likely remain a mystery. I’ve seen this frequently throughout my career – departments and managers handling “special cases” with vague instructions where nobody even knew what “done” looked like, so they just kept doing whatever was asked. You don’t want this in your process. Every single task your team performs must have clear boundaries: a start and a finish – always!
Pushback and Communication Techniques
We all know – and love or hate – these two words: pushback and communication.
Pushback is simply explaining why something cannot be done right now. Reasons range from a lack of bandwidth, to the request being out of scope, adding excess pressure on the team, or people resisting change.
In general, senior management often views pushback negatively. However, there are ways to push back professionally while maintaining a constructive posture.
The first habit to drop when pushing back like a pro is overusing the word “No.” It carries such a heavy negative connotation that no matter how you phrase it, it often triggers resistance. Instead, try: “Yes, and…”
This shifts the conversation from a blunt “No, we can’t do this” to a professional “Yes, we can do this, and here is what we will need (or what we will have to deprioritize) to make it happen.” It addresses the request constructively while clearly establishing the trade-off.
A very common mistake first-time managers make when pushing back is making it personal. Using phrases like “I feel this is not a good idea” or “I believe this will happen” signals to the other person that you have a personal issue with the request. Instead, frame your refusal around objective factors like impact, quality, resource availability, and team burnout. Focus on what truly matters: delivery and your team.
Here are a few techniques you can use for professional pushback:
- The Impact Assessment: Ask the requester to help prioritize the new task against existing goals.
- The Swap Method: Trade a current task out to fit the new request in.
- The Next Version Approach: Anchor extra requests to future project cycles.
Lastly, always push back in a way that leaves your bridges intact. Don’t ruin relationships with higher-ups over a single task. As a leader, you are expected to exercise judgment and balance priorities. Sometimes you need to pick your battles wisely – losing a small battle to win the broader strategy.
Team Protection and Stakeholder Trust
Two crucial aspects every leader dealing with scope creep must balance are protection and trust. One is for your team; the other is for your stakeholders. If a leader lacks either, things get difficult quickly.
Protecting your team means ensuring they aren’t subjected to unnecessary work outside your agreed scope. I see this mistake often with both new and experienced managers: instead of making a proper judgment on what tasks to accept or decline, they say “yes” to everything and end up overwhelming their teams. This leads to pressure, stress, frustration, burnout, and high attrition.
Maintaining trust applies to everyone you work with – both your team and your stakeholders. Trust breaks down when you operate in the shadows or practice “selective communication” – only sharing bits and pieces of information. Without trust, you have nothing to build on.
While it might be tempting to hide challenges for the “greater good” or to avoid upsetting people, transparent trade-offs are far better. They provide full visibility into what’s happening, eliminate the need to make up excuses, and keep everyone aligned on the facts.
Whenever scope changes occur, share them with your team proactively. This keeps them focused on execution without unexpected surprises. Run short alignment sessions or mini-workshops if needed – whatever helps maintain clarity.
Finally, close the loop with post-project reviews. Examine what scope crept in during the project and determine how to prevent it in the future. Think of this as your feedback loop to continually refine your process.
Until next time stay healthy, happy, and safe!