Job tracking software: the difference between a list and a board

Nearly every tool that calls itself job tracking software gives you the same thing: a list of jobs, with a status column, sortable. It is not useless. It is just answering a different question from the one anyone on a shop floor is asking.

What a list is good at

A list is an inventory. It answers "what do we have" and "what is this one's state" — and it answers them precisely, for one row at a time.

That is genuinely the right shape for some work. If jobs are independent, if they do not queue behind each other, and if nobody needs to see the whole system at once, a list is fine and a board is decoration.

What a list hides

The moment work moves through stages, a list starts hiding the thing you most need.

It hides the queue. Twelve jobs marked "in progress" tells you twelve jobs are in progress. It does not tell you that nine of them are stacked behind one machine and three are actually moving. Same status, completely different problem.

It hides duration. A row does not show how long it has been sitting in its current state. A job that entered "waiting on approval" this morning and one that entered it nine days ago look identical.

It needs reading. A list has to be scanned, row by row, and understood. A board is a picture: a tall column is a pile-up, and you see it from across the room without reading a word.

In progress is not a stage

The clearest symptom of a list pretending to be a workflow is a status called "in progress."

It is not a stage. It is the absence of one. Every job that is not new and not finished lands in it, which means the bucket that holds most of the work tells you the least about it.

Split it into the stages the work actually passes through, and two things happen immediately. Cars stop hiding — a job "in progress" for nine days turns out to have been waiting on a part for eight of them. And you find out which stage is the constraint, because the constraint is simply the column with the most cards in it and the longest average dwell.

The two numbers worth having

Once work moves through named stages, you get two numbers that end most arguments about where the week went.

Dwell per stage. How long jobs sit in each column on average. The largest dwell is your bottleneck. Not the loudest stage, not the one that feels busiest — the one where time actually accumulates.

Cycle time. How long a job takes end to end, from arrival to handover. The number the business is actually judged on, and the one that moves when you fix a bottleneck.

Both come free from a board that people move cards on. Neither is available from a list where "in progress" covers eight days of a nine-day job. That is the practical argument for a board: it is not a nicer view of the same data, it is a source of data a list never collected.

When a list is genuinely the right answer

Not everything should be a board.

If jobs do not queue — if each one is independent and nothing waits behind anything else — a board adds ceremony without adding information. If the team is one person, the queue is in their head and it is accurate. If what you need is search and filter across thousands of historical records, a list is the correct tool and a board would be unusable.

The test is simple. Ask whether anyone in your operation regularly needs to know where things are stuck, rather than what exists. If nobody asks that, a list is fine. If somebody walks the floor every morning to find out, that walk is the board you do not have yet.