When I was asked to update a small set of keyboard shortcuts during a platform redesign, I could have just made the updates and moved on.

Instead, I asked a different question: what would a shortcut system look like — one that could scale with the platform without creating confusion later?

That question changed the scope of the work in the best possible way.

The Problem

Keyboard shortcuts in clinical software aren't just a convenience feature. For pathologists working through dozens of cases a day, they're a efficiency and trust mechanism. Inconsistent shortcuts erode confidence quietly — users stop relying on them, or worse, misfire in high-stakes moments.

Two risks were clear if we just patched the immediate request:

Fragmentation — without a structured approach, shortcuts added feature by feature would become inconsistent over time, building a mental model that was impossible to predict.

Scalability — new features would require rework and user relearning if patterns weren't established now.

The Approach

I proposed a lightweight framework built around four principles:

Logical grouping — modifier patterns (Ctrl + key) organized by action type, so users could build reliable mental models rather than memorizing an arbitrary list.

Ergonomic design — shortcuts designed for left-hand reach, recognizing that most clinical users had a mouse in their right hand. The keyboard was secondary input, so it needed to work that way.

Mnemonic mapping — keys tied to intuitive letters where possible, reducing cognitive load during adoption.

Discoverability — tooltips and menu surfacing recommended so users could learn the system organically over time, rather than needing to hunt for documentation.

The Outcome

Several shortcuts were implemented immediately. Others are queued for future releases — but because the framework exists, those additions will fit cleanly into patterns users have already learned.

The system is invisible when it works. That was the goal.

What This Reinforced

A small request is often an opportunity to build something durable. Taking the time to think one level above the immediate task — from "update these shortcuts" to "design a shortcut system" — meant the work compounded instead of just shipping and moving on.

Strong interaction foundations are only noticed when they're missing.