As the lead and only designer for this project, I:

Crafted the interaction design while adhering to the GoToMeeting website visual design style.
Created a clickable prototype used for 5 rounds of in-person user testing.
Coordinated with the user research team to assist with, observe, and learn from the user testing.
Collaborated closely with the Marketing team to ensure all requirements were met.

Simplifying the Information Architecture

I worked closely with the Marketing team to understand the website requirements. Initially there was a big push to not only use the same look and feel as the newly redesigned Collaboration Suite website, but also to use the same information architecture.

While the use of the same visual style absolutely made sense to me, I felt that the information architecture wasn't suited for GoToMyPC prospects. The Collaboration Suite website elegantly showcased the GoToMeeting, GoToWebinar and GoToTraining products. The initial proposal from the Marketing team was to take that template and translate it into the three GoToMyPC versions a customer could purchase: Personal, Pro and Corporate. Like each product on the Collaboration Suite, each GoToMyPC version would have it's own set of pages describing how it works and the available feature set.

This seemed like overkill to me, so I investigated further. My user researcher highlighted a trend from previous rounds of GoToMyPC user interviews: customers were not aware of the various GoToMyPC products - it was always viewed as one product. Further discussions with Customer Care representatives confirmed this sentiment.

With this user data, I pitched a streamled version of the information architecture to the marketing team. One product would be showcased instead of three, better fitting into the user's mental model and reducing the number of pages in the project by 25%. The Marketing team approved.

Page Savings. By redesigning the information architecture to better reflect the user's mental model, the team would reduce the total number of pages by 25%. — **Page Savings**. By redesigning the information architecture to better reflect the user's mental model, the team would reduce the total number of pages by 25%.

Wireframes. I created initial wireframes reflecting the agreed upon information architecture. It served as a great design communication tool for the team, especially when discussing content strategy. — **Wireframes**. I created initial wireframes reflecting the agreed upon information architecture. It served as a great design communication tool for the team, especially when discussing content strategy.

Usability Testing

After we decided upon all the page content, I transitioned into high fidelity designs in a clickable prototype. With this prototype, we completed five rounds of usability testing for the website redesign. After each session, the team would convene, discuss what was observed, and finalize on updates based on the findings. For each round of testing, I created a simple HTML click-through prototype for the first usability test and continued to update it for the subsequent sessions.