Table of Contents:
- The Price of Ambition: How God of War Reimagines the Gaming Industry
- Playtests: Guerrilla Games' Experience and Their Impact on Development
- An Innovative Approach to Playtesting in the Gaming Industry
- Playtest Frequency: The Key to Success
- The Diversity of Playtest Types in Game Development
- Effective Feedback from Testers
- Development Lessons Learned: The God of War Team's Experience
- Player Feedback and the Game's Final Scene (Spoiler alert!)
- Pizza with Olives: How Reviews Influence Game Development
- Analysis of Difficulty Levels in Playtests
- The Importance of Playtests in Game Development

Game designer from scratch to PRO: 7 steps to success
Find out moreThe Price of Ambition: How God of War is Reimagining the Gaming Industry

Early in the development of God of War, it became clear that the creation process would require significant effort. Creative Director Cory Barlog brought a fresh perspective to the franchise that impacted every aspect of the project. This innovative approach to game design and narrative formed the foundation for a reimagined experience that attracted both long-time fans and new players. Every element of the game, from combat mechanics to storytelling, was reimagined to create a unique and memorable experience.
The main changes to the project included the introduction of an innovative combat system and a unique camera system that operates in single-shot mode. This innovation required the team to be creative and deeply understand the technical capabilities of the PlayStation 4, as this was Santa Monica Studio's first project for this console. As a result, the game acquired a unique style and dynamism, making it appealing to a wide audience of gamers.
Despite all the innovations, the developers faced an important question: "Is this still God of War?" This question came up repeatedly during the lengthy pre-production process, which lasted longer than planned.

By 2016, the developers had begun creating an alpha version, which, unfortunately, did not meet player expectations. The game felt dull and disjointed, and the lack of narrative elements only made this perception worse. With limited time, the team urgently needed to make changes and improvements to make the project more appealing and engaging for the audience.
Key gameplay changes in God of War significantly updated the gameplay, offering players a unique experience. One of the main changes was the switch to a third-person view, which allows for deeper immersion in the game's atmosphere and better interaction with the environment. Combat became more tactical, thanks to a new control mechanism that involves the use of skills and abilities, not just simple attacks.
Furthermore, the character and weapon leveling system gave players more options to customize their playstyle. The removal of fixed levels and the shift to open environments allowed for more fluid and dynamic gameplay. Puzzle-solving mechanics and world exploration also received significant updates, adding new elements of interaction and strategy.
These changes make God of War more engaging and rich, providing players with new experiences and opportunities to explore the game's rich world.
The game combines RPG and action elements, focusing on character development and interaction with the environment. As players progress, they can improve their character's skills, explore fascinating locations, and interact with various objects and characters. This creates a unique gaming experience that allows each player to develop their own strategy and approach to progression.
The alpha version of God of War was released in 2017. This game, a continuation of the renowned series, attracted players with its innovations, gripping storyline, and stunning graphics. Following the adventures of Kratos and his son Atreus, God of War introduced a new interpretation of mythology and deep emotional connections between its characters. The success of the alpha marked a major step toward the full game's release, which received acclaim from critics and players worldwide.
The alpha completed in 2016, marking a key milestone in its development. This phase allowed the developers to test key features and mechanics and gather feedback from early players. Completing the alpha opened new horizons for further improvement and optimization of the gameplay, which in turn increased interest in the project among gamers.
For more information about the God of War development process, visit the official Santa Monica Studio website. You can also find useful materials on IGN, which features news, interviews, and articles dedicated to this iconic franchise.
Playtesting: Guerrilla Games' Experience and Their Impact on Development
To effectively evaluate gameplay, the development team actively uses playtests. This is especially important for Santa Monica Studio, which has been striving to improve its testing methods since the release of the original God of War in 2005. As Ed Darien points out, playtests previously did not always produce the expected results, since tester feedback often merely confirmed existing facts, without offering fresh ideas or constructive criticism. However, modern approaches to playtesting allow for a deeper understanding of player needs and identify aspects requiring improvement, which significantly impacts the quality of the final product.
With the transition to development of the new God of War part, doubts arose about the need for playtests, given the ineffective previous experience. In this context, the experience of our colleagues at Guerrilla Games was helpful. Their difficulties in transitioning from the linear design of Killzone to the open world of Horizon: Zero Dawn provided a valuable lesson. They also encountered similar problems and were able to find effective solutions. Guerrilla Games' experience emphasizes the importance of testing and adaptation during the development process, which can significantly improve the quality of the final product.

Santa Monica Studio decided to attract professionals from the department SIE UX research to improve their project. According to Ed Darien, specialists, in particular Kevin Kicker, SIE's lead UX researcher, played a significant role in this process. Their recommendations and methods for analyzing user experience significantly improved the quality of development and contributed to the creation of a successful game product. As a result of this collaboration, it was possible not only to optimize processes but also to better understand player needs, which ultimately reflected in the positive perception of the finished game.
An Innovative Approach to Playtesting in the Gaming Industry
Modern game developers are faced with the need to rethink the playtesting process. A key aspect of this process is understanding its goals. The main goal of playtests is to validate the decisions made by developers. However, not every tester's feedback should become a reason for changes. For example, if a player expresses dissatisfaction with the new look of Kratos, this should not always be considered justified, since such a design may be part of the original concept of the game. It's important to consider when player feedback indicates that the image doesn't match the intended vision, as this may become the basis for adjustments. Thus, the proper use of playtests allows developers to create higher-quality games that meet user expectations.

According to recent data, developers have defined the primary objectives of playtests. This facilitates more targeted and effective data collection from testers. Clearly defining goals improves the quality of testing and significantly accelerates the process of identifying and fixing product bugs. This makes the development and execution of playtests more productive, which ultimately has a positive impact on the final result and user satisfaction.
Feedback should be specific and quantifiable. Previously, developers limited themselves to general questions to testers about interface usability, but now deeper and more detailed feedback is required. This allows for the identification of root causes of problems and the implementation of necessary improvements. This approach to collecting feedback not only improves product quality but also promotes more effective interaction between the development team and users.
Playtests are becoming a key element in the game development process, and teams have begun to create specialized groups to optimize them. For example, Santa Monica Studio has formed a dedicated team led by Cory Barlog that quickly responds to development changes. This allows them to improve the quality of their games based on player feedback and adapt processes in real time.
The Santa Monica Studio team conducts additional tests with minor adjustments to evaluate the effectiveness of the changes. This approach provides greater control over the process. After each test session, final briefings are held to discuss tester feedback and generate ideas for future tests. This helps optimize the development process and improve the final product.
Playtest Frequency: The Key to Success
Determining the frequency of playtests is a key step in game development. Regular playtesting provides developers with timely feedback and confidence in the direction they are taking. Establishing a stable testing schedule allows for targeted changes to the game and a deeper analysis of its individual elements. Experience shows that it's impossible to perfectly refine any aspect in a single iteration, so regular playtests become the foundation for achieving high-quality results. This not only helps identify weaknesses, but also contributes to improving the gameplay, which ultimately leads to a more attractive and engaging product for users.

The Variety of Playtest Types in Game Development
Playtests organized by Santa Monica Studio are divided into two main types: unguided and usability testing. These methods are important stages in the development process, giving the team the opportunity to discover and fix flaws early on, before the game is released to market. Unguided playtests allow players to interact with the game without restrictions, which provides valuable information about internal perception and gameplay. Usability testing focuses on assessing the usability and accessibility of the interface, which contributes to the creation of a more intuitive and attractive product. Both types of testing contribute to the improvement of the game quality and increase user satisfaction, which is critical for a successful launch.
Unguided playtests are designed to comprehensively evaluate the game, allowing developers to observe player behavior in a natural gaming environment. A key aspect of these tests is minimal intervention by the development team, which contributes to a more realistic gaming experience. This approach helps identify various game issues, including narrative flaws, difficulty imbalances, and issues related to the economy and progression. Conducting open playtests is an important stage in the development process, as they provide valuable feedback and help improve the quality of the final product. Based on the data collected during open playtests, the team develops more detailed usability tests. These sessions are aimed at analyzing specific aspects identified in previous tests. For example, if a test participant reports low engagement with the combat system, this could be due to various factors, such as camera responsiveness or mechanic balancing. To achieve maximum effectiveness in usability tests, the developers strive to minimize the influence of extraneous factors in order to focus on analyzing the content being tested and improving the user experience. This allows for more intuitive and engaging game mechanics, which in turn contributes to increased user satisfaction and product success in the marketplace.

