I agree that it should be easily reachable. Just not through one single keypress. macOS’s Spotlight serves a similar purpose and is reachable via Cmd + Space (with the Cmd key being right next to the space bar). That’s just as easy to do as hitting one button but is extremely unlikely to happen by accident.
I personally use the start menu mainly for shutting down the computer as all commonly used programs are pinned to the task bar. A shortcut that opens it has no value to me as opposed to e.g. one that shows or hides a terminal window or one that mutes/unmutes me in Teams even when it’s in the background.
And I do consider it disruptive because having the start menu unexpectedly pop open and swallow several keypresses (and in the worst case launching some application I didn’t want to run) takes my attention away from what I was doing and forces it into something completely irrelevant. If this pulls me out of deep focus I can lose the equivalent of ten minutes of work due to one keypress.
The core of the problem is that this behavior is very annoying for people who don’t use the start menu all the time and there’s no way to change it. If it was just a default for a rebindable shortcut then it’d be a minor hassle once and nobody would complain. But the way it is it feels like Microsoft is trying to force-feed me the start menu, workflow be damned.
I’m not sure about the “losing 10 minutes of work” part but I have to agree it’s stupid that users are unable to configure the shortcut in any way, and this workflow is kinda forced. I guess I don’t mind as much because I like that workflow.
If it was configurable, the default setting would be somewhat irrelevant but I also have to agree that a single key press stealing focus is maybe not the best design choice. I can also see how it’s more accessible and easier for new users but I guess it’s probably more annoying than helpful overall.
I think a good way to handle this – as well as the wildly unpopular accessibility functions the post is about – would be to have it configurable and simply ask about it during initial user setup (aka OOBE).
That way people who didn’t need it can turn it off and won’t stumble over it after accidentally pressing the Windows key or holding down Shift a bit too long. People who need it can have it enabled right from the get-go without having to trigger some dialog first. Everyone’s happy and having one extra step during initial setup isn’t that much of a hassle.
Bonus points if Windows had configurable global hotkeys and I could make the Windows key do whatever I want. But the OOBE thing would be a good solution already.
I agree that it should be easily reachable. Just not through one single keypress. macOS’s Spotlight serves a similar purpose and is reachable via Cmd + Space (with the Cmd key being right next to the space bar). That’s just as easy to do as hitting one button but is extremely unlikely to happen by accident.
I personally use the start menu mainly for shutting down the computer as all commonly used programs are pinned to the task bar. A shortcut that opens it has no value to me as opposed to e.g. one that shows or hides a terminal window or one that mutes/unmutes me in Teams even when it’s in the background.
And I do consider it disruptive because having the start menu unexpectedly pop open and swallow several keypresses (and in the worst case launching some application I didn’t want to run) takes my attention away from what I was doing and forces it into something completely irrelevant. If this pulls me out of deep focus I can lose the equivalent of ten minutes of work due to one keypress.
The core of the problem is that this behavior is very annoying for people who don’t use the start menu all the time and there’s no way to change it. If it was just a default for a rebindable shortcut then it’d be a minor hassle once and nobody would complain. But the way it is it feels like Microsoft is trying to force-feed me the start menu, workflow be damned.
I’m not sure about the “losing 10 minutes of work” part but I have to agree it’s stupid that users are unable to configure the shortcut in any way, and this workflow is kinda forced. I guess I don’t mind as much because I like that workflow.
If it was configurable, the default setting would be somewhat irrelevant but I also have to agree that a single key press stealing focus is maybe not the best design choice. I can also see how it’s more accessible and easier for new users but I guess it’s probably more annoying than helpful overall.
I think a good way to handle this – as well as the wildly unpopular accessibility functions the post is about – would be to have it configurable and simply ask about it during initial user setup (aka OOBE).
That way people who didn’t need it can turn it off and won’t stumble over it after accidentally pressing the Windows key or holding down Shift a bit too long. People who need it can have it enabled right from the get-go without having to trigger some dialog first. Everyone’s happy and having one extra step during initial setup isn’t that much of a hassle.
Bonus points if Windows had configurable global hotkeys and I could make the Windows key do whatever I want. But the OOBE thing would be a good solution already.