If you are interested in creating, implementing, or instructing someone to implement your project, then this article is for you, because the words “concept” and “GDD” will scroll very often in your dictionary. So it’s worth starting with the basics. What is a Game Design Document and concept? What do they mean for the principal and contractor? I invite you to read it.
Concept
Idea, idea and thought. These are the most relevant synonyms for what a concept is. This is the core of the entire plan, on the basis of which we will create a unified vision of the target product. These can be expectations, requirements, and assumptions. These are the plans and reasons why you would like to implement this project. All this is provided as a short description that will allow the performer to better understand your needs. The concept is a kind of compass for us, which points us in the direction in which we, as developers, should move. The mechanism of this compass is the client. It is up to him / her how accurately he / she will convey his / her vision in the concept, which will lead us to the fulfillment of the assignment in the future.
Having settled on the rhetoric of the compass, imagine one that at different times shows you a different path, which at some point, for unknown reasons, leads you astray and forces you to turn back. This is how the concept changes during the project implementation process. If the compass had been well oriented before the whole adventure started, we wouldn’t have had to waste time wandering around, we could have headed straight for the goal. That’s why it’s so important to know your expectations and goals.
An accurate presentation of the concept will not only compensate the client for the additional costs associated with the changes made in the process, but also help us achieve the goal on time without additional and unnecessary turbulence.
GDD
The Game Design Document is already a highly descriptive document for your project. For the principal, it should be a summary of his order, everything that is in the contract concluded between the customer and him. It defines the area and boundaries of the work that the contractor must perform. It’s like an already published book that you’re the author of. Maybe at some stage you would like to add something else to it, but it has already been released. You can do everything at the work stage, but when you finally accept this document, this order will only apply to the content in it. We are writing the first version of GDD after adopting the general concept. Then we move on to possible revisions and corrections. After accepting the document, we proceed to the implementation. This is the order it should look like. Unfortunately, this is not always the case… and then the stairs can begin. Some clients who contact us sometimes wish that on the day they come to us with this vision, they have already started working on it in programming and graphics. This can’t be happening. Drawing up a GDD allows us to imagine the foundation on which we currently stand. You can’t build a house without a construction plan, and you can’t create an app without designing its final shape. I believe that at first you may think that this is a rather banal comparison (home construction and applications), but it is the most appropriate one. From our point of view, this is exactly what it looks like.
Our clients, of course, are always aware of the GDD at every stage of their work, because together with us they are its creators, but you should remember that this is a confidential document, and only they can have access to it at this time, and any changes made to it must be agreed in advance with the company. by us.
What should you keep in mindwhen you assign someone a VR/AR/XR/MR project?
First of all, despite the enormous imagination required in our industry, we can’t read minds. Sometimes, as it turns out in collaboration with a client, such a skill would be very useful, but, unfortunately, we have not yet mastered it. Therefore, it is important to accurately state your vision, prepare links, graphic examples, and inspirationthat would be good to see in the concept. Sounds, videos, images, poems: everything that will help us better understand your goal, so that, like this previously mentioned compass, you can guide us in the right direction.
Be sure to remember your sincerity and the decisions you make. I had the opportunity to lead a project whose aesthetic and graphic implementation the client entrusted to us “fully’, because he believed that he did not have any vision, and we will certainly do it better. As we decided what we did, we started implementing the project. After some time, it turned out that our work began to receive comments related to the selected graphic layer. Unfortunately, the design turned out to be contrary to the client’s visual expectations. Then we heard “ ‘ But I thought it would be different.’ Then I asked: How did you imagine it? Then the client sent me photos / graphic links and described everything in detail. That is, on the one hand, first we heard that she had no vision, and then it turned out that his expectations from her were quite clear and clear. Then we had to make costly changes for both parties that it could have been avoided in a very simple way. First, if we have a vision, let’s present it immediately, even the most vague. Secondly, if we decide to put the project in the hands of a contractor, we take responsibility for it.
Why is the concept and GDD so important to us?
Because it is mainly on these documents that our work is based. The concept is the path we follow to meet the customer’s requirements and expectations. This is the key to their desired goal. Therefore, I sincerely, sincerely recommend that every person who decides to start a project should not underestimate this part in any way.
Game Design Document, on the other hand, is often called the Design Bible for a reason. When creating this document, we always strive to make it a book in which we can find answers to any questions that concern us during the project implementation. The sacred approach may seem rather exaggerated here, but only such an approach guarantees us and the client respite and peace of mind during the order execution. Thanks to this, we don’t need to ask them questions from time to time, we don’t need to wait for their response, we don’t need to stop working when this answer is not available, and we need it urgently. This approach guarantees, first of all, the smoothness of the project and the ability to maintain the established deadlines.
Developing “games ‘ is not just fun, as some might think.. This is the time of the entire team, it is the money of those who participate in the project, it is long testing sessions and possible fixes, it is a big technological task that requires time and careful planning. This is primarily responsibility and competence. That is why these documents are so important to us, and it is for these aforementioned reasons that we always take them deadly seriously. Our experience has taught us this.
Maciej Fiałkowski, EpicVR
