Can Ticket Counts Measure Team Performance?

Ticket counts alone cannot tell us how well a team performed. A team can complete many tasks while the problem it set out to solve remains. We encountered this while reducing log-platform costs.

The team improved expensive queries and reduced CPU usage. It also reduced log volume for some services. Each task produced an improvement, but total cost still missed the target.

Total log ingestion was growing, and addressing that growth had remained a lower priority. Reducing processing resources alone was not enough to accommodate the growth and meet the cost target. Individual tasks showed progress, but the team goal required further work.

Missing the cost target does not erase the query improvements or resource savings. The reduced load deserves recognition as the result of that work. How much it contributed to the team’s cost goal needs a separate check. Reviewing task results alongside progress toward the team goal makes it possible to identify what still needs attention.

A team has limited time. In this case, addressing ingestion growth needed to take priority over further query optimization. Reviewing team performance needed to go beyond counting completed tasks and determine where to spend the remaining time to reach the cost target.