Event App
Product Background
|
Results/Metrics
- We observed customers using it regularly, including using it for tasks we hadn't anticipated they would use it for (like taking it to the front of the room when asked to read a paragraph from one section).
- We did not observe any particular frustration nor did users express any complaints about the functionality or usability of the app. (However, users often won’t).
Next iteration:
- Encourage customers to rate the app in the app store to ensure a feedback loop.
- Expand the functionality of the app, allowing customers to explore the places of Winona, the campus and the people of the company in a in a more expansive way way.
Process/Methods Used:
- Identified business requirements: app needed to match the brand of the entire event and in many cases would need to match the look/feel of the print booklet. It also needed to encompass some unique aspects of the brand including being welcoming in nature and giving people good introduction to the people with whom they would be interacting.
- Identified user tasks and requirements: we met with the summit event coordinators and walked through the summit booklet and the facilitator guide to pull out any point at which the customers were asked to carry out a task or would need to be able to find something at the conference center on their own.
- Created paper prototype: based on the business requirements and user tasks, we created very simple sketches that contained the functionality and flow of the information as we understood the customer to need.
- Rapid user testing with paper prototypes: we paper-prototype tested with a few internal folks to get a quick read on whether the flow of the elements and the functions were on point.
- Developer/Designer created in DPS: the designer gathered necessary assets from marketing and created the app using DPS (adobe's digital publishing suite).
- Rapid user testing: once we had a working model, we tested it again with internal folks and made a few more adjustments to other functionality that we noticed users expecting.