Skip to content

The Altar of the Gantt Chart

  • by

The Altar of the Gantt Chart

We are constantly buffering. A deep look at the modern obsession with tracking work over actually completing it.

The blue light of the monitor hums against my retinas at exactly 8:05 AM. I’m staring at a progress bar that has been stuck at 99% for what feels like an eternity, though the digital clock tells me it’s only been 45 seconds. It’s a cruel metaphor for the modern workplace. We are constantly buffering. We are 95% done with the planning, 85% done with the alignment, and 105% over-saturated with the meta-work of explaining what we haven’t actually started yet. My coffee is already lukewarm, a casualty of the first ‘quick sync’ of the day that managed to consume 35 minutes of oxygen without producing a single actionable sentence.

Project Velocity

99% Buffer

99%

I’m clicking through Jira tickets like a monk reciting rosary beads. Each status change from ‘To Do’ to ‘In Progress’ feels like a small, hollow victory. We’ve built a cathedral to the process, but the pews are empty and the roof is leaking. We spend more time polishing the pews-updating the cards, tagging the stakeholders, color-coding the dependencies-than we do actually fixing the holes in the ceiling. It’s the Project Management Cult, and I’m currently the reluctant high priest of a spreadsheet that contains 235 rows of pure, unadulterated fiction.

The Smell of Sawdust

Michael H. is standing by the door of his workshop, shaking a literal can of spray paint. He’s an escape room designer, a man whose entire professional existence is dedicated to creating physical puzzles that people pay $45 to solve. He doesn’t have a Scrum Master. He doesn’t have a Kanban board that spans three monitors. He has a workbench covered in sawdust and a magnetic lock that won’t engage because the alignment is off by exactly 5 millimeters. He looks at me, still tethered to my laptop, and asks why I’m staring at a digital box instead of looking at the product. I tell him I’m ‘managing the pipeline.’ He laughs, and it’s the kind of laugh that makes you realize you’ve spent $575 of company time today just talking about how to save $125 on a software license.

🛠️

The Workbench

Tangible Output

📊

The Spreadsheet

Reporting Overhead

🧭

Map vs Territory

Conceptual Shift

We’ve mistaken the map for the territory. The project plan is supposed to be a guide, a rough sketch of the mountain we intend to climb. Instead, we’ve decided that if we just draw a really detailed map, the mountain will somehow climb itself. We’ve become obsessed with the aesthetics of productivity. A well-organized Trello board looks like success. A clean Burndown chart feels like progress. But you can’t live in a blueprint, and you can’t drive a car made of status reports. I once saw a team spend 15 days debating the nomenclature of their tagging system while the actual server was melting in the corner. They were so busy categorizing the fire that they forgot to pick up the extinguisher.

The representation of work has become more valuable than the work itself.

Sanitizing the Messiness

There is a specific kind of madness that takes over when a process becomes a religion. You start to see it in the language. We don’t have conversations anymore; we have ‘touch-points.’ We don’t finish things; we ‘ship MVPs.’ We’ve sanitized the messiness of creation because messiness is hard to track in a Sunday evening report. Michael H. understands messiness. When he’s building a puzzle, he knows that the ‘flow’ of the room is something you feel in his gut, not something you calculate in a cell.

65

Hours perfecting one sound

(Not on the critical path, but essential for belief)

He tells me about a time he spent 65 hours perfecting the sound of a falling stone. No project manager would have approved that. It wasn’t on the critical path. It didn’t move the needle on the quarterly objectives. But when the players hear that sound, they believe the world he built. They feel the quality. They experience the soul of the work.

“When the players hear that sound, they believe the world he built. They feel the quality. They experience the soul of the work.”

– Michael H. (The Craftsman)

I find myself nodding, even as my Slack notifications chirp with the frantic energy of 15 people asking for an ‘ETA on the update.’ The irony is that the more I update them, the further the ETA recedes. Every minute I spend explaining why we are behind is a minute I am not spent getting us ahead. It’s a recursive loop of administrative overhead. I’ve calculated that for every 5 hours of actual engineering or design we do, we generate 5 hours of reporting. We are operating at 50% efficiency by design. It’s a systemic tax we pay for the illusion of control.

