CD Projekt's New Documentation Strategy: How Witcher 4 and Cyberpunk 2 Are Being Built Differently

Introduction: From Chaos to Order in Game Development

When CD Projekt Red unveiled their plans for The Witcher 4 and Cyberpunk 2, the buzz centered on Unreal Engine 5’s visual prowess and rumors of returning characters. Yet behind the scenes, a far less glamorous but equally vital transformation is underway: a complete overhaul of how the studio documents its development. For decades, CD Projekt’s internal records were a source of frustration—missing lore bibles, abandoned tool guides, and sketchy design notes that forced developers to reinvent the wheel. Now, with a new production process mandating that all internal documentation be kept meticulously up to date, the studio aims to build a more resilient foundation for its flagship franchises.

This shift, detailed by technical writer team lead Jarosław Ruciński and senior technical writer Adrian Fulneczek at the Digital Dragons conference in Kraków, reflects a hard-won lesson. From the troubled launch of Cyberpunk 2077 to delays on Phantom Liberty and the upcoming Witcher remake by Fool’s Theory, poor documentation has repeatedly sabotaged progress. The new approach promises to break that cycle.

The Chaos of the Past: Documentation Failures That Plagued CD Projekt

To understand the importance of the new system, one must look back at the consequences of neglect. Over the past 20 years, CD Projekt experienced a revolving door of talent. When key lorekeepers or tool experts left, their knowledge often went with them. “It was chaos,” recalled a senior developer familiar with the process. For example, the narrative bible for The Witcher series—a comprehensive guide to characters, factions, and timelines—was not consistently maintained. When a new writer joined the team for Cyberpunk 2077’s Phantom Liberty expansion, they had to piece together foundational lore from scattered emails and outdated documents.

Another pain point was the shelving of internal tools. To cut costs, the studio abandoned several proprietary utilities that streamlined asset creation. When later projects needed those tools, no one remembered how they worked, and the documentation was either missing or incomplete. This inefficiency contributed to production bottlenecks and even forced the team to redo work already completed in earlier engines.

The issue extended to external partners. Fool’s Theory, the team behind the upcoming Witcher remake, faced delays because CD Projekt could not provide a coherent archive of original design decisions. As Fulneczek noted, “You can’t outsource development without clear records. We learned that the hard way.”

Learning from Mistakes: A Standardized Documentation Pipeline

The solution, implemented for The Witcher 4 and Cyberpunk 2, is a rigorous new production process that demands developers update their notes at every milestone. Whether it’s a narrative bible, a tool guide, or a folder of concept sketches, every piece of internal knowledge must be logged and version-controlled. The process applies to all disciplines—writers, artists, programmers, and designers—ensuring that no departure or team restructuring can derail progress.

Ruciński emphasized that this isn’t about bureaucracy but about empowering creativity. “When you have confidence that the foundational information is correct, you can focus on innovation,” he said. Key elements of the pipeline include:

• Centralized repositories for all documentation, accessible to any team member with proper clearance.
• Mandatory updates at each development milestone, reviewed by technical writers to ensure clarity and completeness.
• Cross-referencing systems that link design documents with code repositories and art assets.
• Living documents that evolve with the project, rather than static files that become obsolete.

The role of technical writers has been elevated from peripheral editors to integral project coordinators. They work alongside leads to flag gaps in documentation and help teams maintain consistency across the sprawling narratives of The Witcher 4 and Cyberpunk 2.

The Role of Technical Writers: Insights from the CD Projekt Team

Both Ruciński and Fulneczek highlighted that their team’s value goes beyond writing. They conduct documentation audits to identify missing or redundant information, and they run workshops to teach developers best practices. “It’s about changing the culture,” Fulneczek explained. “In the past, documenting was seen as a chore. Now it’s part of the job, just like coding or designing.”

The shift has already produced measurable improvements. For instance, during the pre-production of Cyberpunk 2, the technical writing team discovered an outdated timeline for key factions. By correcting it early, they prevented a chain of errors that would have required massive rework later. Similar wins are expected for The Witcher 4, which weaves together multiple timelines and character arcs.

Why Documentation Matters: A Stronger Foundation for Future Games

Beyond immediate efficiency, the new system is designed to serve future sequels and spin-offs. With The Witcher 4 set to launch a new saga and Cyberpunk 2 expanding its universe, the documentation will act as a reusable asset. Developers working on later games will have access to complete archives, reducing onboarding time and preserving creative vision.

Consider the Witcher remake by Fool’s Theory: had proper documentation existed for the original game’s systems and story, external development could have proceeded more smoothly. CD Projekt’s new approach aims to eliminate such friction for all future collaborations. “We’re building a library, not a stack of sticky notes,” Ruciński said.

This investment in documentation also protects against talent turnover. The gaming industry is notorious for high employee mobility, and CD Projekt is no exception. By capturing knowledge as it’s created, the studio ensures that institutional memory survives even when key individuals leave.

Conclusion: A Hard Lesson, Finally Learned

The journey from chaos to order has been painful for CD Projekt, but the studio now stands as a case study in the power of comprehensive internal documentation. For gamers eagerly awaiting The Witcher 4 and Cyberpunk 2, the new process means fewer delays, richer stories, and more polished experiences. Behind every stunning screenshot and deep quest line now stands a simple but powerful foundation: a document that was kept up to date, one milestone at a time.

As the industry watches, CD Projekt Red’s experiment may well become a blueprint for other studios grappling with the same challenges. After two decades of trial and error, the message is clear: document early, document often, and build a legacy that can be passed down.