Mapping

"Part of where I'm going, is knowing where I'm coming from" -Gavin Degraw

Information designers utilize mapping techniques to show where objects are located in relation to one another. Mapping is an incredibly versatile tool that “makes all kinds of ideas about the spatial relationships of objects unexpectedly clear” (Roam, 2009, p. 166). Information maps are used to create a visual connection between interrelated concepts, structures, or processes in a clear and incisive manner. According to Horn (1994), information mapping makes it easier to write technical materials, provide more specific content and analysis, and leads to more effective and efficient learning.

Applications of mapping in information design:

• Wayfinding
• Infographics
• Wireframes 
• Blueprints
• Information architecture, such as sitemaps
• Project documentation: team organizational chart, work plan diagram, etc. (Baer, 2009, p. 34)
• Diagrams
• Webbing
• Matrix
• Charts
• Timeline
• Structure mapping
• Process mapping
• Concept mapping

Concept mapping has become increasingly useful as a research tool and an instructional technique to facilitate meaningful learning” (Novak, J. & Gowin, B. & Johansen, G., 2006).  For this blog post, I created concept maps to demonstrate each step in Roam’s visual thinking process: look, see, imagine, show.  Then I created a process map that demonstrates visual thinking as it really happens (Roam, 2009, p. 41). 

Once I sketched out my process map, I used Microsoft Office object palette to create concept maps for the four steps in the visual design process:

References:

Baer, K. (2008). Information Design Workboook. Massachusetts: MIT Press.

Horn, R. (1994, March). Information Mapping. Training in Business and Industry. Retrieved from http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=0CDEQFjAB&url=http%3A%2F%2Fwww.stanford.edu%2F~rhorn%2Fa%2Ftopic%2Fstwrtng_infomap%2FartclInfoMappingTraining.pdf&ei=tetrT4yDDKjs0gHq7N3HBg&usg=AFQjCNEuhfBo-eisnCTPYQPtnUyvIpZMBA&sig2=QODvhG1cgYU7p79EQPTRrQ

Jacobson, R. (1999). Information Design. Massachusetts: MIT Press.

Novak, J. & Gowin, B. & Johansen, G. (2006). The use of concept mapping and knowledge vee mapping. Cornell University. Retrieved from http://onlinelibrary.wiley.com/doi/10.1002/sce.3730670511/abstract

Roam, D. (2009). The back of the napkin: Solving problems and selling ideas with pictures. New York: Penguin Group.

Informational Design Process

"People ignore design that ignores people." -Frank Chimero

Designing information for a particular audience is a problem solving process that requires careful thought, collaboration, and planning. Each step of the process is described in the graphic below (Baer, 2008): 

* Please click on the graphic to view enlarged image

This process ensures that the client and the design team are on the same page throughout each phase of the project. The only improvement I suggest is to include more information about the target audience during the creative brief and collaborate with representative audience members during the development of personas and scenarios. This will prevent the team from making assumptions about the audience that may mislead designers during the prototype development phase. I think that the preliminary questions are the most important phase of the project because it is imperative to gain a thorough understanding of the client's unique needs and develop a collaborative relationship in order for the project to be successful.

For my blog, I have considered how to present information to members of the class in a clear and concise manner. I have created graphics to help the audience gain a better understanding of key messages. I have used feedback from my classmates to edit the content of posts and consider their recommendations in later posts. I considered the importance of a user-centric design and arranged the elements of the blog to give the important features greater visibility. I have eliminated certain elements that I felt were not necessary for the audience's purposes. This process has also helped me understand that I cannot look at the entire class as one audience, because we have different learning styles and technical experience.