Nothing is quite as visceral as the slow, rhythmic ticking of a wall clock when your eyes are already burning from a morning incident involving a bottle of tea-tree shampoo and a lapse in basic coordination. I am sitting in the third chair from the left in Conference Room 5, blinking through a chemical haze, watching Jerry navigate a slide deck that appears to have been designed in the late 95s. We are currently 45 minutes into a scheduled 65-minute status update. There are 15 of us in the room. If you calculate the average hourly rate of everyone present, this specific hour is costing the company approximately $1555, yet the only thing being produced is a collective sense of spiritual erosion.

Jerry is currently reading Slide 15 aloud. Word for word. It is a bulleted list of things we all already know, because they were included in the 25 emails he sent earlier this week. This isn’t communication; it is a séance. We are gathered here to summon the ghost of productivity, hoping that by sitting in the same room and nodding at the same colored charts, we can pretend that work is happening. My eyes sting, a sharp reminder that some things-like rinsing your hair-require direct, individual action, while others-like this meeting-are designed to diffuse that very concept of agency.

The Defensive Strategy of Consensus

Bailey once told me that the scariest thing about corporate culture isn’t the risk of failure, but the way we use meetings to ensure that if something does fail, the blame is spread so thin across 15 people that no one actually has to feel the weight of it. It’s a distributed liability model disguised as ‘collaboration.’

We use these 65-minute blocks to perform consensus. It’s a carefully choreographed dance where the goal isn’t to reach a decision, but to create a ‘Cover Your Ass’ artifact for our calendars. If the project eventually veers off course, Jerry can point to the calendar and say, ‘We had a 65-minute alignment session on the 25th, and no one raised any red flags.’ It’s a defensive strategy, not an offensive one. We are playing to not lose, rather than playing to win. This addiction to synchronous communication reveals a deep-seated organizational fear of individual accountability. We are terrified of a world where one person makes a call and lives with the consequences, so we retreat into the safety of the group dither.

Friction as a Feature

There is a specific kind of exhaustion that sets in around the 35-minute mark of a one-way monologue. It’s the realization that your time is being treated as a cheap commodity. In a world where every second of a user’s journey is being optimized for speed and clarity, why do we tolerate the opposite in our internal lives? When you look at how modern systems are built-take the way a platform like mawartoto approaches its interface-the focus is always on removing the friction that slows a person down. The goal is a hassle-free journey, a straight line from intent to outcome. Yet, in this conference room, we are intentionally building a labyrinth of friction. We are taking a 5-minute piece of information and stretching it across a 65-minute canvas, adding layers of unnecessary commentary and ‘circle-back’ invitations that serve no one.

I find myself wondering if Jerry knows. Does he see the 15 glazed expressions? Does he feel the 55% drop in oxygen in the room? Or is he, too, a victim of the script? He might be just as miserable as I am, trapped in a cycle where he feels he has to prove his value by the length of his presentations. If he only spoke for 5 minutes, would people think he isn’t working? We’ve created a system where ‘busy-ness’ is the primary metric of worth, and a 65-minute meeting is the ultimate badge of being busy. It is the visual proof that you are doing ‘important things’ with ‘important people,’ even if those things consist mostly of debating the hex code of a header that 5 people will ever see.

Bailey P.-A. would probably lose their mind in this environment. In the carnival world, if you waste 45 minutes talking about a problem instead of looking at the hardware, someone could actually get hurt. There is a gravity to that world that is missing here. Here, the only thing at risk is the company’s bottom line and our collective sanity. We’ve drifted so far into the realm of the abstract that we’ve forgotten how to be direct. We’ve forgotten that a 15-minute honest conversation is worth more than a 235-slide deck. We are so busy building bridges of consensus that we’ve forgotten how to actually cross the river.

Calling Things What They Are

We need to stop using the word ‘meeting’ as a catch-all for every interaction. We should call them what they are. This isn’t a status update; it’s a ‘reassurance ritual.’ We aren’t here to update the status of the project; we are here to update the status of our own anxieties. If we were honest, we’d admit that 85% of what happens in this room could be handled by a single, well-written paragraph. But a paragraph doesn’t fill a 65-minute slot on a calendar. A paragraph doesn’t provide the same theatrical weight as a conference room with a glass wall and a catered tray of 25 stale bagels.

I stand up as the chairs scrape against the carpet, a sound that 15 people have been waiting for with the intensity of a prison break. My eyes are mostly clear now, though the edges of my vision are still a bit rosy. I walk past Jerry, who is closing his laptop with the satisfied air of a man who has successfully killed 65 minutes of everyone’s life. He asks me what I thought of the presentation. I think about the $1555. I think about Bailey P.-A. checking 55 bolts in the rain. I think about the 25 emails I still haven’t answered.

‘I think it could have been a post-it note, Jerry,’ I say, not unkindly. He laughs, thinking I’m joking. I’m not. I’m already halfway out the door, headed back to my desk to do the actual work that this meeting was supposed to be about, wondering how many more of these 65-minute graveyards I’ll have to walk through before we finally decide to stop performing and start moving.