Why performative work dominates corporate engineering teams

In today’s corporate tech landscape, a troubling trend has taken root: performative work often overshadows meaningful engineering. Seasoned engineers at several major companies—including household names in Silicon Valley—have shared firsthand accounts of teams where the majority of effort goes toward activities that management deems impressive, while a select few high-performers quietly advance the company’s actual goals.

This disconnect between perception and productivity is more than just an anecdotal gripe; it’s a systemic issue that risks eroding both morale and innovation. Engineers who spoke anonymously described environments where managers’ calendars are dominated by back-to-back one-on-one meetings with developers, many of which yield little practical value. The result? A workforce that resembles corporate office workers cosplaying as engineers, more concerned with optics than outcomes.

The illusion of progress in large tech firms

Performative work thrives in environments where visibility trumps impact. In some teams, engineers spend disproportionate time creating elaborate dashboards, attending status meetings, or documenting processes that no one reads. While these activities may appear productive to outsiders, they often contribute minimally to the project’s core objectives. Meanwhile, the engineers who deliver functional code, solve critical bugs, or innovate new features often work behind the scenes, their contributions obscured by the noise of performative tasks.

One engineer recalled a project where a manager praised a team for completing a "sprint" filled with non-technical tasks, while the actual codebase remained stagnant. "We were celebrating busywork," they said. "Meanwhile, the real work was happening elsewhere, but no one noticed because it wasn’t flashy."

The role of management in amplifying performative culture

Leadership plays a pivotal role in either reinforcing or dismantling performative work cultures. In many large organizations, managers are incentivized to prioritize metrics that are easy to measure—meeting attendance, document completion, or the number of pull requests—over outcomes like system reliability or user satisfaction. This misalignment creates a perverse incentive structure where employees are rewarded for appearing busy rather than delivering results.

A former engineering director at a Fortune 500 company explained, "When I tried to shift focus to tangible outcomes, I was told my metrics were ‘too hard to track.’ Meanwhile, the team next door was praised for hosting a series of ‘innovation workshops’ that produced no code."

The human cost: demoralization and attrition

The psychological toll of performative work is significant. Engineers who feel their contributions are undervalued or ignored often experience burnout, disengagement, or even attrition. The frustration isn’t just about inefficient processes; it’s about the erosion of professional pride. When high-performers see their work overshadowed by performative tasks, they may question why they’re exerting effort at all.

One software engineer shared, "I left my last job because I realized I was spending more time crafting slides for a quarterly review than writing code. The performative culture had seeped into every aspect of the job, and it wasn’t worth the paycheck."

Breaking the cycle: actionable steps for engineers and leaders

Reversing the trend of performative work requires intentional effort from both engineers and leadership. Engineers can advocate for clearer metrics that align with business outcomes, such as system uptime, feature adoption, or bug resolution rates. They can also push back against meetings or tasks that don’t directly contribute to these goals.

For managers, the solution lies in redefining success. Instead of rewarding activity, they should prioritize impact—whether that’s shipping a critical feature, reducing technical debt, or improving user experience. Some teams have experimented with "no-meeting days" or asynchronous communication tools to reduce performative busywork.

Ultimately, the goal isn’t to eliminate all collaboration or documentation, but to ensure that every task serves a clear purpose. As one engineer put it, "We’re not here to look like engineers; we’re here to be engineers."

The tech industry’s future depends on its ability to distinguish between genuine progress and the illusion of it. For those stuck in performative cultures, the question isn’t whether change is possible—it’s whether anyone is willing to fight for it.