Meeting Scheduler
WEBEX PRODUCTIVITY TOOLS
MY ROLE
Interaction designer
KEY CONTRIBUTION
Identify the issue
Set up the workshop for product strategy discussion
Help PM and ENG envision the impact on user experience
ABOUT PROJECT
Outlook plug in is one of the most important components in WebEx productivity tools. As an inject components in outlook, we had lots of restrictions from time to time which make the products not as stable as we expected.
From the report provided by our user researcher, some of the customers feel really confused about how to start and how to schedule a WebEx meeting with our plug in.
I talked with my program manager set up a workshop with stakeholders to explore the revolution concepts on scheduling.
DESIGN CHALLENGE
01. Scaleable solution
We were envision to have a revolution concept which can scaled to multiple calendars including but not limited within Microsoft outlook.
02. Consistent experience across center
WebEx productivity tools supported the scheduling of meeting center, event center and training center. It's quite debatable if we need to have a consistent scheduling experience for different center when we are pursuing a more independent scheduling experience.
UNDERSTAND THE JOURNEY
I volunteered to set up the workshop and worked with our user researcher to record every steps and actions we took as an example of the user journey for scheduling.
There are way more things to do besides sending out the invitation for scheduling this events. The interesting thing is we always wrote our critical user journey from the moment user started an appointment in outlook, which is not literate wrong but way more details might missing.
DESIGN SPRINT
I set up a two day design sprint with our stakeholders including program manager, software engineers and some designers who are working for scheduling in Cisco.
The goal of first day is discussing all barriers we are facing as a plug in for outlook. In the meantime, collecting the user pain points and technique boundaries.
In second day, I presented some ideas we can exploring based on first day's discussion and worked with the team to quick iterated on the concepts.
LESSONS LEARNED
After this design sprint, we got every one on the same page for the future of scheduling. Even not all ideas in this design sprint were able to be delivered as a part of product, this exercises helped to build the relationship among cross functional teams and evaluated the solutions from varies dimensions.
As a designer, we sometimes pursuing the fancy design, but it always good to have some realistic advices from other teams.
SOLUTIONS
Here is the takeaway from the design sprint and became a part of components eventually.
