MY ROLE : Lead Designer Design Manager
DESIGN TEAM : 2 Visual Designers 3 Interaction Designers
PROJECT DURATION :24 months
STAKEHOLDERS : EVP / GM Product Managers Industrial DesignersMarketing Developers
As part of the Unified Collaboration Technology Group inside of Cisco, my role was to manage all things design with the entire portfolio of desktop endpoints. During my tenure, we shifted from being a product-led group to a design-led group. The first project led by design was the Cisco Desk Hub. The problem statement presented to the design team by Product Management was "the current deskphone commands too much real estate for the value it brings" Our goal was to design an endpoint based on experiences instead of features and our mission was to research how our users needs have evolved over time and to figure out what product solutions could best fill those needs. The current deskphone at the time (below) relied on a corded handset, hardkeys, and softkeys all while being a completely standalone unit.
Our customers consisted of universties, government offices, militaries, hospitals, financial institutions and Fortune 500/100 companies from around the world, also...our deskphone sits on the desk of the President of the United States. For the desk hub, we wanted to research customers who primarily used video calling as one of the requirements was to support 4K video calling for this device.
The design team partnered closely with PM's to conduct customer interviews, surveys and related industry research. We gathered incredible insights and learned that our customers had very different and unique needs. We gave a readout of our findings to the design team and product management team and identified the top 4 opportunites to support in our new solution.
I represented the design team and partnered with a core group of talented individuals to lead the charge of what this product was to become. Our group was initially one Designer, one Product Manager, three Software Engineers and one Hardware Engineer. I shared the findings from our interviews, surveys and on-site visits and together we ran through the list of captured use cases challenging each other to come up with brilliant solutions. We used mind mapping and various other brainstorming exercises to ideate solutions and proposals.
The experiences we were solving for had several constraints. The hardware solution had to be price sensitive, take up a small footprint and be modular enough to accomodate our various use cases. We drew 100's of product sketches on the whiteboard, similar to the one below. This shows an example of how we could leverage a users mobile device to function as the main screen for our device. This idea was ultimately abandoned because we needed to operate a complexity of functions that we just couldnt accomplish with a few hardware buttons. We knew the device needed to have a built in screen. We also knew the device was going to competing for attention with a laptop, a mobile device and likely an external monitor. Ultimately we realized this device was going to live at arms length from the user, not be front and center and would need to have an extremely simple "just-in-time" interface.
We locked ourselves in a room and brainstormed daily how we could solve alot of our interaction collisions with the laptop, mobile, Webex, headsets and hybrid deployments. I took these design challenges back to the design team to get started on solutioning and worked with the engineers to figure out how we could quickly test our concepts. We needed a show stopper demo to our stakeholders showcasing the power and flexibiltiy of the device and how it seemlessly interacted with headsets, laptops, monitors and mobile devices. We quickly started ordering whatever hardware we could get our hands on to start assembling a prototype. I worked very closely with the software engineers and the design team to make sure we were not just moving fast enough but putting together some killer experiences.
I created a first pass of wireframes to cover primary use cases: incoming call, outgoing call (call history), join webex meeting in progress and view meetings for today. We used those screens to guage what size the touch targets should be for primary and secondary targets. We also conducted several in-house feedback sessions with stakeholders, not only to get feedback but to share the progress. At the same time, we were building out use cases for the integrated headset we were designing and starting to build out that prototype to work in harmony with the hub prototype - it was all starting to take shape.
After we had consolidated the feeback from our testing sessions, we were ready to test the next set of use cases: signing in and reserving the desk by placing your mobile phone on the wireless charger, transferring a call from your mobile to the hub and from the hub to the mobile, and how you can register the device to both cloud and on-premise in a hybrid configuration. The hybrid deployment offered the best calling features with all of the benefits of Webex from the cloud.
For testing, we hooked up the device in a small room, connected to a external monitor, and asked folks to go in, reserve the desk, check their meetings, join a webex meeting, then sign out of the device by simply lifting their phone from the dock (signout prompt). This test session told us we were really on to something, we were ready to demo to the SVP/GM so that he could start positiioning us for an upcoming tradeshow and to help align deliverables with the Webex team.
Now that we have traction on our primary use cases, it was time to start prototyping and testing the remaining use cases. How do we leverage the laptop and an external 4k camera. This was a modular system afterall and since we were designing both the hardware and the software, we could really nail down the experience. In fail fast fashion, we started with off the shelf components to quickly test assumptions about our solutions. Through various testing sessions, we realized people were confused on what to talk into and where the remote participants audio was coming from. We then designed an interface to allow the user to choose the mic of choice and the speaker output of choice between all of their devices. This was largely due to the fact the a lot of external monitors do not have built in speakers. Once we were able to intergrate with the audio on multiple devices, we wanted to deeply integrate with the Webex client on the laptop. Now...the user can simply answer an incoming call from their laptop, which will route to the hub and offload the intensive processing required for encoding/decoding audio video.
The first customer shipment included an interface that very much aligned with our exsiting phones and design system. Shortly after launch the Webex team released an all new branding effort, updating their design system and visuals for each platform. The interface on the phone was updated to align with Webex visuals and was marketed and branded as a Webex device.