The laser pointer is vibrating against the screen, a tiny red dot trembling on Step 31 of a diagram that looks less like a workflow and more like the wiring for a nuclear submarine. I am sitting in the third row, leaning back, watching the consultant’s neck turn a specific shade of crimson as he explains the ‘synergistic hand-off’ between the creative team and the compliance department. There are 21 people in this room. If you calculate the hourly rate of everyone present, this meeting has already cost the company $1301, and we haven’t even decided if the blog post should be written yet. We are just discussing the process of requesting the writing of the post.

I’ve spent the last 21 minutes trying to find a way to gracefully exit a conversation with a colleague about his sourdough starter, so my patience for performative bureaucracy is at a record low. We are obsessed with the architecture of the work because the work itself is terrifying. If we spend 51 hours a month tweaking our project management boards, we don’t have to face the blank page. We don’t have to make the hard choice between Strategy A and Strategy B. We just move cards from one column to another and call it ‘optimization.’

The Digital Sherpa and the Software Swamp

Maria S. knows this better than anyone. She is a podcast transcript editor, a job that exists at the messy intersection of human speech and digital precision. Maria S. once showed me her dashboard. She had 11 different browser tabs open just to process a single 41-minute episode. One app for the raw audio, one for the AI transcription, one for the manual corrections, one for the client’s feedback, one for the billing, and six others that ‘streamlined’ the communication between the first five.

‘I spend 61 percent of my day just moving data between tools,’ she told me, her eyes reflecting the pale blue light of a screen that had frozen for the third time that hour. She isn’t editing anymore; she’s a digital sherpa, carrying heavy loads of metadata across a mountain range of software. We built these tools to save us, but they have become the very thing we need saving from. We are drowning in the efficiency of the middleman.

[The process is the noise; the work is the signal.]

I catch myself doing it, too. I’ll spend 41 minutes researching the ‘perfect’ note-taking app, comparing features like back-linking and graph views, while the actual article I need to write sits untouched in the corner of my mind. It’s a form of sophisticated procrastination. It’s much easier to organize a shelf than it is to write a book. We have 11 different ways to ‘slack’ a coworker, yet we haven’t actually spoken to them in 31 days. We send a ticket. We tag a person in a comment. We create a ‘huddle’ that nobody wants to join.

Think about the last time you bought a kitchen appliance. You didn’t need a 27-step flowchart to decide you were hungry. You needed a tool that worked, a place that had it, and a way to get it home. When the friction of buying becomes greater than the utility of the product, the system has failed. This is why I appreciate the blunt honesty of a place like

Bomba.md-you need a stove? Here is the stove. You don’t need to join a Discord server or attend a webinar on ‘Stove Integration Strategies’ to make an omelet. You just need the hardware.

In the corporate world, we’ve lost that directness. We’ve replaced ‘Hey, can you write this?’ with a Jira ticket that requires 11 mandatory fields, including ‘Level of Effort’ and ‘Strategic Alignment.’ The writer, who could have finished the draft in 91 minutes, now spends 41 minutes just navigating the administrative debris. By the time they actually start typing, the creative spark has been smothered by a wet blanket of ‘best practices.’

Frictionless Interference

Maria S. told me about a client who insisted on using a ‘real-time collaborative feedback tool’ for her transcripts. Instead of just marking up a Word document, they used a platform that allowed 21 different stakeholders to leave comments in real-time. Maria S. watched as the document became a battlefield of conflicting opinions. One person wanted ‘more energy,’ while another wanted ‘more gravitas.’ Because the tool made it so easy to comment, everyone commented on everything. It was frictionless interference.

If the tool hadn’t been there, the stakeholders would have had to talk to each other. They would have had to reach a consensus before speaking to Maria S. The ‘optimization’ of the feedback process actually destroyed the clarity of the result. If I can show you a chart with 31 green checkboxes, I don’t have to show you a product that actually moves the needle. I can prove I was busy. I can prove the process was followed. If the project fails, we don’t blame the vision; we blame the ‘bottleneck’ in step 41. We then hire another consultant to optimize the bottleneck, adding 11 more steps to the flowchart. It’s a self-perpetuating loop of meta-work.

Losing Meaning in the Metrics

I’ve been trying to end a conversation with my own internal critic for 21 minutes now. The one that says if I don’t use the latest AI-driven task manager, I’m falling behind. But then I remember Maria S. and her 11 tabs. I remember the consultant and his red laser pointer. I think about how much more we could achieve if we just did the work instead of talking about how we’re going to do the work.

We have created a world where the ‘how’ has completely cannibalized the ‘why.’ We are so worried about the 1 percent gain in efficiency that we ignore the 91 percent loss in meaning. We optimize the speed of the treadmill without ever asking where the treadmill is going.

I watched the consultant click to the next slide. It was a ‘Roadmap for Process Evolution.’ It contained 11 phases, each with its own acronym. The marketing lead sighed, a long, slow sound that seemed to leak out of her very soul. She just wanted a blog post. She had the idea 51 minutes ago, but now, trapped in the amber of this presentation, the idea was already starting to feel old.

The most efficient process is often the one you have the courage to skip.

We need to stop pretending that software can solve cultural problems. If your team doesn’t trust each other, a new Kanban board won’t fix it. If your goals are unclear, an 11-step approval process will only make them more confusing. Optimization should be about removing things, not adding them. It should be about clearing the path so that someone like Maria S. can just edit a damn podcast without needing a degree in systems administration.

I eventually left that meeting. I didn’t wait for the Q&A. I didn’t wait for the ‘next steps’ email that I knew would arrive in 11 minutes. I walked back to my desk, closed all of my open tabs, and opened a single, blank text file. It felt naked. It felt dangerous. There were no columns to move, no tags to assign, no status updates to provide. There was just the work.

And for the first time in 21 days, I actually felt productive.

Axe Sharpening vs. Hitting the Tree

We are so busy sharpening the axe that we never actually hit the tree. We’ve turned the grind into a ritual, a series of 31-step dances that we perform to appease the gods of Productivity. But the gods aren’t watching. They’re busy using a simple tool to solve a simple problem, while we’re still trying to figure out which Slack integration will help us decide what’s for lunch. Maybe the most ‘optimized’ thing we can do is just look at each other and say what needs to be said. No flowchart required.