The air in the conference room has that recycled, slightly metallic taste of a building that hasn’t breathed in 45 years. We are currently 125 minutes into a sprint planning session that was supposed to be a quick 55-minute alignment. On the screen, a Jira ticket is being dissected with the surgical precision of an autopsy, yet the patient-our collective productivity-has been dead for an hour. The debate is currently centered on whether ‘Refactoring the Auth Module’ constitutes a 3-point story or a 5-point story. We have spent 35 minutes discussing this. The irony is heavy enough to sink a ship: the actual coding required to fix the underlying issue would take approximately 85 minutes. We are burning 15 man-hours of collective salary to decide how to label 85 minutes of work.
The Anchor of Tactile Reality
I’m sitting here testing my pens. I have 15 of them lined up on my notebook. This morning, before the sun was even fully over the horizon, I sat at my desk and systematically tested every single pen I own. I was looking for a specific kind of resistance.
Some were too slick, gliding over the page without any feedback, like a manager promising a ‘seamless transition’ to a new software suite. Others were scratchy, catching on the fibers of the paper. I finally settled on a black 0.5mm felt tip that feels like it’s actually biting into the page. It’s the only thing that feels real in this room. The scratch of the nib is a physical anchor in a sea of abstract ‘velocity’ and ‘story points.’
The Cargo Cult of Process
We have optimized the ritual to the point of extinction. We have daily stand-ups where 15 people stand in a circle and recite what they did yesterday, which is usually ‘I was in meetings,’ and what they are doing today, which is ‘I will be in meetings.’ We have retrospectives where we talk about how we need to communicate better, and then we create a new Slack channel that nobody reads.
The Art of Necessary Friction
Claire K. understands this better than most, though she works in a completely different world. She’s a museum lighting designer, the kind of person who worries about the ultraviolet degradation of a 445-year-old silk tapestry. I met her at a gallery opening where I was complaining about a particularly grueling 105-point sprint. She didn’t offer sympathy; she offered a critique of my entire industry. She told me about a project where the board of directors spent 25 months debating the ‘thematic resonance’ of the lobby lighting. They held 155 meetings. They hired 5 different consultants.
In a world of theoretical optimizations, looking at the practical reality of how power actually moves is refreshing. It’s why people look toward specialists like Rick G Energy when they need to stop talking about efficiency and start actually seeing it in the hardware. There is a certain point where the planning must stop and the voltage must flow. If you spend 55 days planning a grid but never lay the cable, you’re just a guy with a very expensive drawing.
Lost in Resonance
Igniting the Art
She told me, ‘They wanted to talk about the light, but they didn’t want to see the art.’ That’s us. We want to talk about the work. We want to measure the work. We want to put the work into a colorful pie chart that we can show to a Vice President who has 15 minutes of attention span. But we don’t actually want to sit in the quiet, terrifying silence of a blank text editor and solve a hard problem. Solve a problem? That’s risky. Following a process is safe. You can’t get fired for following a process, even if the process leads you directly into a brick wall at 65 miles per hour.
Busyness vs. Achievement
There’s a strange comfort in the bureaucracy. It provides a buffer. If I spend my day in 5 back-to–back meetings, I can tell myself I was ‘busy.’ I can point to my calendar, which is a solid block of blue, and feel a sense of accomplishment. But busyness is a lazy substitute for achievement. It’s a way of avoiding the emotional labor of focused work.
Coding is hard. Designing a system is hard. It requires a level of cognitive load that can’t be sustained while simultaneously monitoring a dozen ‘urgent’ notifications. We’ve created a system that treats developers like CPUs-plug them in, give them a task, and expect 100% utilization. But humans aren’t CPUs. We are more like 85-watt lightbulbs in a circuit that’s being constantly surged. Eventually, the filament snaps.
Wasted Deployment Time
225 Hours
Wasted time in a 15-step pipeline (45 mins per 1-line CSS change).
I was so focused on the ‘how’ that I completely lost sight of the ‘why.’ The ‘why’ was a customer who just wanted the ‘Submit’ button to be blue. Instead, they got a 25-page PDF detailing our commitment to ISO-certified deployment standards.
This obsession with the map over the territory is rampant in heavy industries too, though they tend to be more honest about the costs. When you’re looking at energy systems, you can’t just ‘Agile’ your way out of a power failure. You need systems that are designed for the actual outcome-the delivery of electrons.
Optimizing the Doodle: 25 Iterations
Doodling geometric shapes with intricate detail while the meeting drags.
I am optimizing the doodle. I am applying ‘Continuous Improvement’ to a drawing of a cube that will be thrown in the trash in 15 minutes.
The Beauty of Unscalable Action
I think back to Claire K. and her 15-hour sessions in darkened galleries. She doesn’t have a stand-up. She has a ladder and a light meter. She climbs the ladder, adjusts the barn doors on a fixture by 5 degrees, climbs down, looks at the painting, and then climbs back up to do it again. It’s tedious. It’s manual. It’s ‘unscalable.’
The Unmeasurable Outcome
Climb & Adjust (5°)
The Glow
No Story Points
But at the end of the night, the Rembrandt is glowing in a way that makes your breath catch in your throat. There is no Jira ticket for ‘making someone’s breath catch.’ There is no story point for ‘beauty.’ And yet, that’s the only thing that matters. The rest is just noise.
The Pathologizing of Deep Thought
If we took 75% of the time we spend talking about work and gave it back to the people actually doing the work, what would happen? Managers would see a developer sitting quietly, staring at a wall for 45 minutes, and they would assume that developer is ‘idle.’ They wouldn’t realize that the developer is currently simulating a 5-dimensional data structure in their head, trying to find the one bottleneck that’s slowing down the entire system. We have pathologized deep thought because deep thought doesn’t look like ‘work’ on a dashboard.
The Spider’s Efficiency
I once spent 25 minutes watching a spider build a web in the corner of my office. It didn’t have a project manager. It didn’t have a sprint goal. It just had a biological imperative to catch flies. It laid out the radial lines first, then the spiral. It tested the tension of each thread. If a thread was too loose, it ate it and started over. It was the most efficient engineering project I’ve ever seen.
And when it was done, the spider didn’t hold a retrospective to discuss what went well. It just sat in the middle and waited. It understood that the work was done and now it was time for the outcome. We, on the other hand, would have scheduled a 55-minute meeting to discuss the ‘Spider-Web Synergy’ and then accidentally walked into the web while looking at our phones.
Stop Pointing. Start Building.
I realize that I am part of the problem. I’m sitting here, consenting to this. I’m nodding when the Scrum Master looks at me, even though my mind is 1005 miles away. I am choosing the safety of the ritual over the friction of a confrontation. I am optimizing my own comfort.
BUILD THE THING NOW
We need to value the 85 minutes of flow over the 155 minutes of friction.