The quality and validity of your visualization project hinges on collecting good data. You will likely collect data from existing sources and prepare methods of collecting your own data. You will be planning your data collection in parallel with prototyping your team's dashboard. They will co-evolve.
Download Currently Available Data Locate freely available data that you will (or may) use for your project and download a copy. If it is CSV data, import the data into a spreadsheet and verify the columns are correct. Place any files in your group's online folder.
Create Survey(s) for Custom Data Collection If your team needs to collect some of its own data you can create an online survey or ask in person. Either way you will want to create a Google form (or similar) to record results, since responses can automatically generate a spreadsheet of data. Once you create any surveys, test them to ensure that the responses generate the data that you expect. Keep a copy of surveys in your group's folder
Optionally, Prepare a Request for Data If you would like to request non-public data from a source that you believe has valuable information, prepare your request and how you will deliver that request. This could be by email, personal request, letter, or other social media. Keep a copy of the text in your group's folder.
Evaluate your Survey(s) with Another Team Once any surveys are created, conduct a dry-run with another team. You can do this whether it is intended to be an online survey or interview.
Be prepared to share with your class your data collection plan and be sure to document each items as described above.
Once you have finished your data collection and the development of your online visualization, prepare a few slides to present your team's development process for the the following.
Data Collection Outline the methods of data collection and sources of your data. Be prepared to explain the primary challenges you faced in the process.
Design and Styling Outline the inspiration, reasoning, and process behind the design and style elements. Be prepared to explain the primary challenges you faced in the process.
Programming Outline the process used to program the visualization, including methods used to debug problems. Be prepared to explain the primary challenges you faced in the process.
Practice how your team will demonstrate and explain your visualization to the class. Prepare a few questions to ask the class in order to get feedback and ideas on your visualization.
A presentation and link to your visualization.
Now that you have a clear design target for the data and visualization, it's time to determine a simple plan for development. The following three activities are a good way to divide up tasks and responsibilities.
Data Collection - Your team should already have some good data downloaded and you may have surveys ready to go from your earlier planning. You will still want to consider new online searches or surveys as your team learns more during development. A large part of your time will be refining, testing, and executing your surveys. You will want to ensure that all data is in a usable format for programming the visualizations.
Programming - There are different paths you could take to programming your visualization and you may actually want to mix your methods. For example, you could create static charts in Google sheets and export them as a .png image file and insert them with HTML in your final web page. But for dynamic and custom visualizations, you will want to work in Javascript using the template and code examples as a starting point. Carefully consider your options.
Design Style and Writing - The style and writing for your visualization should not be taken lightly. Carefully develop a style (colors, fonts, layout, etc.) that is clear, engaging, and reflects the purpose of your work. While you will aim for creating only two or three paragraphs of text as part of your visualization, you want the writing to also be very clear, engaging, and fully reflect the purpose of your work. Do several iterations for improvement. You will also be responsible for the clarity of labels and annotation in your visualizations.
Once you have determined who will take what roles, discuss the first steps each team member will take in the development and how you will collaborate along the way.
Design a prototype of the solution for a detailed internal review and evaluation by a sample of stakeholders. Based on what you learn from your prototype, organize a development strategy to methodically collect data, program, and style your solution with efficiency and quality. Also prepare for the promotion and launch of your solution, and conduct unit testing to ensure all is in working order before an in-class demonstration.
Keep in mind that your prototyping will co-evolve with your team's data collection planning.
Each prototype can be mixed-media, like the example above, where you use a sketch embedded in a Google document to represent what your dashboard may look like.
Each prototype should contain the same elements your final dashboard will have.
A title.
The dashboard visuals. This can be a neatly done sketch or charts created by a digital tool like a spreadsheet.
A link (fake at the moment) to how you will share your data. Don't worry about including any current data you have.
A paragraph or two that clearly describes the methods your team used, the value the visualization has to stakeholders, and any conclusions your team can claim from the data analysis. For your prototypes this will simply be a draft description.
A listing of team members and your school.
Date.
Style the page as you like, but don't worry too much about style and color. Focus on clarity and content.
Before you get feedback on your prototypes, determine how you will prompt participants to give you feedback. This will be a flexible script to ensure you get useful results. Here is a recommended outline to begin the process. Adapt it to your needs.
Briefly explain the background of your class project to the participant and that you are looking for feedback on your prototype before you begin full development.
Ask the participant to study your prototype for a moment. Give them some time to look at it. (This is why a clear and legible prototype is important.)
Ask the participant what they believe the purpose of the visualization would be and what important information might somebody learn from it. Let the participant know that you are not quizzing them, but trying to ensure the design is self-apparent in its purpose. Allow the discussion to go where it leads without taking too much time.
Ask the participant if they have any other ideas or insights to improve with your project.
Thank her or him for participating in the evaluation and let them know how they can see your team's final work later.
Get feedback from classmates outside of your team to check for any obvious problems, then each team member should get feedback from at least 2 people outside of class on your prototypes. Be prepared to outline and discuss the feedback received.
Document your team's prototypes and the summary of feedback.
The building blocks of your visualization dashboard are individual charts and visuals. You will now conceptualize the details for each of these building blocks that will support your proposal and value statement. Begin by describing six or more visual elements that may end up being in your dashboard.
This might be a good time to use visual techniques for thinking like Dan Roam provides. These concepts may help your team think about how different visuals can help answer who, what, what, where, and when types of questions.
Outline the following for at least six potential visual elements (e.g. charts) in your dashboard,. There is no particular order to this outline, because each description co-evolves. Just start with what makes sense for you.
What type of visual may be used for this element? Precisely describe and sketch the type of visual intended (e.g. bar chart), including what data goes on what axis. Use this resource (starting on slide 4) to guide you in selecting a type of visual. Sketch out each visual with enough detail to help your team discuss and plan design choices. Include axis labels. Take photos of your sketches to document as needed.
Why is this visual element valuable? Describe how this particular element supports your value statement in your proposal. What important questions does it help answer? You are building a more detailed explanation of your value statement with each visual element.
What data is needed for this visual element? Describe the data needed to make the visual element, along with appropriate units of measure. You can think of this as the column labels of a data table you will need to create the visual.
What are the likely sources of your data? List the potential sources of information for each element. Do a thorough internet search for existing sources as needed. Your source may also be a future survey or interviews you conduct.
A document or spreadsheet the outlines the the items above for each potential visual element of the dashboard.
