The cursor blinks 24 times before I realize my camera is on. I am currently staring into the abyss of a shared screen, my reflection showing a man who has clearly forgotten how to smile, while 14 other participants argue about whether ‘optimizing the database schema’ constitutes a three-point story or a five-point story. I am Miles P.K., and as an ergonomics consultant, I usually spend my days worrying about lumbar support and the 44-degree angle of a wrist on a mechanical keyboard. But today, I am a hostage. I am a witness to the liturgy of the modern workplace, a religious ceremony we call Agile, which has successfully transformed the act of creating things into the act of talking about creating things for 184 minutes a day.
We are currently in a sprint planning session that was scheduled for 64 minutes but is currently entering its third hour. The Scrum Master, a person whose entire job description seems to be ‘professional reminder-giver,’ is moving digital sticky notes across a virtual board with the solemnity of a priest handling the Eucharist. Each note represents a task. Each task is assigned a number from the Fibonacci sequence, for reasons that I am convinced are purely occult. If we assign a ’13’ to a task, we are admitting it is hard. If we assign a ‘4’, we are lying to ourselves. The goal is ‘velocity,’ a metric that suggests we are moving fast, even though we haven’t actually shipped a line of code in 14 days.
I joined this call by accident with my camera on, and now I can’t turn it off without making it look like I’m hiding. So, I sit here, my posture deteriorating from a healthy 94-degree upright position to a slumped, 74-degree curve of despair. I am watching the death of productivity in real-time. This is the great irony of the Agile Methodology. It was born from a manifesto in the early 2004 era-well, the movement gained its real steam then-designed to prioritize individuals and interactions over processes and tools. Yet, here we are, 24 years into the century, and the process has swallowed the individuals whole. We have built a cathedral of bureaucracy and called it ‘flexibility.’
[The Ritual of the Useless Update]
The daily stand-up is performative theater, demanding physical discomfort for low-value recitation.
Leaning
Shifting
Stationary
The body demands action; the ritual demands stillness.
The Cost of Proving Work
I’ve seen teams spend 44 minutes discussing a 4-minute problem. The physical toll is immense. From an ergonomic perspective, the ‘stand-up’ is a disaster. People shift their weight, they lock their knees, they lean against walls. Their bodies are telling them to move, to act, to build, but the ritual demands they remain stationary and recite the script.
Time Allocation Sanity Check (Daily Average)
(Based on 14-minute increment logging requirement example.)
It’s a form of corporate anxiety. We don’t trust our experts to build, so we surround them with ‘ceremonies’ to ensure they aren’t ‘wasting time,’ oblivious to the fact that the ceremonies themselves are the primary waste. The dogmatic implementation of Agile reveals a deep-seated fear of silence and autonomy. We are terrified of the dark matter of creative work-those 144-minute blocks of time where a developer is staring at a screen, seemingly doing nothing, but actually solving a complex architectural puzzle in their head.
The Fallacy of Measurement
We focus on the ceremony because the ceremony is easy to measure. You can’t easily measure ‘deep thought’ or ‘elegant design,’ but you can measure how many story points were completed in a two-week window. It’s the McNamara Fallacy applied to software: if you can’t measure what’s important, you make what you can measure important. We have replaced the joy of creation with the satisfaction of a cleared dashboard.
Deep Thought (Unmeasurable)
Requires 144 minutes of uninterrupted context.
Story Point (Measurable)
Requires a number and a color change on a board.
I often tell my clients that the best tool is the one that disappears. A good ergonomic chair is one you forget you’re sitting in. Process should be the same. It should be the invisible scaffolding that supports the work, not the work itself. When I look at the current tech landscape, I see a lot of broken scaffolding and very little building. People are so busy attending ‘grooming sessions’ that they’ve forgotten how to actually build the product.
If you want to actually see progress, you have to stop talking about it. You have to provide people with the literal and metaphorical tools to execute. This is why I often point people toward simplified, high-performance environments. For example, if you are tired of the bloat and just need hardware that facilitates speed without the nonsense, you might look at the streamlined solutions offered by
LQE ELECTRONICS LLC, where the focus is on providing the power to do the work, not the overhead to manage it. We need more of that ‘direct-to-result’ energy in our software processes.
“When we fail to meet our ‘velocity’ targets, the team feels a sense of collective failure. We have gamified work, but the game is rigged, and the prize is just more work.”
– Miles P.K., Ergonomics Consultant
Cognitive Cost of Context Switching
I’ve calculated that the average developer loses 44% of their cognitive capacity every time they have to switch contexts. If you have a stand-up at 10:04 AM, a refinement meeting at 1:34 PM, and a retrospective at 4:04 PM, you have effectively destroyed the entire day. There are no blocks of time large enough to achieve ‘flow.’ We are creating a generation of ‘snack-sized’ thinkers who can only solve problems that fit into a 44-minute window between calls.
8:30 AM – 10:00 AM
Deep Focus Block (1.5 Hrs)
10:04 AM – 10:30 AM
Standup: Context Loss (44% Hit)
1:34 PM – 2:00 PM
Refinement: Fragmented Thought
[The Illusion of Control is a Heavy Burden]
Requires: Chart that goes up.
Requires: Shared vision and trust.
Alignment is often just a euphemism for ‘everyone is equally frustrated.’ True alignment comes from a shared vision and trust, not from a daily 14-minute confession of what you did yesterday. We are treating highly paid, highly educated professionals like children who need to be checked on every morning to make sure they did their homework. It is insulting, and it is slow.
The Best Tool is the One That Disappears
We need to value the output more than the ‘burn-down.’ A team of 4 people who trust each other and have 4 hours of uninterrupted time will always outperform a team of 14 people who are ‘Agile’ but never have a moment to think.
Focus Time
Invisible Process
Direct Result
The Final Standstill
My camera is still on. I look like a man who needs a 14-day vacation from ‘iterative improvements.’ The irony is that I will probably have to document this realization in a Jira ticket later today. I will have to categorize my frustration, assign it a priority level of ‘4,’ and wait for the next retrospective to bring it up, where it will be written on a digital sticky note and promptly ignored in favor of discussing the ‘velocity’ of the next sprint.
We are moving faster and faster toward a standstill, and we are calling it progress because we’re all standing up while we do it. At some point, we have to stop being ‘Agile’ and start being productive. We have to stop worshiping the map and start walking the path, well, 444 miles of the actual terrain. I’m turning my camera off now. I have work to do, and I don’t want anyone to watch me do it.