Surprisingly, similar problems (e.g., design issues, discrepant material, anomalous test results, changes to or misinterpretation of requirements) occur on multiple projects and missions. Some are even repeated on the same project over time as staff changes. Timely communication of the problem through a Lessons Learned database or similar system, the impact, and its resolution, creates awareness and reduces risk of repeat. Also, even when such databases do exist, they are not always referred to. One way to ensure they are, is to include a step in a design review or project milestone, for example, that shows the alert system or database has been reviewed for any relevant items. This may also enhance the likelihood that the database will be kept up to date.