Nobody on your team agrees what finished means

I have watched more small teams stall on the same hidden rock than I can count, and it is never the rock they think it is. They think it is resourcing, or focus, or that one person, and they are almost always wrong, because the thing actually holding them up is that no two people in the room mean the same thing by the word finished. One person means it works on their machine. One person means it is tested. One person means the customer has it in their hands and has not complained. One person, quietly, means it is as good as they personally can bear to make it, which is a standard no schedule has ever survived. None of them are wrong, exactly, and that is the trouble, because a disagreement in which everyone is a little bit right is the kind that never gets an argument and therefore never gets resolved. It just sits under the work, adding a week here and a bad Friday there, and everyone blames the calendar. The reason this is so costly on a small team specifically is that a large team can absorb it. A large team has a whole function whose job is to decide what done means and to make everyone else observe the decision, and you may resent that function but it is doing real work. On a team of five there is no such referee, and so the definition lives in five separate heads, and the handoffs between those heads are where the time quietly dies. Someone marks a thing complete and moves on, genuinely believing they have finished, and someone downstream picks it up and finds it is finished in a sense they never signed up for, and now there is rework, and the rework feels like carelessness when it is really just translation. The fix is dull and it works, which is the only kind of fix I trust. You sit the team down, not for long, and you make each person say out loud what has to be true before they will call a thing done, and you write those sentences on one page where everyone can see them, and you have the argument exactly once, on purpose, in daylight, instead of a hundred times by accident in the dark. You will find the disagreement you have been having for months without knowing it, and you will settle it in an afternoon, and people will leave the room faintly annoyed at how simple it turned out to be. That annoyance is the sound of money coming back. Do not overbuild it. You do not need a policy or a tool or a page nobody will reread. You need one shared sentence about what finished means, agreed by the people who have to mean it, and the nerve to point at that sentence the next time two people disagree without realising they disagree. A small team's one great advantage is that it can hold a single idea in common. Most of them simply never check whether they actually do.