Defect backlog hygiene beats writing more cases

Teams often respond to quality pressure by writing more test cases. That feels productive. It rarely fixes the real drag: a defect backlog full of duplicates, zombies, and tickets nobody trusts.

When I join a programme, I treat the backlog as a product surface. Every open defect should answer three questions: is it still real, who owns the next action, and what happens if we ship without it.

The method is deliberately boring. Sweep by age and status. Close invalid or unreproducible items with a clear comment. Merge duplicates. Re-prioritise only what still threatens users or release confidence. Then publish a short dashboard so Engineering and Product see the same picture.

On one long-running delivery programme, owning that hygiene cut noise enough that engineers spent noticeably less time re-triaging the same issues — roughly a 40–50% efficiency lift on the defect conversation itself.

More cases can still matter. They matter more after the backlog is honest. Otherwise you are documenting a fog.