A small shift happened in my workflow over the last year, and I didn’t fully notice it until recently:
I don’t type nearly as much anymore.
A lot of my day used to be spent writing — code, messages, docs, search queries, notes.
Now a much bigger portion of it is spent reading, reviewing, comparing, monitoring, and switching between contexts.
AI is a big reason why.
Instead of generating every draft from scratch, I’m now often:
- reviewing AI output
- comparing versions
- checking whether something is correct
- jumping between browser tabs, apps, terminals, and docs
- monitoring results instead of manually producing every line myself
That sounds like a software change.
But for me, it also became a physical interaction change.
My hand is on the mouse most of the day now.
And that exposed something I hadn’t really questioned before: most of my productivity actions are still designed around the keyboard.
Things like:
- taking a screenshot
- switching apps
- snapping windows
- opening a bookmarked URL
- triggering a repeated shortcut
- moving between “work surfaces” quickly
None of those are difficult.
But when your workflow becomes more mouse-heavy and less typing-heavy, reaching back to the keyboard starts to feel less like a shortcut and more like a tiny interruption.
That’s the part that surprised me.
Keyboard shortcuts used to feel seamless because I was already typing all the time.
Now I’m often reading something on screen, following an AI-generated draft, comparing outputs, or scanning multiple windows. In that mode, my mouse is already “active,” while the keyboard feels secondary.
So the old shortcut model still works.
It just no longer fits the flow as naturally.
That mismatch is what pushed me to build a small Windows tool for myself: RightWheel.
The idea is simple:
- hold right-click, scroll, and trigger an action.
I started using it for the handful of things I kept doing over and over:
- switching tasks
- launching common shortcuts
- opening frequently used links
- taking screenshots
- reducing the constant mouse-keyboard-mouse transition
What interested me most wasn’t just the tool itself.
It was the realization behind it:
AI may be changing not only what we do on computers, but how we physically interact with them.
If more of our work becomes:
- reviewing instead of drafting
- orchestrating instead of manually producing
- navigating instead of typing
- supervising systems instead of directly operating every step
...then it makes sense that our input habits might shift too.
The assumption that the keyboard is always the primary productivity surface may come from an earlier shape of digital work.
I’m curious whether other people are feeling this too.
Have AI tools changed your mouse-to-keyboard ratio?
Have you adapted your setup in any way — better mouse software, macros, Stream Deck, window managers, voice input, custom gestures?
I’d love to know what changed in your own day-to-day workflow.