[Image]
This experience supports moments where people are deep in work and want to move without breaking focus. Users are trying to jump between views, actions, and settings quickly, often many times a day. For the business, this kind of experience helps advanced users stay productive and reinforces the product as something built for sustained, serious use.
We tested a keyboard-driven command menu inside a B2B project tracking platform. Participants were asked to imagine starting work and using a quick key shortcut to navigate and take action. The test used expectations, comprehension, and frequency to surface how people anticipate accessing the menu, how well they understand the options once it’s open, and whether it fits into their day-to-day workflow.
This type of testing surfaces whether speed features actually support momentum or quietly get ignored. It helps teams see where confidence builds, where awareness breaks down, and how easily advanced functionality becomes habit-forming. For product leaders, these signals matter because small moments of friction can decide whether power features feel essential or invisible.
User Needs & Business Goals
This experience supports users who want to stay in flow by giving them a quicker path to common actions, while helping the business increase engagement with advanced features. Users want to feel efficient and in control, and the platform benefits when those shortcuts become part of daily habits.
This concept was tested with project managers, product managers, and team leads in the United States. Participants reviewed a keyboard-driven command menu inside a B2B project tracking platform and were asked to imagine using it during their normal work. They evaluated how they would access it, how well they understood the options, and how often they would rely on it.
User Needs
In this moment, users are trying to move quickly without stopping to reorient or hunt for controls.
-
The experience should feel efficient, helping users act quickly with minimal friction (efficient).
-
The experience should feel intuitive, matching common shortcut patterns they already know (intuitive).
-
The experience should feel empowering, giving users a sense of control over how they work (empowering).
-
The experience should feel usable, with clear options that are easy to scan and select (usable).
-
The experience should feel valuable, clearly saving time during everyday tasks (valuable).
Together, these needs matter because speed only helps if users understand what’s available and trust it enough to use it repeatedly.
Business Goals From the business perspective, this experience supports deeper product adoption and sustained usage.
-
Increase feature adoption by encouraging use of advanced navigation tools.
-
Improve retention by making daily workflows faster and less frustrating.
-
Strengthen perceived product maturity for experienced, high-value users.
-
Reduce friction in common tasks to support productivity at scale.
-
Reinforce differentiation as a tool built for serious, repeat usage.
These goals create long-term value by aligning user efficiency with sustained engagement and loyalty.
Choose Metrics to Test Your User Shortcuts
This experience tests how people move quickly through work when time and focus matter. A design stack of UX metrics was selected to understand whether the shortcut menu fits naturally into existing habits and supports fast decision-making. The metrics were chosen by mapping core user needs to signals that show up clearly in real behavior: Expectations, Comprehension, and Frequency.
Intuitive → Expectations
Users want shortcuts to match patterns they already know before they even try them. Expectations capture whether the shortcut feels obvious or surprising at first glance. This metric surfaces early confidence, showing whether people trust that the experience will behave the way they assume it should.
Usable → Comprehension
Once the menu is open, users need to quickly understand what actions are available and what each option does. Comprehension reflects how easily people can scan, interpret, and make sense of the command list without stopping to think. This metric captures clarity in the moment of use, not learning over time.
Efficient → Frequency
Speed only matters if people believe they’ll use the feature again and again. Frequency signals whether the shortcut feels valuable enough to become part of daily work. This metric reflects habit potential, showing if the experience supports repeated, low-effort use rather than one-off curiosity.
Together, these metrics show whether the shortcut is discoverable, understandable, and likely to stick—three conditions that determine whether power features actually earn their place in a workflow.
Establish Hunches to Direct Your Testing
Starting with hunches helps teams name what feels uncertain before looking at data. It turns assumptions into something testable, so the team can see where confidence holds and where it might break down. These hunches were used to shape focused questions about speed, clarity, and trust in shortcut-driven workflows.
Example: Project tracking platform command menu
<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Hunch</p></th><th colspan="1" rowspan="1"><p>Question</p></th><th colspan="1" rowspan="1"><p>UX Metric</p></th></tr><tr><td colspan="1" rowspan="1"><p>Experienced users may expect a common shortcut pattern, but some may hesitate if they’re not sure it will actually work. This uncertainty could affect whether they try the shortcut at all.</p></td><td colspan="1" rowspan="1"><p>What keys would you expect to press to open this command menu?</p></td><td colspan="1" rowspan="1"><p>Expectations</p></td></tr><tr><td colspan="1" rowspan="1"><p>Even if users recognize the shortcut, the specific key combination might not fully match what they anticipate. A mismatch here could reduce early confidence.</p></td><td colspan="1" rowspan="1"><p>How well does pressing Command + K or Control + K match your expectations?</p></td><td colspan="1" rowspan="1"><p>Expectations</p></td></tr><tr><td colspan="1" rowspan="1"><p>Once the menu is open, users may understand most options but hesitate if labels feel too broad or unclear. This could slow decision-making in a moment meant to be fast.</p></td><td colspan="1" rowspan="1"><p> How well do you understand your options in this command menu?</p></td><td colspan="1" rowspan="1"><p>Comprehension</p></td></tr><tr><td colspan="1" rowspan="1"><p>Users may see the menu as useful, but only adopt it regularly if it clearly saves time in daily work. Perceived effort versus payoff could affect repeat use.</p></td><td colspan="1" rowspan="1"><p>How often would you use this quick key command menu?</p></td><td colspan="1" rowspan="1"><p>Frequency</p></td></tr></tbody></table>
These hunches collectively aim to evaluate whether shortcut-driven navigation supports understanding, confidence, and momentum without interrupting how people already work.
Turn Hunches into Test Questions
Turning hunches into concrete questions helps ensure we’re testing real uncertainty, not assumptions. Pairing each UX metric with a specific question type creates signals that are easy to observe and compare across participants.
**Expectations (Open response + rating)**
Question type: Open-ended expectation + scaled alignment
Example: What keys would you expect to press to open this command menu?
**Expectations (Scaled alignment)**
Question type: Likert scale
Example: How well does pressing Command + K or Control + K match your expectations?
**Comprehension (Understanding scale)**
Question type: Likert scale
Example: How well do you understand your options in this command menu?
**Frequency (Usage intent)**
Question type: Multiple choice frequency scale
Example: How often would you use this quick key command menu during your normal work?
Calculate UX Metric Scores from User Feedback
We tested the Power User Shortcuts concept to understand how experienced project managers, product managers, and team leads perceive and adopt a keyboard-driven command menu inside a project tracking platform. Participants were asked to imagine starting work and using a shortcut to move quickly between actions and views. The design stack included Expectations, Comprehension, and Frequency, combining attitudinal signals about confidence and understanding with behavioral intent around repeat use.
-
Very Good = 90% and above
-
Good = 70%–89%
-
Average = 50%–69%
-
Poor = 30%–49%
-
Very Poor = below 30%
The overall test score was 74% (Good). This reflects an experience that works well once engaged, with clear strengths in understanding and repeat-use potential, alongside early uncertainty at the point of discovery.
**Expectations (57% — Average):**
Users did not consistently anticipate how to open the command menu or fully trust the shortcut before trying it. While many expected a familiar pattern, uncertainty around the exact keys created hesitation at the entry point. This suggests early confidence is uneven, even among experienced users.
**Comprehension (76% — Good):**
Once the menu was open, most users understood the available options and how they mapped to common actions. Scanning and interpreting the list felt manageable, with only minor confusion around a few labels. This indicates the menu supports fast decision-making after discovery.
**Frequency (78% — Good):**
Participants frequently indicated they would use the shortcut as part of regular work. Many described it as a clear time-saver during busy days, signaling strong potential for habit formation. Repeat use appears likely once users see the value in practice.
[Image]
xperience that delivers on speed and clarity after first use, but loses momentum early if expectations are not met. The dominant tension sits between discovery and payoff: once users cross the entry threshold, confidence builds quickly, but getting them there remains the most fragile moment.
Click here to check out the raw survey data and UX metric scores for Linear’s power user shortcuts.
Draw Signals from Your Design Stack
Here’s how signals were surfaced from this project tracking platform’s power user shortcuts test results by following five steps:
1. Focus on poorly scoring or imbalanced metrics
[Image]
The overall test score was 74% (Good). Frequency (78%) and Comprehension (76%) were the strongest signals, while Expectations lagged behind at 57%. The weaker expectations score is driven by uncertainty around the shortcut itself. Many users expected a familiar pattern, but not everyone immediately trusted that it existed or would work the way they assumed. Signal: The value of the shortcut is clear once discovered, but discoverability and initial trust are the main points of tension.
2. Identify patterns across metrics
[Image]
Comprehension and frequency reinforce each other. When users understood the menu, they could quickly see how it would fit into daily work. Expectations, however, sit apart. This suggests the friction happens before interaction begins, not during use. The tension here is familiarity versus visibility. Power users recognize the pattern, but only after they notice it.
3. Determine if user needs are being met
[Image]
-
Efficient: Met — Users consistently pointed to speed and reduced navigation effort.
-
Intuitive: Partially met — Shortcut patterns felt familiar, but not universally expected.
-
Empowering: Met — Users described feeling more in control of their workflow.
-
Usable: Met — Options were generally easy to scan and understand once open.
-
Valuable: Met — Many users described clear time savings in everyday tasks.
4. Compare outcomes to business goals
-
Increase feature adoption: Partially supported — Strong usage intent once discovered, weaker initial expectations.
-
Improve retention: Supported — Frequent-use signals suggest habit formation potential.
-
Strengthen perceived product maturity: Supported — Power users associate shortcuts with advanced tools.
-
Reduce friction in common tasks: Supported — Users consistently referenced speed and flow.
-
Reinforce differentiation: Partially supported — Differentiation depends on visibility, not capability.
5. Surface signals & establish a direction
Signals derived from the data:
[Image]
-
Power users understand and value command menus once they engage with them.
-
Frequency signals suggest this could become part of daily workflows.
-
Expectations are the weakest point, indicating an early confidence gap.
-
The main friction appears before use, not during use.
Direction based on business context:
The evidence points toward an experience that works well for experienced users who recognize shortcut patterns. The opportunity lies in bridging the gap between assumed knowledge and first-time awareness, especially for users new to the platform or new to shortcut-driven workflows.
This is a strong efficiency-driven experience with clear value for power users. Its success depends less on how it works and more on whether users realize it’s there and trust it early enough to adopt it.
