Übermensch in a Cubicle Farm Pt 3: Golden Handcuffs and Hunger Games
We've been tracing an argument across this series. Post 1 went back to the industrial-era construction of the white-collar professional identity. Post 2 followed that architecture into Silicon Valley, where it got turbocharged with founder mythology and libertarian individualism. Today we get to the mechanisms that made it all stick.
Because the cultural story from Post 2 -- the 10x mythology, the founder aspiration, the mission-carrier identity -- wouldn't have lasted without material reinforcement. The ideology needed a structural foundation, and it got one. Two interlocking mechanisms, in particular, did more to shape tech workers' relationship to their own labor than any amount of Patagonia vests or free lunches.
If you've worked in tech for more than a few years, you've lived inside both of them. This post is about seeing them clearly.
The Equity Architecture
Restricted stock units and options became the dominant compensation mechanism in tech not simply because they were tax-efficient or because they aligned employee and company incentives. They became dominant because they solved several employer problems simultaneously. The retention effect was explicit. The anti-solidarity effect was structural.
The basic design: you receive stock that vests over time, typically four years with a one-year cliff. You own nothing before the cliff. After it, you accumulate quarterly. The equity refresh -- new grants issued annually to keep the unvested total attractive -- extends the retention window indefinitely for high performers.
What this creates is a rolling multi-year financial exposure. At almost any point in a tech worker's tenure, a meaningful amount of unvested compensation is held against their continued employment. This is a retention mechanism, and a sophisticated one, but it's worth being precise about what it is: deferred compensation with conditions attached. The industry's habit of calling it a "grant" -- something extra, something bestowed -- rather than a "wage component with strings" is doing ideological work that's easy to miss from the inside.
For product managers, this structure has a specific wrinkle. PM equity grants tend to sit in a middle tier -- meaningful enough to create retention pressure, rarely large enough to generate the life-changing outcomes that the mythology implied were available to everyone. The compensation was real. The "quasi-owner" psychology it was supposed to generate was real. The actual ownership stake, for most PMs, was modest enough that "owner" was a significant overstatement. The identity was purchased at a discount.
The deeper effect: once unvested equity is a significant portion of your total compensation, the company's performance becomes your performance. A strong quarter feels personal. A rough patch feels threatening. You are no longer an employee evaluating whether your employer is treating you well relative to alternatives. You are a stakeholder hoping for appreciation. That psychological shift is, from an employer's standpoint, enormously valuable. It is also the thing that makes collective reflection about working conditions feel like self-sabotage.
The Tournament Structure
If equity compensation recruited tech workers into a quasi-ownership identity, stack ranking did something more direct: it made peer solidarity structurally irrational.
The vitality curve, formalized by Jack Welch at GE, works by sorting employees into performance tiers annually -- top performers, middle, and a bottom cohort that gets managed out, every cycle, regardless of absolute performance. The critical feature is the forced distribution: your rating is not purely about how good you are. It is about how good you are relative to your peers. In a fixed distribution, your colleague's strong performance is, materially, a competitive threat to your own rating.
Microsoft ran this system for over a decade. A 2012 Vanity Fair investigation documented the predictable result: engineers avoiding teams with other strong performers, because a talented peer group meant competing against talented people for a finite pool of high ratings. The rational individual move was to work alongside people you could outshine. The system had engineered the erosion of collaborative instinct at the structural level. Microsoft abandoned stack ranking in 2013, acknowledging publicly what insiders had known for years.
The lesson was not generalized. The rest of the industry continued running variants of the same logic under different names: "performance calibration," "relative assessment," "leveling consistency." The distribution math survived the rebranding.
For product management, this system has always been particularly punishing, and the reason is structural. PM performance is genuinely hard to measure in isolation. The output of a PM is a team's output -- shipped product, adoption, business outcomes -- and isolating the PM's individual contribution from the engineering, design, and marketing work around them requires judgment calls that are inherently political. The calibration session, where managers advocate for their reports against each other, is where PM careers are actually made or damaged. The process is opaque, the criteria are partially subjective, and the outcome is described as objective assessment.
Most PMs know this, at some level. Fewer examine what it means structurally: that your career advancement is partly a function of your manager's political capital and advocacy skill, not just your work. And that the people across the table in that calibration session are your peers, who are doing the same work with the same constraints, but whose advancement is in competition with yours.
The Interaction Effect
RSUs and stack ranking, together, produce something more specific than either does alone.
Equity compensation makes you financially dependent on your continued employment at this specific employer, with unvested stock as the anchor. Stack ranking makes the peers who are your most natural allies your material competitors. The interaction: you are simultaneously too financially exposed to risk the disruption that collective action would bring, and too structurally competitive with your peers to develop the shared-interest consciousness that collective action requires.
This was not designed as an anti-organizing system. It was designed to retain employees and motivate performance. The anti-solidarity effects were structural byproducts that nobody in a position to change them had much incentive to address.
The outcome is identical either way. A workforce that is financially tethered to its employer and structurally competitive with its peers is a workforce that is very unlikely to develop collective responses to shared problems. Which means individual optimization becomes the only available strategy, even when the problems are collective ones.
What Didn't Scale
This system worked, in a constrained sense, during the growth era. The four-year vest cage is tolerable when the underlying equity appreciates substantially. The performance tournament is tolerable when being in the top tier means genuinely significant financial outcomes. The system was calibrated for a specific period of hypergrowth, and it delivered real rewards to enough people that the constraints felt manageable.
The stress test came when the industry massively expanded its workforce through the mid-to-late 2010s, bringing in a large cohort for whom the mythology held but the underlying math had changed. The equity was real, the vesting schedule was real, the performance tournament was real -- but the outcomes for median performers in a maturing industry were considerably less dramatic than the founding mythology implied. The implicit contract -- perform well and the rewards will be commensurate -- was increasingly requiring careful reading of the fine print.
For product management specifically, this era produced a large population of competent practitioners working in roles the mythology had framed as stepping stones to something else, in an industry that was running out of the next thing to step to. The 2022-2023 layoff cycle didn't create that problem. It just made it visible.
That's our next stop.
Next: "The Ticket Queue Is Not a Career" – the SaaS era, the CS degree bubble, the bifurcation nobody named, and the layoff cycle that cracked the implicit contract open.
