How to Respond When Your Project is Late
April 28, 2025
At some point in your career, you’ll be on a project that is running behind.
Maybe the scope was bigger than expected. Maybe a few technical risks exploded. Perhaps the estimate was wrong from the start. Most likely, it was a little bit of all of those.
No matter the reason, the situation is the same: you’re not going to deliver on time. And that realization is a tough one — especially as a software engineer, where hitting deadlines often feels tied to your professional reputation. If you’re the tech lead on the project, it feels like the whole world is slowly collapsing.
But here’s the truth: being late doesn’t mean you’re bad at your job. It means you’re working in an environment where real-world constraints — complexity, uncertainty, competing priorities — sometimes win.
What matters most now is how you respond.
Here’s a practical guide based on my experience on how to handle a late project with honesty and professionalism.
Be Honest (First with Yourself, Then with Others)
It’s tempting to tell yourself, “Maybe if I just work a little harder, I can still make it.”
Sometimes, that’s true — small gaps can be closed with extra focus and grit. But more often, magical thinking just delays the inevitable. If your project is genuinely off-track, facing that fact earlier is better.
Practice extreme ownership here, especially if you are the project leader. Own reality in conversations with your manager or other stakeholders, letting them know you are aware of the situation. Avoid trying to hide behind vanity metrics or vague status updates, too.
You’re not admitting failure — you’re showing leadership.
Understand Why You’re Late
You can’t fix what you don’t understand.
Before making promises about new dates or deliverables, take a step back and make a quick but serious diagnosis:
- Was the original scope unclear or underestimated?
- Were there unexpected technical challenges?
- Did external factors (like organizational changes, higher-priority work, or dependencies) interfere?
- Were early warning signs missed or downplayed?
It’s rarely just “we were slow.” Usually, late projects are the visible symptom of deeper issues: planning gaps, missing context, or resource constraints.
Spending even a few hours here — pulling in the team and reviewing the history — will help you make smarter, more defensible decisions about what happens next.
Prioritize Ruthlessly and Think Tactically
When deadlines begin to slip, it can be easy to see the whole project as a sinking ship. You either need to jump off or go down with it.
The reality is that just because a project is late doesn’t mean it is a lost cause. Realizing the project (or the plan of execution) isn’t going as well can be an incredible opportunity to step back and ask “What matters most here?” “What value are we trying to deliver?” You might even find ways to deliver more value than you thought.
You should try to reduce scope where possible, identify the most important deliverables, and then work with stakeholders to replan your project. Some great questions could be:
- What is truly essential for a usable release?
- What can be postponed to a future iteration?
- What doesn’t need to happen at all? (You’ll be surprised how much of this snuck into your plan)
Another way to say it is to get tactical. If you’ve planned well beyond just the immediate project, the group or company strategy is likely still the same as when the project started. With this new information (being late is new information!), you can now ask, “How does this project help accomplish that strategy?”
You can then learn where to pivot, where to focus, and what to abandon.
Communicate — Clearly and Often
When a project falls behind, you’ll feel the urge to act like nothing is wrong or communicate vague status updates instead of what is happening. Even if it isn’t a whole project and just your slice of the work, there is a real pull to say “still working on it” when you’ve been stuck for hours, days… or weeks!
Resist that urge! Remember the first point in this article; you have to be honest with yourself and own reality.
Instead of hiding behind jargon or hoping you’ll be able to catch up, build a rhythm of proactive updates.
- How far behind you are (not just days, but in terms of key deliverables).
- What has gotten in your way and could use help with (real problems here, not excuses)
- What adjustments are you making or looking to make (i.e., what is your plan)?
- What risks remain (so people aren’t blindsided again)?
Think of this communication as building a partnership. You’re inviting stakeholders to help you make the best possible decisions, given reality. You aren’t just admitting defeat but helping to develop a new plan.
Even if you don’t have all the answers yet, a heads-up allows others to start thinking about options with you. The earlier you communicate this, the better, including communicating like this well before you are close to being late.
Don’t Overwork
When projects slip, there’s a strong temptation to “just push harder.” In some workplaces, this isn’t a temptation but a demand (in which case, I’d advocate for seeking new employment especially if this happens regularly).
A little focused effort can help for sure. But expecting heroics (nights, weekends, unsustainable hours) almost always backfires: quality drops, morale crashes, burnout lingers long after the deadline passes.
Instead, take the long view. Protect sustainable pace and health wherever you can. Advocate for it if you have the influence and send people home after a certain time if you have authority.
Seek other avenues to get more time back as well. Do you really need all those meetings during crunch time? Can the whole team turn off all their notifications to external teams for a week (and temporarily shift support to the team’s manager)?
It isn’t about working more; it’s about protecting the existing time as strongly as possible.
Final Thoughts
A late project is uncomfortable. It can feel personal. But it doesn’t have to define you or your team.
How you handle being late often matters far more than whether you were late at all.
Be honest and practice extreme ownership. Learn to work with your stakeholders to reprioritize and think tactically about what you can deliver. And avoid the temptation to ignore it or overwork in an attempt to catch up.
You can learn a lot and build strong leadership skills in this moment. It can also be a moment where you burn yourself, your team, or your relationships because you aren’t willing to own reality.
Choose the first option. It’s uncomfortable, but that is where growth happens anyway.
Happy coding!
If you enjoyed this article, you should join my newsletter! Every other Tuesday, I send you tools, resources, and a new article to help you build great teams that build great software.
Dan Goslen is a software engineer, climber, and coffee drinker. He has spent 10 years writing software systems that range from monoliths to micro-services and everywhere in between. He's passionate about building great software teams that build great software. He currently works as a software engineer in Raleigh, NC where he lives with his wife and son.