LinearCraft6 min read

Building for the hands before the mouse

Single letter shortcuts, a command palette, and no spinners.

The surface: Moving through the issue list, creating an issue, and changing its status, priority and assignee without touching the trackpad.
What the user wants: I want to file and triage a pile of issues quickly, without a tool that makes me hunt through menus for every field.

The command palette

Cmd+K opens a fuzzy search over commands, and the palette shows the keyboard shortcut for each command next to its name.

Recognition over recall, with a teaching loop

A palette works for the beginner because they can search in plain words instead of memorising anything. Printing the shortcut beside every entry turns each use into a lesson. The novice path and the expert path are the same path, so nobody has to decide when to graduate.

Single letter shortcuts on a selection

With an issue selected, one key opens the relevant picker: a key for assignee, another for status, another for priority and another for labels.

Modeless selection then verb

Select an object, then press a key that names the property. The grammar is consistent enough that a user guesses correctly at properties they have never edited. Shortcuts stop being a list to memorise and become a pattern to apply.

The picker that opens

Each shortcut opens a small searchable list at the cursor rather than a modal dialog, and typing filters it. Enter commits and escape cancels.

Keep the hands in place

A modal dialog moves attention to the centre of the screen and usually demands a mouse to dismiss. A cursor-anchored list preserves the user's visual context and their hand position. The same enter and escape contract everywhere means the exit is never a thing to think about.

Instant state change

Changing a field updates the interface immediately and syncs in the background. The list does not block with a spinner while the server confirms.

Optimistic UI and perceived latency

Responses under roughly a tenth of a second feel like direct manipulation, and anything slower feels like operating a machine at a distance. Applying the change locally first keeps triage at the speed of thought. The cost is that the product must handle the rare failed write honestly rather than silently.

Constrained fields

Statuses, priorities and cycles come from small fixed sets that an admin can adjust but not explode into arbitrary custom workflows.

Constraint as a feature

Keyboard speed depends on a small enough option space that one keystroke plus two letters lands on the right value. An unbounded schema would break the shortcut grammar. Linear is trading configurability for speed on purpose, and every keyboard-first tool has to make that trade.

The shortcut overlay

Pressing the question mark key brings up a categorised list of shortcuts over the current screen.

Help at the point of need

Documentation in another tab is documentation nobody reads. An overlay summoned by one key answers the question inside the moment it was asked and disappears without a navigation. It also signals that there is a shortcut for the thing you are about to do slowly.

How the slow way teaches the fast one

Nobody reads the shortcut list. What works is showing the shortcut at the exact moment somebody has just done the same thing the long way, when they can feel what it would have saved.

What not to copy

The speed is mostly invisible to a first-time user who is still clicking. Someone evaluating the tool in a ten minute trial may see a plain issue tracker and never find the layer that justifies the switch.
Deliberate constraint becomes a migration wall. Teams with real regulatory or multi-stage approval workflows cannot express them, and the honest answer is that they are not the customer, which is a hard thing for a sales team to say.
Keyboard-first design can collide with screen reader and switch access expectations if custom pickers are not carefully described. Shortcut density is an accessibility win for some people and a hazard for others.
Optimistic updates push failure handling into the background. When a sync conflict does happen, the user has already moved on, and recovering their trust costs more than the spinner would have.

The takeaway

Show the shortcut every time someone does the slow version, and the slow version teaches the fast one.

Finished the teardown? Bank it and the day counts toward your run.

Where the principles come from

The Humane Interface, Jef Raskin
Response Times: The 3 Important Limits, Jakob Nielsen, NN/g
Flexibility and Efficiency of Use (heuristic 7), NN/g
Badass: Making Users Awesome, Kathy Sierra

Written from public behaviour of the product, not from inside it. Interfaces change often, so treat the flow described here as of the time of writing and check the live product before quoting it.