Qventus app: deliver real-time nudges to patient care team

Right data for the right people at the right time

Please contact me for the password to access project content.


Nov. 2018 - Present
PM and 2 Engineers
Lead Designer / Quasi-PM
Targeted Users
Emergency department (ED) care team
Design Scope
Full design lifecycle (UXR, UX/UI) Design sprint Redesign concept
Improved usability of mobile app, nudge framework and redesign concept

Product suite and mobile app

Qventus is the first system of action, from historic analytical data to predictive recipe, trying to simplify healthcare operations by empowering teams to excel in real time. The solutions include dashboard for root cause analysis, patient board for proactive planning, system operational board for situational awareness, and mobile app to deliver real-time interventions.

Mobile app for the care team in the ED

For most hospitals, the ED is the primary entry point for patients driving up to 70% of hospital admissions. But in this highly dynamic and variable environment, ED are normally overwhelmed with sudden patient influxes, long wait times, patients boarded in hallways and dissatisfied patients walking out.

Qventus mobile app targets at solving ED problems by identify surges, delays, dissatisfied patients and push real time notifications to prompt preparations downstream. It also enables team collaboration across departments and functions to address problems in the same chat thread. Each chat thread is called a nudge quoted Richard Thaler’s behavior science concept.

Engagement problems

Experience goals of the mobile app are to reduce cognitive burden and engage frontline care team. But data tells us another story.

Started from early 2018 Qventus set up the infrastructure to collect usage data and there are tracking funnels through Amplitude. Mobile data showed the usage were dropping continuously to our surprise. After the app was launched at the hospital site, fewer users came back to use the app after a month or so.

To find out the root caues of the usage drop, we started setting up onsite interviews and partnered with customer success team to collect feedback from our users.

Targeted users - ED nurses

Through talking to different ED nurses, we captured their workflows and touchpoints in the persona format. It helps align the whole team on the user empathy and acts as a reference point when we’re talking about user problems.

Below are the two main problems indentified from the user feedback.

Friction while using the app

During the interview, users shared that they’re having trouble logging into the app. Nurses are interacting with different information systems at work, and Qventus required them to remember another set of credentials which is quite challenging.

Second, users got overwhelmed with all the notifications coming in, but no way to clear up the thread or see which one is important. When they got off work, mobile app still buzzed with all notifications which then forced them to log out of the app. Then it circled back to the login problem.

“Now what?”

Another important finding from the interviews is that care teams don’t know what to do with all the notifications received. “I’ve got these alerts, but I don’t know what to do with them”, quoted from a charge nurse. We realized that prompts are not providing enough context or actinable items to solve the problem. Compared with what care team already know, they don't add enough value to their operations. Nudges start losing interests from the care team and thus less engaged users.

Design challenge

How might we reduce the mobile app usage friction and increase value delivered to ED nurses?

Experience goals

- Delightful to engage users, helpful while not intrusive

- Foster collaboration and positive mindset within the care team

- Insightful and automated, push useful data to users rather than pull

Solution framework

I worked closely with two mobile engineers, and also acted as the quasi PM role in the beginning of the project. Through design workshops with the team and key stakeholders, we came up with our mobile roadmap. It’s targeted at delivering incremental improvements, while setting up framework for the long term redesign of mobile app.

Reduce friction

After reviewing customer interview notes with the team, we identified a few key areas to improve the app usability:

1. Difficult login flow with hospital url and credential required

2. Overwhelmed notifications and home feed view

3. Not able to mute notifications even when off shift

4. Among hundreds of messages, which one is important?

Login flow redesign

Current flow requires the user to enter hospital url and then directs them to the login section. As the tracking data shows that more than half of users gave up at the step one of entering URL, it’s a friction point which is removable by binding user email with the domain URL so that it's more efficient to login.

User validation on login redesign

We interviewed current users of mobile app remotely to validate the login flow, and got very positive feedback. Quote from a user, “When can we have this and what do you need me do to make it happen?” The SSO model got a lot of interest from across clients and it’s currently work in progress to generalize the capability to more clients.

