On Friday I posted a list of what grows on a late project while the scope section barely moves: the stakeholder list, the approval chain, the meeting count, and the people who have to be told first.
That post was about what grows. This issue is about the moment it's agreed to, which is usually a short conversation between two people who both think the thing being asked is small. Most of the time they're right about the size of the ask, and neither of them looks at what it pushes out of the week.
The Shift
What is scope creep, in practice?
Scope creep is work a project takes on without anyone pricing it, and most of it is agreed to in person or in chat, one small yes at a time.
The formal route has a form and an approver. The informal route is a hallway, a chat message that opens with "quick one", or the last two minutes of a call, and it tends to carry more of the growth because it's faster and friendlier than the form.
Nobody is the villain in it. The person asking thinks it's small because from where they sit it is, and the person agreeing says yes because a yes ends the conversation and a no starts a negotiation. So the fix belongs in the conversation itself, while both people are still in it.
The System
How do you catch a quiet yes before it becomes the plan?
Add one sentence before the yes: say what the ask costs, and let the person asking choose.
Four moves, in the order they happen.
1. Hear the size word. "Quick one", "can you just", "while you're in there", "shouldn't take long", "since we're already touching it". The smaller an ask sounds, the less likely anyone prices it, so the size word is your cue to slow down by one sentence.
2. Say the price out loud. "Yes, and it takes Thursday's testing slot, so the report moves to Monday. Want that trade?" The asker hears a choice with their name on it, and you haven't refused anything.
3. If you can't price it, say when you can. "Give me until noon tomorrow to size it, then you'll get a proper answer." A dated pause keeps the goodwill and takes the pressure off answering on the spot.
4. Let them pick. Sometimes the answer is "do it anyway, the report can wait", and that's a good outcome: the person who owns the priority made the trade, in the open. The quiet yes is the version where the same trade happens and neither of you notices.
The Receipt
The receipt is two sentences you send after the conversation, in the same channel it happened in:
Confirming what we just agreed: I'll add [the ask], and [what it displaces] moves to [new date]. If that trade doesn't work for you, tell me by [day].
It takes a minute, it gives the trade a witness, and the person who made the choice sees it in writing while it's still fresh.
The AI Assist
When a "quick one" lands in chat and you're not sure what it costs, paste it here before you answer:
Below is a request I just received, word for word, followed by what I have committed for this week and next. First, list the work the request probably includes beyond the obvious task (reviews, testing, approvals, people who would need to be told) as questions I should ask the requester, and mark each one UNKNOWN. Do not estimate effort or dates. Then name which of my commitments it would most likely displace, and say why. Finally, draft a reply under 40 words that either says yes and states that trade, or asks for a specific time to size it before answering. Keep the tone friendly, and leave the choice to accept or decline with me.
The first list is usually where the ask stops looking small.
The Move
This week, the next time you hear "quick one", put the price in the conversation before the yes. Try it once, and watch how the other person takes being handed the choice.
Reply prompt: which phrase starts the most quiet yeses on your team? Reply with it. I'd like to collect them for a future issue.
P.S. New here? Subscribe free and the Execution Signal Starter Pack lands in your inbox: get the Starter Pack.