There’s a rhythm to a ticket-tracker week, and if you’ve ever run a sprint you can hum it.
Monday: the board is honest, because nobody has touched it. Tuesday through Thursday: reality and the board drift apart — code merges, branches stall, cards stay put. Friday morning: a flurry of updates, dragged cards, and status comments, right before the review meeting. Friday afternoon: the board looks great and says almost nothing.
The board isn’t a mirror. It’s a weekly performance.
The grooming tax
The Friday update ritual has a cost, and it’s not the 20 minutes of card-dragging. It’s what the ritual teaches:
- Progress is something you report, not something you show. The artifact of work becomes the comment on the ticket, not the merge.
- The meeting is the deadline. Work gets described so it survives a status review, which is a different skill than finishing it.
- Optimism is safe, honesty is expensive. “90% done” is a claim nobody can check until next week. By then there’s a new board.
Nobody is gaming anything on purpose. The tool just only knows what people type, and people type before meetings.
What an honest Friday looks like
Here’s the test we use: ignore the board entirely and ask the repo.
- What merged to main this week?
- Which PRs are still open, and how old is the oldest one?
- Which branches got a commit in the last 48 hours — and which haven’t moved since Tuesday?
- Is CI green on the things called “done”?
Those four answers are the real sprint review. They don’t need anyone to prep, they can’t be polished in the ten minutes before the meeting, and they’re available on Tuesday too — which is when you can still do something about them.
The habit that breaks the cycle
The fix isn’t discipline. Nobody keeps a second system updated out of discipline for long. The fix is to stop maintaining a second system at all: put the commits, PRs, and CI next to the tasks so the board reads its status from the work instead of from weekly testimony.
That’s what Kahoona is built around — your board streams live GitHub activity beside your tasks, so Friday’s board looks the same as Wednesday’s: just true.
👉 See what your team actually shipped this week
Related: Jira shows tickets, not truth · Why commits belong next to tasks