lauramlive

Requirements Gathering

First, a colleague and I created a flowchart to better understand the business requirements. This served as a effective communication piece to identify and discuss potential user experience pitfalls, the most important one being that GoToMeeting Free and GoToMeeting would continue to exist as separate products, with separate accounts and technology bases, while co-existing within the same app.

Wireframes + Design Direction Validation

Based on this user flow, a colleague and I developed lightweight wireframes to finalize the design approach and understand technical feasibility. Even though we could not adjust the product direction to combine these separate products into one offering, we proposed a couple updates that would help users transition:

• First-time download screens. This is something we and the product team had considered for a while, but had yet to implement.   
• Simplification of out of session experience. Currently the "Join" tab displays meeting scraped from a user's mobile calendar and "Host" allows users to log in and start or schedule their own meetings. GoToMeeting users found this confusing - why would their own meetings display in both places, since meetings they host naturally appear in their calendar?

As a team, we decided to postpone out of session simplification until a future iteration; this allowed us designers more time to validate the idea. 

Click or tap through the prototype below to view the lightweight wireframe used for team discussion and user validation. 

User Validation

Once wireframes were complete, I conducted a round of user testing via usertesting.com to validate the direction. From the session we learned the following:

• Overall, users performed well on the main tasks, which included: joining a GoToMeeting free session; muting & unmuting themselves; viewing who else is in the meeting; leaving the meeting.
• Some users weren't sure if the indicator for how many others are in the meeting included them or not. 

We resolved the indicator issue with the implementation of webcams: when a user was not displaying their webcam, a simple silhouette would appear as a digital representation of the user. The number of webcams served as a indicator as to how many others were in the meeting.

Final Designs

I moved forward with crafting high fidelity designs that adhered to platform conventions (navigation schemes, some iconography, typography) while staying true to Citrix visual and interaction guidelines (color palette, tone of voice). I worked closely with the development teams (developers, quality assurance engineers, content editor and the product owner) to implement the final designs.

Feel free to click or tap through the prototype below to view main screens from the effort.