Servant Leadership is what I've found to be most productive when managing developers - the idea that the manager is there as a servant of the team, to remove problems and allow the team to work at their full capacity. However, this assumes that the team wants to work at its full capacity.
I've seen large corporate teams that do not. They clock in a couple of PRs a day, leave their cameras and mics off in meetings, etc. I can understand the desire to get them in the office to control them. But that's not going to solve the problem - you can't force a developer to write good code by standing over them and watching them.
It's a management problem. If the team isn't performing, getting them in the office isn't going to help. Replace the manager with a more effective one.