{"id":34697,"date":"2026-05-19T12:23:04","date_gmt":"2026-05-19T12:23:04","guid":{"rendered":"https:\/\/gaitgames.com\/?p=34697"},"modified":"2026-05-19T12:23:04","modified_gmt":"2026-05-19T12:23:04","slug":"lessons-from-cd-projekts-documentation-mistakes-insights-for-the-witcher-4-and-cyberpunk-2","status":"publish","type":"post","link":"https:\/\/gaitgames.com\/?p=34697","title":{"rendered":"“Lessons from CD Projekt’s Documentation Mistakes: Insights for The Witcher 4 and Cyberpunk 2”"},"content":{"rendered":"
<\/a><\/div>\n

# The Evolution of Documentation in Game Development: Lessons from CD Projekt Red<\/p>\n

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\u2014documentation. 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.<\/p>\n

## A New Era of Development Documentation<\/p>\n

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\u0142aw Ruci\u0144ski and senior technical writer Adrian Fulneczek discussed at the Digital Dragons conference the lessons learned from the studio\u2019s 20-year history. They emphasized that adequate documentation would be fundamental to avoiding the pitfalls that plagued previous projects. <\/p>\n

The studio\u2019s 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.<\/p>\n

## Acknowledging Historical Shortcomings<\/p>\n

Ruci\u0144ski 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 \u201ctribal knowledge.\u201d This meant when key individuals left the company, essential information often vanished with them.<\/p>\n

Fulneczek illustrated the consequences of inadequate documentation through the chaotic development scenes of the *Witcher 3* and *Cyberpunk 2077*. The shutdown of the team\u2019s internal wiki after the completion of *The Witcher 3* exemplifies a significant misjudgment\u2014one that ultimately led to gaps in knowledge and understanding when new tools and expansions were being developed.<\/p>\n

Ruci\u0144ski\u2019s poignant remark, \u201cthe reality is that information, it has a half-life,\u201d 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.<\/p>\n

## The Importance of Documenting Processes<\/p>\n

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\u2019s launch.<\/p>\n

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 \u201cgate,\u201d 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.<\/p>\n

## A Collaborative Knowledge Base<\/p>\n

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\u0144ski highlighted, this method is particularly beneficial for a global studio operating across different time zones, where reliance on real-time communication can falter.<\/p>\n

Ruci\u0144ski’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.<\/p>\n

## Conclusion: A Lesson in Documentation<\/p>\n

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.<\/p>\n

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.<\/p>\n","protected":false},"excerpt":{"rendered":"

<\/a><\/div>\n

\nThe Witcher 4<\/a> and Cyberpunk 2 have gotten ample attention for their whizbang Unreal Engine features<\/a> and potential major cast resurrections<\/a>, but one of their key ‘enhancements’ may seem horribly dry: their creation will be much, much<\/em> better documented than any Witcher or Cyberpunk game before. This also means that they will be a stronger foundation for Witcher and Cyberpunk games to come<\/a>. Both games are following a new production process that obliges the devs to keep their internal development notes up to date, from milestone to milestone \u2013 whether it be a narrative bible, a tool guide or a folder of sketches.<\/p>\n

As technical writer team lead Jaros&lstrok;aw Ruci&nacute;ski and senior technical writer Adrian Fulneczek explained during a presentation at this year’s Digital Dragons conference in Krak\u00f3w, CD Projekt have learned the value of good internal documentation the hard way over the past 20 years, with company lorekeepers departing and crucial tools shelved to cut costs, sabotaging work on everything from Cyberpunk 2077<\/a>‘s Phantom Liberty DLC to the forthcoming Witcher remake at Fool’s Theory.\n<\/p>\n

Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":34698,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"Default","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-34697","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/gaitgames.com\/index.php?rest_route=\/wp\/v2\/posts\/34697","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gaitgames.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gaitgames.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gaitgames.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/gaitgames.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=34697"}],"version-history":[{"count":0,"href":"https:\/\/gaitgames.com\/index.php?rest_route=\/wp\/v2\/posts\/34697\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/gaitgames.com\/index.php?rest_route=\/wp\/v2\/media\/34698"}],"wp:attachment":[{"href":"https:\/\/gaitgames.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=34697"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gaitgames.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=34697"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gaitgames.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=34697"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}