Why does my team keep missing deadlines?
It's rarely because people aren't working hard. Missed deadlines come from a small set of system problems: optimistic estimates, growing scope, dependencies, unclear goals and too much work in progress. Every project has some of these. What decides how much they cost you is how early you find out.
First, find out which problem you have
Look at your last few missed deadlines and ask one question of each: when did someone on the team first see it coming, and when did you hear about it?
- The team saw it weeks ahead and you heard days ahead: you have an early-warning problem.
- Everyone was surprised: you have a planning problem.
Most teams have both. If everyone was surprised, start with planning. An early-warning tool can't warn you about a risk nobody sees.
The causes, and what fixes them
| Cause | What it looks like | What fixes it |
|---|---|---|
| Optimistic estimates | Dates based on how long the work should take | Estimate from how long similar work actually took, and make the buffer explicit. The planning fallacy is well documented (Buehler, Griffin & Ross, 1994). |
| Scope growth | "While we're in there…" | Every addition moves something, either the date or other scope. Make the trade out loud. |
| Dependencies | Waiting on another team, a vendor or a review | Name them at kickoff, and check them as often as your own work. |
| Unclear goal | Nobody can say what "done" means | Write a goal the team could rate its confidence against. How to write one → |
| Too much in progress | Seven things started, three finished | Cap work in progress. Finish before starting. |
| Late news | "Fine" until the last week | A regular, low-cost way for the team to say how confident they are, where raising a risk costs nothing. |
Why late news is the one that costs you the date
Software project status reports are biased about 60% of the time, and optimistic bias is twice as likely as pessimistic (Snow, Keil & Wallace, 2007). Nobody has to lie for this to happen. People are reluctant to be the bearer of bad news, and each layer rounds the uncertainty off a little more.
Two weeks before the date, your options are a fire drill or an apology. Six weeks out, you can cut scope, add help, chase the dependency or reset expectations. Most of the fixes on this page work better the earlier you know.
What to do this week
- Swap the question. Replace "How's it going?" with the confidence vote SAFe teams take at the end of every PI planning, often done as a fist of five: "How confident are you, 1 to 5, that we'll hit the goal by the deadline?" The difference is to ask it every week, not once a quarter.
- Look at the spread, not the average. One low answer among high ones usually means someone is seeing something the others aren't.
- Ask again next week. The direction matters more than any single reading.
- Never punish the low answer. If raising a risk costs someone, you'll stop hearing about risks.
Software, by the gap you find
Choose a tool for the problem you actually have. These do different jobs and work together.
| If the gap is… | Tools to evaluate | What they do |
|---|---|---|
| Bad news arrives late, and projects look fine until they aren't | Genchi | The SAFe confidence vote, run continuously: a regular, anonymous 1-click vote in Slack, combined by project and tracked over time, so leaders see which projects the team expects to miss. |
| Work and progress are hard to see | Jira, Linear, Asana | Track the work, its state and its dates. |
| People are committed beyond their capacity | Float, Tempo | Show allocations and available capacity. |
| Blockers get buried in chat | Steady, Geekbot | Collect written async updates and surface blockers. |
Genchi works alongside your tracker and imports projects from Jira and Asana.
Genchi is our product. The others are listed because they solve different problems, and most teams need more than one.
Hear about trouble while options are still cheap
Set up a project, invite the team, and your first confidence vote goes out tomorrow.
START FREE TRIAL2-week free trial. Teams of up to 10 stay free; larger teams pay $2.50/user/month for every billed user (~$250/month for a 100-person org). No credit card to start.