Activity Percentage

In-Depth Definition

Activity percentage can help identify unusual gaps, but it is easy to overuse. It rewards visible input rather than outcomes, and it can be gamed by automation tools. Treat it as one supporting signal inside a broader proof-of-work record, not as a standalone productivity score.

How It Works in Practice

• Input events, keystrokes and pointer movements, are sampled across a tracked period and expressed as the share of that period showing interaction.
• It measures presence at a device. It does not measure effort, difficulty, quality or value, and no threshold turns it into those things.
• It is trivially inflatable, since any tool generating periodic input raises the number without any work occurring.
• It is most defensible as a supporting signal in a wider record, and least defensible as a standalone key metric.

A Worked Example

Two developers each log 8 hours. The first shows 82 percent activity and spent the day renaming variables and clearing a queue of trivial tickets. The second shows 31 percent, spent five hours at a whiteboard and in review, and shipped the fix for an outage that had recurred for months. Ranked by activity percentage, the wrong person is at the top.

The Common Mistake

Setting a target. The moment a team learns that 70 percent is expected, the number stops measuring anything: everyone reaches 70 percent, some by working and some by jiggling a mouse, and you have lost the diagnostic value while gaining a source of resentment. Use it to notice anomalies worth a conversation, never as a threshold anyone is held to.