It’s 4:00 PM on a Friday. A prompt appears in Slack, a chipper little bot asking you to log your "weekly frictions." You dutifully type them out. The CI pipeline was mysteriously slow on Tuesday morning. A poorly documented internal API cost you half of Wednesday. The staging database fell over again Thursday, blocking a critical deployment. You hit send. You think you’re helping the new Developer Experience team find things to fix.
You are mistaken. You are punching a clock.
The movement to improve the "developer experience," or DevEx, began with a noble goal: remove the tedious obstacles that keep engineers from doing meaningful work. It was about creating flow, automating toil, and building tools that felt intuitive instead of hostile. But in the hands of management, this empathetic mission has been twisted into a new form of scientific management. The friction log is not a request for help. It is an audit of your wasted minutes.
Look at the dashboards that DevEx teams are so proud to present. They don’t measure joy, creativity, or insight. They measure velocity. Cycle time, from first commit to deployment. Pull request pickup time. Deployment frequency. These are the metrics of the factory floor, borrowed from the Toyota Production System, now aimed squarely at the act of thinking. Every moment not spent shipping code is defined as a failure, a "friction" to be optimized away.
The tools are becoming more sophisticated. Git analytics platforms generate "impact" scores and flag engineers whose code requires more review cycles. Slack bots publicly nudge developers whose pull requests sit idle for a few hours. Internal developer portals, meant to be helpful service catalogs, are also perfect instrumentation for tracking who uses which tools and how quickly they complete prescribed "golden path" workflows.
The subtext is clear: your time is not your own. Your thought process is a resource to be allocated and squeezed for maximum efficiency. Pausing to read a paper, sketching a new architecture on a whiteboard, or having a long, rambling conversation with a colleague that unlocks a key design insight—none of these activities fit into the spreadsheet. They are friction. They cannot be easily measured, so they are deemed worthless.
This relentless optimization has a corrosive effect. It discourages engineers from tackling the truly hard, ambiguous problems. Why risk a week of messy exploration in a legacy system when your performance is being judged on a steady stream of small, predictable commits? It punishes mentorship, which shows up as a drag on the mentor's personal output. It creates a culture of risk-aversion, where nobody wants to be the person whose experiment fails and tanks the team's "cycle time" for the quarter.
The real friction isn't a slow test suite. It's the anxiety of being constantly measured. It's the pressure to perform productivity rather than actually produce good work. The goal of a healthy engineering culture should be to create trust and autonomy, to give smart people the space to solve hard problems. Instead, we are building digital panopticons. We are giving developers better shovels, but only so they can dig faster while a supervisor with a stopwatch looks on. And we have the gall to call it "experience."
Generated by Reportify AI — Automate your team's status reports, standups, and weekly updates. Try free →