Challenge Summary

Welcome to "Living Progress - CrowdAnalytics - Application Wireframes Challenge". In this challenge, we are looking for your help to create the best possible app UX for analyzing civic input in crowdsourced ideation, commenting, and analyze unstructured data in an efficient manner. In this Living Progress challenge we are looking for you to explore a new project and team collaboration site for the Crowd Analytics APP.

We will focus on two different user flows for this wireframe challenge. Starting with a new user, we will explore a landing page that provides an overview of Crowd Analytics and onboards the new user by getting them prepared to start launching projects and using Crowd Analytics. 

From this initial landing page we will transition our new user into an experienced user of Crowd Analytics who is managing multiple projects and teams from their personalized dashboard. From their dashboard, users should be able to at a glance have a high level understanding of the projects that they are currently working on with Crowd Analytics as well as collaborate with associated team members on a project level. 

In addition to the initial landing page/ dashboard, this wireframe challenge will explore what a project detail page looks like, offering the user a deeper view of a project and the data sets associated within a project. Users will be able to view messages and notifications associated with a project from team members.

Round 1

Initial Submission for client review
01. Overview/ Onboarding/ Landing screen:
02. User Home Screen
03. Creating New Project Screen
04. Project Details Screen
05. Data Set Detail Screen
06. Categorize Screen

Round 2

All requirements as stated in challenge details with client feedback applied
01. Overview/ Onboarding/ Landing screen:
02. User Home Screen
03. Creating New Project Screen
04. Project Details Screen
05. Data Set Detail Screen
06. Categorize Screen
07. About Crowd Analytics Screen
08. Team Section Screen
09. Messages/ Notifications Screen
10. Contact Screen
11. Press/ News Screen
Background information
Governments across the world are increasingly applying open government practices such as crowdsourcing to develop stronger policies and to engage citizens, providing access to civic influencing beyond election cycle. When hundreds of ideas from citizens flow in, the crowdsourcers are facing a problem: Lack of efficient analysis and synthesis tools.

By using HPE big data analysis tools for natural language processing and machine learning, "Civic CrowdAnalytics" tools automates the analysis and synthesis of crowdsourced civic input. Citizens input will be used more efficiently in crowdsourced policymaking, when governments and NGOs have a reliable and efficient analysis tool for to use. Thousands of ideas will be refined very efficiently to an executive summary and compelling visualizations.

"Civic CrowdAnalytics" application will solve the problem, and thus we will take steps towards a more participatory, inclusive and transparent democratic society, making sure that every citizen has an equal opportunity to get their voices heard.

Challenge Goals 
- Develop a collaborative data analytics tool that allows users to import analyze and collaborate on data projects.
- Create a tool that provides transparency to data analytics by showing the parameters that are used in the analysis, and the data will be public too. Therefore potential data manipulation can be detected more easily.
- Develop a web application which allows users to search and analyze crowdsourced civic ideas and comments for public policies

Focus Area :
Civic participation, Governance, Participatory democracy, Policymaking, Data analysis, Education.

Key Features:
Must Have Features
- Categorizing data by identifying keywords
- Categorizing data by identifying semantic entities
- Categorizing data by detecting relationships in expressions
- Analyzing data by detecting sentiments (positive/negative)
- Identifying patterns and outliers in the data

Nice to Have Features
- API integration with output sharing apps such as SlideShare and storing apps like Dropbox and Box
- More advanced data analytics features, e.g. analytics recommendations, in the line of: "Try adding these variables to analysis", giving users, agency to work with analytics

Use Cases :
- Use Case 1: As a city staff member, I want to analyze a crowdsourced dataset and produce a report about the civic input from the last two weeks;
- Use Case 2: As a city staff member, I want to import the data in an csv format from crowdsourcing platform.
- Use Case 3:  As a city staff member, I want to choose parameters with which to analyze the data. The parameters include: idea categories, frequency of occurrence of ideas, and the sentiment of feedback (positive/negative) in comments.
- Use Case 4:  As a city staff member, I want to see the breakdown of the analysis in a simple summarized format. The summary tells me e.g. the number of ideas in each category (the categories can be for instance: public transit, private transit, infrastructure), idea clusters that are closely related to each other, and the sentiment (positive/negative) about the ideas.
- System Use Case: Content categorization will be done by using content and entity extraction through HPE Haven OnDemand APIs. Starting with supervised machine learning, the algorithms will be trained to fit to datasets in civic crowdsourcing. When the analysis reaches a good reliability level, the analysis proceeds to unsupervised machine learning, based on the patterns detected in the first step. The data analysis will be powered by HPE Vertica and IDOL, ensuring the scalability of the analysis and stellar visual outputs. It also enables integrations with other analysis tools such as R, which can be useful in the data analysis.
- System Use Case: System will analyze and display association relationships between words in the crowd-sourced entries.

