TABLE OF CONTENTS
In September we made progress on the next phase of our Dexcom offering moving towards an Institutional Review Board (IRB) study. Our new product development process led by Responsible Individuals started to bear fruit, as we successfully took on more projects at once and made progress across our transition to a membership model and additional value-adds like at home blood kit tests as well as explorations across the the core product guided journey experience and ways we could go deeper using Tags, scoring changes, and social experiences.
In September, we moved forward towards an Institutional Review Board (IRB) study and partnership with Dexcom, which will allow for real time data integration for Levels members. The objective of this study is to develop and analyze a reference data set describing the glycemic patterns among real world users of real-time, unblinded, continuous glucose monitoring. By working with an IRB we will get authorization for first-of-its-kind access to CGM for tens of thousands of study participants and the ability to analyze and publish on this unique dataset. We expect to submit our proposal later this month and begin the study in earnest later in Q4.
Engineering started for our transition to a membership model and are still targeting a November switch over. In the new membership sign up flow, members are prompted to select a subscription option with the option of recurring delivery of CGM sensors (monthly/bimonthly/quarterly). We’ll be adding more value to the membership over time, like at cost blood kit testing.
One of our top objectives is to continue exploring to improve the guided journey with Levels. In September, we focused on targeted member feedback calls for people who did not engage well with the Levels program to learn more about opportunities for improvement. From that effort, a few key areas emerged: onboarding, logging, and daily moments that can serve as touch points to help people unpack what happened and what to do next. We started some early designs for improving the onboarding experience as well as a new Day Review experience. Logging efforts were focused on Tagging.
Building off our experimentation in August, we selected a few variants that showed promise for updating out Metabolic Score. Overall, we learned that the existing score still has value, but that there may be an opportunity to further contextualize the score and deliver it at the right moment. In October, we’ll be testing a version of the score that focuses more on progress than on evoking a feeling of failing or succeeding.
Engineering implementation for our tagging primitive started in September and will continue into October. Tags is the current bet on how we’ll help people understand their food choices more deeply as well as optimize for friction-free data entry. To date, we’ve optimized for a friction-free logging experience, which has meant we haven’t focused on gaining deeper food log details, outside of a photo and text string note. With the introduction of tags, we’re aiming to automatically parse relevant ingredients from people’s food logs (as well as providing a manual tagging option) and then showing insights related to the tag. You can think of our Meal Insights feature as a prototype for our full tagging feature, where we’ll have a new primitive surface on which to weave in social experiences and comparisons for a given food ingredient that has been tagged. For example, if the word “rice” is tagged, you can imagine a landing page that shows how rice affects people differently as well as what the community has found to offer better responses as a food swap.
In progress implementation
In progress implementation
You can see more of our thinking in this Loom from Alan: