You're Paying for 8 Hours but Getting Less Than 4 — Fix the Environment, and Your ND Employees WILL Outproduce Everyone

I've run a version of this question with founders and executives for years. I'll ask them: of the eight hours your employees are being paid to work today, how many hours of actual focused, productive output do you think you're getting?

Most say five or six. A few ambitious ones say seven. I have never — not once — had someone say three.

And yet. Here we are.

The Microsoft Work Trend Index found that 57% of the average workday is now spent in communication — meetings, emails, chats, pings (Microsoft, 2023). That leaves 43% for everything else. Execution. Creative thinking. Problem solving. You know — the actual work.

But RescueTime tracking real computer activity across hundreds of thousands of knowledge workers, found something even harder to look at: the average employee gets 2 hours 50 minutes of focused, productive work done in a typical 8-hour workday 🤯.

Not five. Not six. Three point four. And here's the thing: we don't know how many of those workers were neurotypical vs. neurodiverse. The surveys didn't ask. So what we have is a blended baseline — a mixed population, in a poorly-designed environment — producing 3.4 hours of focused output per day.

If we had to estimate within that blended 3.4-hour average — and this is directional, not proven — it's reasonable to expect that neurotypical employees are probably closer to 4–4.5 hours, and neurodiverse employees in those same broken environments are closer to 2. But here's what that means: fix the environment, and both numbers move. Dramatically. And that's where the real story is.

Here's a concrete illustration of where those hours go. Your team has a 10am meeting. It ends at 10:45. The next one starts at 11:30. That's 45 minutes in between — which sounds like productive time. But research shows it takes approximately 23 minutes for the average knowledge worker to recover full deep focus after a single interruption (Gloria Mark, UC Irvine, 2008). Which means your employee gets roughly 22 minutes of real focused work before the next meeting pulls them out again 💸.

Now run that across a day with four meetings. You blocked your people’. You've fragmented their entire day into pieces too small to do meaningful work in.

For neurotypical employees, that fragmentation is expensive. For ND brains — where task switching is often deliberate rather than automatic, where a difficult interaction in the previous meeting can occupy the background processes for far longer than 23 minutes — the math gets worse. The recovery window isn't just longer. It's less predictable. And the accumulated cost of never fully getting into flow compounds over days, then weeks, then months 📉.

Here's another one that doesn't show up in any productivity report, but I promise you it's happening in your org right now. In environments without real async communication norms, messaging looks like this 👇

Every exchange in that ping-pong sequence is a context break. Not just for the person answering — for the person asking too, who's now waiting, checking back, following up. Multiply that by a team of 10, across a full workday, and you have an interruption machine running inside your messaging tool 24/7.

Now apply this to ND employees specifically. Without clear async norms, there's also the message-crafting tax: reading and re-reading a vague incoming message to interpret intent. Spending 10–15 minutes composing a reply to ensure it won't be misread. The absence of async standards doesn't just waste time — it creates a communication anxiety loop that lands disproportionately on the people already running the most cognitive overhead.

I've been following the work of Lacey Artemis at Neuromix, who is doing some of the most rigorous thinking I've seen on sensory design in workspaces. One concept from her SOLACE framework stops me every time: accumulated sensory load.

The idea is this: sensory load doesn't spike and reset. It stacks. Every ambient noise filtered. Every fluorescent flicker ignored. Every unexpected social interaction navigated without preparation. None of these individually looks like the thing that broke someone's concentration. But collectively, they accumulate — quietly, invisibly — until a tipping point. As she puts it: an avalanche isn't caused by the final disturbance. The pressure was building long before.

She frames it with a model I find genuinely clarifying: imagine every employee starts the day with 100 points of cognitive resilience. Except a high sensory sensitivity employee might arrive with only 50. And then the open-plan office — fluorescent lighting, ambient conversation, visual clutter, unpredictable interruptions — deducts another 25 before they've sat down. At that point, slower output and difficulty getting into flow aren't personal failings. They're predictable outcomes of the conditions 📐.

Here's what this means for how you interpret the 3.4-hour number: it's not a talent problem. It's a sensory budget problem. And the standard office environment is hemorrhaging that budget before the first deep work session of the day has a chance to begin.

And before remote advocates claim the high ground here — a poorly designed remote environment isn't automatically better 🖥️. Back-to-back Zoom calls recreate meeting fatigue without the commute. Repetitive daily standups consume hundreds of hours of synchronous time per year. And for ND employees in particular, video calls carry a hidden cost that most managers have never thought about.

