Cyberpunk 2077: A Launch-Day Post-Mortem

Archive note: this is a backdated post, written years later while rebuilding this site. It’s dated to the moment it covers, but the hindsight is real.

Cyberpunk 2077 launched on December 10. By December 17, Sony had removed it from the PlayStation Store entirely and started offering refunds — something I cannot remember happening to a AAA release, ever. Microsoft followed with expanded refunds. CD Projekt Red’s stock cratered, the apologies are still rolling out, and “I will gladly take responsibility” is competing for quote of the year.

Eight years of hype. Three public delays. Keanu Reeves on stage. And the most anticipated game of the generation shipped, on PS4 and Xbox One, in a state players describe as broken — crashes, comedy-reel glitches, blurry textures, NPCs T-posing through the apocalypse. On high-end PCs it’s reportedly a different, often great, game. Which makes the whole thing more instructive, not less.

This is a software story, not a game story

I’m writing about it here because everything about this launch rhymes with how software projects fail everywhere:

1. The demo environment lied. The game was shown for years on top-tier PC hardware while being sold primarily to base-model 2013 consoles. Every team has a version of this: it worked on the dev machine, the staging server, the good network. You ship to the hardware your users have, and that’s the only benchmark that counts.
2. Deadlines moved three times, scope didn’t. Delays announced while reportedly still requiring heavy crunch mean the estimate wasn’t wrong by weeks — the plan was wrong structurally. When a date slips repeatedly and the feature list doesn’t shrink, the third date is no more real than the first.
3. They hid the evidence. Review copies were PC-only, console review embargoes effectively held until launch day. That’s not spin; that’s knowing. The cover-up converted a quality problem into a trust problem — and refund programs, store delistings, and possible investor lawsuits are what trust problems cost.
4. Marketing wrote checks engineering had to cash. “It’ll be ready when it’s ready” was the studio’s brand. The pre-order machine made that promise impossible to keep. When sales pressure sets the date, the date wins and the product loses.

The frustrating part: the good game inside

By most accounts there’s a remarkable game in there — Night City’s design, the writing, the quests. That’s what makes this a tragedy instead of a farce. The failure wasn’t talent. It was the gap between what was promised, what was possible, and who was allowed to say so out loud.

If you’ve ever been the developer in the room saying “this isn’t ready” while the launch graphics get finalized — this month was your vindication, at someone else’s expense.

What I’m taking from it

No Man’s Sky came back from a launch like this through years of quiet, ego-free work, so redemption is possible. But the lesson for the rest of us who ship software is cheaper to learn secondhand: the release date is a promise about quality, not just timing. Honest software — like honest people — doesn’t need an embargo.

Wake up, samurai. We have patches to ship.