Hello Devforum Members,
Introduction
I’ve worked with multiple development studios in the past very eager to make a game or project. I have joined these studios in multiple positions, sometimes as a builder, sometimes as a scripter, or a UI designer, whatever the job called for.
One thing that I have noticed quite a bit about these development studios is that I personally don’t like how they cooperate with their developers, including myself. So I am writing this post with tips for development studios on how to properly manage developers in your development studio and cooperate with them in a much better way (from a developer/person taking the job’s perspective of the project)
The Reason
The reason I am writing this in the perspective of the developer is that I feel this perspective is often ignored or put aside (based on my previous experiences working with development studios). And I feel that is it also important for a development studio to understand the perspective of the project from your developers.
Tips
1. Share the details of the project
It is understandable when the leader of a development studio does not want to share the details of the game with their developers. You may be concerned about the idea being stolen, or betrayals. But honestly, I think an even worse situation is created within the team when the project isn’t fully understood by everyone.
When everyone is aware of the project, not only can more creative minds contribute to the project, but a stronger bond to the project and the team is created. And as a result, the motivation of the developers increase. A lot of devs come at first for the robux, but I believe it important to try and make it more than just robux, but also get them into the project too! More creative minds can work in sync, developers will feel more motivated and excited for the project because they will feel more a part of it, and a huge portion of themselves will be put into the project.
2. Please, do not expect any developer to be a mind reader
I can not even remember how many times I have been in a situation where the lead dev is trying to explain what I have to do, but is rushing in explanation. In other words, explaining a few things here and there, skipping portions of the explanation, and talking fast is not helpful. Developers are not mind readers, and going back to reason 1, it is even worse when the developer has no idea what the project is even about.
It always feels like there is a rush to get right into the game development process, but please, just take a few days to stick back in the planning stages. Work with your team, share the details of the project, let everyone contribute. Multiple minds are better than just one. And take quite a bit of time just to make sure the developers know exactly what they have to do.
3. If payment really is the motivation, don’t leave it to the end
As I mentioned before, a dev studio should try as much as possible to not make robux or payment a developers motivation for the project. But if this really is going to be the motivation, or even after you tried, payment still has little part to do with the developer’s motivation, then don’t leave it to the end.
When I dev for a studio and I spend weeks working on whatever they tell me to do. Script what I need too, design and build what I need too, and I am looking forward to payment, waiting gets frustrating. And I am not trying to sound impatient, but hardwork needs rewards eventually. And it’s hard to continue when the development process seems never-ending and you came there for the payment in the first place. In other words, don’t make your developers feel like they will never be rewarded.
Maybe instead try something like paying the developer little by little as they work. Not only does that help to prevent scamming, but when the dev gets paid it can feel like a speed boost to continue. Remember, devs aren’t machines, they need motivation for a project.
4. Check in with developers
You know the awkward silence when a chat goes dead for a bit? Well, that’s probably not a good thing, and it’s not something that should continue too long. In my experience, it helps when the team just checks in every now and then to know the development process is going smoothly. When a chat or communication is completely silent for a few hours and the only thing that breaks the silence is a sentence or 2 here and there, it may feel like the project is slowly dying. And developers are slowly losing touch with the project, once again possibly decreasing their level of motivation for the project. And yes, I know this kind of sounds absurd, but I have seen it happen.
For some teams, this may cause a problem, and for some, it may not. But it doesn’t hurt to keep the chat alive every few minutes (maybe 15-30) and just spend 2-3 minutes talking back and forth a bit to let everyone know that work is still continuing. This may help preserve the motivation of developers and keep the dev team up and alive.
5. Don’t change the job unless the developer openly volunteers.
I have often found my self in a situation where I joined the team for one job but as the project advances the lead dev asks if you can do this or that, or something not originally mentioned in the job. Now don’t get me wrong, if a developer really is into the project they join and they are glad it’s advancing and want to contribute more, that’s fine. But they should never be forced or pressured into doing so. It can mess with their plans, and make the job just harder for them. Even if you plan on paying them more, the developer may not be able to handle it or may not want to handle it.
And it puts devs in awkward situations too. When I get asked things like this, it can very quickly cause drama in the team and increase the number of disputes and lower motivation and trust.
If you want to put it out there and hope someone volunteers, just generally mention it. Don’t target it at once person which can make them feel pressured.
For exmaple:
Bad:
Hey player0, I know it was not originally in your job, but can you do a few more buildings? I will pay you extra robux.
Good:
Alright the project is going great, we just need a few more buildings done. If anyone wants to do it, ask me.
And if someone on the team is interested, they will (making their own decision without pressure) volunteer. And then after you could try and mention an addition to their payment.
6. Don’t randomly change the game idea mid way
This is something that can be very frustrating. When a team has talked, planned and worked together on a game idea and concept and began work, and then one lead dev just randomly decides to change the entire project without input from the other team members. Remember this is a team, and if the team together chose an idea then most likley all of the team members are into the idea. This will increase motivation and cooperation when every team member is into what they are making.
Also, when deciding the game idea/concept it self I believe that a majority vote kind of method is not a good idea. In my opinion it’d be best if the entire team was into the idea, except everyone but one person.
Conclusion
Thank you for reading. Now some of you may disagree with some of these tips, but these tips are just my opinion based on my experience.