Tommy Wong

Our students are busy adults having to balance work, school, and their personal lives. Many students are eager to utilize time as they commute to work, are in waiting rooms, or out running errands to maximize their learning. We call these transition periods, “micro-moments.” How do we utilize micro-moments to help students effectively learn?

Pick a learning objective and design a learning activity around a specific micro-moment.

You will design an app to collect tickets from conference attendees.

• Attendees can be regular (paying) attendees, volunteers, or presenters.
• Conferences can be anywhere in the world, so organizers frequently use hotel staff or hire temps locally. Because of this, ticket collection is done through an app that can be installed on any IOS or Android phone.
• These people have limited knowledge of the event and are not expected to answer questions about it. They can direct people with questions to an information booth (out of scope).
• Lines can get long. The organizer's goal is to move people through the line as quickly as possible.
• There can be multiple entrances and/or lines with different users collecting tickets at each one.

Log In

Users must log in with a pre-assigned user name and password (managing these is out of scope).

Selecting a Conference

The system could contain hundreds of conferences, even ones scheduled for a year or two out.

Users work one conference at a time. Give them a way to select the right conference. To be sure they have the right one, they need to know the conference name, location and dates.

The system should keep that selection until the user exits that conference or closes the app. (In other words, they do not want to select a conference per attendee).

Attendees

Attendees must have their tickets scanned before entering the conference for the first time. (You can assume that they then receive a badge or other form of ID that lets them enter and leave without scanning for the remainder of the conference.)

Each attendee has their own ticket (no family / company / group tickets). The system will record the scan and log a success.

Anyone attending for free (e.g., volunteers and presenters) will still have a ticket. The system will record the scan and log a success.

Anyone whose ticket has an outstanding balance will be rejected. The system will log the scan as a Payment Due failure. When this happens, the user will route the attendee to a payment booth. After paying they can scan the same ticket again. The payment process itself is outside the scope of this system, but it will remove the outstanding balance so the second scan succeeds.

Anyone whose ticket has already been scanned will be rejected and logged as a duplicate. What happens next is up to the user and out of scope (e.g., ask for ID and let them through if it matches the name on the ticket). A key goal is to prevent people from getting into conferences without paying.

Anyone without a ticket will be routed to a payment booth to buy one or get a reprint. The system will not record this event. When payment is complete, they will return to the line and have their new ticket scanned. Exactly what happens is outside the scope of this system.

Monitoring

Users must be able to monitor the overall ticket collection process.

• Users collecting tickets need to know when they are done and can move on to other tasks
• Event managers might want to delay something until everyone is in the door

The following are key metrics:

• Total attendees. This number can change with last-minute registrations and cancellations.
• Total tickets collected for the entire conference. Not just current user. Changes as tickets are collected.
• Outstanding Payment Due errors for the entire conference. Not just current user. Incremented when Payment Due error occurs, decremented when payment is made.
• Total tickets not yet collected for the entire conference.

History

Users must be able to see a history of all scans of any status for the current conference, showing:

• Attendee Name
• Status (limited to these types)
  • Success
  • Payment due
  • Duplicate (e.g., someone trying to use the same ticket twice).
• Time scanned
• User who scanned the ticket

Scan UI and Interaction

Users collect tickets by using their phone's camera to scan a barcode printed on the ticket.

Show the UI and interaction for the scan. Design something that will work on IOS or Android. Do not create separate wireframes for each platform. The bar code might not be readable (camera not focused, mangled ticket).

If the bar code is readable, it must clearly indicate that the ticket is good (paid in full + not already used), or that a problem exists and identify the problem. Regardless of outcome, the app must show the attendee's name in case the user wants to ask for ID.

This process must be very fast and clear because there could be hundreds of people waiting.

Design a landing page for an upcoming tour of Utah, by the President of the University of Utah.

Information:

The newly selected president of the University of Utah, Ruth Watkins is going to be embarking on a statewide tour of Utah. She will be meeting with community members, students, families, and potential students. The name of this trip will be "Ruth 66". The branding will have a Route 66 theme. Ruth will be making 66 stops throughout the state of Utah (communities, colleges, universities, schools, points of interest, etc.). The target audience for this site will be future students and their parents.

Requirements:

• Main landing page, to include at a minimum Ruth's schedule (attached, use as much or as little as you feel is necessary) and any visual assets.
• A user registration page
• Any other pages you deem necessary

Digital and social are also areas where consumers are increasingly moving toward to seek inspiration, connect and purchase.

As the technology and the marketplace change, we believe there is a specific consumer that is more inclined to be active in social and digital. And these are the consumers we believe will push the business and brand in the future. In addition, our ideal consumer desires to live a “healthy aware” lifestyle; they understand the importance of health, are willing to take steps toward becoming healthier and at some point, believe that supplementation will allow them to achieve their goals.

Overall, a company challenge is to help enable our distributors to acquire these kinds of new consumers. We know these people can choose from a variety of different retailers, online, physical, other MLMs, specialty, to fulfill their health supplement needs – our competition is vast. To compete, our experiences and tools need to be refreshed to meet a minimum expectation.

A specific pain point in our business is our shop experience; it’s distributor-focused, but needs to be focused on our new target consumer. We believe it should express our brand, educate on product/tech and help guide unfamiliar consumers toward the right product. Our request is to research our current shop experience and select a feature, page or flow (or introduce something new) to iterate on to better serve the goals of improved brand representation, better product guidance or better education.