It starts innocuously. A stakeholder walks into a meeting and says: "Can we just also add this one small thing?"

That word — JUST — is the most dangerous word in project management. In a single syllable, it minimizes effort, bypasses process, and opens the door to scope creep. And scope creep, left unchecked, is one of the leading reasons projects fail to deliver on time, on budget, or at all.

What Is Scope Creep?

Scope creep is the gradual expansion of a project's scope beyond what was originally agreed — without corresponding adjustments to time, budget, or resources. It rarely arrives all at once. It sneaks in through small requests, informal approvals, and well-intentioned "quick additions."

"We're already building it — adding this feature won't take long."

By the time anyone notices, the project has grown significantly beyond its original boundaries — but the deadline and budget haven't moved.

A Real Example

Early in my career, I was managing a system implementation project. Midway through execution, a senior stakeholder asked if we could "just" add a custom dashboard for the executive team. It seemed reasonable. The team was already in the system. How long could it take?

Three weeks. That's how long it took — including requirements clarification, design, development, testing, and sign-off. Three weeks that weren't in the plan, pushed our go-live date, and strained the team. Three weeks that began with a single word: just.

Why Does It Happen?

• No formal change control process — or one that exists but isn't enforced
• Fear of saying no — PMs want to be seen as helpful and accommodating
• Unclear scope definition — if the original scope was vague, everything feels "in scope"
• Stakeholder pressure — senior stakeholders can bypass process informally
• Good intentions — the team genuinely wants to deliver more value

How to Prevent It

1. Define scope clearly and in writing — at the start. A detailed Scope Statement, Work Breakdown Structure (WBS), and Project Charter are your first line of defence. What's in scope must be explicit. What's out of scope must be equally explicit.

2. Implement a Change Control Process. Every change request — no matter how small — must go through a formal process. Document the request, assess the impact on time, cost, and resources, get the right approvals, and only then proceed.

3. Educate your stakeholders. Stakeholders often don't realize that "small" changes have real consequences. Part of your job as a PM is to make the invisible costs visible.

4. Say no — or say "yes, but." You don't have to refuse every change. But you must be clear about the trade-off. "Yes, we can add that — and here's what it will cost us in time and budget." Let the sponsor decide with full information.

5. Monitor scope continuously. Scope creep is easier to catch early. Review your scope baseline at every status meeting and flag any deviation immediately.

The Bottom Line

Scope creep is not just a project management problem — it's a communication and governance problem. The good news is that it's entirely preventable with the right processes, the right mindset, and the courage to have honest conversations early.

The next time you hear the word "just" in a project meeting, treat it as a warning signal. Ask the question. Assess the impact. Follow the process.

Because in project management, "just" is never just anything.

— Abhijit Ambulkar, Founder, Project Xcellence

Burnout in project management is more common than we talk about.

And yet — almost nobody talks about it openly.

What is burnout — really?

Most people confuse burnout with being tired or stressed. They are not the same thing.

Stress is temporary. You recover over a weekend. Burnout is different. It is a state of chronic exhaustion — physical, mental and emotional — where even rest stops feeling like rest.

You stop caring about outcomes that once excited you. You feel detached from your own work. And no matter how much effort you put in — it never feels enough.

In project management, burnout is more common than we admit. We just call it 'part of the job.'

Why do Project Managers burn out?

After 20+ years of delivering projects globally, I have seen this pattern repeatedly.

• Carrying pressure that was never yours to carry — Someone else made a commitment. You are expected to deliver it.
• Fighting battles on every front simultaneously — Stakeholders pulling in different directions. Team gaps. Scope creep. Management asking for a status report in the middle of a crisis.
• No structure to fall back on — Every project feels like starting from scratch. No playbook. No clear escalation path. No one to lean on.
• Believing that asking for help is weakness — This one is the most dangerous. Many PMs absorb everything silently — until there is nothing left to absorb.

How do you prevent or recover from burnout?

Two areas matter most:

1. Project Management Skills

PMI's Ways of Working framework gives us a powerful lens here.

Predictive — plan better upfront. Define scope clearly. Set realistic timelines. Do not accept a commitment you know is impossible to deliver.

Agile — build in checkpoints. Deliver in smaller chunks. Let go of the need to control everything. Adapt as you go.

Hybrid — know which approach fits your project. Not every project needs full waterfall. Not every project suits pure agile. The skill is in choosing wisely — and communicating that choice clearly.

Most importantly — learn to escalate early. Steering Committees exist for a reason. Senior management exists for a reason. Use them — before a problem becomes a crisis.

2. Life Skills

• Separate yourself from the project. It is your responsibility — but it is not your identity.
• Know when to switch off. Rest is not a reward. It is part of performing at your best.
• Build your support system. A mentor. A peer. Someone who has been through it. You do not need to figure this out alone.
• Ask for help before you need it desperately. Asking for support is not weakness. It is leadership.

I have seen this all in the early part of my project management career and came out the other side. If you are going through this — you are not alone. And it is not a permanent state.

From your experience — what do you think is the #1 reason Project Managers burn out?

— Abhijit Ambulkar, Founder, Project Xcellence

There is a conversation happening in boardrooms, PMO forums, and LinkedIn threads that goes something like this: "Will AI replace project managers?" It is the wrong question. The right question is: "What will the PMO look like when AI does what it currently pays people to do manually?"

The Current PMO Is Built on Manual Labour

If you strip away the frameworks, the governance language, and the dashboards, most PMOs today are doing four things: collecting data, consolidating reports, chasing updates, and presenting summaries. Each of these is time-consuming, error-prone, and — critically — not where a trained project professional adds their highest value. AI is about to automate all four.

What AI Will Take Over

Status reporting is among the first functions to be transformed. AI-powered tools — from Microsoft Copilot embedded in Teams and Project, to intelligent features now appearing in Oracle PPM Cloud and other enterprise platforms — are becoming capable of pulling live project data, identifying schedule variances, and generating executive summaries without manual effort. Risk registers that once sat static between quarterly reviews can be continuously fed with real-time project signals. Resource utilisation reports that once consumed hours of a PMO analyst's time are being produced in a fraction of the time. The administrative spine of the PMO — the part that consumes most of its bandwidth — is being systematically automated.

What AI Cannot Replace

Judgment. Context. Relationships. A risk flagged by an AI model is a data point. A seasoned project professional who knows that the flagged vendor has a history of underdelivering in Q4, that the sponsor is under political pressure from the board, and that the timeline was always optimistic — that person is irreplaceable. AI surfaces information. Humans interpret it. The PMO of the future will spend far less time on reporting and far more time on decision support, stakeholder alignment, and organisational change.

The PMO That Will Thrive

Organisations that treat the PMO as a reporting function will find that AI makes them redundant. Organisations that treat the PMO as a strategic capability — one that shapes how projects are selected, governed, and delivered — will find that AI makes them exponentially more powerful. The question for every PMO leader today is not whether to adopt AI. It is whether their function is adding the kind of value that AI cannot replicate.

What This Means for PM Professionals

Upskill on AI tools — not to become a data scientist, but to stop being dependent on manual processes that AI can do better. Understand how to prompt AI effectively for project context. Learn to interpret AI-generated risk signals with professional judgment. And most importantly, invest in the human skills — stakeholder management, executive communication, strategic thinking — that will define the value of the PMO in the decade ahead.

— Abhijit Ambulkar, Founder, Project Xcellence