Prototyping and iterating are essential parts of game development, but they can also be challenging and time-consuming. How do you know when to keep working on a prototype or iteration, and when to move on or scrap it altogether? In this article, you will learn some practical tips and criteria to help you make this decision, based on your goals, feedback, data, and intuition.
The first step is to define your goals for your prototype or iteration. What are you trying to test, learn, or achieve with it? How does it relate to your overall vision and scope for the game? Having clear and specific goals will help you measure your progress and evaluate your results. For example, you might want to test a core mechanic, explore a new genre, or improve a certain aspect of the gameplay.
Don't skip this step and spend as much as you need. it happened to me so many times that our team started a prototype but after a while, we didn't know if we were correct or just working on random things because we thought we needed them. It's also good to stop and look from the top occasionally to see if you are still on the correct path to your goal.
Let's accept the fact that you have to kill many prototypes... Don't fall in love with them, and protect your objectivity. Be aware of two main factors: KPIs and user feedback. Continuously evaluate your prototype against your KPIs - if it consistently falls short, it's a red flag. At the same time, pay close attention to feedback from your target users. Negative feedback, especially if it's a trend, it strongly indicates that the prototype isn't where it should be. When either of these factors -KPIs or user feedback- consistently indicates underperformance or dissatisfaction, it's time to consider killing the prototype. The decision should be data-driven, focusing on the efficiency of your resources and the potential for success.
One approach in prototyping is to split more complex prototype to partial prototypes. If the team structure allow for it it is good way to try more things at once or prototype in "isolation". Just don't trust partial prototypes completely. While certain things might not on their own (in isolation) it is vial to have means to test them in context of other partial prototypes. By taking more modular approach it is less likely whole thing will be thrown away as a result, thus saving on resources. Mind you, this will require little bit of planning beforehand.
The second step is to seek feedback from various sources, such as playtesters, peers, mentors, or potential customers. Feedback can help you validate your assumptions, identify strengths and weaknesses, and discover new opportunities and challenges. However, feedback can also be subjective, conflicting, or biased, so you need to be selective and critical about what you listen to and what you ignore. For example, you might want to prioritize feedback that is consistent, constructive, and aligned with your goals.
The third step is to analyze data from your prototype or iteration, such as metrics, analytics, or logs. Data can help you quantify your performance, track your trends, and compare your outcomes. However, data can also be incomplete, inaccurate, or misleading, so you need to be careful and contextual about what you measure and what you infer. For example, you might want to focus on data that is relevant, reliable, and actionable.
The fourth step is to trust your intuition, which is your gut feeling, instinct, or hunch. Intuition can help you tap into your creativity, passion, and vision, and guide you when you face uncertainty, ambiguity, or complexity. However, intuition can also be influenced by emotions, biases, or habits, so you need to be aware and balanced about what you feel and what you think. For example, you might want to follow your intuition when it is strong, clear, and consistent.
Sometimes prototypes "fail". It can be because of unforeseen factors, or because the proposed ideas don't work as intended, or maybe something simply isn't as fun as you hoped it might. They're supposed to be disposable. If your intuition tells you to abandon it, don't let attachment or investment be the thing that keeps you attached longer than you should. Besides, you can always rework ideas, repurpose parts, or let abandoned prototypes inspire you later. Abandoning a prototype doesn't mean throwing away work - it just means moving on when you recognize something is falling short.
The fifth step is to evaluate your options, which are the possible actions you can take after your prototype or iteration. You can either continue, pivot, or abandon. To continue means to keep working on your prototype or iteration, with minor or major changes. To pivot means to change your direction, strategy, or approach, based on your findings. To abandon means to stop working on your prototype or iteration, and move on to something else. To evaluate your options, you need to weigh the pros and cons of each one, based on your goals, feedback, data, and intuition.
The sixth and final step is to make your decision, which is the action you choose to take after your prototype or iteration. There is no definitive or universal answer to this question, as it depends on many factors and circumstances. However, some general guidelines are: to continue if you are satisfied, confident, and motivated; to pivot if you are curious, flexible, and adaptable; and to abandon if you are frustrated, bored, or stuck. Whatever you decide, you should be ready to learn from your experience, and apply your insights to your next prototype or iteration.
A lot depends on what is possible for you. Are you a solo dev or a bigger team? Do you have a budget and/or are you hoping to land a publisher at some point? Ideally you'd have a full picture of what you need for the project, if you don't, a little prototyping should help you realize what are the requirements to achieve what you envision. If you need 3D animations, do you have an animator? Is there an asset that fits your need perfectly? If the game has characters, how complex is it to make them, do they speak? what to do about the sound assets? Pre-made assets only go so far, paid or free. Your scope should reflect your available resources. If your prototype reveals a larger scope than expected, it's probably time to move on.