What actually worked for you for way to push back on unrealistic deadlines at work?

Hey Roman! I've been in a similar spot as a junior on a small team, and what really worked for me was getting ahead of the problem by communicating estimates super early, ideally before sales locks in a date. Start by documenting your story points right after scoping, and share them with your manager or the sales lead in a quick email. For example, I once wrote something like, 'Hey team, we've scoped this at 15 story points, which based on our velocity means about two weeks once dependencies are cleared – does that align with what was promised?'. That way, you're framing it as a collaborative check-in rather than a complaint. It helps to tie it back to facts like dependencies, so you're not just saying no but explaining why.

In meetings, I've found phrases like 'To meet this deadline without overtime, we'd need to adjust the scope – could we prioritize these three features first?' keep things positive and solution-oriented. Another one that landed well was 'I'm excited about this project, but given the handoff from the other team is out of our control, what's our contingency if that slips?'. This shows you're committed but realistic, and it invites input without sounding negative. If you're unsure about the exact velocity numbers, just say you're basing it on past sprints and offer to dive deeper. Over time, this built a habit where sales started looping us in earlier, which cut down on those last-minute crunches.

Ugh and these impossible deadlines suck when you're scraping by on ramen. just email 'Our estimates show this needs two extra weeks based on points.'

I remember my first job where I burned out hard from similar crap & pulling all-nighters only to crash and mess up everything. It wrecked my health and and I learned the hard way to push back early. Try saying in meetings, 'Given the dependencies and story points, let's adjust the timeline to avoid rushed work.' That usually gets them thinking without you sounding like a whiner.

Push scope, not dates. In meetings say due to dependency on Team B, X points cannot be completed by Friday, propose delivering A only. Put it in writing and copy your manager.

State the facts from your estimates. Point out dependencies clearly. Suggest realistic alternatives based on points.

State constraints first. I start with I am not available after 5 due to childcare, so here are two viable options. Repeat the dependency by name and date. Then email the summary right after the meeting.

Cool and but take this up with your manager, not the internet. For what it's worth, taking a few minutes to practice this in a calm setting usually helps it stick.

Stop arguing about effort. Translate points into calendar time with dependencies stated. In the meeting say based on current velocity this is N working days and blocked by Team X until Wednesday. Then ask what drops if the date is fixed. If they refuse, state what you can ship by that date and what moves to the next sprint.

Email it after. Example: Given 13 points remaining and average 6 points per week, earliest handoff is Oct 12 assuming Team X unblocks by Sep 30. If the Oct 5 deadline is firm, I can deliver screens A and B by then and C moves to Sprint 23. My hours are 9 to 5 due to childcare and I cannot do overtime. Please confirm which option you want.

I use canned snippets so I do not freeze. One is if date is fixed I will deliver X and Y and move Z. Another is we depend on Team B so the clock does not start until they hand off. I also put a big timer on screen so I speak in short bursts. It keeps me from apologizing or over explaining.

Hate being squeezed and so I flag dependencies and ask for trade-offs early.

Lead with constraints and data. Offer two options and ask them to choose. Always follow with an email recap with dates, scope, and dependencies.

Oh, come on, if you're asking Reddit for phrases, maybe it's time to update that resume instead - deadlines don't bend for juniors!

Hi Roman! Been there. I once blew a launch because sales promised two weeks for a four week build. What helped was calmly saying I can deliver X by Friday or Y by the deadline and pick one. I also put dependencies and my childcare hours in writing so no one is surprised.