The symptom
A team closes eighteen tasks in one cycle. The review lists the work done. It does not say what that work changed.
The signal
“Eighteen closed. What changed for the user?”
What’s going on
A task in the tracking tool coordinates work: who does what, in what order, where it stands. Counting closed tasks measures activity. When the number closed becomes the goal, the team cuts the work finer and the number rises while nothing changes for the user.
The right number is the result’s: the customer’s waiting time, the error count, support requests, the time to get paid. Tie every important piece of work to one of them.
Separate what was done, what was checked, and what is expected. “The fix is in place” is an action. “The case that was failing now passes” is a check. “Support requests should go down” is an assumption, until you look.
Usefulness is not limited to new things. Maintenance that keeps the service up, an inquiry that rules out a false lead, an accessibility fix: those are results, as long as you say which.
Check this
Take one finished piece of work and complete:
What it changed: …
The number or the fact that shows it: …
If you do not know, go and get the answer from the person concerned. At the next review, present that work by its effect.
To discuss
Which recent piece of work was useful without adding a feature?