Lessons from Chaos: How CD Projekt's New Documentation Strategy Shapes The Witcher 4 and Cyberpunk 2
Introduction
When CD Projekt Red announced The Witcher 4 and Cyberpunk 2, the focus naturally fell on flashy Unreal Engine demos and rumors of returning characters. But one of the most transformative changes behind the scenes is far less glamorous—and far more essential: a rigorous new approach to internal documentation. After decades of mismanaged notes, lost lore, and shelved tools, the studio is finally turning a chaotic legacy into a structured foundation for its next-generation titles.
The Cost of Poor Documentation
For years, CD Projekt relied on informal, scattered documentation methods. Key narrative bibles, tool guides, and concept sketches were often incomplete or stored in ways that made them nearly impossible to find when needed. This approach created cascading problems: when veteran developers or lorekeepers left the company, their knowledge vanished with them. The result was repeated inefficiencies, rework, and delays.
Case Study: Phantom Liberty’s Hidden Hurdles
The development of Cyberpunk 2077: Phantom Liberty was particularly affected. Teams had to reconstruct design decisions from memory because milestone notes were spotty or contradictory. This not only slowed down production but also introduced inconsistencies in the game’s world-building and mechanics. Similarly, the upcoming Witcher remake being developed by Fool’s Theory has uncovered gaps in the original trilogy’s documentation, forcing reverse‑engineering of system designs that should have been preserved.
Shelved Tools, Hidden Costs
Another major issue was the practice of shelving internal tools to cut short‑term expenses. Without proper records, those tools—some essential for asset creation, animation, or scripting—became unusable or required costly reconstruction. This cycle of save‑now, pay‑later sapped resources that could have been directed toward innovation and polish.
A New Production Process: Disciplined Documentation from Day One
To break the cycle, CD Projekt Red has implemented a mandatory documentation protocol for both The Witcher 4 and Cyberpunk 2. The new process requires developers to update their internal notes regularly—at every milestone. Whether it’s a narrative bible, a technical guide for a new tool, or a folder of concept sketches, every piece of information must be kept current and accessible.
The Role of Technical Writers
This shift is overseen by a dedicated team of technical writers led by Jarosław Ruciński and Adrian Fulneczek. During a presentation at Digital Dragons in Kraków, they explained that the team works directly with developers to create and maintain “living documents.” These are not static PDFs but evolving wikis and databases that are version‑controlled and searchable. The goal is to ensure that any developer—new or tenured—can find the information they need without interrupting the workflow of others.
Benefits of Living Documents
- Preserving Institutional Knowledge: When employees leave, their contributions remain in a structured, well‑indexed format.
- Reducing Onboarding Time: New hires can get up to speed by consulting centralized documentation instead of relying on word‑of‑mouth.
- Enabling Cross‑Team Collaboration: Narrative, art, and engineering teams can align their work by referencing the same source of truth.
- Future‑Proofing Franchises: Sequels and spin‑offs (like the Witcher remake) will have a clear blueprint of previous decisions.
Building a Stronger Foundation for The Witcher and Cyberpunk Futures
Beyond just fixing past mistakes, the new documentation strategy is designed to be a long‑term asset. Both The Witcher 4 and Cyberpunk 2 are intended to serve as launchpads for subsequent games and expansions. With comprehensive records, CD Projekt can rapidly iterate on existing systems without revisiting old debates or redoing lost work.
Integration with Unreal Engine
The transition to Unreal Engine 5 adds another layer of complexity—and opportunity. The documentation teams are creating specialized guides that map CD Projekt’s proprietary workflows onto the new engine. This ensures that the technical foundation of both games is not only well‑documented but also scalable as the studio grows its portfolio.
Conclusion
While fans eagerly await gameplay trailers and story reveals, the real breakthrough for CD Projekt Red may be happening in the background: a cultural shift from chaotic knowledge hoarding to disciplined sharing. As Ruciński and Fulneczek noted, “Documentation is not a burden; it’s the scaffolding that lets creativity stand tall.” If this new process succeeds, The Witcher 4 and Cyberpunk 2 will be remembered not just as great games, but as the catalysts for a smarter, more sustainable way of making them.