Problem Scope
How can we align SLS engineers across discipline teams on performance requirement usage contexts?
How our problem evolved
Original Problem Statement
How do we help systems engineers know when they're "done" with this stage of designing the rocket and, more specifically, understand the complex information required to do so?
How our Problem Changed
Over the course of our research, we found that the greater problem was getting to "done," rather than identifying when a phase was "done."

We discovered that Level 3 discipline engineers often find themselves misaligned when it comes to how they approach work--specifically, how they interpret and use performance requirements. The consequences of misaligned work include costly schedule delays and demoralized teams heading back to the drawing board. This, of course, led us to our final, working design opportunity and problem scope.
KEY INSIGHT 1
Decentralized data is difficult to locate and communicate
KEY INSIGHT 2
Lack of transparency around other teamsā€™ requirement usage context hinders successful communication
KEY INSIGHT 3
Communication and decision-making is often unstructured and undocumented