From the Perspective of Pattern/Alexander Pattern Format
...where ever there are assumptions, we can only create value when the assumptions have been validated, i.e. proven to be true and not assumptions. Whether they are USER NEEDS ASSUMPTIONS, BUSINESS ASSUMPTIONS ,or SOLUTION ASSUMPTIONS, the value will only be created after it's been validated.
Three delimiting diamonds
A group of people need a way to turn assumptions into facts in order to create value
Conventional planning has risk of discounting, or externalizing, assumptions so they are out of scope of the plans. However, those assumptions will ultimately be accounted for - the only questions is when and at what cost.
For instance, the plans (design, development and delivery) for a new feature may:
assume the users need(s) are well understood,
assume the users need(s) are solved by the functional design (aka viable)
assume the uses need(s) are solved (i.e. desirable) by the user experience design (aka desirable)
assumes the business can build, deliver, and support the feature (aka feasible)
assumes the business can afford to developmen
By delivering the feature requirements to be built and delivered, theses defining the requirements for the featurethat the user will Any plans based on assumptions is very likely to fail, the only question is what will fail. Are the user needs wrong,
Another three diamonds
For one cycle of the the Pattern/Learning Loop
start a new cycle of the Pattern/Learning Loop