The two-week problem
Teams don't abandon task managers on day one. They abandon them around week two.
Week one everyone's enthusiastic. By week two, someone needs to know which client a task belongs to, and it isn't on the card, so they ask in chat. Then someone else needs to know whether the paperwork came back, and that isn't on the card either. Within a fortnight the real conversation has migrated back to WhatsApp and the board is a graveyard.
The tool didn't fail because it lacked features. It failed because it didn't know anything about the work.
What a custom field actually is
A custom field is just an extra labelled line on a task card. A name and a value:
| Field | Value |
|---|---|
| Care programme | NHTD |
| Borough | Queens |
| Language | Russian |
That's the entire mechanic. It's unglamorous, and it's the difference between a card you can act on and a card you have to research.
The test for whether you need one
Ask this about any task: what do I have to go and look up before I can start?
Whatever the answer is, that's your field. If people keep asking the same question in the comments, that question is a field. If someone keeps writing the same thing at the front of every title — "[Acme] fix the header" — that's a field wearing a disguise.
Conversely: if a field would be blank on most cards, or nobody has ever asked for it, skip it. Fields you don't use are just noise, and noise is how boards start feeling like admin.
Two businesses, same product, nothing alike
We watch this play out with the teams using NeonBoard, and the contrast is the clearest argument for the whole idea.
Advantage Home Care runs two completely separate funnels out of one agency — families looking for care at home, and caregivers applying for jobs and training. Their intake cards carry the care programme, Medicaid status, borough and the family's language. Their recruiting cards carry certifications and training cohort. Same product, two vocabularies, because an intake coordinator and a recruiter are not doing the same job.
Syntaxa Studio doesn't organise by department at all. They're a software studio running several client projects at once, so their boards follow the delivery phase instead. Build cards carry the repo and the demo date; retainer cards carry hours used against the monthly allowance.
Neither of them started from a template. They started from a conversation about how they already work, and the fields fell out of it.
Keeping it from getting messy
A few habits that keep fields useful rather than sprawling:
Reuse names. Start typing a field name and previously used ones are suggested. Accept the suggestion. "Client", "client name" and "Client Name" as three separate fields is how a tidy board turns into a landfill.
Add fields late, not early. Don't design the perfect schema on day one. Run the board for a week, notice what people keep asking, then add exactly those.
Cap it around five. If a card needs eleven fields to be understood, the card is probably two cards.
Delete what nobody fills in. A field that's blank on forty cards is telling you something.
The short version
Titles and due dates are table stakes — everything has those. What makes a board become the place your team actually works is that it holds the details your team already cares about, in the words your team already uses.
Get that right and nobody has to be reminded to use it. They use it because it's faster than asking.