Design and Features Consideration
- The UI/UX will be intuitive and easy to use so that the primary user groups – representatives in non-profit organizations and staff members in government – can use it without specific technological skills
- The tool provides a simple user-interface for submitting crowdsourced unstructured data for analysis
- The user-interface provides options for parameters that define the object of analysis in the data set.
- The user can, for instance, choose to analyze the frequency of recurring ideas for innovations in public transit, and the sentiments of the following comments
- As a result, the user will see a breakdown of the most common ideas, and the public’s reaction to those ideas.

Screen Flow
The following screens only for recommendations, if you have a better concepts that will provide better solution for our goals, please feel free to create it.

Primary Screens:
01. Overview/ Onboarding/ Landing screen
- Consider what a new user experience is like for a first time visitor to this site. This initial landing page should serve as a one page overview/ onboarding experience that familiarizes the user with what Crowd Analytics can do as well as how the user can start creating projects and assigning team members to start working with Crowd Analytics. 
- Consider this example of the type of landing page we are looking to design for. 
- This will be more of a "Welcome" page introducing a user to Crowd Analytics and providing an overview as to what Crowd Analytics does and how a user can get started with projects using Crowd Analytics. Consider having areas for screenshots of Crowd Analytics, feature descriptions, benefits, and reasons why a user would use Crowd Analytics.
- Perhaps consider showing a "getting started" guide that walks a user thru creating a project and getting started with Crowd Analytics.
- Other items to consider would be any new features or updates for Crowd Analytics that could be updated on this overview landing page
- Review the background information on Crowd Analytics and provide some concepts on how to display this page for a new user and consider how to guide the user along in starting a project and using Crowd Analytics.
- Should show and explain the different types of data visualization offered in the Crowd Analytics site. ( Categorization, Common Entities, Heat Map, Sentiment Analysis, Cluster Map, Associations, Tables, Category Drill Downs)

02. User Home Screen
- Once a user has a good understanding of what they can do with Crowd Analytics and has started projects and has assigned team members, the default view for the return user will be a personalized palette containing quick links to their projects, data sets, artifacts, and team collaboration from working with Crowd Analytics. We would like to see 2 different states of this User Home Page. 

Version 1:
- Consider what this dashboard would look like for a first time user who DOES NOT have any projects running with Crowd Analytics. Show a version of the User Home Page with a tile, button, or other call to action that would get the new user to start a new project and add it to their palette. See "Creating a New Project Screen" requirement below for form field details. 

Version 2:
- The other view we want to explore for this page is for a user who has a number of projects underway with Crowd Analytics and their palette should focus mainly on access to the projects. It should be a Home Page interface containing list of projects, team members, notifications, messages, and associated data sets.

Other items to consider for the Home Page experience design:
- Ability to add a new project.  
- News and updates stream.
- Notifications and messages.
- A Project list with high level details about the project
-- A project has metadata: The name of the project, the start and end-date, etc.
-- Team members on the project
-- Data Sets/ associated artifacts

03. Creating New Project Screen
- From the project section on the dashboard a user has the ability to create a new project. This will launch a flow where a user will fill out a form with the following information for creating a project within Crowd Analytics.
- Here are the necessary fields for add a new project:
Project
-- Name
-- Description
-- Project owner
-- Start date (date picker)

- Upon new project creation, user will be asked to choose a data set up upload to the project
Input File Definition 
-- After uploading a data set, the users will need to define the format and field types in the file.
-- For example, the data type (String, Numeric) of each field.  
-- Also the users should define whether a particular column is text to be analyzed/categorized or whether the input is a category or something else...an ID or other numeric value for example.
-- User's need to designate whether a file is test or training data set as well.

04. Project Details Screen
- After selecting a project to view from the dashboard or defining the fields in your first data set, the user will be taken to a Project Details page. 
- This will serve as a landing page for a project that will contain a list of data sets associated for the project, the data set artifacts (analysis documents, visualizations, groupings, and other assets created within Crowd Analytics) team members, and messages, notifications for the project level. 
- There are several actions that they can choose each of which are associated with a particular data file.  Users cannot perform these actions if they haven't defined metadata for the input files.  The actions are:
-- Enter metadata (takes user to Data Set Detail page)
-- Categorize 
-- Concepts 
-- Sentiment Analysis 
-- Association Analysis

- Clicking on one of the actions above create a subdirectory under the project which takes the name of the data file followed by the Action Name.  Each of the actions generates reports/output files which will be contained in the folders.  A sample name for one of these subfolders might be "Palo Alto Data Set - Analyze Sentiments".
- Projects folders and subfolders may be shared between users.

- The project details page should also support the following functions:
-- Ability to edit/ rename/ and delete data sets.
-- Ability to add a new data set (a data set is just a file)
---- Adding a new data set would prompt the user to upload a new data set

- Artifacts such as reports and visualizations will be generated as users execute the various analysis functions.  The app should record basic details about the files generated:
-- File Name
-- Date Created
-- Created By
-- Description

- The commenting feature for data set artifacts is important to show in your design concepts. Consider how to facilitate a collaboration on these data set artifacts. A rich commenting and collaboration UI is desired here.

- The flow for adding a new user/member:
-- Invite by entering in an email address

05. Data Set Detail Screen
- Each data set should have an interface with following information:
-- Filename
-- Date Created
-- Created by
-- Description
-- Folder
-- File Type (xlsx, csv)
-- Classification Data Set Type:  Test or Training Data

- Also Data Set detail should allow users to define metadata about the file contents. Users will need to designate the data type of each field.  Also the field list should define whether a particular column is text to be analyzed/categorized or whether the input is a category. Or whether the field contains some other kind of data an id, numeric value, or a qualitative value.
- It would be a nice feature to be able display some sample values for each of the category fields.  Maybe there is a dropdown or something that lets you show the complete list.

06. Categorize Screen
WF Reference Page 5
- If user choose the "Categorize" menu, they will be redirected to this page
- User will be able to define the category that they wany to use. System will provides existing category that already available in the system.
- User can create new category if they can't find the correct category for their dataset
- If user found the correct category, they can choose examples of civic data that they can analyze
- User will be able to export their current action to CSV or PDF or send via email.

Action Results -- Each of the Actions above defined in the Project Detail screen is going to result in some kind of analysis from the system behind the scenes.  Users should be able to navigate to the web pages hosting the following content.  At the same time, we should provide excel, csv, and pdf documents in the folders associated with each file.  (Or users can download the content into the folders)  Please provide examples of the following reports and visualizations.  Let’s focus on the web versions of these pages for now.

Categorize Choose Result
WF Reference Page 6
- Once user select the category and examples, they will be asked about what kind the end result that they want to see.
- There are several selection for the end result, and they are:
-- Categories as Cluster
-- Categories as heat map
-- Associations
-- Categories in Spreadsheet
-- Category Drill-down
- User will be able to export their current action to CSV or PDF or send via email.

Categorize Heatmap - this html page can be created dynamically after a user clicks Categorize.
WF Reference Page 7
- If user choose "Categories as heat", they will be redirected to this page.
- User can see specific details about the category in heatmap visualization
- Specific keywords, data, parameters will be shown according their popularity in heatmap.
- Focus on presenting how the heatmap should be shown in this page. how to presented the dataset, where you need to put the heatmap label, etc
- User will be able to export their current action to CSV or PDF or send via email.

Categorize Drill-Down
WF Reference Page 8
- If user choose "Categories Drill-Down", they will be redirected to this page.
- User can see specific details about the category in drill down mode.
- Show civic data information from general ones into specific details (category --> result number --> frequent words --> categorized feedback --> etc)
- User will be able to export their current action to CSV or PDF or send via email.

Association Analysis
WF Reference Page 9
- If user chooses "Association Analysis", they will be redirected to this page.
- User can search for words/dataset associations on specific category from this screen.
- Once user put the keyword, the result will be shown in table like shown in the references document.
- User will be able to export their current action to CSV or PDF or send via email.

Sentiment Analysis
WF Reference Page 10
- If user choose the "Sentiment Analysis" menu item, they will be redirected to this page
- In this screen, user will be able to view comparison data of each dataset in graph mode.
- User will be able to export their current action to CSV or PDF or send via email.

Secondary Screens:
07. About Crowd Analytics Screen

- An overview of the Crowd Analytics app and purpose
- Could be similar to the landing page

08. Team Section Screen
- Intro to the Crowd Analytics team
- Team photos and bios

09. Messages/ Notifications Screen
- This will cover messages, activity, and notifications that are linked to a project level.
 
10. Contact Screen
- This section will provide users with general contact information to engage with Crowd Analytics support team

11. Press/ News Screen
- Press and news content articles and updates.

Learn Axure:
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/learn

Screen Size
Create it as Desktop version : 1280px width with height adjusting accordingly. 

Documentation :
- Wireframes18_chad_2016_06_01 copyTA.pdf
- Sample Data.docx
- Sample Mood Board to inspire you

Target Audience
There are two primary user group that will use this applications:
- Policy makers involved in open policy making (civil servants, government and city staff members, politicians (elected representatives), NGOs using crowdsourcing)
- Citizens who want to analyze the crowd's input in a policy process they are interested in.

Judging Criteria
- Overall User Experience
- Completeness and accuracy of the wireframe as defined in the challenge spec
- How well your wireframes provide a consistent user flow.
- How well your wireframe captures all the functionality.
- Any suggestions, interactions and user flows you recommend (provide any notes or comments for the client).

Submission & 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
All requested contest requirements as clickable HTML files generated by Axure.  All the content must be listed and the pages are linked together to show page flow.

Source Files
- Wireframes should be built in Axure. The resulting source files used to generate the clickable HTML files.
- All the content must be listed and the pages are linked together to show page flow.
- All fully editable original source files of the submitted wireframe as required by the contest under "Source Files" in the sidebar should be included in your Source zip file.

Final Fixes:
As part of the final fixes phase, you may be asked to modify content or user click paths.

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.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • HTML
  • RP file created with Axure

You must include all source files with your submission.

Submission limit

Unlimited

ID: 30054475