In the aftermath of one of gaming's most cautionary launches, CD Projekt Red is turning to an unlikely instrument of redemption: documentation. The Polish studio, whose Cyberpunk 2077 release became a symbol of ambition outpacing process, is now embedding mandatory checkpoints and 'definition of done' standards into the development of both The Witcher 4 and the Cyberpunk 2077 sequel. It is a quiet but telling act — an acknowledgment that the discipline of recording what has been built is inseparable from the wisdom of knowing how to build well.
CD Projekt Red Implements Strict Documentation Requirements for Witcher 4 and Cyberpunk Sequel
Documentation didn't slow the work down; it sped it up.
Mark
So they're basically saying that Cyberpunk 2077 was such a mess that they need to force people to write things down?
Mimi
Not exactly. The issue wasn't that people didn't know what they were doing—it's that as the project grew, nobody had a single source of truth. Developers would make changes, but the documentation wouldn't get updated, so new people coming in wouldn't know what had actually been decided. It compounds over time.
Luke
But we should be careful here. The article says documentation wasn't mandatory at milestones before. That's one factor in development chaos. There were also crunch, scope creep, and management decisions. Documentation alone doesn't fix those.
Mimi
True, but Ruciński's point about Gwent is concrete: when documentation was current, new team members could contribute faster. That's measurable.
Mark
So they're treating documentation as a tool to speed things up, not just a bureaucratic box to check?
Mimi
Exactly. It's an investment. Yes, someone has to maintain those documents every month. But that cost is offset by not having to re-explain decisions or re-discover what was already decided.
Luke
The question is whether CD Projekt Red will actually enforce this when a deadline looms. Lots of studios have good intentions about process. Fewer stick to them under pressure.
Mark
Fair point. We won't know if this works until The Witcher 4 ships.
Mimi
Right. And even then, we might not know whether it was the documentation that made the difference or just that they learned from Cyberpunk and managed scope better.
Luke
The studio is being smart to apply this to both The Witcher 4 and the Cyberpunk sequel at the same time. If it works, they've got proof across two major projects.
O Pulso
- The ghost of Cyberpunk 2077's disastrous launch — pulled from storefronts, patched for years — still haunts CD Projekt Red's reputation and shapes every decision about what comes next.
- The studio has now made documentation a hard gate at every project milestone, meaning no work advances without a complete and current record of what was done and why.
- Counterintuitively, their own Gwent card game proved that rigorous documentation in a fast-moving live service environment actually accelerated development rather than burdening it.
- The Witcher 4 carries enormous cultural weight after its predecessor became a landmark of the genre, and the studio is betting that operational discipline is the foundation that talent alone cannot replace.
- Whether these structural reforms will hold under the pressure of a major AAA release remains the open question — but the intent to institutionalize hard lessons is clearer than it has ever been.
In the aftermath of one of gaming's most cautionary launches, CD Projekt Red is turning to an unlikely instrument of redemption: documentation. The Polish studio, whose Cyberpunk 2077 release became a symbol of ambition outpacing process, is now embedding mandatory checkpoints and 'definition of done' standards into the development of both The Witcher 4 and the Cyberpunk 2077 sequel. It is a quiet but telling act — an acknowledgment that the discipline of recording what has been built is inseparable from the wisdom of knowing how to build well.
CD Projekt Red is placing a quiet but significant wager: that better documentation can prevent the next catastrophe. The studio, still carrying the reputational weight of Cyberpunk 2077's broken launch — severe enough that Sony removed it from its digital storefront — is now enforcing strict new standards across both The Witcher 4 and the Cyberpunk 2077 sequel.
At this year's Digital Dragons conference, senior technical writer Adrian Fulneczek outlined the new framework. The studio has redefined what 'done' means in practice: every milestone now ends at a checkpoint that requires complete, current documentation before development can move forward. It is the kind of discipline that feels obvious only after its absence has proven costly.
Team lead Jarosław Ruciński noted that such requirements simply did not exist during the production of older titles — including The Witcher 3, which became a celebrated classic despite a development process that nearly derailed it. The new rules are designed to ensure history does not repeat itself across two major projects at once.
The studio already had a working model to draw from. Gwent: The Witcher Card Game was the best-documented project in CDPR's history, and despite the constant churn of a live service game, that documentation proved to be an accelerant rather than a burden — new contributors could orient themselves quickly and begin working without delay.
The Witcher 4 was revealed at The Game Awards in 2024 and has since gone largely quiet publicly. Its predecessor set a towering cultural standard, and the sequel must honor that legacy with both creative ambition and the operational steadiness that earlier projects lacked. Whether these reforms will hold under the full pressure of a major launch remains to be seen — but the studio's determination not to repeat its most painful mistakes has rarely been more visible.
CD Projekt Red is betting that better paperwork can prevent the next disaster. The Polish studio, still living down the Cyberpunk 2077 launch—a game so broken at release that Sony pulled it from digital storefronts—is now imposing strict documentation requirements on both The Witcher 4 and the Cyberpunk 2077 sequel. The move reflects a hard-won lesson: chaos in development leaves scars that no amount of post-launch patching can fully erase.
During a presentation at this year's Digital Dragons conference, senior technical writer Adrian Fulneczek laid out the new approach plainly: the studio has established a fresh definition of what "done" actually means. This isn't abstract philosophy. Every project milestone now ends with a gate—a checkpoint that requires, among other things, complete and current documentation before work can proceed. It's the kind of discipline that sounds obvious in retrospect, which is precisely why its absence in earlier projects proved so costly.
Jarosław Ruciński, who leads the technical writing team, explained that documentation wasn't mandatory at these gates during the production of CD Projekt Red's older titles. The Witcher 3: Wild Hunt, despite becoming one of the most acclaimed open-world role-playing games ever made, suffered from development chaos that could have derailed it entirely. The new requirements exist to ensure that doesn't happen again—and to apply those lessons to both upcoming projects simultaneously.
Interestingly, the studio already had a model for how this could work. Gwent: The Witcher Card Game, the studio's digital card game spinoff, was the best-documented project in the company's history. Ruciński acknowledged the apparent paradox: in a live service environment where the game changes constantly—patches, new content, balance adjustments arriving monthly—documentation seems like a luxury the team can't afford. But that upfront cost of maintaining current documents actually accelerated development. New artists, coders, and designers could jump into any task immediately because they had the information they needed. Documentation didn't slow the work down; it sped it up.
The stakes for The Witcher 4 are substantial. The game was revealed at The Game Awards in 2024, followed by a technical demo that showcased how CD Projekt Red plans to leverage the generational leap since The Witcher 3. Since then, the studio has said almost nothing publicly. The predecessor set a towering standard—a game that, despite its troubled development, became a cultural touchstone. The new sequel has to honor that legacy without trying to outdo it, a delicate balance that requires not just talent but also the kind of operational discipline that documentation enforces. Whether these new requirements will actually prevent another launch crisis remains to be seen, but the studio is clearly determined not to repeat the mistakes that nearly broke its reputation.
Citações Notáveis
We've got some new requirements, especially a new definition of 'done'— Adrian Fulneczek, senior technical writer, CD Projekt Red
In a live service environment, it is easy to say that you don't have the time to document everything, because the game is changing so fast. But somebody has to do that. It is a cost.— Jarosław Ruciński, technical writer team lead, CD Projekt Red
Quer a matéria completa?
Leia o original em Wccftech ↗
General News