To build a successful solution, you have to be agile and progress steadily. But are BAs asking the right questions? Have we addressed hidden properties that may impede further progress? The presentation focuses on the importance of designing solution quality attributes (also known as non-functional requirements) and how to define them in collaboration with stakeholders, primarily with Quality Attribute Scenarios approach by Carnegie Mellon Software Engineering Institute. The ultimate goal is to avoid failure and reach higher satisfaction for both users and company stakeholders behind the solution.