I keep unmuting myself on purpose
I don’t do it to be rude. I do it because I’m tired of being silent.
It’s 10:17 a.m. on a Tuesday. I’m in a quarterly sync with six people. My mic’s muted. My camera’s off. My hands are on the keyboard, and I’ve got something to say — something important. I reach for the mute shortcut. I hit Cmd+Shift+M. Nothing happens.
I look at the screen. Zoom’s open. I’m in Zoom.
I try Cmd+D. Still nothing.
I try Cmd+Shift+A. Still nothing.
I hit the spacebar. Nothing.
I sigh. I reach for my mouse. I click the button on the bottom left. I unmute. I speak. My voice cracks a little. I didn’t mean to sound so tense.
And then I realize: I didn’t even need to unmute.
I could’ve just... pressed the Dune.
It’s not that I’m bad with shortcuts. I’m not. I’ve got a spreadsheet of them. I’ve got sticky notes on my monitor. I’ve even got a macro that auto-detects which app I’m in and suggests the right combo. But I still mess up. Every. Single. Time.
Because every app has its own language. And I’m not fluent in any of them.
The chaos of context
I used to think it was just me. That I was the guy who couldn’t remember his own shortcuts. But I’ve talked to five other people this week — all remote workers, all in tech — and every single one of them has the same story.
Microsoft Teams? Cmd+Shift+M.
Zoom? Cmd+D.
Google Meet? Ctrl+Shift+A.
Slack Huddles? Cmd+Shift+K.
Webex? Ctrl+Shift+M.
And don’t even get me started on the camera. Some apps use the same key. Some don’t. Some toggle both at once. Some require you to hold. Some don’t. Some require a double-tap. Some require a click-and-hold. Some require you to open a menu and click a tiny icon that’s half-covered by a notification badge.
It’s not a design problem.
It’s a betrayal.
We’ve spent the last decade building tools that are supposed to make us more efficient. And yet, the one thing we do 40 times a day — mute our mic — is the one thing that’s been deliberately made harder.
Why?
Because nobody’s owning the problem.
Hardware isn’t the answer. But it’s the only thing that works.
I’ve tried everything.
I bought a Stream Deck. It’s beautiful. It’s customizable. It’s also the size of a small cutting board and takes up half my desk. I tried macros. I tried automation scripts. I tried binding the mute function to my trackpad’s corner tap. I even tried training myself to use voice commands.
None of it stuck.
Because the problem isn’t the shortcut.
It’s the context.
You’re in a meeting. You’re thinking about what to say next. You’re not thinking about which app you’re in. You’re not thinking about your keyboard layout. You’re not thinking about whether you’re on a Mac or a Windows box.
You’re thinking about your point.
And then you hit the wrong key.
And now you’re unmuting yourself in front of your boss.
Or you’re turning off your camera when you meant to mute.
Or you’re accidentally leaving your mic on while you say something you shouldn’t.
I’ve done all three.
Enter Dune
I got the Dune keypad two weeks ago.
It’s a stick of gum. Aluminum. No battery. No charger. Just three buttons that plug into your USB-C port.
It doesn’t care what app you’re in.
It just knows what you want to do.
One button: mute.
One button: camera.
One button: bring window to front.
No shortcuts. No combos. No confusion.
It’s not magic.
It’s simplicity.
I didn’t have to relearn anything.
I didn’t have to memorize a new set of rules.
I just reached for it.
And now, when I’m in a meeting, I don’t think about shortcuts.
I think about what I want to say.
And then I press the button.
The real cost of bad UX
This isn’t about convenience.
It’s about dignity.
Every time you fumble with a mute button, you’re not just wasting time.
You’re broadcasting your insecurity.
You’re signaling that you’re not in control.
You’re the person who can’t figure out how to turn off their mic.
And in a world where every meeting is a performance, that’s the worst thing you can be.
I used to feel stupid when I messed up.
Now I feel angry.
Angry that we’ve accepted this as normal.
Angry that companies build billion-dollar platforms and can’t agree on a single shortcut.
Angry that the people who design these tools think we’re okay with this.
We’re not.
The future is tactile
The Dune isn’t perfect.
I’ve accidentally unmuted myself twice because my sleeve brushed the device while reaching for coffee.
The keys are a little stiff.
The app is still clunky.
But it’s the first thing I’ve used that doesn’t make me feel like a glitch in the system.
And that’s the point.
We don’t need more features.
We need fewer choices.
We need hardware that remembers what we’re trying to do.
We need tools that don’t make us work harder just to be heard.
I don’t want a better shortcut.
I want a mute button that just works.
And if that means I have to carry a $119 piece of aluminum around with me?
Then so be it.
Because I’d rather be heard than silent.
And I’d rather be angry than quiet.
The silence we’re taught to accept
I used to think the problem was my memory.
I’d tell myself: "You’re just bad at remembering shortcuts. You need to practice more. You need to build muscle memory."
But then I started asking other people.
And I realized: nobody remembers.
Not the interns. Not the VPs. Not the CTOs.
We all just... fumble.
And we all pretend it’s fine.
We laugh it off.
"Oh, I hit the wrong key again!"
"Haha, I turned off my camera on purpose!"
"I’ve been muted for 12 minutes and no one noticed. I think I’m invisible."
We’ve normalized the chaos.
We’ve turned a fundamental human need — to be heard — into a technical obstacle course.
And the worst part?
No one’s fixing it.
Because no one’s in charge.
Zoom doesn’t own the shortcut. Microsoft doesn’t own it. Google doesn’t own it. Slack doesn’t own it.
They all built their own version. And now we’re stuck with the mess.
The myth of "user customization"
You know what’s worse than inconsistent shortcuts?
The idea that we’re supposed to customize our way out of it.
"Just set up your own macros!"
"Use automation!"
"Build your own script!"
That’s not a solution.
That’s a cop-out.
We’re not software engineers.
We’re not power users.
We’re people trying to get work done.
And if the only way to mute your mic is to write a Python script or hire a developer to set up a Claude prompt...
Then the tool has failed.
Dune doesn’t ask you to code.
It doesn’t ask you to learn.
It just asks you to press.
And that’s the difference.
Why this matters beyond meetings
This isn’t just about Zoom or Teams.
It’s about how we treat people in digital spaces.
We’ve built tools that assume we’re always in control.
That we’re always paying attention.
That we’re always ready.
But we’re not.
We’re tired.
We’re distracted.
We’re multitasking.
We’re juggling Slack, email, a toddler, a dog, a cat, and a 10-minute countdown to the next meeting.
And yet, the tools we use demand perfect focus.
They demand precision.
They demand memorization.
They demand that we be better than we are.
That’s not design.
That’s punishment.
Dune doesn’t punish.
It assumes.
It assumes you want to mute.
It assumes you want to turn off your camera.
It assumes you’re in a hurry.
And it gives you a button.
No menus.
No shortcuts.
No learning curve.
Just a press.
The next step
I don’t expect every company to adopt Dune.
I don’t even expect them to copy it.
But I do expect them to stop pretending this isn’t a problem.
If you’re building a meeting app, and you think your shortcut system is fine...
You’re wrong.
It’s not fine.
It’s broken.
And the people using it are paying the price — in frustration, in embarrassment, in lost time, in lost confidence.
We need a standard.
Not a mandate.
But a consensus.
A single key.
One for mute.
One for camera.
One for join.
And if we can’t get that?
Then at least stop making it harder.
Stop adding new shortcuts.
Stop changing them.
Stop pretending we’re okay with this.
We’re not.
And if you’re building tools for humans?
You should know that already.
For more on how hardware can simplify digital workflows, see The Quiet Revolution in Remote Work Tools.
If you’re tired of juggling multiple meeting apps, check out Why We Need a Unified Meeting Protocol.
Learn how design decisions impact daily productivity in The Cost of Choice Overload in Productivity Apps.