An Easier Way to Check In

Kaiser Permanente
2023

Role

UX Lead — UX Research, Interaction Design, Visual Design, User Flows, Rapid Prototyping

Team

  • Laura Beckford, Product Manager
  • Jean-Paul Cozzatti, Product Manager
  • Sreedhar Vinnamuri, Tech Lead
  • Eric Frye - UX Researcher
  • Rosemary Birkholz, UX Writer

Timeline & Status

8 Weeks – Rolled out Q2.2023

Overview

After learning that a portion of members were finding it difficult to successfully check in to their appointments upon arrival using the active SMS check in feature. Our team was tasked with learning about and addressing the friction areas within the check in experience.

I led the end-to-end experience design direction and introduced the 1 tap arrival feature which enabled members to complete check-in directly through their KP App.

The pilot was met with outstanding member sentiment reaching an immediate 40% adoption rate and pulling in a surveyed Net Promoter Score of 80.

Why It’s important

On-site administrative personnel are spread thin. By empowering members to complete check-in and arrival registration digitally, we can enhance their efficiency, enabling them to focus on higher-value tasks. This not only optimizes our staff's performance but also streamlines the on-site experience for our members by allowing them to concentrate on the primary purpose of their visit.

An illustration that show the different stages of the project against a Kanban.

Design Principles and Approach

As we navigated the complexities of improving the check-in experience, I anchored our design decisions on three North Star principles.

Product Excellence:

Overdeliver on user expectations with design.

Proactive Feedback:

Anticipate and communicate progress and errors.

Optimize for Clarity:

Clear, informative, and concise instructions.
Flow analysis
A screenshot that shows a flow chart with notes throughout
Affinity clustering
A screenshot, of stickynotes with member feedback. These were used to create a heatmap of key problem areas

Getting a baseline for the end to end flow

Before talking to members we first wanted to create a baseline understanding of the end to end journey. To do this I set up a workshop with key stakeholders where we mapped out the user flow of the experience. We used Miro sticky notes to document resources, questions, functionality insights.

Looking to our members

I conducted 5 user interviews to uncover what the member point of view was when using the available check in systems. Aside from moderating, I also planned and wrote our interview guideline document which explored the end-to-end experience of the participants with the check in systems.

Interview takeaways

  • Members didn’t fully trust the system to work due to system crashes.
  • Having to opt into SMS every time was time consuming and a hassle.
  • There was worry that replying to the SMS message wasn’t going to notify the care team, due to past experiences where they didn’t receive an acknowledgement for their check in action.
  • The process of checking in with a human was reassuring because they could take the time to ask questions like how to get to the waiting room.

The Problem

Members lack trust in the SMS check-in system because of system crashes, uncertainties about check-in acknowledgment, and an inefficient and cumbersome opt-in process.
Lightning demos
A picture of ideas sketches.

Collaborating on design & technical solutions:

It was clear that we needed to work with our engineering team to address the underlying problems causing the technical hiccups.

“We can plan out, design and deliver the perfect experience, but if it doesn’t work, well it doesn’t work…”

Eight minds are better than one

I brought in all the key stakeholders into a 2-hour workshop where we could all voice our ideas on what we could do to improve the overall check-in experience. The goal was to review our problem statement and ideate solutions that we could further explore.

  • We sketched out our ideas.
  • Explained our concepts.
  • Anonymously voted based on feasibility and impact.

Narrowing our focus

Given our current knowledge and the ideas that we brainstormed, we opted to split the work between two teams.

One team concentrated on addressing the bugs to establish a new baseline for task-flow completion and SMS opt-in. Meanwhile, our team pursued a concept I introduced, which would allow us to utilize the application's interface for on-site check-ins.

The Idea

How might we implement a primary check-in mechanism within the app that offers users context, direction, and feedback during their check-in process? By encouraging more users to utilize an in-app check-in feature, we can enhance the user experience through enriched context. Additionally, shifting away from SMS notifications in favor of in-app push notifications could result in operational cost savings, as the latter is more cost-effective.
A picture of the base user flow of the experience that we improved upon
Current flow
Updated flow
A picture of an improved userflow.
an image containing user interfaces that are grey scaled to communicate that these were rough ideas.

Preparing for testing

Based on the ideation workshop insights, I rapidly prototyped a low fidelity task-flow to put in-front of our members, while simultaneously working with our UX Researcher Eric Fry to create a testing plan.

What we tested:

Introduced cashed data within the SMS opt in task flow to reduce the steps needed to opt in.

Updated the location of the express check in entry point within the app and introduced a default check-in method within the app that’s able to provide context, direction and feedback on their check in action.

Questions we wanted answered

  • Do participants have trouble understanding how to use the I’m Here feature?
  • Confirm whether participants can access their QR code if needed?
  • Can participants easily and confidently access the new check in entry point?
  • Is the content easy and clear to read and understand?
  • Do user expect to see anything that we may have missed?

What we learned

  • All 5 successfully found and understood how to use the new check in entry-point.
  • All 5 participants understood how to use the I’m here feature.
  • 3 of the 5 participants had trouble understanding how to access their QR code.

What they said

  • “I prefer this layout versus what I see today” - P2
  • P2.“The button is infinitely easier.” - P5
  • P5“I like that It tells me exactly where to go and the checkmark makes it clear that it was successful.” - P3

Making it perfect

Usability testing taught us that our concept was something that users would find useful. But there was still the case for addressing the friction points that we observed & aligning our design approach so that the feature would fit perfectly within the the broader complex ecosystem. To mention a few here are some design considerations that I thought about when refining our experience designs.

User Feedback & KPI’s

Address user feedback, ensuring easy access to the other check in methods is crucial. Establishing metrics to measure feature success, for roll out.

Design System & Accessibility

Refining check-in stages and ensuring intuitive feedback during each state, while also considering possible error states.

Interaction & Error Handling

Ensuring post-testing designs are consistent with the cross-functional design system and ADA requirements.

Challenges and learnings

During this project, I faced a significant setback when our product manager left halfway through. It was unexpected, but I saw it as an opportunity to learn about the role. I stepped up, learned quickly, and made sure our team kept moving forward.

The next challenge was collaborating with different teams since we were analyzing the entire user journey, this involved many experience groups. To ensure success, I emphasized open communication and ensured regular feedback to make sure everyone was on the same page.

If time wasn’t a constraint

Based on our research, we knew that facilities typically have a TV screen or monitor in the waiting room that displays patients' wait times. I suggested pulling in that data to display on the 'completed' state of the appointment details page. However, we didn't explore this idea further because it was identified early on that the technical challenges would be significant.