Innovation Roadmap


Photo by Slidebean on Unsplash

Timeline: Summer ‘20 Design Sprint 

Type: Industry Challenge 

Team Roadmap:  Stacey Chin, Sophia Dominguez, Aaron Sun, and David Yi Yang

Mentors: Karen Yeung (Dexcom), Lars Mueller, and Heidi Rataj


Dexcom offers a variety of options for a user to share and analyze glucose data. Dexcom asked this team to develop a roadmap for a new application to support access to glucose data. The students identified and ranked key features, developed prototypes for multiple platforms, and presented them as a product roadmap.

The team began with a competitive analysis to identify common features and implementations. They included solutions from the OpenSource community and identified critical opportunities to differentiate a Dexcom solution. Armed with this understanding the students interviewed users of these existing systems as well as prospective users of the new application. All information from these interviews were summarized in:

  • Two personas
  • Value proposition canvas
  • Storyboard
  • Journey Map

After the first 5 weeks, insights and first sketches of the application were presented to over 30 Dexcom stakeholders.

In this project, the collaboration with Dexcom was especially close.

Students presented weekly to Dexcom’s UX design, product management, marketing, and human factors. They also discussed the feasibility of ideas with developers for different platforms. 

Ideation and Prototype

In the remaining five weeks, the students started to focus on creating a roadmap for this product. They selected features with the highest priority to design a minimum viable product and created a flowchart to discuss the app structure with stakeholders. After confirmation from Dexcom, they quickly designed prototypes and started to iterate. All insights were captured in a rainbow sheet. 

Students had to understand the new prototype in the context of existing Dexcom offerings. They discussed with the product management and human factors team how the app can be deployed, how users will be onboarded and how potential errors will be handled across applications.

“I can’t stop looking at it like I expect to see a number there. I think it can make watching your numbers in your face without feeling overwhelmed by it.”

Finally, the team conducted a Kano Model survey to gauge interest in further features. Together with qualitative insights, they were able to present a clear roadmap and tested an MVP prototype after 10 weeks of intense work.