Interaction Design & Written Language
"Anyone who has observed even a single usability test knows the importance of the words used to label navigation, actions, and content for user comprehension and task completion. But a writer’s skill set extends beyond copyrighting. When designing solutions for activities, it is especially important to understand that an activity, like a written narrative has a beginning, an end, and above all a point.
Leading users through a narrative requires maintaining enough context and information to communicate current status as well as enough interest and clarity to get them to the end. Likewise enabling activities through design requires the right amount of communication: some verbal and some visual. This wide definition of Design Communicator (DC) is reflected in the evolution of the role at Cooper:
“We originally started out thinking that DCs were either going to be like tech writers, or be junior Interaction Designers (IxDs) who would eventually move into the IxD role. As the role evolved, though, we realized that when we combined a visual, structural thinker (the IxD) with a more sequential, verbal thinker (the DC), great things happened. We could iterate the design and uncover potential problems very quickly, and the end result was better and more thoroughly articulated than it otherwise would have been.” -Kim Goodwin, Cooper" continued ... (Via Functioning Form)

Interface Designer as Design Communicator.











0 Comments:
Post a Comment
<< Home