The Return-to-Office Tax Nobody Talks About


TL;DR: Back in the office, back to the same problem — my status is invisible to anyone walking by. No door, back to the hallway, no signal for whether I'm heads-down or free. Built a $15 ESP32 status light that reads my calendar and flips red when I'm busy, green when I'm not. One glance from the hallway. Problem solved. Code at github.com/kix1979/StatusLight.

Back in the Noise.

I'm back in the office. Cube life, open floor, teammates on all sides. Back to the main hallway where everyone walks by on their way to somewhere else.

I will gladly take this over a private office. The fishbowl with glass walls and a door that signals "I'm important" — no thanks. I'd rather be in it with my team. That tradeoff made sense to me.

What I didn't think about is the tax.

The problem isn't interruptions. It's recovery.

When I'm remote, my status is obvious. Green dot means available. Red means on a call. Slack, Teams, whatever — the signal is right there. Nobody guesses.

In the office, there's no dot. There's just me, sitting at my desk, back to the hallway. Deep focus and an active meeting look exactly the same from ten feet away. So people stop. Reasonable thing to do — there's no signal saying otherwise.

The interruption itself is usually fine. Quick question, fast answer, done. That's not the tax.

The tax is the re-entry. Getting back to where you were. Reconstructing the context you were holding in your head. That doesn't take 30 seconds... it takes 10 minutes. Do that four times in a morning and you've lost 40 minutes to nothing. No output, no meeting, no artifact. Just recovery time from context switches that didn't need to happen. Did I say context switching? Ah the good old days.

The obvious fixes don't work

Headphones are supposed to be the universal signal. The problem is they're ambiguous. Am I on a call? Listening to music? Did I just forget to take them out when I walked to the canteen? Nobody knows. The signal is too weak.

Calendar blocks help nobody if they don't check it. And they won't check it. They're walking down the hallway, they see you, they have a question. They're not stopping to pull up your calendar first.

Post-its, signs, all of it — invisible at hallway distance. Requires someone to be close enough to read it, which means you've already made eye contact, which means the interruption already happened.

Every passive signal fails the same way. It puts the work on the other person. That work doesn't get done.

So I built a light

ESP32 dev board. WS2812B NeoPixel LED. A 3D-printed puck sitting on the corner of my desk, visible from the hallway.

A swift on my Mac polls my calendar free/busy status every 30 seconds. When I'm marked busy, the light goes red. When I'm free, it goes green. That's it.

The part that matters: calendar-based means predictive. The light flips before my call starts, not after I'm already mid-sentence with someone walking in. It knows I'm about to be unavailable. It signals that before the collision happens.

Red means stop. Green means go. I didn't invent that convention. I just pointed it at my desk.

Full build guide, firmware, wiring, and the macOS script are at github.com/kix1979/StatusLight.

Why it works when the other things don't

The signal is ambient. Pre-attentive. Color registers before conscious thought — you don't decide to notice it, you just notice it. One glance from the hallway is enough. No one has to think, no one has to check anything, no one has to get close enough to read a sign.

It removes the guesswork. Green means come ask. Red means come back later. The decision is already made.

The side effect I didn't expect

When the light goes red, I feel it. I didn't build it for that. But externalizing your own status does something. It makes the commitment more real. I'm more locked in when the signal is on. Less likely to drift. The light is for other people but it turns out it works on me too. I didn't realize how much I really enjoy it, until I went home and didn't have it in my home office.

Where this goes next

The hardware is intentionally dumb. REST API, three states, one LED neopixel (ok 7 LEDs). The logic lives in software and that's where the interesting stuff happens.

Next on the list: Slack status sync, so remote teammates get the same signal. A manual "heads down" mode for deep work blocks that aren't on the calendar. Maybe calendar-to-Slack bridging so the whole thing is automatic end to end. Revising the model to nest the lights, maybe do a opaque topper...

The platform scales. The concept doesn't change.

The actual point

This isn't about the light.

It's about protecting your attention in an environment that wasn't designed to help you do that. Open offices optimize for collaboration and visibility. That's a real tradeoff — I made it on purpose. But collaboration-by-default has a cost, and that cost comes out of your focus budget every single day.

The parts cost $15. The focus they protect is worth a lot more.

Parts List

PartNotes
ESP32-WROOM-32 DevKitAny standard ESP32 dev board works
WS2812B NeoPixel LEDSingle LED or small strip
USB cable + 5V power supplyPowers the ESP32
3D printed enclosurePETG or PLA

Total cost: ~$15 depending on what you have on hand.

Full code and wiring at github.com/kix1979/StatusLight.

Written by AI and conceived by a human.

Comments

Post a Comment

Popular posts from this blog

I Took My Own Advice in an Interview. Pure Storage Didn't Flinch.

Image
I'm joining Pure Storage on March 2nd to be part of the technical marketing team, and I'm genuinely excited about it. During the interview process, I took my own advice from a blog post I wrote a few weeks ago and asked them the question that makes most candidates nervous: "What concerns do you have about me for this role?" They didn't flinch. They gave me real feedback. We had an actual conversation about fit, not just a polished interview performance. That's when I knew this was the right place. What Got Me Excited The conversations with Pure focused on enablement. Not campaigns. Not metrics. Enablement. How do we help the people in front of customers have better conversations? How do we give them what they actually need to succeed? Those questions resonated with me because I've done that work before. I know what it's like when you have the right materials at the right time. When customer stories are authentic and metrics are real. When enablem...
Read more

If I do the homework, you owe me a phone call. The death of decency in hiring.

Image
Honestly, I almost didn't post this. You know how it is. You don't want to look salty. You don't want to look difficult. It’s easier to just roll your eyes and move on to the next application. But I can’t be the only one dealing with this nonsense, so I’m saying it. Here’s the situation: I’m interviewing for a senior role. Things are going great. The hiring manager is cool, we’re clicking, the vision matches. Then comes the homework. And not a 30-minute writing sample. They asked for the full package: A 12-month strategic plan for Analyst Relations. How to position them for MQs, Waves, the works. I sat down and did the work. I audited their competitors. I built the roadmap. I gave them a strategy I would usually charge a consulting fee for. I sent it off, ready to talk shop. The result? Ghosted by the human, rejected by the robot. No feedback. No "hey, thanks for the effort." Just a generic, no-reply template email: “We have decided not to move forward.” Since w...
Read more

The One Question That Terrifies Candidates But Wins Offers - It's not "How's the Culture?"

Image
If I’ve been a little quiet on here lately, it’s not because I’m sipping coconuts on a beach. It’s because I’ve been in the trenches. I’ve been doing the rounds—interviewing with a bunch of different companies, shaking hands (or bumping elbows), and sitting in a lot of hot seats. And when you do that many interviews back-to-back, you start to see patterns. You see the same generic questions, the same awkward pauses, and the same moment where the power dynamic shifts. It happens when the interviewer closes their laptop, leans back, and asks: "So, do you have any questions for me?" Most people play it safe here. They ask about work-life balance or what a typical Tuesday looks like. Those are fine, but let’s be real: polite questions don't get you the job. If you really want to stand out—and more importantly, if you want to know if you actually got the gig, you need to stop being a passenger. You need to be bold. You need to ask the questions that make your palms sweat. Her...
Read more