Module Three: The Process of Information Design

Any process goes from start to finish. The trick is defining what the actual start is and what the finish is. For example, the process of Christmas shopping can start and end with different activities. Some people start with making a list and end with watching gifts being opened. Others may start with the actual purchasing of gifts and end their process with wrapping the presents. Neither process is right or wrong and both processes have strengths and weaknesses.

Information design requires process planning that views projects from the very first step to the final outcome. This requires careful planning, critical thinking, systems thinking, brainstorming, and effective communication

Steps of an Information Design Process

1. Who? What? Where? When? How?

The first step is to ascertain the scope and strategy for the project. These questions will help define the project parameters that identify the range, the audience, the use, and the content for the information. The data gathered facilitates the action plan for the project.

2. Creative Brief-(two to ten pages)

The next step is to organize and arrange the gathered data to facilitate the design phase. The creative brief outlines the important project information to convey the “project background and goals” (Baer, p. 50).

       

3. Persona and Scenario

Information needs to be designed so that users can read, understand, and process the presented material. A persona mocks the intended user group and provides reactions, observations, and rebuttals based on users habits, needs, propensity, and proficiency. The mock users can execute different ways of using and interpreting the information to provide feedback that allows the design to be refined based on the feedback.

4. Prototype, Research and Testing

Prototype

The final product is tested using a prototype presentation that allows users to test the product and ensure it accomplishes its objective. Two examples of prototypes are a sitemap and blueprint.

              Sitemap

A sitemap is a tool that presents structure, flow, and nomenclature which provides a visual image of the entire project including all sections and levels. Sitemaps are helpful for web designs, menu sequences, and interactive media. A project map allows for revision history to be tracked, approved, and finalized. As a result, the client can become acclimated to the basic flow of a design before implementation. The sitemap also communicates the details and meaning of the essential project components.

http://www.utexas.edu/learn/designprocess/graphics/sitemap.jpg

              Blueprint

A blueprint provides the details to the sitemap that allows for a view of project organization. It encompasses the project parameters and allows for workability assessments. The blueprint is somewhat rudimentary and simplistic in that it will not encompass the finite details of color, final text, or other graphic elements that the final polished design will have. Blueprints, often called wireframes, provide user reactions that begin the testing process. While blueprints are often linked to plans for buildings they can also be used for blog designs.

http://page49.wordpress.com/2010/04/16/information-architecture-%E2%80%93-design-and-documentation/

Research and Testing

User feedback is essential to the design process and the previous steps provided isolated, but important, feedback. The next phase is to select representative users to ensure each step is tested outside the internal group of designers and the client. Testing should be done in phases to minimize extensive changes. The testing prototypes “need to look enough like the final so it’s clear to users” what they are (Baer, p. 82). Alternately, prototypes for testing should not be so close to final that they are mistaken for the final and then become preferred. Testing is conducted using the client’s customers or through outside agencies that find appropriate users. Different types of testing apply to different projects and in some instances surveys, live testing, group tests, or individual test are more applicable.

   Testing types
Concept Tests-early test that discusses the design with potential users

Participatory Design-sorting through ideas by interacting one-on-one with participants or with the card sorting exercise.

Design Testing-a process to get specific feedback on functionality or appearance based on different scenario usage.

Focus Groups-evaluation of a developed product by a group of people. It is more productive when groups are used for a quick consensus and participants are not strangers.

Usability Testing-ensures functionality is working as the designer envisioned and that average users have the same user experience as the designer.

Beta and Performance Testing-tests the design in the contexts of practical use. Simulates how users will interact and tests possible scenarios.

Important Steps

The most important step in any process is the beginning conversations that set the stage for the project. “Many factors that determine the success of a design piece are unrelated to the formal aspects of design but have everything to do with the context in which the design is created” (Bear, p. 32). Understanding the client and their organization is critically important to the final outcome of the project. I think this process goes further than the first questioning step of the information design process. Understanding the complexities of the organization is necessary to develop the framework and context of the project. Recognizing the organizations history, inner-workings, challenges, constraints, previous experiences, and authority positions establishes the initial baseline for the project. This information is needed before the audience and content can be developed.

Other Steps to Consider

In addition to gathering preliminary client information, it is important to develop project milestones and success metrics.

              Milestones

Milestones define a tangible step in the process that is met before the next step can begin. This also provides a concrete way to measure project completion steps. A sample of a milestone chart used within my organization is below.

              Success Metrics

The success metrics should demonstrate the attainment of defined goals and targets. In an organization, these should ultimately support the strategic plan. Success metrics might be a final grade, number of comments, sales figures, or website downloads.