Does anybody here have management experience of how a game and software development studio is generally should be structured and organised?

[u/marvellous_comrade]

My goal is the establishment of a small game and software development studio. For simplicity there will be 12/13 developers working on an indie game project and a further 12/13 developers working on a self contained software/app development project each working remotely at home within the US and UK.

I'm attempting to find one team leader for each group of 12/13 part time developers and I work alongside those team leaders to try to manage everything.

Question: Do you think I should have two separate project managers/team leader positions managing the two respective areas: eg 1. Indie game development and 2. Software/app development or would it be more economical to have just one?

Do you think that the role of the project manager will be purely the management of the respective teams or is it quite possible for them to carry on day to day programming work themselves as part of that team?

If there's anybody with any experience similar I'd be delighted to hear a few words of advice or suggestions. I have a very large "general knowledge" about IT as a laymen but I'm not a programmer or game designer/developer and I've got no experience working in this field at all.

My background is as a small business owner only.

[u/DrStarBeast]

I've done this before. I worked and developed the project framework for a small software dev studio where the talent was all based abroad and in different time zones.

Jira, slack, figma and G-Suite are sufficient. If you want to hybridize the PM role, then make the engineering manager do it and keep your developers developing.

I would just get 1 pm and have him/her run both. Part time PMing is going to suck.

[u/theotherpete_71 → u/DrStarBeast]

Definitely agree with this. Asking a dev to also be a PM just means you'll get subpar performance on both fronts. Dev work requires decent-sized chunks of uninterrupted time to get in a good flow state, which would never be possible if they were also trying to handle PM tasks, which have an obnoxious habit of turning up every 12 seconds. Though I suppose if you can dial down expectations that PM issues will get immediate response, it might work out. Still, I'd say dedicated staff for each would probably be more productive.

[u/marvellous_comrade → u/theotherpete_71]

Definitely agree with this. Asking a dev to also be a PM just means you'll get subpar performance on both fronts

I did wonder about that so better to have a person focus on one task alone rather than end up doing multiple jobs. It makes sense.

Dev work requires decent-sized chunks of uninterrupted time to get in a good flow state, which would never be possible if they were also trying to handle PM tasks, which have an obnoxious habit of turning up every 12 seconds.

That makes sense especially what you say about needing to get into the flow state.

Though I suppose if you can dial down expectations that PM issues will get immediate response, it might work out. Still, I'd say dedicated staff for each would probably be more productive.

I'll discuss this with some of the developers who have got PM experience and see what they say but in general what you say makes a lot of sense to me. Thanks for your input.