From the Perspective of Pattern/Alexander Pattern Format
Pattern/Alexander Pattern Format/Archetypal Solution Picture: *
Pattern/Alexander Pattern Format/Larger Context Introductory Paragraph: *
... you are running discovery and/or delivery cycles (Pattern/Learning Loop), perhaps with limited time and/or money
Three delimiting diamonds
Pattern/Alexander/Pattern Format/Problem Headline: *
need to increase Pattern/Minimal Viable Solution/Value Creation (i.e. benefit from solving some Pattern/Minimal Viable Solution/Unmet Needs - user or business - and increase throughput (i.e. delivery of value over time) and increase adaptability (i.e. ability to respond to situational changes such as a change in priorities, change in schedule)
Pattern/Alexander Pattern Format/Pattern Body: *
Pattern/Alexander Pattern Format/Solution Headline: *
only creating assets that create immediate value (i.e. immediately solve user or business need(s)), avoids creating assets that solve possible future needs (user, business)
only spend the effort on solving immediate value and leave time for other high(er) priority needs, avoids solving for future value and taking time away from solving other immediate high(er) priority needs
when discoverery
build test of just critical assumptions, not too few and not too many; cut in 1/2 and 1/2 again by minimizing to test key piece(s) of critical assumptions
when delivery
build productized solution for validated and immediate and high-value needs; not assumed needs, not future needs
counter with investment for future use - based on product development expertise combined with confidence level of assumed needs or future needs
Another three diamonds
Pattern/Alexander Pattern Format/New Context Paragraph: *
measure solution metrics, recognize when we need to iterate to next solution
Relationships
Parts
