Ticket triage: deciding what gets answered first
Triage sorts incoming requests by urgency and owner before anybody starts work. How to set priorities that hold, who should do it, and why first-in-first-out fails.
Ettex Boards: five columns, work-in-progress limits that actually block a move, and grouping by priority, assignee or label when the column view stops answering the question.
A board is useful because it makes two things visible at a glance: what is in flight, and what is stuck. Ettex Boards is built around that rather than around decoration — five columns from Backlog to Done, limits on how much may sit in the middle of them, and the ability to regroup the same cards when the columns stop being the interesting axis.
A board without limits becomes a list of everything somebody intended to do, which is a mood rather than a plan. A limit does something uncomfortable and useful: when Review is full, moving another card in is refused, so the only way forward is to clear a review or to explicitly decide what to drop. That conversation is the entire value. Teams that raise the limit whenever it blocks them have chosen a slower board with extra steps — the honest move is usually to lower it.
Watch Review rather than In progress. Work piling up in Review usually means one person is the bottleneck for approvals, which is a scheduling problem disguised as a capacity problem — and it is the commonest reason a board stalls while everybody looks busy.
Ettex Board suits a small team running one flow, and keeps the cards local so the board stays responsive. Where the work has to be reported on rather than moved — owners, dates, costs, history — that belongs in a register alongside, because a board answers what is happening now and a register answers what happened.
Three cards in Review. Moving a card into a full column is blocked rather than warned about.
Yes — by priority, assignee or label. The cards are the same; only the grouping changes.
No. A board shows flow and bottlenecks; a list shows everything owed. Teams that need both usually keep the board for the current week and the list for the commitment.
Triage sorts incoming requests by urgency and owner before anybody starts work. How to set priorities that hold, who should do it, and why first-in-first-out fails.
A milestone marks a verifiable completion, not a point in the calendar. How to choose them, how many to have, and why percentage-complete reporting replaced them badly.
The critical path is the sequence that sets the end date. How to find it without software, why most status reports chase the wrong tasks, and what float really means.