RAISP01 BP02 Consider design trade-offs across competing objectives
Analyze how meeting one release requirement could impact others and establish clear protocols for managing these situations. Your release criteria will sometimes pull your system design in different directions.
For example, making your system more transparent might affect its accuracy, or adding stronger privacy protections could make it harder to explain how decisions are made. Focus on meeting the minimum requirements for each criteria rather than excelling at some while falling short on others.
Level of risk exposed if this best practice is not established: Medium
Implementation considerations
-
Identify where your release criteria might work against each other. Understand how meeting one requirement could make it harder to meet another. For example, adding privacy features might lower accuracy, or making decisions more explainable might slow things down.
-
Set clear priority rules that favor meeting minimum requirements for the criteria over excelling at individual ones. Work with your team, legal experts, and business stakeholders to decide approaches like we'll accept 85% accuracy if it assists us achieve 90% privacy protection rather than maximize accuracy.
-
Design your system using a holistic approach that meets release criteria requirements. Consider how your architecture, models, and components work together as a whole to achieve acceptable performance across each area instead of optimizing individual parts separately.
-
Build your system according to these balanced design choices, focusing on hitting your minimum goals across everything such as 85% accuracy, 90% privacy protection, and acceptable response times rather than pushing for peak performance in a single area.
Resources
Related documents:
