Here’s a provocative claim: remote teams pay an inherent “trust tax.”
I’ve worked at Google (in-person), Airbnb (hybrid), and now a fully remote startup. After observing engineering teams in all three contexts, I’ve noticed something: remote teams have extra communication overhead specifically designed to build confidence that work is happening.
I call this the “trust tax.”
What Is the Trust Tax?
The trust tax is the productivity cost of compensating for reduced visibility in remote work. It manifests as:
- Over-documentation: Writing detailed updates not because they’re needed, but to prove work is happening
- Extra status updates: More check-ins than necessary to signal you’re productive
- Longer decision cycles: Needing more consensus because you can’t “read the room”
- Duplicate communication: Saying the same thing in Slack, email, and meetings
- Defensive behavior: Excessive CYA communication to protect yourself
Each individually is small. Collectively, I estimate they create a 10-15% productivity drag.
The Root Cause: Visibility Bias
In offices, managers could see busy = productive. Engineer at desk, typing, in meetings = they’re working hard.
This is terrible management, but it created a false sense of confidence.
Remote removes this visual signal. Managers panic. “How do I know people are working?” They demand more status updates, more meetings, more “visibility.”
The team responds by performing productivity instead of being productive. We enter a doom loop of trust tax.
Strategies That Reduce Trust Tax
1. Default to Transparency
Make work visible by default, not by request. Public Slack channels. Open roadmaps. Shared dashboards. When information is accessible, people don’t need to ask for it.
2. Regular Video Face Time
Even in async-first teams, regular video sync builds human connection. We do weekly team syncs where we actually see each other. This builds trust that reduces tax.
3. Explicit Working Agreements
Write down: When should people respond? What’s urgent vs. not? Who decides what? Clarity reduces anxiety and defensive communication.
4. Showcase Work-in-Progress
Share messy, unfinished work. Not just polished deliverables. This normalizes that good work is iterative and builds confidence in process.
5. Measure Outcomes, Kill Activity Metrics
If you measure outputs (features shipped, bugs fixed, customer impact), you don’t need activity theater. Trust comes from results.
6. Invest in Annual In-Person Gatherings
One week together per year does more for trust than daily standups. Face-to-face builds social capital that carries through remote work.
The Cultural Shift
Reducing trust tax requires cultural change from “prove you’re working” to “assume good intent.”
This is uncomfortable for managers. It requires actually managing by outcomes, not managing by observation.
But it’s the only way remote work scales. You can’t build a high-trust culture on surveillance.
My Specific Example: Demo Day
We run weekly “demo day” - 30 minutes, anyone can show anything, 5-minute slots. Engineers demo features, designers show mockups, product shares customer feedback, even finance shows new reporting.
Two effects:
- Everyone sees what everyone’s working on (visibility without asking)
- Celebrating work-in-progress normalizes that not everything is polished (reduces defensive behavior)
This single ritual has reduced our trust tax measurably. Fewer “what’s the status of X?” questions. More confidence across the team.
The Caveat
Some trust tax is necessary overhead. Remote teams DO need more intentional communication than co-located teams.
The goal isn’t zero - it’s minimizing unnecessary tax while maintaining healthy transparency.
What’s your trust tax? How does your team reduce it?