People & Perspectives
Program & Project Management

The Three Little Words That Signal Trouble in Scope-Land

"Can we just...?" Ah, those three little words. No matter what follows, every time I hear those words, my mind races to the potential ripple effects that might unfold.

But here’s the thing: not every "can we just...?" idea is a disaster waiting to happen. In fact, many can be opportunities in disguise. It’s all about how we approach them. It's like taking a detour that unexpectedly leads to an amazing view. The key isn't to avoid the detour, but to navigate it with intention. By carefully aligning our choices with the big picture, we can transform these moments into “opportunities” for growth and innovation.  

Now, I'm not a project manager, I'm a learning strategist. But even non-project managers need to know how to deal with scope creep. In my years of experience working across learning strategy, design, and development, I've seen the “Can we just” scenario play out more times than I can count. Whether it's interviewing “just few more” stakeholders, considering "just one more" audience role, adding a “small content topic” or a “quick terminology update”, these seemingly minor requests can quickly add up, stretching both project budget and timelines.  

That said, I've also seen how well-considered adjustments can make a big impact.  Whether it's refining a key message, sharpening a visual, or adjusting the tone to better resonate with a specific audience, thoughtful changes can elevate the entire learning experience. Sometimes, it’s that one adjustment that turns good into great. That’s why I’ve learned to stay curious, keep the end goal in focus, and make each choice count. When changes are approached with intention and clarity, they don’t derail a project, they sharpen it. That’s the power of reframing scope creep: it flips the script from “what we can’t do” to “what’s the right thing to do,” turning tricky conversations into creative opportunities and exciting win-wins.

Shifting the perspective on “small changes”

Early in my career when someone asked, “can we just”, my internal reaction was usually a sigh and a mental calculation of how much extra work it would be. I saw those requests as roadblocks that risked derailing progress and kept looking for reasons to say “No”. It felt like a frustrating interruption, something that threatened to throw off all my carefully laid plans. And I know I wasn't alone in feeling that way; it's a common experience for many of us starting out.

But with more experience, I started to view them differently. What once felt like interruptions now feel like inflection points offering opportunities to realign, adapt, and sometimes unlock a stronger version of the original idea.

In the flow of a project, “small changes” can show up in all kinds of ways.

  • Maybe someone spots a missing piece and says, “Oh! We need that!”, identifying a gap in the content, a step that was overlooked, or a detail that’s now essential.
  • Or the team gains a fresh insight that shifts direction: “Our strategy just evolved!” These aren’t just tweaks; they reflect learning in motion.
  • Sometimes it’s a creative spark that pushes the work from “Meh” to “Wow,” driven by the desire to raise the bar and truly engage the audience.
  • And other times, it’s a practical update to stay relevant: “Wait, that’s not how it works anymore!”- a change in policy, tech, or audience expectations that needs to be addressed.

All these moments reflect responsiveness, attention to detail, and a drive to improve. It’s true that these adjustments can impact timelines, resource plans, and budgets, but that doesn’t mean we should avoid them. It means we need to pause, ask the right questions, and make intentional decisions. Does this change serve our goals? Does it raise the quality in a meaningful way? Is now the right time? What’s the trade-off? What is the impact on cost and timelines?

By reframing these moments, scope conversations become less about guarding boundaries and more about making smart, purposeful choices. Because at the end of the day, it’s about saying “yes” to what matters most.

Strategies to reframe scope conversations

Scope conversations are a necessary part of any project, but they often carry a negative tone, associated with limitations, budget constraints, or delays. When left unchecked, these discussions can turn into contentious exchanges rather than opportunities for collaboration and alignment. Reframing scope conversations into strategic discussions helps teams focus on outcomes, build trust, and make smarter decisions together.

Instead of a knee-jerk reaction to change requests, adopt a proactive and strategic approach. Always acknowledge the request, carefully consider its impact, and then collaborate on the next steps.

Here are some strategies that could come in handy:

