Challenge Summary
Welcome to the Atrocity Prevention Visualization Design Concepts Challenge! In this challenge we are looking for your best concepts in how to visualize atrocities around the world. Along with visualizing what atrocities have happened in the past, we want to use that data to help monitor and/ or predict and prevent future atrocities. For this challenge we are focusing on a small set of screens to showcase the concept and idea. These are concepts, so we are looking for you to analyze the problem and propose the best UI and UX solutions. Good luck and ask any questions in the forum.
Round 1
- 01 Initial Map View
- 02 Detailed View/ State of Atrocity
- 03 Prevention/ Prediction Screen
Round 2
Include any checkpoint feedback and all finished screens
- 01 Initial Map View
- 02 Detailed View/ State of Atrocity
- 03 Prevention/ Prediction Screen
Atrocities are defined as “an extremely wicked or cruel act, typically one involving physical violence or injury.” Examples of atrocities can include genocide, war crimes, and inhumanity. Atrocities are often committed during wars and armed conflicts.
Required Screens/ States:
These are design concepts, so we are looking for expert ideas and designs oh best to present the information, navigation, and content. Below are some suggestions of specific screens/ states that would be useful. We are also open to additional and other ideas.
01 Initial Map View
- Initial map view of an area or region
- Default map would be a global map with the ability to zoom in or scan regions on a global map
- A “heatmap” style depiction of what are the “hotspots” of atrocities.
- Needs to have general map navigation functionality
- Should have filtering, searching, and refinement functionality. We are looking for your ideas on what is the best UX for the user; and the UI to make that possible.
- Some way to designate or mark where a specific atrocity took place. This could be through pins, markers, or some other data point.
- Ability for the user to view or change “modes” to view prevention/ prediction information and graphics.
- Different views might be interesting for this as well; think timelines, metrics (based on current map area/ region vs. global), prediction metrics (links to detailed view), etc.
- Our current set of data extends from 1995 - Current
- Our predictive capabilities are 30-60 days out from present day
02 Detailed View/ State of Atrocity
- A user can click/ hover on a data point for a specific atrocity to view more detailed information about that specific event(s)
- Detailed information could include: Name, type of atrocity, specific location, number of deaths/ people affected, dates the event took place (could be a single date or a span; ex 1998-2001), Cost of collateral damage
- Think about how to represent and present this information in an interesting way; infographics, charts, graphs, etc. Be creative, but make sure the information is still easily readable and usable. Make sure you visuals can be coded and developed easily.
- There should be a button or some way for the user to view prediction/ prevention metrics, graphs, and/ or information for this specific event (happening again or continuing to happen) or in the same area/ region.
03 Prevention/ Prediction Screen
- The likelihood that an atrocity will happen or continue to happen in a specific area or region
- This doesn’t necessarily have to be a separate screen, but should be readily available to the user and be easy and intuitive to get to and view
- The information presented will be based on historical data a metrics. We need some way to visualize that type of information.
- Again, these are concept designs, we are more interested in how you interpret the problem and design for it, than having specific and 100% accurate content.
Screen Requirements:
Desktop Resolution: 1280px wide (height can expand as needed)
Additional Input Sources & Information:
- Branding: Branding is open, but should follow a clean and modern design aesthetic. This aids in usability and is less distracting from the real content and data.
- Inspiration: We’ve put together and InVision Board with some examples and ideas to get you thinking in the right direction. Use these as inputs and to spark ideas from.
Target Audience:
Researchers
Judging Criteria:
- Concepts and ideas presented
- How well you capture the appropriate user flow and present their path through the app
- Overall UI design and layouts
- How well the UX follows modern flows and current best practices
Submissions & Source Files:
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Submit JPG/PNG for your submission files. Make sure you are labeling and numbering your files in the correct order. Example: 01-1FileName.png, 01-2FileName.png, 02FileName.png, etc.
Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop and saved as layered PSD files.
Final Fixes:
As part of the final fixes phase you may be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback. See more information about Final Fixes
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.