You get asked "can you have this done by Friday?" and you say yes, even though you already know it needs two weeks. I will show you why your brain does that and the small daily rep that gets you to say "here is what Friday actually gets you" instead.
Quick background so you know where this comes from. I'm Christopher. I spent nine years in the Marine Corps, then moved into software and data engineering, including edge computer vision work for the Air Force on a project called Athena. In the Marines, a bad estimate can get people hurt, so you learn to tell leadership the truth about time.
If you keep agreeing to impossible deadlines, you are not weak and you are not bad at estimating. You are protecting yourself from a moment of discomfort, and paying for it with three weeks of stress.
What you actually hear
Your lead says: "Any chance this ships Friday?"
What you hear: "Good engineers say yes. If you push back, you're the slow one. You're the problem."
So you say "should be fine." Then you work nights, cut the tests, ship something shaky, and spend next week fixing it. Or you miss the date anyway, and now you have the conversation you were avoiding, just later and worse.
Here is the part that took me years to see: the question was a question. Your lead wanted information. You gave them a comforting story instead.
Why it hits so hard
I don't believe you build confidence. I believe you unhide it. You already have the knowledge to say "that's two weeks." You did the math in your head before they finished the sentence. What is missing is not skill. It is permission to let someone be briefly disappointed in you.
Your brain runs a selective filter called the reticular activating system, the RAS. It decides what gets your attention, and it learns from what life fed it. Maybe a parent got angry when you said no. Maybe an old manager rolled their eyes the one time you pushed back. Your filter took notes: disagreeing with someone in charge equals danger.
So now, in a planning meeting, the filter skips past the facts and locks onto the risk of a frown. You cannot logic your way out of that. "Just be honest" bounces off, because the filter does not run on logic. It runs on experience. So you feed it new experiences.
The daily rep: compliment a stranger
Once a day, give one genuine, specific compliment to a stranger. Nice boots. Great laugh. That dog is a legend. Say it, smile, keep walking.
I know that sounds unrelated to sprint planning. It is the same muscle at low stakes. You are saying something true out loud, to someone whose reaction you can't control, while your body braces for it to go badly. The first few will spike your heart rate. Then they stop.
The rule that makes it work: the win is the action, never the result. They ignore you, win. They light up, win. You only managed to think it, still a win. If you only count the ones that go well, you are training the old program that says speaking up only counts when people approve. The rep is the point.
That is rung one of a short ladder:
- Genuine compliments to strangers
- Compliment plus a quick "how's your day going?"
- A longer conversation, no agenda
Move up only when the current rung stops spiking you.
Bring it to your deadlines
Once the stranger reps feel easy, run the same reps at work.
Buy yourself ten seconds. You do not have to answer on the spot. "Let me look at it and get back to you in an hour" is a complete sentence.
Trade, don't refuse. Never answer with a flat no. Answer with options. "Friday gets you the API and the happy path. Full error handling and tests is the following Wednesday. Which do you want?" Now you are not the blocker. You are the person who made the tradeoff visible.
Name the risk once, in writing. One short message: "Heads up, the Friday date assumes the auth team's change lands by Tuesday. If it slips, we slip." You are not complaining. You are giving your lead the information they asked for.
Count the sentence, not the reaction. Same rule as the compliments. You said the real number out loud, win. They pushed back, still a win. Their job is the decision. Your job is the truth.
What Athena taught me about honest numbers
On Athena, edge sensors ran a local model, and when it flagged something significant it shipped context from before, during, and after the event back to AWS so the models could be retrained. That only worked because the data was honest. If the sensors had quietly dropped the messy events to make the numbers look clean, the models would have gotten worse, and nobody would have known why.
Your estimates are field data for your team. When you shave two weeks down to three days to avoid a frown, you are dropping the messy events. The plan looks clean, and it is wrong.
You already know the real number. Old training just taught you that saying it is the dangerous part.
Your mission this week
- Compliment one stranger a day for seven days.
- The next time someone asks for a date, say "let me check and get back to you" before answering.
- Answer one deadline request with two options instead of a yes.
- Write one short risk note to your lead about something you have been quietly worried about.
Then tell me in the comments: what is the deadline you said yes to this year that you knew was impossible the moment you heard it?
Top comments (16)
Christopher, the mechanism you named is the whole thing: a disappointed face stops being danger once nothing happens after it. Two things to add.
The drill only counts if the disappointment can come back. Sending back a wrong order at a place you eat at every week. Declining a meeting with someone you see Monday. A no to a stranger is free, same as a compliment to a stranger, which is why the compliment rep never transferred. Both of those cost nothing, so neither one trains anything.
Ascendra, on the one-on-one that freezes in a planning meeting: the freeze is not about the words, it is about who is watching. So don't rehearse the sentence in private. Carry the same sentence into one bigger room at a time. Say the number to your lead alone on Tuesday. Say the identical sentence Wednesday with one more person in the room. By the planning meeting it is not a new move, it is the third time you have said it and it still sounds like yours.
Different words every time is what makes it a mood. Same words is what makes it a price.
"Same words is what makes it a price" is a great way to put it. And yeah, you nailed why the stranger reps plateau. Your brain only updates when there was something real on the line and nothing bad came back. The wrong order at your regular spot works because you have to walk back in there next week and it turns out fine. That's the evidence that actually sticks.
That's the part I'd push one turn further: nothing bad coming back is not evidence by itself. Somebody has to notice it didn't.
At the regular spot the wrong order is remembered, and so are you next week. That memory is the ledger. A stranger's face has no ledger, which is why a no to a stranger costs nothing and teaches nothing.
So the drill isn't "say no often." It's "say the small no in front of someone who has to see you again." Witness plus repeat. Take either one away and it's practice, not proof.
"Witness plus repeat" is a great add, and I agree. Your brain doesn't update on what didn't happen unless something marks it. That's why I tell people to actually notice it afterward, even just to themselves, like "I said no and they still waved at me today." That's the ledger entry. A stranger can still be a decent first rung for someone who freezes completely, but you're right, the proof that carries over comes from the people you have to see again.
Friday gets the API and the happy path, nothing else.
That's it right there. Clear scope, no apology, and everybody knows exactly what they're getting on Friday.
That shared definition is the part that saves the next week. If Friday slips, at least nobody is guessing what slipped with it.
Exactly. A slip with a shared definition is just a schedule change. A slip with no definition turns into a week of everyone guessing and nobody trusting the next date.
That trust part is the real cost. A new date is easy to accept when everyone already knows what changed.
Yep. People can handle a new date fine. What they can't handle is finding out late or not knowing what moved.
"The question was a question" is the sentence I would put on the wall. A lead asking about Friday wants information, and a comfortable yes gives them a story instead.
Ken's menu framing in the comments is how I have seen this work with clients too. "Friday gets you login and the empty state, two weeks adds the four edge cases" turns a refusal into a choice, and choices are much harder to argue with than reluctance. It also leaves a written record of what was agreed, so if something slips nobody has to guess what it was.
I would add one thing to Alex's point about assumptions: write down what Friday does not include. Most deadline fights I have seen came from an exclusion nobody said out loud.
The compliment drill is an unusual idea, but I like that it trains the body rather than the argument. Have you seen it carry over for people who are fine in one to one talks but freeze in a planning meeting?
Writing down what Friday does not include is such a good add. Half the fights are about the thing nobody said out loud. On the planning meeting question, the compliment rep on its own usually doesn't carry over, because a stranger and a room full of your team feel like totally different threats to your brain. What carries over is stepping it up one room at a time, which is basically what Ken laid out. Same sentence to your lead alone, then with one more person, then the meeting. Each step shows your brain the bigger audience isn't danger either, and the freeze loosens because the confidence was already there, the room was just covering it up.
The useful shift is from accepting a date to negotiating scope and evidence. A small plan with assumptions, known risks, and a review checkpoint gives stakeholders something concrete to choose from instead of a false yes that fails later.
That's exactly it. A false yes feels safe for about ten seconds and then it's a problem for weeks. The plan with assumptions and a checkpoint is great, and honestly the hard part for most people isn't knowing to do it, it's saying it out loud in the room when their brain is screaming that pushing back is dangerous. Once they do it a few times and nothing bad happens, it stops feeling like a confrontation and just becomes how they talk about work.
Christopher is right about the thing that matters: the question was a question. So answer it with a price, not a mood.
Say the number out loud. "Friday gets you login and the empty state. Two weeks gets you login, the empty state, and the four edge cases you'll be filing bugs about in March. Pick."
That isn't a no. It's a menu. A no on its own reads as reluctance, and reluctance gets argued with. A no that arrives holding the list is a trade, and a lead can choose from a trade.
One push on the daily rep. Complimenting strangers trains you to be liked by people who can't hurt you. The rep that transfers is a small no to someone whose disappointment is cheap: a wrong order sent back, a meeting you don't need, a date that only works if you cut the tests. Get used to that face being briefly unhappy, and the Friday face stops being scary.
Love the menu framing. A no holding a list is a trade, not a fight, and that's exactly why it lands. And fair push on the daily rep. Compliments are a good warm up because they get people talking at all, but you're right that the stuff that really transfers is the small no where someone is briefly unhappy with you. Sending back a wrong order is a perfect one. Your brain learns that a disappointed face isn't danger, and once it stops flagging that as a threat, the Friday face loses most of its power.