As with any work that requires collaboration with other people, we need to pay significant attention to how we communicate with each other. With a team consisting of people who specialize in various fields, it is especially important how we want to present them with expectationsrelated to their work. If you present them inaccurately, it is difficult to expect that they will be executed correctly. However, when it comes to job allocation, specific tasks are important. – a clear position in this situation. By having certain specific expectations, we can better control the progress associated with the responsibilities assigned to us. When a problem is ambiguous, we can’t be sure that the way we understand the problem will also be read by an indirect person.

But what if a person starts receiving conflicting information? How should it achieve the goal set earlier and what can be the approach to it? Can we draw out the consequences associated with a” poorly ‘ completed task when its purpose was not clearly defined? Understanding, the ability to express your expectations and present real opportunities related to achieving your goal-all these qualities are necessary for working on a project. Not only from the project manager – > team, but also from the client – > partner. Why is this so important?

Leniency

An understanding person is someone who can understand the reasons for someone else’s mistakes. But how does leniency apply to project work? It’s very easy for people to judge. Often, a negative assessment of someone’s work is easier for us than thinking about the mistakes we’ve made. It’s easier to demand than to be a person who has to meet other people’s requirements. Leniency in working on a project is a trait associated not so much with attracting blind consequences for a mistake made, but rather with the desire to find out the cause of this misunderstanding and make sure that it does not happen again in the future. With this approach, we can learn lessons any situation, and we avoid duplicating those mistakes that can be particularly costly in our work.

We already know what characteristics to use when dealing with a negative situation, but how can we avoid them altogether? Of course, you should clearly state your expectations. The goal we want to achieve. This will help avoid many misunderstandings. It is also necessary to clearly define what is required in a particular project, so that this vision can clearly guide us in the implementation process.

Why compromise at all? You don’t need to, but…

Thanks to mutual concessions, we can always achieve our goal. But why make any concessions at all? We don’t need to. If we clearly state our goal and set out all our expectations and assumptions in a concept. Then we will work together to create our GDD (game design document), and finally, we will ask you to accept this document or discuss possible changes with us. Here’s what it looks like in practice. However, when we reach the final acceptance of the document on the basis of which work is being carried out, estimates related to working hours and estimates are made, it is difficult for us to change the content of these assumptions when we are already in the process of implementing them. If you work with us to ensure that the document is complete, I guarantee that you will not need any concessions. However, if after acceptance you find that you have missed something or something is missing, and you would like to add it necessarily, you should consider that there is no compromise. The amount and date of project implementation are determined on the basis of the accepted document-if we need: We need to reach some kind of compromise that is unexpected during the implementation stages of the content that you want to suddenly introduce.

Goal

In my opinion, this is the most important element that needs to be determined before starting any work. We always need to know what purpose you want to create this app for. Why did you decide to invest in it? What benefits would you like it to bring to potential users? Answering these questions will help us better understand your intentions and the concept we want to develop. As I said before, not everything that is obvious to you should be obvious to us. We are a team dedicated to developing VR apps every day as well as other industries related to virtual reality technologies. Our daily lives are very different from the daily lives of our clients, who very often specialize in completely different areas – often not even in any way related to what we did before. We attract people from the pharmaceutical industry, engineers, paramedics, people involved in experiments in physics, people who make large mechanical structures on a daily basis, and we also cooperate with industries that are exclusively interested in entertainment… so you should understand – we are experts in the field of virtual reality, and every day our duties look like unlike the ones you do every day. We expect that you will have to share your knowledge with usso that we can really understand what you are doing, why you are doing it, and how we can help you. Concepts that you can use every day, abbreviations all this may be alien to us, just as virtual reality technology may be alien to you. That’s why we need to talk together to understand your needs, expectations, and know, in fact, the field you’re working on enough to be able to meet those expectations. Having a specific goal even with limited knowledge in the field, we can know at least what to ask – what information we still need to achieve this goal-which is why it’s so important. For us, this is the direction of the path that we should follow. How do I get to my destination without even having a specified path?

Bottom line: overall goal and end result.

You must define a goal before you start working on the project. For us, this is a very important indicator of how we should direct our work. Without this element, it will be difficult for us to meet the expectations associated with the implementation of the application. A specific goal allows you to formulate a complete product vision at an early stage and identify possible problems that may arise during order fulfillment. The ability to make compromises allows us, on the other hand, to skillfully implement this goal when in the process of achieving new tasks that were previously ignored during the planning stage. Then we try to combine this with an understanding of the app’s purpose to get the endresult that will fully satisfy our partner. During this process, we also need to understand how we are implementing this vision. It is also important to be able to really assess the situation associated with previously made decisions, which may be necessary in the case of a creative process that develops during the project.

Maciej Fiałkowski, EpicVr