Team motivation
Hello again Fuwanovel, it's Dfbreezy (now named Kotario). This new entry is going to talk about the problems when motivating team members to work and to commune.
There are alot of problems with development. The ones that are most known, are funding, recruitment and meeting deadlines. Yes, those exist and are very well known because Devs highlight that very frequently. But one other element that is largely overlooked is team motivation or involvement. How is this a problem? Read further to find out.
Picture you have a nice concept. In fact you've completed the first draft of the said concept. You then go into recruitment based on the summary of the concept... not the concept itself. Of course the recruitee does a passover of the summary, checks whether the genres fit with him, and inquire about their all important pay.
This process is done and repeated over and over again in the EVN sector. It's basic practice to some extent. But that is where the problem begins friends. After the payment is settled, almost every team member (minus writers) never actually takes the time to assess the content of the project until it's over and done with. All the ask is for what you need and References.
That is the problem. You, in reading the content, should know what is needed based on the description of the scenes in the concept material. But most of that is waived based on "I'm working on multiple projects".
I myself have had this problem with my team, with only 50% of the team actually reading the content. Luckily my character artist falls in that category. Because of that, i feel we have a distinctive disadvantage against other studios whose members actively take part in shaping the story itself, not just the VN aspect.
It may just be my assumption and speculation at this point, but what if team immersion could affect the final product positively and make it far better than it normally is? Some good food for thought, i'd say.
1 Comment
Recommended Comments