Five Reasons for Scenario Based Design
I found this paper challenging. Confusion ensued from the mix of the title ("Five Reasons") and the numbered sections (which, like a good Spinal Tap amplifier, went above 11!) After sorting through the author's approach, I still found I needed to translate his headings to understand his general meaning: 1) Challenge: When you're designing, you're rarely simultaneously reflecting. Solution: When building scenarios, you're continuously reflecting and improving 2) Challenge: Design situations are ever-changing. Solution: Scenarios can ground you in those things that don't change, and give you flexibility regarding those things that do! 3) Challenge: A single design change can have unintended consequences. Solution: Flesh out all the perspectives in a design scenario and you have a tool for prediciting consequences of any changes. 4) Challenge: Tech knowledge (how to implement something) lags design knolwege. Solution: Scenarios can be abstracted and simplified - ??? 5) Challenge: External factors constrain design. Solution: This is a reality...just deal with it.