Help Power Users Move Faster

The business goal

Help power users complete important work with less friction and more confidence.

The UX choice

Use a command palette as a fast, keyboard-first system for discovering and running product actions—not as a simple search box.

Why this choice works

A well-designed command palette shortens the path to value for experienced users while keeping important actions discoverable. Fuzzy matching, grouped results, and visible feedback make the interface feel capable instead of hidden.

What to design

• Use fuzzy matching so queries such as “stg” can still surface Settings, Storage, and Staging.
• - Group results into Recent, Actions, and Pages so a long list stays scannable.
• - Support the full keyboard loop: arrows move, Enter runs, and Esc closes.
• - Open with recent or suggested commands instead of an empty state.
• - Keep the palette open while asynchronous results load and show an inline spinner.

Practical implementation rules

• Match queries as fuzzy subsequences.
• - Prefill recent and suggested commands.
• - Make keyboard navigation complete and predictable.

What to avoid

• Exact-only matching that returns no results for natural abbreviations.
• - A blank palette with nothing useful to select.
• - Freezing the whole screen while an asynchronous command loads.

Easystartup publishing angle

For a startup, frame the command palette as a retention and productivity lever: when users can find valuable actions quickly, they reach outcomes sooner and need less support.

Quick takeaway

A command palette earns its place when it makes the next action easier to discover and faster to complete.