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 (2)
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.