Open for new installations worldwide One-time price 1 year support included
Choosing software

Why your last task app died in month two

The software was not the problem. The one question that predicts whether a tool is still in use in month three, and how to ask it before you pay.

By Davinder Singh · 4 min read ·

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.

How to test it before you pay

Most trials are run by the most organised person in the business, during the quietest fortnight of the year, on work that was already under control. They prove nothing except that the software functions.

Design the trial to fail if it is going to:

  1. Pick your least enthusiastic member of staff, not your most organised one.
  2. Run it through a normal-to-busy fortnight, never a quiet one.
  3. Use real work, including the messy jobs nobody wants to write down.
  4. Stop reminding people after day three. That silence is the thing you are actually measuring.
  5. On day fourteen, ask one question: is the list true? Not “did people like it”.

If the list is accurate on day fourteen without you having nagged, the tool works for your team and you should buy it. If it is not, no feature on the roadmap will fix it, and a cheaper subscription will not either.

Best of all, this test is free – most board tools have a free tier generous enough to run it properly. Find out with a free board before you spend anything with anybody, including us.

What to do if the answer is “they will not”

Then the requirement is not a better board. It is a system that builds the list from something your team already does.

That is what Bosun is: the assistant lives in WhatsApp, which is already on every phone and already open, and it turns the messages people already send into a tracked list. Nobody installs anything, nobody logs in, and there is no update step to skip. Your team carries on as they were; the difference is that somebody can now ask what is outstanding and get a true answer.

We are also not the right answer for every team – if your people sit at desks all day, a board is cheaper and better, and we would rather say so now. The twelve questions to ask any vendor, us included, are in the buyer’s guide.

Written by Davinder Singh Founder, Bosun

Davinder Singh builds Bosun, the white-label WhatsApp operations assistant, and sets up and supports every client launch himself.

About the author How we write these guides
Part of the guideTeam task software buyer's guide
Ready when you are

Your brand. Your server. Your assistant.

Watch it read a real message and build the job list, before you spend anything.

WhatsApp Pricing Book a demo