# The Evolution of Documentation in Game Development: Lessons from CD Projekt Red
As the gaming industry rapidly evolves, so too does the approach to development processes. Two significant upcoming titles, *The Witcher 4* and *Cyberpunk 2*, from CD Projekt Red have gained considerable attention not only for their advanced features utilizing Unreal Engine but also for a vital aspect often overlooked—documentation. Unlike previous titles in these franchises, the development of these games will be characterized by rigorous internal documentation practices that promise to lay a stronger foundation for future projects.
## A New Era of Development Documentation
CD Projekt Red has reflected on its past experiences, particularly the development of *Cyberpunk 2077* and earlier iterations of *The Witcher*, to recognize the importance of thorough documentation. Technical writer team lead Jarosław Ruciński and senior technical writer Adrian Fulneczek discussed at the Digital Dragons conference the lessons learned from the studio’s 20-year history. They emphasized that adequate documentation would be fundamental to avoiding the pitfalls that plagued previous projects.
The studio’s shift to a structured documentation process addresses challenges encountered during past releases, where lack of organized internal knowledge led to complications and inefficiencies, particularly evident during the development of *Cyberpunk 2077* and the *Witcher* remake.
## Acknowledging Historical Shortcomings
Ruciński noted that as the studio transformed from a small team to a large operation with over a thousand employees, the sheer scale of projects made relying on collective memory inadequate. In their early days, knowledge was passed around informally, relying on “tribal knowledge.” This meant when key individuals left the company, essential information often vanished with them.
Fulneczek illustrated the consequences of inadequate documentation through the chaotic development scenes of the *Witcher 3* and *Cyberpunk 2077*. The shutdown of the team’s internal wiki after the completion of *The Witcher 3* exemplifies a significant misjudgment—one that ultimately led to gaps in knowledge and understanding when new tools and expansions were being developed.
Ruciński’s poignant remark, “the reality is that information, it has a half-life,” encapsulates the inevitability of knowledge degradation without proper documentation. As a consequence, developers faced extended periods of trial and error, drastically reducing productivity and increasing frustration.
## The Importance of Documenting Processes
The development of *Cyberpunk 2077* served as an empirical case study in the necessity of comprehensive documentation, especially in large-scale projects. Fulneczek recounted how the complexities and the extensive changes during development created over 8000 pages of documentation. Unfortunately, the prioritization of immediate project deadlines meant that documentation took a backseat, contributing to severe complications during the game’s launch.
Recognizing this shortcoming led to a significant policy change for *The Witcher 4* and *Cyberpunk 2*. Each development phase will now culminate in a documentation “gate,” a stage that ensures comprehensive records are maintained and accessible before moving forward. This systematic approach guarantees that knowledge is not only documented but also readily available to all development teams involved, promoting cross-pollination of ideas and solutions.
## A Collaborative Knowledge Base
The new approach emphasizes collaboration and ease of access to information. Both teams developing *The Witcher 4* and *Cyberpunk 2* will utilize the same knowledge repository. This ensures that any solutions discovered by one team can be quickly adopted by the other. As Ruciński highlighted, this method is particularly beneficial for a global studio operating across different time zones, where reliance on real-time communication can falter.
Ruciński’s insights shed light on the exciting potential for immediate benefits that robust documentation can offer. Instead of viewing documentation solely as a long-term asset meant for future reference, it can also be a powerful tool that expedites current productivity, inspiring a faster development culture.
## Conclusion: A Lesson in Documentation
The experiences of CD Projekt Red serve as a critical reminder in the gaming industry: effective documentation is not merely a bureaucratic necessity but a foundational element that can significantly influence project outcomes. As the studio embarks on the development of *The Witcher 4* and *Cyberpunk 2*, their commitment to rigorous documentation illustrates a forward-thinking approach that recognizes the lessons learned from past challenges.
In a field where the landscape can rapidly shift, having organized and accessible knowledge ensures sustained innovation and creative solutions, empowering developers to build upon the wisdom of their predecessors while avoiding the pitfalls of historical amnesia. Thus, while the folklore of woodland monsters and the thrill of dystopian narratives captivate players, the unseen scaffolding of documentation will be instrumental in sculpting the future of the *Witcher* and *Cyberpunk* worlds.
