How a team of 5 stopped fighting over deadlines
When who is waiting on whom lives in everyone’s head, standups get tense and delivery gets unpredictable. Here is what changes for a small team when those dependencies become something everyone can point at.
The UnaTask team, Building UnaTask. Jul 6, 2026. 4 min read.
Picture a team of five. A designer, two engineers, someone on product, someone on the client side. Good people, all busy, all pulling. And yet every couple of weeks the same argument, in the same tired voices: this was supposed to be done, I was waiting on it, I did not know you were waiting, why did nobody say. Nobody is wrong in that argument, which is what makes it so hard to end.
The real problem is not the people, it is where the plan lives. On a team that size the dependencies are all real and all invisible, held in five different heads that each remember a slightly different version. The designer thinks the copy is coming Tuesday. The engineer thinks the design is coming Tuesday. Both are planning around the other, neither can see the other’s plan, and the collision only becomes visible on the day it happens.
Before: a mystery everyone half remembered
Standups were a lot of reconstructing. Who is this waiting on again, is that still blocked, I thought you had that. Half the meeting went to rebuilding a shared picture of the week that fell apart again the moment everyone walked away. Delivery dates were guesses, because a date is only as good as your view of what stands between you and it.
The change: one picture, shared
The shift is almost boringly simple. The dependencies stop living in five heads and start living on one timeline that everyone can see. Who waits for whom is a set of wires between cards. When something is going to clash, the wire between the two tasks turns red, in front of the whole team, a week before it would have blown up in a standup.
The moment it pays for itself
The turning point is not a feature, it is a Monday. Someone opens the project, sees a red wire between the design and the build, and moves one task two days before either person had even noticed the problem. The argument that would have happened on Thursday never gets scheduled. That is the whole return: a conflict caught while it is still just a small adjustment, instead of a delay everyone has to absorb.
You cannot argue about a plan you can both see. You just fix it.
After: delivery you can actually promise
Once the dependencies are visible, the tense standups get shorter and quieter, because there is nothing left to reconstruct. The dates get more honest, because everyone is reading them off the same picture. And when a client asks when it will be done, the answer stops being a hopeful guess and starts being something you can point at.
None of this asks the team to work harder or care more. They already did both. It just takes the plan out of five separate heads and puts it somewhere everyone can stand and look at together. Open a project, draw the dependencies you have all been carrying, and let the timeline hold them for you.