Dashboard Examples

Dashboard Designneed for a user centric view : 

Dashboard Designneed for a user centric view 15 July 2009

Slide 2: 

Examples

Slide 3: 

GAP Minder (Acquired by Google) Gapminder is a non-profit venture promoting sustainable global development and achievement of the United Nations Millennium Development Goals by increased use and understanding of statistics and other information about social, economic and environmental development at local, national and global levels.

Slide 4: 

http://graphs.gapminder.org/world/

Slide 6: 

USASpending.gov USAspending.gov, a re-launch of www.fedspending.org, provides information to the public, as collected from federal agencies, in an easy to use website.

Slide 7: 

http://it.usaspending.gov/

Slide 9: 

Data.gov A primary goal of Data.gov is to improve access to Federal data and expand creative use of those data beyond the walls of government by encouraging innovative ideas (e.g., web applications)

Slide 10: 

http://www.data.gov/

The Problem : 

The Problem Though some agencies have done a great job of getting their data and documents online, the accessibility and usability of government data overall can be improved. The Change:View Data Release From the User's Point of View, not the Agency'sIn short, why should user-citizens have to know which government silo handles which problem to get answers? Data.gov creates the possibility that at least in data, that won't be the case. But one key will be designing the site to think about data use-cases, not agency needs. http://howto.wired.com/wiki/Open_Up_Government_Data#The_Problem

Slide 12: 

User Centered Design UCD is a well-established process that is used by many organizations to deliver products that meet users' expectations.

The Users : 

Easy-to-use software doesn't just happen. It requires focusing on the product's potential users from the very beginning and checking at each step of the way with these users to be sure they like and are comfortable with the final design. Who will be using the product? http://www-01.ibm.com/software/ucd/ucd.html#whatisucd The Users

The Process : 

The Process When the target audience has been identified, representative users can be recruited to work with the team. These users help establish the requirements for the product by answering questions that include the following: What do you want the product to do for you? In what sort of environment will you be using the product? What are your priorities when using the software? For example, which functions will you use most often?

The Principles : 

The Principles Set business goals.   Determining the target market, intended users, and primary competition is central to all design and user participation. Understand users. A commitment to understand and involve the intended user is essential to the design process. If you want a user to understand your product, you must first understand the user. Assess competitiveness.   Superior design requires ongoing awareness of the competition and its customers. When you understand your users' tasks, you must test those same tasks against competitive alternatives and compare their results with yours. Design the total user experience.   Everything a user sees and touches is designed together by a multidisciplinary team. This includes the way a product is advertised, ordered, bought, packaged, maintained, installed, administered, documented, upgraded, and supported. Evaluate designs.   User feedback is gathered early and often, using prototypes of widely ranging fidelity, and this feedback drives product design and development. Manage by continual user observation.   Throughout the life of the product, continue to monitor and listen to your users, and let their feedback inform your responses to market changes and competitive activity.

UCD Activities during design stages : 

UCD Activities during design stages Product Definition Audience definition, a definition of the new product or product enhancement Task Analysis Evaluate customer requirements, develop an audience and customer description, evaluate task analysis data; Current and future tasks plus task attributes, typical scenarios of use Design and Walk-through Set high-level design objectives; identify model, metaphors, main messages, and alternative design solutions; propose alternative design solutions; choose a solution based on user input; Low-fidelity prototypes of high-level designs or mockups for design walk-through (or both), "go or no go" recommendation based on users’ response to the high-level design; collect users’ reaction to the high-level design Evaluation and Validation Set specific design objectives, alternatives; prototype, evaluate, and validate designs; hold low-level design reviews; iterate the design based on analysis of users' experiences with it ; Low-fidelity prototypes of specific design solutions

Slide 17: 

Thank You