This tool exists because rework costs everyone time.

It's not here to rank anyone or justify decisions about people. It's here because when a ticket bounces back, everyone loses time—the dev, QA, the team. Understanding where that happens helps us fix the handoffs, the requirements, and the process.

Start with your own trends

Look at patterns over time, not a single release. Improvement and consistency matter more than any one data point.

This is a signal, not a score

Rework reflects how well our system supports quality—code, requirements, testing, and handoffs—not individual ability or effort.

Ask “what changed?”

When data shifts, look for context:

• New or more complex work
• Changes in process or workflow
• Different types of tickets or integrations

Focus on reducing rework

The goal is not perfect numbers. The goal is less rework over time and smoother delivery.

Use for reflection, not comparison

This data is most valuable in:

• Personal reflection
• 1:1 conversations
• Team retrospectives

It is not intended for ranking or comparing individuals.

If the data feels wrong, say so

The tool should help us learn. If something doesn't match reality, it's worth discussing. That conversation is more valuable than any number on this screen.

Refresh Churn Data

Upload the three CSV files generated by the churn analysis script. This will replace all existing churn data.