Prioritization and iteration using evaluation evidence

Week 6, Lesson 3. The full evaluation system is built. The hard work is done. SQL errors, retrieval failures, policy violations are all identified and backed by evidence from Weeks 1 through 5. This is where most teams stumble. They know what to fix but not which to fix first. That is the gap between knowing and shipping. In the last lesson, a quick three-factor priority score was used: impact times confidence divided by effort. That works for ranking within one set of findings. But when managing a full evaluation backlog with dozens of competing improvements, more dimensions are needed. This lesson's framework adds user harm, frequency, time-to-learn, and strategic alignment to produce a complete prioritization model. This lesson teaches how to convert a messy backlog of known issues into a ranked iteration plan where every work item has clear acceptance criteria and every ranking is defensible with evidence. No more arguing about opinions. The result is a systematic method.