The Wilderness Test: Expertise Demands Autonomy

Collaboration is the euphemism we use to hide our fear of individual agency.

“

“Move now or freeze later.”

Chloe H. would find this entire setup laughable, if not dangerous. I spent a week with her in the high desert last year-she’s a wilderness survival instructor who doesn’t believe in “vibes,” only in caloric math and terrain reality. We were caught in a sudden downdraft on a ridge, the temperature dropping 14 degrees in less than 4 minutes. There was no time for a roadmap refinement session. She didn’t ask for a show of hands on where to cache the gear or invite the ‘stakeholders’ to weigh in on our wind-chill strategy. She looked at the darkening sky, pointed at a jagged rock outcropping, and said, “Move now or freeze later.”

In that moment, her expertise was a tool, not a suggestion. In the office, expertise is a decoration. We want to own experts, but we don’t actually want them to act like experts. Acting like an expert requires autonomy. It requires the ability to look at a room of 14 people and say, “This is a waste of time, here is the solution, I’m going back to my desk to build it.” But our corporate cultures are designed to punish that kind of efficiency. We call it “not being a team player.” We call it “siloed thinking.” So, instead of building the solution, the expert sits in the meeting, nodding at the person who has the loudest voice but the least amount of context.

I look at David again. He’s finally given up on his icons and is now staring at the ceiling tiles. There are 44 of them in his direct line of sight. I know this because I’ve counted them twice during the last update on “cross-functional communication protocols.” There is something deeply tragic about a person who is capable of building world-class infrastructure being reduced to counting acoustic foam squares because a middle manager is afraid to make a call without a consensus.

This isn’t just about lost hours; it’s about the systematic erosion of the professional soul. When you hire someone to do something they’re brilliant at and then systematically prevent them from doing it, you aren’t just wasting $444 an hour in combined salary. You’re teaching them to be cynical. You’re telling them that their skill doesn’t actually matter as much as their presence in a calendar block. You are training your best people to stop caring. Why put in the effort to innovate when you know that any original thought will be pulverized by the 14-headed hydra of the weekly sync?

The Fetishization of Busyness

We’ve reached a point where “work” is what happens in the 14-minute gaps between Zoom calls. We have fetishized the appearance of busy-ness over the reality of progress. If you’re at your desk, head down, headphones on, typing furiously, people wonder if you’re being “antisocial.” If you’re in a glass-walled conference room nodding at a whiteboard, you’re a leader. We have mistaken the noise of discussion for the signal of achievement.

Chloe H. told me once that the most dangerous thing in the woods isn’t a bear or a cliff; it’s the “lethargy of the group.” It’s the phenomenon where a group of five people will walk slower than the slowest person, but a group of twenty will eventually stop moving altogether to discuss why they aren’t moving. They will debate the merits of the map while the sun goes down, and by the time they reach a consensus on which way is North, they’re already shivering.

We need spaces where the work is the priority, not the performance of the work. Places that respect the immersion required to solve hard problems. If you look at the architecture of high-output digital environments, like what is being cultivated at ems89, you see a shift back toward the ‘deep work’ ethos. It is an admission that you cannot schedule genius for 2:44 PM on a Tuesday between a budget review and a HR sync. Real work requires a level of focus that is fundamentally incompatible with the “always-on, always-available” meeting culture. It requires the bravery to leave people alone.

The True Cost: Talent Bleed

I remember another time with Chloe H., when we were trying to navigate a particularly dense patch of brush. One of the students kept stopping to ask if we should “regroup and re-evaluate.” Chloe didn’t even look back. She just said, “Evaluation is for when you’re lost. We aren’t lost. You just don’t like how hard the walking is.” That resonates. Half of our meetings aren’t about finding the way; we already know the way. We just don’t like how hard the actual execution is, so we’d rather sit in a climate-controlled room and talk about the walking instead of doing it.

There is a financial cost to this, of course. If you take 14 people with an average salary of $154,000 and put them in a room for two hours, that meeting cost the company roughly $1,034 in direct salary alone, not counting the opportunity cost of what they *didn’t* build. But the hidden cost is the talent bleed. The best engineers, the best designers, the best thinkers-they don’t leave companies for more money. They leave because they are tired of being statues. They leave because they want to go somewhere where they can actually use the tools they spent a decade mastering.

I’ve seen it happen 24 times in the last two years. A brilliant hire comes in, full of fire and ready to disrupt the status quo. By month 4, they’ve realized that the status quo is a fortress built of Outlook invites. By month 14, they’ve updated their resume and are taking “doctor’s appointments” that suspiciously coincide with interviews at startups that promise a “no-meeting Wednesdays” policy.

Reclaiming Deep Work

We have to stop treating meetings as a neutral activity. They are an invasive species. They consume the habitat of deep thought until there is nothing left but the dry husks of action items that no one has the time to complete. We need to empower the Davids of the world to say, “I’m not coming to that meeting because I’m busy doing the thing the meeting is about.”

As I sit here in Room 4B, the person at the front of the room is now showing a slide about “Efficiency Metrics.” The irony is so thick I can almost taste it. It tastes like copper and frustration. I look down at my laptop. I have 154 unread Slack messages. 4 of them are from my boss, asking why the deployment is behind schedule. I want to stand up. I want to point at the 14 people in this room and say, “The deployment is behind schedule because we have spent 44 hours this month talking about the schedule instead of touching the code.”