The hidden delay: catch date conflicts before they hurt
The worst delays are the ones nobody saw coming, a blocker quietly ending after the thing it was blocking was due. On a timeline that clash is a red line you can see a week before it lands.
The UnaTask team, Building UnaTask. Jul 6, 2026. 4 min read.
The project was going to be done Friday. Everyone said so, on Monday, and everyone meant it. Then Thursday came and the thing that was supposed to be finished was still in progress, and the thing waiting on it could not start, and the deadline that felt safe all week fell over in an afternoon. Nobody was careless. The delay was just hidden, and hidden delays always surface too late to do anything about.
This is what lists do to you. A list is very good at telling you what exists and very bad at telling you what collides. The blocker sits on one line with a date. The task waiting on it sits on another line with an earlier date. Both look fine on their own. The conflict lives in the gap between them, where nobody is looking, and a list has no way to show you a gap.
So we made the gap visible. When you lay your tasks on a timeline and draw the dependencies between them, the software can do the one bit of arithmetic that matters: does this blocker actually finish before the thing it blocks is meant to begin?
The red wire
When the answer is no, the line between the two tasks turns red. That is it. No report to run, no status to read, no meeting to schedule. A task that ends after its dependent is due draws a red wire straight to the place the plan is about to break. The hidden delay stops being hidden, and it does it while there is still time to move.
Fixing it, in three moves
A red wire is not a scolding, it is a choice. You have three honest ways to clear it, and you can see each one land on the timeline as you try it.
- Move the dependent task later, so it starts after its blocker really finishes.
- Shorten the blocker, if the work can be trimmed, so it ends in time.
- Cut the link, if it turns out one did not truly need the other after all.
A conflict you can see on Monday is a conversation, not a crisis.
The same Friday, without the surprise
Run that week again. On Monday the wire between the two tasks is already red. You nudge one of them two days, the red clears, and the Thursday where everything fell over simply never arrives. The deadline that felt safe actually was, because you could see the one place it was not.
Delays do not have to be dramatic to be expensive. Most of them are quiet, small silences between a task and the thing waiting on it. Put the work on a timeline, let the conflicts turn red, and the surprises get boring. Boring is exactly what you want a deadline to be.