The arc is so consistent you could set a calendar by it.
Week one: columns set up, everybody invited, cards created, genuine enthusiasm. Week two: two people have stopped updating theirs. Week four: the board says one thing and the workshop says another. Month two: everybody is back to asking each other, and the board is a tab nobody opens. Month six: you are still paying for it.
Nothing was wrong with the software. The mainstream board and project tools are mature, well-built products used successfully by millions of people. The failure is structural, and it is worth naming precisely, because the same failure will kill the next tool too if you do not account for it.
The failure is the update step
Updating a card is extra work. It happens after the real work, by somebody with dirty hands and eleven minutes left in the day, on a phone, standing up. It produces nothing they can see. It benefits somebody else – you.
Any system that depends on that step loses to the system that does not need it. And the system that does not need it is the group chat, which is why your team went back to it.
Notice what this implies: the people least likely to maintain a board are precisely the people whose work you most need visibility of. Office staff with a browser open all day will keep a board current. Technicians, kitchen staff, field engineers and drivers will not, reliably, for longer than a few weeks – not out of obstinacy, but because the friction is real and the benefit is invisible to them.
The one question that predicts failure
Before features, price, integrations or anything else, ask this about any tool you are considering:
How many of my people have to open something they do not currently open?
That answer predicts month-three survival better than every other factor combined.
- Everybody must open a new app. Expect decay unless somebody enforces it daily, forever. Someone has to own that enforcement, and it is usually you.
- Only managers must open it. Considerably better odds – fewer people, and people whose job includes admin.
- Nobody must open anything new. The constraint is removed entirely.
Every other question in a software evaluation matters less than this one. It is also the question vendors are least keen to dwell on, which is itself informative – ask what their month-three usage looks like and watch whether you get a number.