Hedged Against Chaos

We fear the unknown. Management, at its core, is an attempt to hedge against the inherent chaos of the human creative process. We want to believe that if we just have enough meetings, we can eliminate risk. But risk is where the breakthrough lives. If you know exactly how a project is going to end before you start it, you aren’t innovating; you’re just following a recipe. And recipes are for bakeries, not for building the next great experience.

When you’re focused on the end result-the actual, tangible impact on the user-the paperwork starts to look like the distraction it really is. This is why brands like

Smackin Tickets resonate with people; they focus on the actual delivery of the experience, the moment the fan gets the ticket and the gate opens, rather than the bureaucratic gymnastics happening behind the scenes. They understand that the customer doesn’t care about your sprint velocity; they care about the seat, the show, and the soul of the event.

Process Time Lost

25

Days Arguing (Red Team)

vs.

Actual Progress

100%

Completion Target

I remember a project where we had a ‘Red Team’ whose only job was to find flaws in the process. We spent 25 days arguing with the Red Team about whether their feedback was properly formatted. It was a hall of mirrors. I felt like that 99% buffering video-constantly on the verge of completion but paralyzed by a lack of bandwidth. The bandwidth wasn’t technical, though. It was emotional. We were too afraid to just do the work and apologize later if the process wasn’t perfect. We wanted the safety of the checklist.

Insight

Activity is not an achievement; motion is not progress.

Embracing the Mistake

Michael H. finally gets the magnet to click. It’s a sharp, satisfying sound that cuts through the hum of my laptop. He didn’t need a status update to know it worked. He just heard it. He saw the result. He’s covered in grease and he looks exhausted, but he has a finished thing in his hands. I have a slide deck. My slide deck has 15 slides, all of which are beautiful, and none of which can open a door. I’m starting to think I’m in the wrong business, or at least, the wrong side of the brain.

The Report

Detailed, Safe, Late

The Code

Messy, Real, Done

I’m going to make a mistake today. I’m going to miss a stand-up. I’m going to leave a ticket in ‘Blocked’ without a detailed comment. I’m going to do this because I need to actually finish the code I started three days ago. The cult will be displeased. There will be an automated email. A project coordinator will send me a direct message with a frowny-face emoji. But the code will be done. The logic will be sound. The user will be able to click a button and have something happen, which is significantly more important than a project manager being able to click a button and see a green checkmark.

Creators or Curators?

Are we building things or just building the record of things?

We’ve reached a point where we need to ask if we are building things or just building the record of things. Are we the creators or the curators of our own stagnation? I think about that 99% buffer again. Maybe it isn’t the internet connection. Maybe the video is just afraid to finish because then it has to be judged. As long as it’s buffering, it’s still ‘in progress.’ It’s still safe from the harsh light of completion. But completion is the only thing that matters. Everything else is just noise.

The Buffer is Over

I close the Jira tab. The silence is immediate and jarring. I pick up my own version of a screwdriver-a clean text editor-and I start to build. No tags. No sprints. No story points. Just the work. I can almost hear Michael H. nodding from across the room. He’s busy resetting a riddle involving 5 skeleton keys and a hidden compartment. He’s not tracking his time. He’s just making sure the mystery is worth solving. And in the end, that’s the only metric that survives the 105-degree heat of the real world. We need to stop worshiping the plan and start respecting the product. Otherwise, we’re just 5 people in a room, watching a screen buffer until the lights go out.

55

Pyramids Lost

I wonder how many hours of human potential have been sacrificed to the god of the ‘Weekly Status Call.’ Probably enough to build 55 pyramids or at least 15 really good escape rooms.

I’m going to stop contributing to that tally. If the work is good, it speaks for itself. If the work is bad, no amount of project management will save it. It’s a simple truth, one that feels dangerously radical in an office culture built on the back of the billable hour. I might get fired, or I might finally ship something worth talking about. Either way, the buffer is finally over.

Stop Worshiping the Plan. Start Respecting the Product.

– End of Transmission