Physician Daily Dashboard

CONTEXT

Clinicians need to orient to their next patient.
Where are they? Who are they? and Why are they being seen?

A full day means many patients moving through waiting rooms, exam rooms, and care-team hand-offs, all at once.
Task Organizer is the shared record of where every one of those patients stands, moment to moment.
It ships as two views: a list for fast scanning across a full patient day, and a day view built on the calendar model clinicians already know.
The list view carried nearly all of the hard design problems; the day view inherited the same decisions with far fewer complications.

CLARITY

The demo worked because it broke its own rules.

The inherited design demoed well and won approval, but it only handled the happy path. It broke its own system's rules to get there.
Before bringing in users or stakeholders, I audited it directly against Redwood's guidelines and accessibility standards, so the case for change would rest on measurable violations, not opinion.
Built to spec and stress-tested under real clinic flows, three failures surfaced: a status badge below minimum touch target size, a location field with no accessible affordance, and a row height that kept expanding once select inputs were added correctly.

RESEARCH - INTERACTION

Three small problems.
The row would not behave.

Status was a badge. It needed to be interactive and was too small to meet minimum touch target requirements.
Location was a text string, there was no accessible affordance to indicate it was actionable.
Adding select inputs doubled the default row height.
I built the expanding row to full Redwood spec to measure exactly how far it would grow. It was worse than the original design implied, and that number became the case for replacing it entirely.

RESEARCH - ACCESSIBILITY

The fix wasn’t this list.
It was every Redwood list.

Keyboard users couldn't tab into list rows and couldn't reach actions within them once they did.
The root cause wasn't this screen. It was how Redwood's multi-column lists were structured.
Proposed restructuring lists as grids with each data point as its own column.
Row and column headers visually hidden but announced to screen readers.
Accepted for development as the keyboard navigation standard across all Redwood lists.

ARCHITECTURE - STRUCTURE

Rebuilt to hold everything the demo couldn’t

The expanding row failed.
- Could not predict the height of AI-generated text.
- Accessibility complexity remained in the expanded state.
Proposed a side panel instead. It provided a predictable space for any amount of content.
That same shift also made the keyboard navigation grid proposal workable: actions now live in a focusable region instead of stacked inside one cell.
Blue as "checked in" lost meaning at scale. When most patients were checked in, the entire board turned blue.
Reclaimed blue for selection only, consistent with other views in Redwood.

FIDELITY - CRAFT

The redesign had to pass the same bar it once broke.

Status shown as a colored text label with a left bar, replacing the badge that couldn't meet touch target size and resolving the color conflict with Redwood's system wide selection state.
Side panel built to match Redwood's own component library, not custom styled.
Blue restored to its single meaning across every view: selection, not status.
Every pattern here audited against the same standards that flagged the original design, so this version passes on its own terms.

ALIGNMENT

Two different teams, two different executives, one proposal.

Led the cross-team alignment between the Oracle Health product team and the Redwood Design System team, building toward proposal presentations for the VPs of both groups.

RDS Executives Oracle Health Executives Clinical SMEs Accessibility SMEs RDS Engineering

Redwood component reviews

Accessibility gaps in the existing component.

The Redwood component the inherited design relied on had its own accessibility issues, separate from the color and badge conflicts the design introduced.

CROSS TEAM PROPOSAL

VP-level alignment across Oracle Health and Redwood

Presented the redesigned status pattern, the selection-color fix, and the accessibility findings to leadership on both sides.

ACCESSIBILITY ROADMAP

Proposal accepted, phased implementation.

The accessibility proposal was accepted with strong support from the Redwood team, with full implementation scheduled for a later phase.

TWEAK - ITERATE

Not just redesigned. Proven.

Original demo. The happy path design that looked good and broke under real constraints.
Diagnosed and annotated. Every accessibility and interaction failure mapped against Redwood standards.
Final redesign. Side panel, reclaimed color, validated with users and stakeholders at every stage.

Let's talk about your
next big idea.

I'm currently open to new design leadership roles. Whether you're building something ambitious or improving what you already have, I'd love to connect.

Get in touch

Clinicians need to orient to their next patient.Where are they? Who are they? and Why are they being seen?