The key is to come up with a working style that doesn't make any sense. If you have problems finding one yourself just hire a consultant. Then spent a lot of time and money to introduce the new working style by force causing massive disruptions in workflows making everybody unhappy. Wait some time until frustration levels peak and productivity is plummeting. Then offer the team to come up with a better working style that they would prefer as long as they can agree on it. Be aware that remote game devs might be more resilient to your terror of nonsense. So just force them to be on site at random days.

Remote teams often have different working styles, but aligning on priorities can help. I’ve found that starting with a clear discussion about the project’s goals and deadlines is essential. Then, setting simple, flexible guidelines - like core hours for overlap—creates structure while allowing personal preferences. The right tools, like task trackers and shared calendars, also make it easier for everyone to stay aligned without constant back-and-forth.

Something I always try to do is to ask the team to write their views and processes, And then bring in a third person to give and objective opinion about the provided methods, This way the developers feel heard and don’t get discouraged about providing their opinions, An Objective and Unbiased set of eyes is always a great solution as they see the problem with a view that the working team would not!