CASE STUDY:  MOBILE COMPANION DESIGN
I'm looking to show work in my portfolio as case studies. My priority is to demonstrate my design rationale and process by walking you through the process as opposed to showing the pretty pictures. Plus, the pictures are just not that pretty anyway.

Please let me know what you think and it's okay to be brutally honest!
Thanks,
Nicol
Mobile Companion
HeadSpin helps developers pinpoint the customer experience and application performance issues with real-time visibility
Mobile Companion High Resolution Mocks - v.1
The ProblemI joined HeadSpin during the startup phase. We had a new product allowing developers to experience real-time application performance in different geographical locations. This data would be captured and sent to the HeadSpin platform for analysis and performance recommendations. Performance testing had previously been done via simulation or VPN. The solution involved creating a new companion app replicating the experience on a mobile device, allowing developers to change specific settings on the device, record instances of the session,  send all data back to the dashboard for analysis, change the geographical locations of the device and repeat the process. A minimal UI existed and the requirements lacked clarity and definition, but the expectations from stakeholders were crystal clear; develop a stellar product that would be embraced by the Google development community.
Users & Audience
Since HeadSpin was a Google Ventures startup, the initial users consisted of a forum of Google developers. This highly technical group held very specific ideas of how a performance testing tool should function within their workflow. Furthermore, as heavy Google users, they wanted something that felt familiar to those experiences and seamlessly integrated into their workflow. The intended target audience would be developers using Google Development Tools. We cast a large net with the expectation that we would not only convert but engage a large segment of that audience.  
Team & Role
Having a solid decade of UX Design experience under my belt, I joined HeadSpin as employee #6, the UX Manager and was responsible for creating a product design strategy and all UX design assets (IA, user flows, wireframes, prototypes, visual design, and specs), and follow the process through implementation. I worked closely with the CEO and CTO in order to achieve this goal. I engaged the expertise of the Google Ventures UX Gurus throughout for design input. I also conducted several user interviews with Google developers from our forum.
Design Process
My process always begins with understanding the overall system and any constraints before making decisions. In this case, I needed to understand the dashboard architecture, functionality and how the data points were displayed and consumed in order to inform any design considerations. What decisions could I support with metrics or research from our forum?

Working with the CTO and lead engineer, we prioritized a feature set based on the user stories outlining the pain points with performance testing and workflow captured from developer interviews. From there we agreed on our initial MVP candidate and I started sketching on paper then moved to low-fidelity wireframes using Sketch to iterate quickly through design options. This informed the product strategy direction for the CTO and CEO. 
Interactions Challenges
One of the key interaction challenges was how the data points would be communicated to the web dashboard while a developer is using the mobile companion during a performance testing session. How are the corresponding performance recommendations displayed on the web dashboard? The second key interaction was how to surface the important information in the mobile companion app during a performance testing session with minimal disruption. To achieve this a module was introduced that would run in the foreground of the app being tested only performing key actions while the full app runs in the background.

I created a clickable prototype to demonstrate some of these key interactions for buy-in from our stakeholder group. I also shared this with developers from the forum to validate the design direction.
Visual Design
Once the stakeholder team (CEO, CTO, Lead Engineer and a few users from the forum) agreed on the design direction, I created the high-fidelity mockups following Google’s Material Design framework and worked with an outside company to design icons and help refine the visual design direction. 

In addition, I delivered the corresponding pixel specifications using Zeplin to pass off to the engineering team for implementation. I followed the product through the initial release while continuing to engage our user forum for input. 
Findings
Working for a startup I needed to make quick design decisions based on little information since there were no other competitors in the marketplace. I found information wherever available and learned to leverage my experience as a UX professional and rely on specific training to solve immediate design challenges.

Designing for the developer “persona” proves quite different than designing for other user types. I found that developers tend to have specific ideas in mind for how their tools or products function. Unconsciously, they are constantly thinking of how to improve the user experience; as a result, the information they provide is informed and very specific

At the start of the project, the Mobile Companion was working technology with a minimal UI designed by our CTO. Once the UI was fully designed and additional functionality was added, we saw the user forum engagement increase by over 50%. The number of interactions and time increased significantly because our users were able to experience how the Mobile Companion app was designed to interact with the HeadSpin platform.
↑Back to Top