Start with shared goals, revisit the “Why”

When new ideas arise, approach them with curiosity. Start the conversation by revisiting the overall business/project vision. Aligning everyone to the "why" before diving into the "what" ensures that all decisions support the overarching goals. Instead of focusing solely on the current scope and timelines, consider how the change enhances the learning experience. This mindset fosters collaboration and keeps the project focused on delivering meaningful outcomes.

Example You are leading the design and development of an online learning program for a global organization. Midway through the project, a stakeholder suggests adding voice overs along with captions to enhance learning for all.
The Request “It turns out a lot of our team members at manufacturing units are non-native English speakers, and some have hearing impairments. I wonder voice-overs with captions might make the content more accessible and engaging for everyone.”
The Response Instead of: “That's not part of the agreed scope. We can't accommodate this request at this stage.”
Try “It’s a really good practice to ensure we're meeting the audience where they are. While this feature wasn't included in the original scope, we can explore how to incorporate it effectively. In my experience, the effort to do something like this isn't trivial. Let's discuss the priority of this request and adjustments we will need to make to project scope, timelines, and cost.”

Approach the conversation as a prioritization dialogue

Instead of seeing scope requests as limitations, treat them as opportunities to focus on what will deliver the greatest impact now. Guide stakeholders to prioritize based on strategic goals and audience needs by asking, "What’s most valuable to achieve first?" This turns constraints into strategic choices and encourages shared ownership of the plan.

Example A manager wants interactive branching scenarios added to every section of a compliance course. Instead of saying no, guide the discussion toward prioritizing sections where decision-making is most critical.

“I'd like to see interactive branching scenarios added to all sections of the compliance course. This will give our people the opportunity to practice making the right decisions in realistic scenarios without fear of negative consequences.”
Instead of “We don't have time or budget for branching scenarios in every section. We'll just have to prioritize the basic content for now.”
Try “That's a great idea in terms of deepening learning and engagement through practice. To make sure we're focusing our efforts where they'll have the biggest impact right now, could we take a look at the different sections of the course and identify where those critical decision-making moments are most crucial for compliance?”

Offer a “Yes, and” instead of “No”

Saying a “No” can shut down a conversation and feel dismissive. The Yes, and technique offers a more collaborative and solution-oriented path forward. Instead of a flat denial, you start by acknowledging the value and intent behind the stakeholder's suggestion. The "Yes" part validates their idea. Then comes the crucial "and." This is where you pivot to explore alternative ways to achieve a similar outcome within the existing constraints of the project - be it budget, timeline, or resources.  

Example You are in the design phase of a project with tight timelines and limited budgets. A stakeholder is suggesting adding video interviews with field experts to enhance the relevance of the learning modules.

“I really think we need video interviews with field experts in these learning modules. It'll make them much more engaging!”
Instead of “No, we can't do that. We don't have the budget or the time for video production. It's too complicated.”
Try “Yes, expert interviews would be fantastic for engagement and bringing real-world perspectives. And, to work within our current budget and timeline for this phase, how would you feel about using high-quality audio clips paired with professional photos of the experts as a starting point?”

Use prototypes to ground the conversation

Visualize how a suggested change would play out using a mockup or example to move the conversation from abstract to concrete. Creating quick mockups, wireframes, or even simple visual examples transforms vague ideas into concrete proposals that can be evaluated objectively.

Example You're in the middle of developing a compliance training module when a stakeholder suggests adding gamification elements throughout the course.

“I think we should add gamification to this course—badges, leaderboards, achievement notifications. It would really boost engagement and make compliance training feel less boring.”
Instead of “Gamification is complex and would require significant development time. We'd need to rethink the entire course structure.”
Try That's an exciting direction for increasing engagement. To help us evaluate what's involved, let me put together a quick visual showing what those gamification elements might look like in one section of the module. That way, we can see how it fits with the overall learning experience and discuss the development effort and timeline impact. We can also assess whether it strengthens our compliance objectives or potentially distracts from them. Once we see it in action, we'll be in a much better position to decide on next steps.