Other feature design to reduce friction

Archive: Swiping to archive nudges helps clear up the feed to reduce information overload
Mute: Ability to set mute schedule lets users control notifications when on/off shift
Tagging: Prioritize data feed easily

Results of improved usability

Most of these incremental changes were implemented by two mobile engineers and released to customers within 3 months. The archive feature is well received by end users and usage data indicates a growing number of users interacting with the feature on a daily basis. In addition, as I was making these changes into the product wearing the hat of both designer and PM, my coworkers gave me the “all about outcome” internal reward as a recognition for improving mobile app.

Increase value

Aside from improving usability, how might we augment mobile app to do more than chatting? Below are three areas that mobile team brainstormed together based on input from different stakeholders.

Enable collaboration and decision making

Deliver contextual and actionable data

Transparent outcome and motivated teams

Enriched nudge detail

Kudos for outcome and motivation

Manual nudge to enable collaboration


These sections are in the concept and validated with clients. From interviews, they provided positive feedback and confirmed the use cases where mobile app would serve the value. However due to the mobile team engineering resources, it didn’t make into the development stage.

Design sprint

Outside working on incremental changes to mobile app today, we started the nudge framework project, as the data to action got ranked higher as a company stratigic priority. It would be better to reimagine how nudge could have been done without limits and build the roadmap to deliver the ideal experience step by step.

As the team planned on tackling the challenge, we thought design sprint would be great to help lay down the nudge framework foundation. I proposed to facilitate 5-day design sprint session with the help from another designer and two PMs.

Design sprint goal

How to come up with a nudge framework to enable and motivate care teams to improve healthcare operations?

Special Sprint: Hybrid Research + Design

Different from the standard design sprint, we designed the version of 2-day research plus 3-day sketch/build/test workshops. Because it’s an important project but less urgent project, it’s challenging to run two separate sprints to ask for 10 days’ dedication from th team. Also we conducted the light and hybrid vesion so that everyone is onboard with the pain points directly heard from end users.

Part 1 - Research and Synthesis

Part 2 - Design and Prototype

Outcome: HOOK framework

After one whole week’s workshops, the team came to one single framework to enable care team with a better designed nudge cycle. We also extend Hook Model from Nir Eyal to a sequential system that drives user to change behaviors and form routine habits. This proposal got highly recognized during customer conference, and leadership teams are excited to apply the nudge framework to their daily operations. Though not all the features and redesign make the way into production, it projects a clear and promising roadmap for the nudge framework.

Key takeaways

From coordinating the design sprint, I have learnt a lot about how to run design workshops to solve problems with the team, also the power of diverging and converging along the problem space. It also makes me believe creativity and the best solution comes from joint efforts of the team rather than any individual. I’m truly inspired to continue applying design sprint model to more collaborative design sessions.

Redesign concept

Why I initiated the mobile app redesign is that the current version has limited capabilities to be a core intervention delivery channel. Post the nudge design sprint, we found there are quite a few promising directions for mobile app to evolve towards. My design process composes of four parts: 1) use case analysis, 2) information architecture, 3) wireframe, 4) hi-fi mockups and prototype for validation. After one month of completing these designs, I presented them to different stakeholders to get buy-in so that we could include the redesign in the mobile app roadmap.

Targeted users and core use cases

The four main uses cases for frontline nurses and leadership teams are:

1. Getting alerted on upcoming crowding or problems

2. Check real time census and status while being mobile

3. Prompt to take actions based on contextual information

4. Collaborate with the team about problems/requests

Information architecture


Hi-fi Mockups and Visual Exploration



Redesign concept got a lot of great feedback both internally and externally. One nurse manager commented, "I really like how the app delivers the snapshot of the system status and make it very easy to access patient data.” Our mobile team is planning more extensive user testing sessions to prioritize all the use cases and features so that the team can start building towards the long term vision.