This document discusses the problem of information overflow when testers generate too many defects for stakeholders like developers to analyze and address. It provides examples of how too many defects can prevent developers from fixing any. The key solutions proposed are for testers to prioritize defects before submitting them, only submitting high priority ones, and maintaining separate databases for reported defects and lower priority information. Testers should filter information strategically to support stakeholders while avoiding overwhelming them.