- AllThingsRemote
- Posts
- your remote team isn't unproductive.
your remote team isn't unproductive.
you're just measuring the wrong things...
π Welcome back to All Things Remote: weekly tips for building a better remote team.
Remote workers log an average of 2.5 extra hours per day compared to their in-office counterparts.
Yes, that's more hours. But it's not always more output.
In today's send:
β
Why measuring hours is the wrong metric for remote teams
β
The productivity gap behind most bad management decisions
β
What the best remote managers track instead
I'd love to know:
How does your team currently measure productivity? |
Top reads this week
The work-life balance stats every remote leader should know
The 10 trends redefining remote work right now
4x your communication output. Same quality. No burnout.
The bottleneck isn't what you want to say β it's how long it takes to type it. Wispr Flow removes the bottleneck.
Speak naturally and get polished, send-ready text for executive summaries, client updates, board recaps, investor notes, or just the 30 Slack messages you're behind on. Flow strips filler, formats numbers and lists, and preserves your tone.
Used by teams at OpenAI, Vercel, and Clay. 89% of messages sent with zero edits. Works in every app on Mac, Windows, and iPhone.
Most remote teams don't have a productivity problem.
They have a measurement or tracking problem.
When you can't see your team working, the instinct is to look for signals. Time in tools. Whether they're online on Slack. How quickly someone responds.
None of these will tell you that good work is getting done. They'll just tell you whether someone is at their desk.
But when your team knows they're being measured on presence, they optimise for it. They respond quickly, try to be online always, and try to look busy.
And the actual output, the thinking, the problem-solving and the work that will move things forward ends up getting squeezed into whatever's left.
The gap nobody talks about
That gap has a name: productivity paranoia. And it's driving a lot of bad management decisions.
More check-ins
More monitoring.
More visibility theatre.
Yet none of this closes the gap; it just makes both sides more stressed...
The teams that have figured this out have stopped wondering "are they working?" and started asking "are they delivering?"
Those are very different questions.
What to measure instead

