On Oct 8, 2007, at 11:25 AM, Peter Boersma wrote: > That paragraph seems to imply that you equal design thinking with > concepting, or at least that the end result of design thinking is a > design concept. I cannot believe you would want that idea to > persist, so I am asking you to explain what you really meant... :-) > That's what I've been coming to believe lately. Although certainly thinking as an activity takes place throughout the design process, the largest and most intense proportion of it seems to come at the beginning of the process, during concepting. And since "d-schools" and the like don't often teach things like modeling or typography or other skills to bring a design to fruition, I'm forced to believe that a concept is the outcome of design thinking, while a product or service is the outcome of design.
Bolstering this claim is that design thinking is often applied to areas outside of those in the traditional design realm, such as into business processes. Those areas are not easily prototypable or modeled, outside of actually creating them, so the concept is often all you have to build on. I'm willing to entertain notions to the contrary though. :) Dan ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://gamma.ixda.org/unsubscribe List Guidelines ............ http://gamma.ixda.org/guidelines List Help .................. http://gamma.ixda.org/help
