My Role
Product Designer
Business Analyst
UX Researcher
Team
2 Clients
5 Developers
1 Product Designer
Timeline
1 year
Product
Momentum: Nursing Competency Tracker Application
Tools
Figma
JIRA
Confluence
Platform
Web
Impact
3000+
No. of users
120+
Paper saved per user
37%
Task completion time
41%
Design-dev handoff time
What was the problem?
When I joined the team, Momentum was nothing more than an idea. Amid leadership changes, I found myself wearing many hats - gathering all stakeholder requirements, analyzing business and user needs, designing the user experience — flying solo. What I quickly uncovered was a systemic problem: the entire nurse competency tracking process was paper-based.
Challenge
Every 6 - 8 months, new nurses (trainees / orientees) are hired. They have to go through a training process where they are assigned orientation plan, skill assessments and addendums.
-
Lost documents and inconsistent records
-
Delays in onboarding and competency evaluations
-
Nurses losing track of their own progress
-
Managers struggling to retain evidence
-
Loss of employees
Opportunity
-
Digitize the entire process
-
Hospital provides desktops - build a web application
-
Defining responsibilities and features according to roles and hierarchy
-
Smooth onboarding process
-
Transparent evaluations
-
Analytics of progress
My Process
Understanding the Ecosystem: Mapping roles and needs
With over 3000 nurses across 12 hospitals relying on this future product, I needed to design not just for functionality — but for scale and trust.
I met with nurses to understand : Who does what? Who signs on what? What does success look like to each role?
From this, I defined three major user roles
Nurse Orientee
New nurses who must be evaluated on a different competencies and skills.
Nurse Preceptor
Mentors who guide, observe, and approve competencies
Nurse Leader
Administrators overseeing onboarding, assigning competencies, and creating documents.
Each persona needed a unique dashboard, with role-specific features, permissions, and workflows. I created a user flow diagram that mapped the hierarchy and responsibilities to avoid overlaps and ensure data integrity.
Requirements to Reality: Gathering, Prioritizing & Designing Features
After multiple requirement-gathering sessions, these core needs emerged
Role based sign-offs
Each role signs off with initials, time, and date but views and permissions differ.
Template management
Leaders create/edit/publish/archive competency templates.
Controlled Onboarding
Only nurse leaders can onboard new users.
Progress Control
Ability to pause/stop progress of orientees.
Progress visibility
Color-coded visual progress status visible to all roles and dashboards.
In-App Messaging
Internal communication for important updates.
Design & Development Process
I began by sketching low-fidelity wireframes in Figma, followed by high-fidelity wireframes, prototypes and design system. These designs were:
-
Continuously reviewed (bi-weekly) by stakeholders
-
Iterated based on direct feedback from nurses using real-life scenarios
-
Prioritized based on feasibility and urgency
Going Live: QA, Training, and Launch
I ran QA tests, caught and logged bugs on JIRA
Facilitated training sessions for new developers and team members
We ran a pilot with real users, ironed out the final bugs, and got ready to ship.
Reflections
This project wasn’t just about design. It demanded strategy, leadership, cross-functional collaboration, and empathy. I wasn’t just designing screens — I was translating fragmented, chaotic workflows into a product that empowers nurses, improves hospital operations, and ultimately impacts patient care.
If you are a recruiter or hiring manager, please find the password on my resume