I recently connected with Mark Fister, the CTO and co-founder of Haystack, who shared an interesting insight into the deeper meaning of Zoom fatigue he’s heard time and again from people with Autism.

That's not a figure of speech. That's the real cost of a mandatory camera-on meeting for an autistic employee — tracking faces, reading social cues, managing sensory input, and suppressing natural self-regulation behaviors, all simultaneously, for the duration of the call. The meeting didn't cost an hour. It cost the rest of the afternoon 🎥.

Fister draws a distinction worth understanding. The cost is different depending on the profile:

This connects directly to a framework called Spoon Theory — originally developed by Christine Miserandino to describe chronic illness energy management, and widely adopted in the ND community. Everyone starts the day with a finite number of spoons — units of cognitive and physical energy. The critical difference for neurodiverse employees is both that they may start with fewer spoons, and that communication-heavy work costs them more spoons per interaction.

The best-designed environments — remote or office — are the ones that protect the spoon budget instead of depleting it before noon. As Fister put it: "The best practice says everyone should show up on any given day exactly how they wish to show up. If on this day you do not have the energy for video, turn it off."

I want to address directly what some of you might be thinking right now: if the environment is broken for everyone, and ND employees are taking an additional hit on top — why would you prioritize building for them?

Because the upside is extraordinary. And it changes the math entirely 🚀.

When JPMorgan Chase ran their Autism at Work program — with structured communication norms, reduced sensory friction, and clearer expectations — their autistic employees were 48% faster and 92% more productive than baseline. When EY built their Neuro-Diverse Centers of Excellence, ND hires cut technical training time by 50% through process improvements the neurotypical staff hadn't spotted.

These results came from partial accommodations — not perfect ones. Which means they are almost certainly a floor. So let's run the math directionally 🧮

These numbers are directional, not precision. I'm not going to dress up an extrapolation as a controlled study. But the direction of the argument is grounded in documented outcomes — and the direction says: build the right environment, everyone wins, and your ND employees may produce the highest ROI of anyone on your team.

Here's a question I ask every founder I work with. At the end of a week, how do you know if your team had a productive week?

All answer that the major bug was fixed, marketing campaign launched, or new deal was closed.

When I change the timeframe to a single day, most describe some version of presence. Were people in meetings? Did they reply to messages? Did they seem engaged? Were they visible?

This is measuring the perceived performance of work — not the work itself 🎭. And for neurodiverse employees, that performance is exactly what's draining the spoon budget.

For remote teams: Stop tracking availability like check ins/outs on Slack. Start defining contribution. What does "done" look like for each role, each week? Write it down. Measure those outputs. Kill the ping-pong Slack culture and replace it with one-message async norms.

For office teams: The same logic applies. "Were you at your desk?" is not a metric.

This is NOT a definition of productivity 👇

"What did we ship?" is.

Protect morning blocks — stop scheduling meetings before noon and giving your people's highest-value cognitive hours to the lowest-value activity.

For both: Build in the capacity signal. An async standup that includes "I'm at 60% this week" gives managers early visibility before the production window collapses. This is not surveillance. It's a communication design that makes honesty easier than silence 🛞.

I spent eight years building and leading remote teams before COVID made it fashionable. When I was at InVision, scaling from early stage to $100M+ ARR, the moment things genuinely clicked was when we stopped asking "is everyone online?" and started asking "what did we build?" 🔁

What I didn't fully appreciate at the time was how much of that model was accidentally serving the ND employees on our team. Async-first communication reduced the real-time masking and ping-pong load. Written documentation removed the improvised social performance requirement. Output-based measurement meant the person who needed a quiet morning and then produced extraordinary work from 10am to 2pm was valued for their actual contribution — not penalized for not fitting the mold.

We were building a neuro-inclusive operating model without knowing that's what we were doing.

I think about that a lot now. Especially watching companies call everyone back into environments producing 3.4 hours — and calling it a return to productivity. The math doesn't support it. The employees who already knew that are quietly doing their own calculation about whether they want to be there for what comes next.

I'd love to hear what brought you here. Reply directly — I read every message.

If this resonates, share it with a CEO or HR leader in your network. The conversation needs to start somewhere.

And if you're past the conversation stage and ready to actually build the systems — reach out. That's exactly what I do.