Keep a parking lot for “great ideas”

Not every good idea needs to be implemented right now. Creating a dedicated space, whether it's a shared document, a project board column, or a section in your meeting notes, for capturing valuable suggestions that don't fit the current timeline preserves innovation without derailing progress.

Example During a design review for an onboarding program, a team member gets excited about emerging technology.

“What if we created an AI-powered chatbot to answer new hire questions in real-time? It could be available 24/7 and learn from the most common questions. That would really enhance the experience!”
Instead of “That's way too complex for this project. We need to focus on what we can actually deliver.”
Try “That's exactly the kind of forward-thinking we need. Given where we are in the project timeline and our current resources, I don't think we can tackle it in this phase without impacting our delivery date. But I don't want to lose this thought. Let me add it to our parking lot for future enhancements. Once we complete the core program and see how new hires interact with it, we can revisit this with real data about what kinds of questions come up most frequently. That'll help us build an even stronger case for the chatbot if we decide to pursue it in phase two. Does that sound reasonable?”

Turning Conversations Into Commitments

Even the best conversations mean nothing if decisions aren't captured, communicated, and tracked. All the strategies outlined in this article work because they're supported by a system that creates clarity and accountability.

Every scope conversation should result in clear documentation that captures what was discussed, what was decided, the reason behind the change and the impact on project levers. It's about creating a shared understanding that protects everyone involved.

What does this look like in practice?

  • Start with a clear baseline scope: Start every project by documenting detailed scope which outlines project objectives, deliverables, timelines, budget, and success criteria. This becomes your north star and the reference point for evaluating every "can we just" request. Make sure you align with all your stakeholders on this baseline scope. When everyone knows what was agreed to at the start, it's much easier to have productive conversations about what's changing and why.
  • Establish a formal change control process: Design standardized change request forms capturing essential details: the change description, reason for the request, impact analysis on timeline and budget, and approval status. This ensures nothing falls through the cracks and everyone understands what they're agreeing to.
  • Maintain a change log: Track all scope change requests and assess their cumulative impact on timelines and budgets and ensure that all stakeholders remain informed and aligned. Regular updates to the scope document, combined with impact analyses and periodic reviews, help manage scope creep proactively rather than reactively.

A Final Note: Reframe with Boundaries

Reframing scope conversations can lead to better collaboration, sharper ideas, and more impactful learning experiences but that doesn’t mean saying “yes” to everything. Scope creep is real and managing it is paramount. Without clear goals, defined boundaries, and a process for managing change, even small adjustments can pile up and put timelines, budgets, and outcomes at risk.  

The goal isn’t to resist change; it’s to make the right changes, at the right time, for the right reasons. That means knowing when to adapt and when to hold the line. It means approaching new ideas with curiosity, but filtering them through the lens of purpose, value, and timing.

That said, there will still be situations where the answer will need to be a “No.” compromise the work to keep everyone happy or protect what you knew would deliver real results. Saying yes when you should say no creates its own damage - mediocre deliverables, burned-out teams, and eroded trust.

Remember that every project operates with fundamental levers: scope, cost, time, and quality. These aren't abstract concepts—they're the practical realities that determine whether a project succeeds or struggles. When someone says "can we just," what they're really asking is for you to adjust one or more of these levers. Your role is to help them understand that choice clearly and make it consciously.

The most successful projects aren't the ones that never encounter "can we just" moments. They're the ones where those moments spark productive conversations rooted in shared goals, mutual respect, and strategic thinking. They're the projects where change becomes a tool for improvement rather than a source of chaos.

So the next time you hear those three little words, take a breath. Ask the right questions. Explore the possibilities. And remember that the best answer isn't always "yes" or "no". It's "let's figure out what makes sense together."

Want help tackling scope creep in your organization? Talk to an Oxygen expert today.

Share this
Sign-up for our newsletter

Related Content

All Insights