> And at the end of the day if the employees who write code/produce output are doing that efficiently that is the goal right.
That is the short term goal. But it isn't the only goal. I want my reports to trust me so that if things change or they are having problems that they'll be honest with me and provide feedback so I can make things better. I want my reports to feel valued and emotionally satisfied with their work. This means understanding their career goals and what makes them feel happy so I can make sure that they get the kinds of rewards that matter to them. These sorts of things are important for the long term sustainability of a team even if a team is delivering efficiently at a given moment.
Good one, actually most of my employees feel the same way.
You might have a bad case of a micromanager there, but here‘s my definition:
> Management by walking around emphasizes the importance of interpersonal contact, open appreciation, and recognition. It is one of the most important ways to build civility and performance in the workplace.
I started doing the "walking around" bit after negative feedback ~20 years ago, and stopped again pretty soon after it was clear that while it works, it's a band-aid for getting people confident that it's ok to talk to you whenever, and the real problem was that I'd been pretty burnt out and shut myself off for a while, not that I didn't literally walk the room.
With remote teams what I've done as a workaround with some teams have been to enforce a short 1-on-1 weekly, and tell people if we don't have anything to talk about, then we make it brief. It prevents team members who are reticent about taking your time from having issues build up because they feel it's too small or too personal to schedule a meeting about when they have a time slot they know you'll schedule regardless. For some it was almost always a 5 minute annoyance of me asking if there were any issues, them saying they had nothing to talk about, and for us to leave it at that. But it acted as a safety valve, and every now and again something absolutely critical would get brought up in those calls.
And many times when they had "nothing" to talk about, I'd ask them followup questions about small stuff like e.g. how they got on with specific people, or how a certain project was going, and suddenly it turned out they had plenty of things to talk about.
In teams where you know everyone will speak up, you can dial back both the actual and "virtual" walking of the room, knowing they'll come and tell you, but "walking the room" effectively acts as a way of lowering the barrier to bring up an issue, because they're not "bothering you".
Because for me the concept of managers 'just walking around' gives me that itchy feeling on the back of my neck.
And at the end of the day if the employees who write code/produce output are doing that efficiently that is the goal right.