Key Information

Register
Submit
The challenge is finished.

Challenge Overview

CHALLENGE OBJECTIVES
Welcome to the "Interactive Experience (iX) Studio - Usability Audit Challenge"! In this challenge, we are looking for you to identify UX issues within the provided application. There is no design needed for this challenge. All you need in order to participate is to understand the existing flow, have good attention to detail, and bring your usability knowledge and research.

Note: The challenge prizes are mentioned for the top 3 placement prizes. In addition to that extra prize money of $5 will be awarded to every valid usability bug after client/review board feedback.

  • Design Prototype to be reviewed
  • Usability Testing

ABOUT THE APPLICATION
Interactive Experience Studio (iX Studio) is a web tool that will help transform traditional content such as images, videos, Standard Operating Procedures (SOP's) into data models using machine learning and computer vision (Object Recognition) technology.

The XR journey starts with identifying the equipment and its standard operating procedures (SOP's), troubleshooting details, and maintenance procedures. Most of the time this data may not be ready for solution consumption directly. As a solution provider, the Wipro team will interact with the equipment expert and the content creators (graphic designers/3D designers) to collect the available information and create pictures/videos as the physical equipment is available. Most of these users are not XR experts; hence the iX Studio is an essential tool for equipment experts/trainers to follow step-by-step workflow-based IDE to on-board the content, annotate, train, and create procedures, test and publish the content to field technicians and trainees.

The following journey explains the activities of each user and how it impacts them by simplifying the process, yet deliver quality XR experience:

Interactive Experiene (iX) Studio Appliation Competitors:
You can see what others are doing in this space, more info in the public domain:

Youtube video: 
https://youtu.be/rmXxGO-nEgA

Training based on CAD Data: 
https://cdn2.hubspot.net/hubfs/4276273/ReFlekt_July2018%20Theme/PDF/Product-Card_RF-ONE_.pdf

PROBLEM STATEMENT
The current design is a logical integration of the features and flows.

We are looking for possible areas of improving the present design, where it can be more intuitive, where the tasks can be performed with zero or minimal prior knowledge/interventions.
Please consider multi role-based user scenarios. Since the flows are non-linear, different users come to the application to perform specific role-specific tasks that are also interdependent.
We seek new ideas that improve the usability and the experiences from the current design or challenge the status quo and ask for a revamp of the existing design. 

WHAT TO TEST (SCOPE)

  • You will be testing the image prototype
  • Accepted types of bugs: Usability, UX
  • Content Bugs are OUT OF SCOPE [Spelling and Grammar, Text spacing issues inside a paragraph, Missing/Broken Images/Videos inside an article, Font mismatch, Broken links on news articles, blog posts, products details pages, FAQ, Privacy, Terms and Conditions and articles.]
  • Broken Link issues will not affect the core functionality of the application is likely to be REJECTED.


01 Usability Audit

  • Analyze and list out any Usability issues you see within the flow or on individual pages.
  • Think about bringing in smart and intuitive user experience
  • We are looking for your UX knowledge, research, and suggestions on best UX practices
  • Provide recommendations on improving the user flow for the application


Include the below for each of the UX issues that you find:

  • Title of the Problem
  • Description of the problem
  • How to solve the problem?
  • Any research to support your recommendation
  • Any screenshots or sketches
  • We have options to add a label, based on the type of issue or enhancement - label it accordingly.


Please see below on how to log the UX bugs.

02 User Flow Diagram

  • In addition to finding the UX bugs, we would also like you to submit a flow diagram of the entire flow/ include any  and add any explanation about the flow you have suggested
  • You are free to use any tool to create this or even sketch the flow with a pen & paper
  • Submit this as a png, jpg or word doc or ppt or excel etc file and upload it along with the txt file (please see final deliverables below)

~
HOW TO CREATE A NEW BUG REPORT?


ISSUE REPORTING GUIDELINES

  • Before you log your issue, ensure that there is no similar issue already logged. You can do a quick keyword search, and only when you are sure that there is no other ticket logged for the same issue, create one.
  • Issues must be clearly described.
  • Video/screenshots in your issue description will help tremendously.
  • If an issue is not properly documented, we may reject it and it will not count.
  • If you submit an issue that is seen in multiple screens as multiple issues, they will only count as one defect. Others will be marked as duplicate.
  • Only create issues during the submission phase. After that, any issue logged will not count.
  • We will mark an issue as accepted, rejected, or duplicate either during the submission phase or after.
  • The first participant to find an issue gets the credit - duplicate issues will not be counted.


ADDITIONAL RULES

  • Follow the standard Topcoder Bug Hunt Rules (if any conflict, please ask in the forum)
  • If you do not properly document your bug reports, they will likely be rejected due to a lack of information or documentation. If you submit the same bug in multiple areas/pages, (for instance, the Same validation issue of a form can be found in different pages/sections) you will likely get credit for the original bug report only. The others will all be closed as duplicates.
  • Please don’t make adjustments or change labels of existing issues logged by other competitors.
  • DON'T RE-OPEN the issues closed by the reviewer and anyone who RE-OPENS a ticket will be disqualified from the challenge.
  • DON'T EDIT OR ATTACH FILES to the issues once it has been submitted and anyone who is doing this will be disqualified from the challenge.
  • You must not edit the bug report once created, so make sure you enter all the details at the time you create the issue, otherwise, your issue will be moved to the end of the queue. If you really need to edit an issue you must use the comments section for this (i.e. add a comment to describe any changes you want to make to the issue), and we'll decide whether the changes are major enough to move the issue to the end of the queue.


ISSUE WEIGHT AND SCORING

  • Scoring will be based on the number of bugs by severity. Be sure to correctly attach a severity to your bug.
  • The management team has the right to change an issue category, priority, and severity at their discretion.
  • Only verified issues by challenger/reviewer and accepted by client/review board will be counted - (valid on hold bugs are considered as accepted for final standings). All duplicate & rejected issues will be closed with a penalty and not counted.
  • Log issues according to the guidelines above. Issues that do not follow these guidelines may be rejected due to a lack of information.
  • For challenge scoring, the user with the most verified issues/points will be selected as the winner. If two users submit the same issue, the user that submitted the issue first will receive credit.
  • For any suggestions or improvements, please create separate issues
  • The following points will be awarded as per issue category:
    • Functional Issues: 2 Points
    • User Interface Issues: 2 Points
    • Usability/UX/Suggestion/Improvements: 5 Points
  • The placement points will be calculated after receiving client/review board feedback with accepted bugs only - (valid on hold bugs are considered as accepted for final standings). The client/review board rejected bugs like Duplicate bugs will receive 5 Points penalty per bug whereas, by design, not a bug, no repro and any other bugs will receive no penalty.
  • The 1st and 2nd place submissions must collect at least the client/review board accepted 10 points and total client/review board accepted bugs worth 40 points.
  • The 3rd place submission must collect at least the client/review board accepted 5 points and total client/review board accepted bugs worth 25 points.
  • In case, no participants qualify for the placement prizes as per the above rule, then one winner will be selected who have scored the highest points after reviewers accepted bugs worth 40 points.
  • For challenge scoring, the user with the maximum points will be selected as the winner.
  • If two users have the same points, then the user that submitted the client/review board accepted bug first will receive credit for a higher position.
  • Duplicate/Rejected Bugs Reporting: If you log/report any duplicate bug during the review phase and after client/review board review feedback, then you will receive a penalty of 5 Points per duplicate bug regardless of Bug-type. If you log/report any bug without the required information (insufficient info on bugs or missing repro steps or missing screenshot or missing video, etc.), then you will receive a penalty of 5 Points per rejected bug regardless of Bug-type.
  • There will be no appeals phase. The decision of PM/Copilot for validity and severity of each filled issue will be final.

REFERENCES
- https://medium.com/swlh/what-are-usability-issues-do-they-matter-99bbc62214c0
- https://www.smashingmagazine.com/2018/02/comprehensive-guide-user-experience-design/
- https://www.clockwork.com/news/what-problems-are-we-solving-with-ux-design/
- https://www.webdesignerdepot.com/2018/05/7-ux-principles-for-creating-a-great-website/

AUDIENCE
Industry Users:

  • Equipment Expert
  • Implementer (XR Content Creator from Service Provider or trained in house content creators)
  • Field Technician
  • Remote Expert
  • Trainer
  • Trainee
  • Bio Meds
  • In-house practitioner/assistant


Administrative users:

  • Super Admin
  • Admin
  • Publisher


Final Submission Guidelines

FINAL DELIVERABLES
Submit all your bugs directly to GitLab. When you are done with your submissions please submit a .txt file using the “Submit” button here on the topcoder challenge details page before the submission phase ends. In this file include:

  • Copies of all issues that you submitted (just links should be fine)
  • User-flow (png, jpg or word doc, ppt, excel, etc)
  • topcoder handle (The one displayed in the top right corner near the Profile picture)
  • ���GitLab handle used to raise the issues. (Login to Gitlab and click on the Profile picture > Your Profile. Check the URL https://gitlab.com/[Your Username]

���ALL THE SUBMISSIONS WITHOUT ABOVE INFORMATION WILL BE REJECTED AND WON’T BE PAID.
- IMPORTANT: Submit the above details before the Submission Phase ends. If you can't submit due to technical difficulties within the Submission Phase please email your submission with the above details to support@topcoder.com.
- Participants who haven't submitted will not be paid.
- DON'T use any other link to create new issues OR submit as a document, they won't count and won't be paid.

ELIGIBLE EVENTS:

2021 Topcoder(R) Open

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30144968