Case study summary
PERS - Personal emergency response system
TYPE
Concept project
METHOD
Business analysis, Competitive analysis, Interviews and surveys Affinity mapping, Journey map, Feature prioritisation matrix, wireframing, prototyping
TEAM
3 team member
DURATION
2- week design sprint
TOOLS
Pen & paper, Figma, Miro
MY ROLE
UX designer
Continuous and improved interaction creates a close and harmonious relationship with customers.
Summary
Where we started
Introducing a minimum viable product (MVP) that could solve interaction/communication issues between the service and the subscribers.
The hypothesis
Based on the design studio sessions, we decided to build the interface of our current design, which has the feature of tracking the patients in real-time. It also sends regular updates and reminders through app, and not calls as it takes lot of manpower.
Conducting research
After doing users interviews and affinity mapping, we discovered the following insights: -
-
Subscribers want peace of mind by getting regular updates.
-
They want to be aware of every step during an emergency to reduce anxiety.
Proposed solution
Our proposed solution was to first improve on the regaulr interaction with existing subscribers. Also, a hybrid mobile app, for convience and regular updates . It also, helps with their online presence among the competitors.
The problem
The company was doing just to the point of what industry they were in. They were responding to the user’s call during an emergency, and that’s where their service ends.
Next steps
We also had to keep the feasibility and viability aspects of the implementation of the proposed solution.
Prototype
Reflection
Create win-win scenario
Keep in mind the feasibility and viability from the business side when designing for users.
Build Archetypes, not personas.
Don’t worry about age, demography, and location but focus on the user’s goal, behaviour, needs, and motivations.
You are not the user
Try to keep your bias at bay. You are not making the changes to satisfy your ideas.