David Pierce | Design Portfolio
site icon

Designing for Digital Therapies

ROLE: Design Lead & Interaction Designer

INDUSTRY: Healthcare

DATE: 2019

NOTE: The UI in the project has been updated to obfuscate the client's identity.

An example screen from the project

Context

A major pharmaceutical company hired IA Collaborative to design a first-of-its-kind digital prescription that required a lengthy FDA approval process. We joined the project after another design firm had done significant work on the product.

As the project matured, I shifted from acting as an individual contributor to leading the design team made up of two other interaction designers, two graphic designers, and a content strategist. Our team:

  • Performed UX audits on existing design work.
  • Changed the UX direction for the flagship product based on the needs of our target users—people new to managing aspects of their health with an app—so that it would be a more directed experience.
  • Developed a design system that was flexible enough to use across a suite of products, fit within their brand guidelines, and felt less clinical than other products in their portfolio.

Working as a Player-Coach

At the beginning of the project, I worked alongside another interaction designer to identify UX pitfalls in the inherited design and make improvements ahead of a round of human factors testing.

Based on our work, the client expanded our scope. The team grew, and my responsibilities grew along with it. I took on the role of player-coach—managing the day-to-day relationship with client stakeholders, coordinating timelines across work streams, and coaching less experienced designers in product design fundamentals.

An org chart
Over the course of the project, my role shifted from being an individual contributor (left) to leading the design team (right) and managing day-to-day project operations.

The other designers did not have as much experience with complex digital products, so in the first months of the project we focused our design reviews on establishing good product design practices.

We covered topics like:

  • Establishing product design principles to guide our work
  • Designing for accessibility and can taking advantage of iOS's accessibility features
  • And working alongside developers

Principle Guided Design

Working with our client partners, we established product design principles based on the target users. Our principles included:

  • Make It Accessible - People living with diabetes often suffer from visual impairments.
  • Give Each Screen a Purpose - We were targeting users who did not have experience managing their disease with an app.
  • Explain What's Happening - Build trust by providing helper text and explaining what will happen after they take action.
  • Let the User Take Control - Ultimately, the users know their bodies the best. Let them make the final decision about what they need to do.

The principles helped our team align on decisions more quickly, communicate more concisely, and—perhaps most significantly—gave our client partners a framework for providing constructive feedback, moving beyond personal likes and dislikes.

An example of the before and after of the designs
An example of our product design principles applied. The design we inherited (left) looked approachable but confused users. Our design (right) focused each screen on a discrete task, exposed input options, and added helper content to reassure novice users.

Communicating Design to Client Leaders

Perhaps the project's biggest challenge was communicating design decisions to a team of stakeholders who were experts in their fields but unfamiliar with design. We ran in-person workshops every other month that focused on making big product decisions, reporting out research, and co-creation activities for establishing personas and user journeys.

We invited our stakeholders to join us for remote design reviews every other week. The reviews helped familiarize them with the design process and expand their design vocabulary by discussing work before it was complete. We created a casual environment to discuss design tradeoffs, dive into the reasoning behind an opinion without feeling confrontational, and leave space for the team to try alternate solutions rather than designing by committee.

An example of a UX flow document
Product decisions often got derailed by discussions around details on individual screens. We switched from using polished prototypes to black and white user flows so that our clients could get a complete picture of a feature, digest UX reasoning asynchronously, and avoid distractions from in-progress brand work.
A photo of a design workshop
We ran in-person workshops every other month that focused on making big product decisions, reporting out research, and co-creation activities for establishing personas and user journeys.

Outcomes

Preparing to submit a product for FDA approval is a lengthy process. I left IA Collaborative before the client submitted the product for review. The quality of work and client trust I helped establish led to several contract extensions and a long-term relationship.

✌️ 2025