Wednesday, November 17, 2004
Three Reflections on how to Design Well
Kees Dorst's book ("Understanding Design | 150 Reflections on Being a Designer") has many lessons that can help HCI designers. UsabilityNews comments on 3 of them.
The user plan - as well as designing an artifact you are designing how someone uses it - so make it explicit.
The story - sometimes known as design rationale, and the reason I ask all my project students to keep a diary of their decisions and agonisings, so that they can reconstruct this afterwards to allow them to defend their designs.
Problems and solutions as twins - essentially, interpreting the issues can be done in many ways - and the solution will vary. But the soluton has to meet the needs of the users, so it may be necessary to reinterpret the problem in a differnt way to get a better solution.
Kees Dorst's book ("Understanding Design | 150 Reflections on Being a Designer") has many lessons that can help HCI designers. UsabilityNews comments on 3 of them.
The user plan - as well as designing an artifact you are designing how someone uses it - so make it explicit.
The story - sometimes known as design rationale, and the reason I ask all my project students to keep a diary of their decisions and agonisings, so that they can reconstruct this afterwards to allow them to defend their designs.
Problems and solutions as twins - essentially, interpreting the issues can be done in many ways - and the solution will vary. But the soluton has to meet the needs of the users, so it may be necessary to reinterpret the problem in a differnt way to get a better solution.
Comments:
Post a Comment
(c) 2003-2005 Russell Beale
Atom
RSS