Insulet — My Omnipod

Building a Self-Service Diabetes Dashboard and Corporate Intranet

01 — Overview

Insulet wanted to create a connected digital experience for Omnipod users managing Type 1 and Type 2 diabetes. The experience needed to let users register their Personal Diabetes Manager, reorder pods, access warranty and recall information, and connect with the broader Podder community.

As the team’s sole UX/UI designer, I helped define and prioritize the experience across the My Omnipod mobile app, the PodderCentral self-service dashboard, and Insulet’s first company intranet.

Role: UX/UI Designer

Responsibilities: Requirements gathering, prioritization, user flows, information architecture, wireframing, prototyping, usability testing, visual design, and stakeholder collaboration

Tools: Adobe XD, Photoshop, Zeplin, InVision, Jira, Salesforce, Hotjar, and Crazy Egg

02 — The Problem

Insulet’s marketing and IT teams were developing a responsive experience that would allow Omnipod users to manage several important tasks in one place. However, the organization did not yet have a unified user experience or a clearly prioritized roadmap.

The project also faced two aggressive deadlines:

• Four months to launch the second iteration of the My Omnipod app.

• Eight months to launch the first version of PodderCentral.

• 
  

I inherited the app’s design work from a previous agency and first needed to audit the available files, identify gaps, and ensure that the transition would not interrupt delivery.

As the only UX/UI designer on the IT team, I also needed to improve collaboration between IT and the product-design team. The product team had already created valuable research artifacts, including personas and empathy maps, but these resources were not yet fully integrated into the digital experience.

03 — The Process

3.1 — Understanding the Users

We divided the audience into two primary groups:

• Prospective users who needed to understand Omnipod and determine whether it was right for them.

• Existing Podders who needed to register devices, reorder pods, manage account information, review warranty or recall details, and access ongoing support.

Separating these audiences helped us determine what information each group needed, what belonged in onboarding, and what additional information could be captured through Salesforce.

3.2 — Requirements and Prioritization

Before moving into design, I worked with stakeholders to clarify requirements and determine which initiatives required immediate attention.

This helped the team focus on the most important user and business needs without jumping prematurely into solutions.

I also reviewed the product team’s personas, empathy maps, and research materials to ensure that existing knowledge informed our decisions.

3.3 — User Flows and Information Architecture

I created separate user flows for prospective and existing users. These flows helped distinguish between acquisition, onboarding, account management, ordering, and ongoing support.

The flows allowed us to identify:

• What information users needed at each stage.

• Which steps could be simplified.

• What information Salesforce already contained.

• Where additional information needed to be collected.

• How users would move between My Omnipod and PodderCentral.

Because the research budget was limited, I conducted a card-sorting study with approximately ten internal participants. The results helped identify patterns in terminology, information grouping, and navigation expectations.

3.4 — Exploration and Design Decisions

Once the flows and information architecture were established, I created wireframes and reviewed them weekly with stakeholders.

Before presenting a design, I worked with Salesforce developers and software architects to confirm its technical feasibility. This ensured that stakeholders were reviewing solutions the development team could realistically deliver.

We used Jira and InVision to collect comments and maintain visibility across teams. Frequent reviews helped us address questions early, reduce uncertainty, and build stakeholder support throughout the process.

3.5 — Prototyping and Testing

I developed interactive prototypes for essential tasks and organized usability tests with internal employees.

Although the project did not have the budget to recruit external participants, the internal sessions still helped us identify usability issues and patterns.

I recorded participants’ interactions and used the findings in weekly presentations to explain proposed changes to the navigation, wireframes, and task flows.

04 — The Solution

The resulting experience brought several essential Omnipod services into a more cohesive digital ecosystem.

My Omnipod App

The updated app supported users in accessing product information and managing important tasks related to their Omnipod experience.

PodderCentral Dashboard

The self-service dashboard enabled existing users to:

• Register their Personal Diabetes Manager.

• Manage pod orders and recurring delivery cycles.

• Review warranty and recall information.

• Access account and device information.

• Connect with the Podder community.

Corporate Intranet

I also led the research and design direction for Insulet’s first corporate intranet, helping establish a clearer internal information structure for employees.

05 — The Impact

The work created a prioritized and technically feasible experience across several connected products.

Key outcomes included:

• Clear user flows for prospective and existing customers.

• A validated navigation structure informed by card sorting.

• Tested wireframes and prototypes for essential user tasks.

• Stronger collaboration between IT, product design, marketing, development, and architecture.

• A more structured review process that supported faster decision-making.

• A self-service experience that reduced fragmentation across registration, ordering, account management, and support.

  
  

06 — Reflection

This project reinforced the importance of creating alignment before creating interfaces.

With several products, teams, and deadlines competing for attention, the greatest value I provided was bringing structure to the work—clarifying priorities, connecting existing research to design decisions, and maintaining close collaboration with technical partners.

Working within limited research resources also required flexibility. By adapting card sorting and usability testing to internal participants, I was still able to gather useful evidence, identify patterns, and improve the experience while keeping the project moving.