Key Information

Register
Submit
The challenge is finished.

Challenge Summary

Welcome to the "48HR - NWL Efficient Meetings Mobile App Design Direction Challenge". This is a new type of challenge for Topcoder Design. The goal of this challenge is to quickly create some additional design direction and inputs for a follow up UI design challenge in the NWL Efficient Meetings project. We are looking for you to look over the requirements and proposed features and put together high-level information and visual direction that will become input into the UI challenge.

This is a fast 48hr challenge, so make sure you are using your time wisely. Welcome to this exciting new Topcoder Design challenge type and please don't hesitate to ask any questions in the forum.
The new Design Direction challenge is meant to serve as a precursor to a regular UI design challenge or series of challenges. You can think of this as a "FAST Wireframe Challenge", however we are not necessarily looking for full fledged wireframes. We are looking for additional visual assets and resources that can become inputs into the following design challenge(s). These items could include, but are not limited to: user flow diagrams, sitemaps, quick wireframes of specific or potentially complex screens, UX research and best practices documentation, and user profiles. We are intentionally leaving things a bit broad as we want you to analyze the high-level concept and requirements of the application or project, and prose and produce what assets and inputs would be the most useful for the UI designers.

Efficient Meetings Mobile App - Overview
The NWL (Northumbrian Water) Efficient Meetings mobile app is a scheduling application for meetings that allows the users to see recommendations on what is the most efficient meeting location or meeting type. The goal is to minimize travel and CO2 emissions that come with that.

The app will pull/push data from/to the user's regular calendar app (Outlook). This data will allow the user to see what meetings they already have scheduled, but also allow them to schedule new meetings, directly within the Efficient Meetings app.

While the user is inputting a meeting, the app will use a range of parameters to determine the effectiveness of each meeting, and recommend efficiencies to the meeting organiser/ creator. The user should also be able to see the recommended efficiencies for an already scheduled meeting.

Efficient Meetings Mobile App - Required Features
- We are not highlighting specific screens, as we are looking for your ideas and how you approach the problem. The below requirements MUST be incorporated into your design somehow. Remember to think about and design great mobile user flows and UX.
- Determine if a meeting is at the optimum location – e.g. if the majority of attendees have to travel to a particular meeting location, the app should recommend a more appropriate location or a different meeting type (Skype / Video conference).
- The presentation materials (physical, digital or none) can determine the meeting type: live, video (GoToMeeting,etc.) or audio (Skype,etc.). For example a physical material would have to be presented in a live meeting or a digital would need a video or live meeting and the application should consider this.
- If there are known external conditions (e.g. bad weather or heavy traffic) affecting travel to a meeting then the app should recommend the user leaving early. This could be through a push notification or another alert type.
- Use of analytics to highlight specific recommendations. For example, 60% of meetings at this location are cancelled, perhaps you would like to use a different location?
- Reporting on key metrics such as the carbon footprint, travel time, and overall cost of meetings.
- The cost of meetings would also include actual expenses for the meeting invitees to join. These costs could include gas, train ticket, highway tolls, bus fare, etc. The application would already know where each invitee is located/ traveling from.
- Show how the recommended efficiencies would help reduce the carbon footprint, travel time, and overall cost of meetings.
- Reporting screen/ section. See overall stats for the week, month, year, etc. A data or stats dashboard. We are open to additional reporting features/ data that would be useful for the user(s).
- A static advice & guidance page. (e.g. how can I make my meetings more efficient).

Efficient Meetings Mobile App - Target Device
We are targeting for a Mobile Application:
- Mobile: 750px by 1334px (Height can expand as needed)

Efficient Meetings Mobile App - Target User
- Usable by all internal employees to obtain recommendations.
- Heads of teams/ departments may be more interested in the reporting aspects of the solution.

Deliverable Examples
I think it's important to outline what we are NOT looking for in this challenge. We are not looking for:
- UI Designs
- Full wireframes of every feature, screen, and user flow

What we are looking for:
Note: it is not required that you create all of these assets, these are just examples of the types of assets that we are expecting to see:

User Flow/ Process Diagrams
https://d2slcw3kip6qmk.cloudfront.net/marketing/blog/2017Q1/SSOFlowLoginandSignup.png
https://d2slcw3kip6qmk.cloudfront.net/marketing/blog/2017Q1/UserJourneyFlowTutorial2.png

Sitemap



http://www.uxforthemasses.com/wp-content/uploads/2014/08/Sitemap-example-3.jpg
http://www.uxforthemasses.com/wp-content/uploads/2014/08/Sitemap-example-1.jpg

Rough Wireframes of individual complex screens or user flows
https://jianilu.files.wordpress.com/2013/01/wireframes_revised5.jpg

Experience Map
http://www.uxforthemasses.com/wp-content/uploads/2014/08/Example-experience-map-2.jpg
http://www.uxforthemasses.com/wp-content/uploads/2014/08/Example-experience-map-3.jpg

User Personas
http://www.uxforthemasses.com/wp-content/uploads/2014/08/Example-persona-3.jpg

Customer Journey Maps
http://www.servicedesigntools.org/sites/default/files/res_images/02.jpg
http://adaptivepath.org/site/uploads/2013/04/ap_exploratorium_journeymap_11.png

Mind Maps
https://cdn-images-1.medium.com/max/1200/1*Sk0z1s-u9cVx5eU6rdDHkQ.png

Deliverable Formats
We want to make this challenge easy and fast, therefore we are not setting strict requirements on the format of the deliverables you produce. We are open to whatever format makes sense:
- PDFs
- JPGs
- Axure files
- MarvelApp link
- Etc.

Judging Criteria
- Your submission will be judged on the following criteria:
- Execution of your deliverables
- Usefulness of the deliverables as it relates to the requirements and UI challenge
- Thoughtfulness of the deliverables
 
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72 dpi and place a screenshot of your submission within it.
 
Source Files
All source files of all graphics and deliverables.
 
Final Fixes
As part of the final fixes phase, you may be asked to modify your deliverables.

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.

Stock Photography

Stock photography is not allowed in this challenge. All submitted elements must be designed solely by you. See this page for more details.

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:

  • RP file created with Axure
  • Sketch
  • PDF
  • JPG
  • Any Format

You must include all source files with your submission.

SUBMISSION LIMIT:

Unlimited

SHARE:

ID: 30066886