Unlike free playtests, usability testing is conducted in the format of individual sessions with members of the UX team. During these meetings, players actively share their opinions and provide feedback, which helps the team better understand the perception of the game and its key elements. This approach helps identify the strengths and weaknesses of the gameplay, as well as optimize the interface and improve the user experience. Usability testing is an important tool for improving the quality of the game and user satisfaction.
Efficiently collecting feedback from testers
The development team implemented an effective system for collecting and classifying tester feedback, which significantly optimized the process of obtaining valuable information. All comments were divided into two main categories: open-ended and directed feedback. This allowed for a more accurate analysis of feedback and improvement of the quality of products based on the data obtained.
Open-ended feedback gives players the opportunity to independently highlight important points and share them through a special function known as the "red button". Directed feedback, in turn, is based on the results of targeted surveys conducted by the development team. However, the developers strive to minimize the use of directed feedback to avoid causing unnecessary concerns among testers about potential problems in the game. This approach allows for more honest and open communication between players and developers, which in turn improves the quality of the gaming experience.

The collected data was structured into tables, allowing the team to easily analyze the game elements that most attracted players. One of the key tasks was tracking the ratio of positive to negative feedback. This allowed for a more in-depth assessment of various aspects of the game and the effective allocation of resources for further development. This approach ensures the optimization of game mechanics and an improved user experience.

During the development of the playtesting system, Darien I identified four key elements to consider. These elements play a vital role in successfully creating and implementing effective tests. By paying attention to each of these aspects, you can significantly improve the quality of your testing and improve your results. Understanding these key components will help you optimize your playtesting process and achieve your goals.
- Playtest objectives should be clear and measurable.
- Test frequency should be defined in advance and adhered to strictly so that other developers can count on receiving important information.
- Use different types of playtests to solve specific problems.
- When collecting data, it is important to keep the interests of the entire team in mind to provide them with relevant and up-to-date information.
Development Lessons Learned: The God of War Team's Experience
The team at Santa Monica Studio, responsible for developing God of War, faced many unique challenges that require separate discussion. These challenges relate to both technological aspects and the creative decisions required to create a game that would satisfy fans and attract new audiences. Innovative approaches to character design, story development, and gameplay improvements were crucial aspects the team overcame on the path to creating a successful project. Discussing these challenges can provide profound insight into how great games are born and what drives their success.
One of the game's major issues was the boating mechanic. Originally intended as a tool for open-world exploration, resource gathering, story progression, and combat, the final version of God of War does not include boat combat elements. This proved a difficult decision, as combat has always played a central role in the series.
In the early stages of the alpha build, boat control proved unintuitive and was missing important narrative elements that make boating engaging. This led to negative feedback from testers. The discussions resulted in serious disagreements: the developers were faced with a choice between restoring the combat mechanics on the boat or completely excluding this element from the gameplay.

The problem was exacerbated by testers noting an excessive number of boat-related sequences where the controls weren't precise enough. In response, the development team made a number of changes to the control mechanics, making sailing more comfortable and responsive. These improvements provide better interaction between players and the gameplay and contribute to the overall quality of the gaming experience.

An interesting situation arose during testing: the moorings broke, and the developers assisted the testers in exiting the boat. During one of the playtesting sessions, a playtester stopped at the mooring and was in no hurry to leave the vessel. The developers initially thought the game had frozen, but soon discovered the player simply wanted to hear the story to the end. This moment demonstrated to the team that the game's narrative element was truly effective, and that the boat's presence in the gameplay could be successful even without combat encounters.
This story highlights the importance of paying close attention to feedback, especially during the development of a design concept that has not yet been fully implemented. Correctly perceiving and promptly responding to comments can significantly impact the final result and quality of the project. It is important to consider the opinions of users and experts to create a truly successful and engaging product.
Player Feedback and the Game's Final Scene (Spoiler Alert!)
A key element that underwent changes as a result of playtesting was the game's ending. At the climax, when Kratos defeats the antagonist Balder, his mother Freya vows to take brutal revenge on the hero. Some playtesters expressed the opinion that Freya is a villain. However, the writers did not intend to create a villain. Freya, as a loving mother, is simply reacting to the profound loss of her son, which highlights her human feelings and motivations. This adds depth to her character and makes the conflict more multi-layered.

