[mbar84]

One of the most wonderful developments of the last decade is the "Command Palette" UX pattern. You can have a tool driven predominantly by keyboard and also make all the keyboard shortcuts discoverable (display them next to the command in the dropdown). Maybe just let the UX guys do whatever they want, just so long as I can press Ctrl-K and type the first letters of the command I want to do.

[IIsi50MHz]

I use Excel's "/, Q, <search>" frequently, because I'm often searching for a feature whose name I remember, but whose place or existence in some menu or panel of the Ribbon is ephemeral or not memorable, often changing with window size.

If only activating the search box weren't so slow!

It feels like I'm starting a moderately large app and waiting for it to load (while still being faster than clicking through Ribbons and opening various subpanels by clicking on teensy "arrow in a corner" widgets).

I'd expect it to be a tiny array of text held in memory for instant access, with no perceived delay between when I finish typing "/Q" and the search interface appearing.

But then, I'd also expect the first search result to be selectable by just hitting <Enter>. Having to use an arrow key to navigate down one, then press <Enter> is unfortunate, especially when using an MS Surface's keyboard's half-size up/down arrows.