KidneyLink360 Platform

Project Scope: Healthcare Web & Mobile Experience

Role: Lead UX Designer

Timeline: Aug 2025 – Sep 2025 (2 Months)

Core Tools: Figma, A/B Testing Data Suites, Responsive Frameworks

Key Impact: Lifted user engagement metrics by 25%

Deliverables: Onboarding Flows, A/B Testing Optimization, Cross-Platform Responsive Layouts, Design Reviews

The Problem

Nephrologists were working with fragmented patient data across multiple sections of the platform. There was no single place to:

• Quickly assess critical patient metrics

• Identify patients needing immediate attention

• Initiate communication with other doctors about specific cases

At the same time, the login experience was outdated and didn’t support more flexible authentication methods like mobile-based access.

Constraints

• 2-month timeline

• No dedicated user research phase

• Existing design system (had to strictly adhere)

• Clinical context (clarity and speed over aesthetics)

So the challenge became:

How do I design something useful and intuitive with limited time and no direct user input?

My Approach

Instead of forcing a textbook UX process, I focused on fast, informed decision-making:

1. Pattern-based research (quick research)

With no time for interviews, I:

• Reviewed existing medical dashboards

• Looked at data-heavy UI patterns

• Focused specifically on:

  • Scanability

  • Information hierarchy

  • Alert visibility

This helped me avoid reinventing patterns in a high-stakes domain.

2. Prioritizing “at-a-glance clarity”

The dashboard wasn’t about exploration—it was about instant understanding.

So I structured the experience around:

• Highlighting critical patient metrics first

• Grouping data into clear categories

• Reducing cognitive load for busy clinicians

3. Designing for action, not just visibility

A key requirement was enabling doctors to:

Communicate with other doctors about specific patients directly from the dashboard

So I made sure:

• Each patient entry supported quick messaging triggers

• Actions were placed close to relevant data

Key Design Decisions

Leveraging the existing design system

Rather than introducing new UI patterns:

• I reused established components for consistency

• Maintained familiar interaction patterns

• Ensured faster development handoff

Icon consistency

For the new dashboard tab:

• I followed the platform’s existing icon style (non-filled)

• This helped the new feature feel native, not bolted on

Mobile number login flow

For the login redesign:

• Introduced mobile number–based authentication

• Simplified access while aligning with modern login expectations

The goal was to reduce friction without overcomplicating security flows.

Exploring multiple directions

Instead of locking into one idea:

• I presented two distinct dashboard concepts

• Each varied in layout and information density

This allowed stakeholders to:

• Compare approaches

• Align on what best matched their mental model

One direction was selected and taken forward into prototyping.

Outcome

• The final prototype was included in a conference presentation by a senior stakeholder (Dr. Mike)

• The design was well received by a clinical audience

• The dashboard concept successfully communicated:

  • Patient prioritization

  • Clear data visualization

  • Integrated communication flow

What I Learned

1. Speed forces clarity

With limited time, I had to:

• Focus only on what truly mattered

• Avoid over-designing or over-researching

2. In some environments, “best practices” beat original ideas

In healthcare UX:

• Familiar patterns are often safer than novel ones

• Clarity and trust matter more than creativity

3. Stakeholder alignment is a design skill

Presenting multiple options helped:

• Drive better conversations

• Reduce back-and-forth

• Build confidence in the final direction

What I’d Do Differently

If given more time, I would:

• Validate assumptions with even lightweight user feedback

• Test data prioritization choices with real clinicians

• Explore edge cases (alerts, overload scenarios, etc.)

Final Takeaway

This project wasn’t about following a perfect UX process—it was about:

Making smart, fast decisions in a constrained, high-impact environment.

It strengthened my ability to:

• Work within real-world limitations

• Design for clarity in complex domains

• Balance stakeholder needs with usability principles