For a better understanding of this The developers implemented a dialogue between Kratos, Atreus, and Mimir in the scene. Atreus inquires about Freya's anger. They explain that it's not just anger, but a natural reaction that only parents can understand. This approach helps to further explore the characters' emotional experiences and show the complex relationships in the game.
Atreus's expression in this context illustrates the opinion of testers. This situation highlights the importance of paying close attention to feedback, as it may indicate that some players are misperceiving key plot points. This underscores the need to carefully analyze feedback to improve understanding of the story and create deeper interactions with players.
Pizza with Olives: How Feedback Influences Game Development
Recent game testing yielded one of the most memorable moments—a tester's feedback, which became a real meme in the studio. He expressed dissatisfaction with the new development direction, comparing playing God of War to receiving a pizza topped with olives when he expected a meat topping. This striking example highlights the importance of considering player expectations when developing new titles, which can significantly impact the game's success and audience satisfaction. By listening to testers, developers can better understand what players really want, which ultimately leads to a more engaging and successful product.

Frank feedback can be extremely beneficial to the development process. It's clear that this tester is a devoted fan of the original games, which differ significantly from the reboot in both story and mechanics. Recognizing this fact allows the developers to more accurately tailor the game to the expectations of their target audience, which can ultimately lead to a more successful and engaging product. It's important to consider player feedback to improve the gaming experience and meet their requirements.
The developers realized that not all players would be enthusiastic about the new vision of the game, and that's completely normal. In creating the new project, they decided to focus on narrative and integrate puzzle elements. However, such changes don't always evoke positive reactions. Ed Darien, one of the lead developers, offered a strategic approach to negative feedback. Specifically, the team rebalanced the gameplay mechanics, increasing the number of combat scenes early in the game to meet the expectations of players seeking the dynamic action typical of the original titles. This decision is aimed at creating a more harmonious gaming experience that combines storytelling and action elements, which is likely to attract both existing fans and new players.
Difficulty Level Analysis in Playtests
An interesting incident occurred during one of the most recent gameplay testing sessions. The introduction of difficulty levels into the game's build delighted the combat system designers, as it allowed them to clearly assess how these levels work in practice. Previously, the developers had used a single balanced difficulty, which prevented them from objectively testing this important aspect of the game. The new difficulty system opened up new horizons for analyzing and improving the gameplay experience, revealing the strengths and weaknesses of its mechanics.
One tester presented a detailed analysis of the combat mechanics, detailing scenarios, battle arenas, and enemy archetypes. The designers were inspired by such in-depth and insightful material. However, it soon became apparent that the player was playing the test episode on the lowest difficulty level.
The development team learned several key lessons from this experience. First, critical gameplay aspects such as difficulty levels should be tested early in development. Second, it's worth noting that difficulty level isn't always directly related to gameplay enjoyment. This highlights the need for careful evaluation of all game elements to create a high-quality and engaging product.

Meaning Playtesting in Game Development
According to game development expert Ed Darien, playtests play a key role not only in confirming the team's vision but also in deeply evaluating its implementation. This stage is critical, as it allows for the identification of both the strengths and weaknesses of the gameplay. Playtesting contributes to improving the quality of the game and increasing its appeal to the target audience.
Ed emphasizes the importance of making playtests accessible to the entire development team. Observing how playtesters interact with the game significantly facilitates making necessary changes. A case in point is the creation of God of War, where the team's belief in the effectiveness of playtests allowed them to involve such prominent figures as Cory Barlog in the process. This confirms that playtests not only help improve the quality of the game, but also promote closer collaboration within the team.
Game Designer: From Zero to PRO in 5 Steps
Want to become a game designer? Learn 5 steps to a successful career in games! Read the article.
Find out more
