A set of short, easily digested learnings from the world of Interaction Design, inspired by "101 Things I Learned in Architecture School", by Matthew Frederick
Tuesday, September 1, 2009
Be wary of projects with ill-defined scope
It could be argued that it is often our job to define scope. Certainly, our efforts call into question elements of scope at times and our recommendations can help to tighten the focus on scope. Regardless, a project with ill-defined scope should ring loud alarm bells for the eager interaction designer. If a client can't tell you what the strategic purpose of the solution is or how it will affect a business or user outcome, it is very difficult to know when you have finished doing your job as a User Experience practitioner. Seek an articulation of scope early. If it doesn't exist, be a part of creating it.