One missed deadline turned into a daily proof-of-work system

One project missed a deadline by two days.

The cause was ordinary and shared: a vendor delivered late, the team underestimated testing, and nobody updated the client soon enough. We reviewed the sequence and agreed on several changes.

Then our manager introduced a daily activity log for everyone.

By 4:30 each afternoon, every employee must list the tasks completed, minutes spent, files changed, blockers encountered, and plan for the next day. On remote days, we also post a morning message when we start and an evening message when we stop.

The manager says the system is temporary and intended to rebuild visibility. Six weeks later, it is still running.

The log takes about fifteen minutes when the day is simple. On a complicated day, it takes longer because the work does not fit neatly into task names and minute counts. People now delay small conversations because they are difficult to record. One coworker writes “collaboration—35 minutes” after helping someone, as if ordinary teamwork needs a receipt.

The strange part is that the missed deadline would not have been prevented by this system. The vendor delay was known. The testing risk was discussed. The failure was that no one made the tradeoff or reset the client date. More activity detail would have produced a longer record of the same undecided problem.

The logs have changed behavior anyway. People choose tasks that can be completed and listed. Longer analysis gets broken into artificial fragments. The manager praises days with many completed lines, even when one hard unresolved issue matters more.

I want to propose replacing the daily proof with a weekly outcome view: commitments, risk, decision needed, owner, and date. If a project is slipping, increase the check-in for that project instead of placing the whole team under permanent observation.

Accountability matters. A missed deadline deserves a response. But a response should connect to the reason the deadline was missed.

What evidence would you bring to argue that a tracking system is measuring activity rather than control? How long can a “temporary” visibility measure continue before it becomes the actual management model?