How to Track Project Progress
Most tracking systems answer "what did we report last time." A useful one answers "what's actually true right now," and the difference is bigger than it sounds.
What "tracking" should mean
Tracking project progress is often treated as a reporting exercise: gather the numbers, write the update, send it out. That framing quietly turns progress into something that gets produced periodically rather than something that's simply true at any given moment. The better framing is that tracking should be a picture you can look at, not a document someone has to prepare.
The test for whether a team is actually tracking progress, as opposed to reporting on it, is simple: can you find out where things stand right now, at an arbitrary moment, without interrupting anyone to ask? If the honest answer requires a Slack message or a stand-up, what exists isn't tracking. It's a person functioning as the tracking system, on a delay.
What a trustworthy tracking setup needs
These aren't features. They're properties the tracking has to have or it isn't tracking anything real.
"In progress" has to mean the same specific thing every time a card lands there: actively being worked, not "assigned" or "will start soon." Without a shared definition, the column tells you who owns something, not how far along it is.
Shared ownership of a single item usually means nobody is actually driving it, and its position on the board stops meaning anything until someone claims it.
Not "basically done," not "done pending review." If review is a separate step, it needs a separate column. Otherwise "done" quietly absorbs unfinished work and the count of finished items lies.
Status should come from where a card physically sits, not from a separate field someone has to remember to change. Two sources of truth for the same fact will eventually disagree.
How long has this item sat in its current column? A card that's been "in progress" for three weeks is telling you something a status label alone won't.
Why status fields drift from reality
A dropdown field labeled "status" seems like the obvious way to track progress, and it's usually the first thing to go stale. The reason is structural: updating it is an extra action, disconnected from the work itself, that someone has to remember to do on top of the actual task. On a normal day, remembering to move a task takes priority over remembering to update a field that describes it, so the field lags, sometimes by days, sometimes long enough that nobody trusts it and reverts to asking in person.
A card's position on a board doesn't have this problem, because moving it usually is a natural part of doing the work: pulling it into "in progress" when you start, into "review" when you hand it off. The tracking isn't a separate chore layered on top; it's a side effect of actions someone was going to take anyway.
Progress as a byproduct, not a report
The clearest sign a team has this right is that nobody has to "put together" a progress update. It already exists, continuously, and a status meeting becomes optional rather than the only source of truth. The clearest sign it's wrong is a recurring ritual whose entire purpose is reconstructing what a board should have already shown: a stand-up that's really a status dictation, a weekly report that takes longer to assemble than the work it describes.
This matters most for anyone one level removed from the daily work: a manager overseeing several projects, or a founder checking on a team they don't sit with. Their honest options are asking someone directly, which interrupts that person, or looking at a live picture that's already accurate. Only one of those scales past a handful of people.
A short self-check
- Does everyone on the team agree what "in progress" specifically means?
- Can you tell how long an item has been stuck in its current state?
- Is there exactly one place status lives, or does a spreadsheet quietly duplicate the board?
- Could you answer "where are things right now" without asking a person?
- Does "done" ever get walked back to "not actually done"?
Where this shows up in the tool
This is the specific gap ShipSprint's owner command center is built to close: a single view that answers "where are we" across every team's boards as they actually stand, with a Monday digest for anyone who'd rather start the week with a summary than go looking. The underlying picture comes from where cards actually sit rather than a status field someone updates separately, and a built-in wiki keeps the reasoning behind a decision next to the work it affects, so the history behind a card's current state is one click away rather than a message thread nobody can find again.
Common questions
If status comes from where work sits, this question mostly dissolves. It updates the moment someone moves a card, which happens naturally throughout the day. It only becomes a scheduling question when status is a separate manual step, in which case "how often" is really asking how much staleness the team can tolerate.
Rarely on its own. It's usually someone's rough guess rather than a measurement, and it tends to sit near 90% for a suspiciously long time. A count of items in each column, with their age, tells you more than a single percentage that nobody can actually verify.
As few as the work genuinely requires distinct handling for. Three or four is typical: something like backlog, in progress, review, done. Adding a column for every possible sub-state makes the board harder to read without making progress any more accurate.
It's a good summary of the trend but a poor tool for finding out why. If the line flattens, you still need the board underneath it to see which items are actually stuck and where. The chart tells you something changed, not what.
Related pages
See it on your own work.
A workspace your whole company will actually use is 60 seconds away. No card, no risk, nothing to install.
14-day full-access trial · sample project included · no card required