
Pulse
Streamlining the patient profile management experience for doctors in a Healthcare SaaS
Project type
Contract
Project status
🚀 Launched
Impact
👨⚕️ 80% User Adoption
😀 4.5/5 User Satisfaction
Timeline
3 months
Team
Product Manager Josh Lavinsky
Customer Success Yulia Shibanova
Product Designer (Me)
4 Developers
What is Pulse?
A healthcare SaaS for doctors
Pulse Protocol, established in 2015, is a SaaS healthcare company.
Its flagship product, Pulse, serves as a healthcare workspace designed for doctors and coordinators to effectively manage and grow their medical business. Pulse offers service like managing patient treatment status and profiles, scheduling virtual calls, etc.

Problem statement
Doctors are overwhelmed by patient information
Hospital doctors and coordinators face challenges in efficiently tracking patient treatment statuses and profiles.


🤦♂️ The spreadsheet doctors are using to track patient status.
However, Pulse currently lacks a tool for doctors to manage patient information, leading them to rely on external solutions. This poses a risk of decreased user engagement and retention.
Solutions
A kanban board for doctors
Status-Based Organization: Patients are organized by their status.
Easy-to-Archive: Easily archive files for completed statuses.


Drawers for detailed information
Easy Access Drawer: Browse detailed information directly within the page.
Full-Screen Drawer: Ideal for editing and performing more complex actions.



Mobile responsive
Customized Kanban for mobile with easy-to-navigate cards and details.


Impact
🎉 The new platform with patient management feature has been launched!
🎉 User adaption
80%
😄 Users' satisfaction
(20+ surveys)
4.5/5
📒 Users’ feedback

Fabian Salyer
Medical director @Fertilite Center
“The new feature build an efficient communication bridge to provide service to patients...”
If you want more, here are the challenges & solutions↓
Challenge 1
I Need to learn the complex system within 2 weeks
Pulse has a complex system with intricate information hierarchy and various roles. Here's how I did it.
Role play with customer success
I proposed using role-play: I acted as a patient while my colleague played the doctor. This helped me clearly understand the entire process within the product.

Developing JTBD and user journey
To dig down to the root of these problems and potentially solve them, I conducted 5 sessions of user interviews to build this Job-to-be-done and journey map with the team.


Hosting card-sorting workshop
I led a card sorting exercise with the team, classifying the information into three tiers.

Based on the card sorting results, I created a new information architecture for the patient profile to display the parent-child relationships.

Challenge 2
No ideal solutions were found among competitors
Due to the limited information from direct competitors, I had to think out of the box. Here is how I did.
Learning from task management tools






How do I design 3 views to manage patient status?
Inspired by task management software, I designed three views to present Level 1 information.

Option 1: List view

Option 2: Table view

Option 3: Kanban view
Finally, Kanban View was chosen by me!
→ Time constraints on MVP
→ Users' needs: status is the most critical information
→ Analytics: click-through rates for status are the highest
Optimizing Kanban view: color-code stutas
To optimize kanban feature, I explored color coding options to balance a clean interface with an effective way to highlight statuses.

Optimizing Kanban view: encouraging users to archive package
To address the issue of Kanban potentially slowing down, I designed an easy-to-access archive button.

When hovering over the package, display the archive icon along with a tooltip.

I designed an archive feature for users to view or restore items.

Users' feedback
To optimize kanban feature, I explored color coding options to balance a clean interface with an effective way to highlight statuses.
charisliang121@gmail.com · Linkedin · Resume
Website content and deisgn © Charis Liang