The Small Ask That Ate the Project
- Jul 5
- 8 min read
A dashboard review, one late request, and the small ask that quietly rewrote the plan.
By D.B. Trench
Scope Creep Month on PMTales
This is part of a four-week field series.
We are spending the month on how small asks, soft agreements, and helpful little sentences quietly rewrite the plan.
Coming next across PMTales: stakeholder pressure, meeting fog, ownership drift, status theatre, and delivery confidence that looks green until someone checks underneath.
I have seen projects survive bad estimates, missing approvals, vendor delays, executive drive-bys, and steering committees where the only thing being steered was everyone’s patience.
But the thing that does the real damage is usually smaller.
It comes near the end.
It sounds helpful.
It wears a cardigan.
“Can we just add one small thing?”
There it is.
The phrase that has eaten more project timelines than procurement, sickness, weather, and that one stakeholder who only replies to emails with “see me.”
This particular small thing arrived during a dashboard review.
The project team had fought hard to get there. Not heroically. Not with violin music. Just the normal project kind of hard: requirements clarified three times, data definitions dragged into daylight, a test environment behaving like it had personal issues, and one approval chain that seemed to pass through several geological layers of management.
But they had made it.
The dashboard worked.
Not perfectly. Nothing works perfectly. Perfect is what people ask for when they are not the ones updating the version history at 11:38 p.m.
But it worked.
The sponsor could see the key metrics. The team had validated the numbers. The business analyst had stopped sending emails with “just to confirm” in the subject line, which is how you know healing has begun.
Then Marcus appeared.
There is always a Marcus.
Sometimes his name is not Marcus. Sometimes it is Priya, Greg, Elena, Mike, or “adding Finance for visibility.” But the role is the same. A person who was not close enough to the project to feel the bruises, but close enough to request furniture after the house has been painted.
Marcus had missed most of the journey.
Not maliciously. He was busy. Everyone is busy. Busy is the official weather system of modern work.
He joined the review, looked at the dashboard for perhaps forty seconds, and said, “This is good.”
The project manager made the rookie mistake of feeling relief.
Then Marcus continued.
“What would be really useful is if we could also show this by region, with a drill-down by business unit. Nothing major. Just so leadership can slice it a bit better.”
The camera squares did what camera squares do when a project is about to be harmed.
A few people went still.
Someone looked down, probably at notes, possibly at the void.
The developer’s face changed in that tiny way developers’ faces change when they are trying to decide whether to explain reality or preserve their remaining life force.
The project manager did not say no.
That matters.
Good project managers do not win by saying no to everything. That is not control. That is just being the department of locked doors.
She said, “Let’s walk through what that would affect.”
A beautiful sentence.
Not dramatic. Not confrontational. No table flip. No speech about governance. Just enough friction to stop the request from sliding into the plan like it owned the place.
Marcus said, “Sure. I mean, it should be the same data.”
Friends, when someone says “same data,” check your pockets.
Because the data may be the same in the spiritual sense, but projects are not delivered in the spiritual sense. They are delivered through fields, mappings, permissions, test cases, environments, owners, sign-offs, and people named Sam who know why the export breaks every second Tuesday.
The developer leaned in.
“To show it by region, we need the regional field exposed from the source system.”
Marcus nodded, relaxed.
“And to drill down by business unit, we need to confirm the hierarchy.”
Still relaxed.
“And business unit means different things in Finance, Operations, and Reporting.”
Less relaxed.
“So we need a definition decision first.”
There it was: the hidden door.
Every “small” request has one. Sometimes it leads to data governance. Sometimes to legal. Sometimes to a training update. Sometimes to three teams quietly disagreeing about a word everyone has been using confidently for six years.
Marcus said, “But the field exists, right?”
This is the project equivalent of saying, “But the airport exists,” when asked whether you have booked the flight, packed a bag, cleared security, and found the gate.
The business analyst opened the requirements tracker.
You could almost hear the document sigh.
The project manager said, “The field exists. The approved dashboard does not use it. So the question is whether this is launch scope or a Phase 2 enhancement.”
Marcus gave the familiar answer.
“I don’t want to delay launch.”
Of course he didn’t.
Nobody ever wants to delay launch. They just want the new feature included by launch, without delaying launch, using the same people, same budget, same testing window, and ideally the same upbeat status line in the executive deck.
This is not a plan.
This is a wish wearing a lanyard.
The sponsor jumped in. “It does sound useful, though.”
Useful.
A word that has caused more damage than “urgent.”
Because useful is usually true. That is what makes it dangerous. The thing probably would be useful. The report would be better. The dashboard would be sharper. Leadership would like it. Marcus was not wrong.
That is why scope creep is so effective.
It does not need to be stupid.
It just needs to be unmeasured.
The project manager could have argued the point. She could have defended the approved scope like a castle wall. She could have reminded everyone of the decisions already made, the emails already sent, the sign-offs already obtained, the testing already completed.
All valid.
Also exhausting.
Instead, she asked the question that should be printed on mugs and issued with every project charter:
“What should move to make room for it?”
That question did what good project management questions do.
It changed the conversation from desire to decision.
Marcus paused.
The sponsor paused.
Even the dashboard looked like it was waiting for an answer.
The project manager continued. “We can assess it. But if we add it now, we need to understand the impact. It could affect requirements, data mapping, testing, training, and release notes. So the options are: add time, remove something else, reduce testing, add capacity, or move this to Phase 2.”
Notice what she did not say.
She did not say, “No.”
She did not say, “That is out of scope,” and then stare everyone into compliance.
She did not become the process goblin guarding the sacred spreadsheet.
She put the request beside its consequences and made them stand together in public.
That is the move.
Not drama.
Visibility.
Marcus did not love this.
Most requesters do not love it when their sentence grows invoices, timelines, and test cases. They prefer the original version, where the idea was just an idea and everyone admired its potential.
But the sponsor understood.
“Let’s get the impact first,” she said. “If it’s bigger than it sounds, we’ll park it for Phase 2.”
And there it was.
A small project miracle.
Not the kind where the funding appears.
Not the kind where a dependency resolves itself.
The smaller, rarer kind: a stakeholder briefly accepting that work is real.
The team documented the request.
The estimate came back at twelve business days.
Twelve.
Not because the team was slow. Not because they were negative. Not because they “didn’t understand the value.”
Because the request touched more than the sentence used to describe it.
It needed a definition decision. It needed a source-system change. It needed dashboard logic updates. It needed regression testing. It needed release note changes. It needed the training deck updated because someone, somewhere, would click the new view and ask why their business unit was not where they expected it to be.
That is how projects work.
A request can be verbally small and operationally enormous.
Marcus was surprised.
The team was not.
The sponsor moved it to Phase 2.
Launch survived.
Nobody threw confetti.
There was no inspirational email.
No one wrote, “Excellent scope discipline demonstrated by all.”
The project manager simply updated the log, closed the meeting notes, and probably went to refill a coffee that had gone cold twenty minutes earlier.
This is the part people outside the discipline often miss.
Project management is not always about heroic rescue. Most of the job is preventing small, reasonable things from quietly becoming large, unreasonable obligations.
It is asking one more question before the team absorbs the work.
It is refusing to let “quick” mean “free.”
It is making sure “useful” does not outrank approved, funded, sequenced, and tested.
And it is doing all of that while sounding calm enough that nobody realizes you just stopped the timeline from walking into traffic.
That is the work.
Not glamorous.
Not always appreciated.
Very often the difference between a project that launches and a project that spends the next three weeks explaining why it still has not launched.
So when the small ask appears — and it will — do not panic.
Do not swat it away automatically.
Do not welcome it in and hope the team can “absorb” it, because absorb is just the word organizations use when they want people to pay for scope with evenings, morale, and quiet resentment.
Put it on the table.
Ask what it touches.
Ask what moves.
Ask who decides.
Then write it down before it grows legs.
Because scope creep rarely introduces itself as scope creep.
It comes in friendly.
It says the work looks good.
It compliments the dashboard.
Then it leans over and says:
“Can we just…”
And somewhere in the distance, a project plan feels a chill.
And if your project is already collecting “small” requests like loose change in a couch, the Scope Defense Bundle gives you practical tools for clarifying, documenting, challenging, and managing scope before it eats the rest of the plan.
Field Notes from D.B. Trench
“Small” usually means one of two things:
1. The requester can explain it quickly.
2. The team has not yet explained what it actually touches.
Those are not the same thing.
A late request is not automatically bad. Some are worth doing. Some really do add value.
But every late request needs a tradeoff conversation before it becomes invisible work.
What should move to make room for this?
That one sentence changes the discussion.
It moves people from enthusiasm to ownership. From “wouldn’t it be nice” to “what are we willing to trade?”
And that is where real decisions live.
Free Field Tool
Scope Creep Early Warning Sheet
A 2-page PMTales field sheet for spotting hidden change before it becomes “already agreed.”
Inside: 10 early warning signals, a quick “discussion or decision?” test, a mini drift tracker, tradeoff prompts, and calm scripts for naming change early without making the room defensive.
Free PDF · 10 warning signals · Drift tracker · Tradeoff prompts · Calm scripts
Need Stronger Scope Guardrails?
Scope Defense Bundle
The Scope Defense Bundle turns “small asks” into clear decisions, visible tradeoffs, and written follow-up before the project quietly absorbs the work.
It includes the Start Here Guide, Weekly Scope Review Sheet, Change Impact Snapshot, Boundary Scripts Pack, Escalation Brief Template, Scope Drift Tracker, Tradeoff Log, and Complete Print Workbook.
Fillable PDFs · Printable PDFs · Excel trackers · Complete workbook · Launch price shown on product page
Story Route
Want the longer field tale?
The Scope Creep book is the story-led companion for this kind of slow-motion project disaster: small asks, soft agreements, harmless language, and the quiet rewrite of the work.
Coming Field Reports
Scope Creep Month continues with small asks, hidden tradeoffs, and the polite sentences that eat baselines.
After this series, PMTales moves deeper into meeting fog, ownership drift, stakeholder pressure, status theatre, and the rest of the project chaos ecosystem.
Comments