I think managers being extroverted (or, if you read this thread, useless narcissistic status-seekers with bad home lives!) is part of the answer, but not all.<p>Another simple explanation:<p>For an individual dev, your job might be to, say, take a new feature and then work for hours or days on coding, debugging, documenting, etc. that feature. How that maps to WFH is pretty obvious (just code at home instead of work!) Getting up to talk to another employee is maybe a few times a day thing that just becomes a quick ping on Slack. Likewise, if you have a meeting that day, do it on Zoom.<p>Because you see how you can do your job, you are comfortable with WFH.<p>For a manager, your job is to get the people and teams you manage to work together to accomplish something, and perhaps make a few key decisions now and then. My contention is that, while I have no doubt that there <i>are</i> methods of succeeding at as a manager in a WFH system, it's simply a much bigger change from how managers are used to working.<p>For example, walking around the office to see if anyone catches your eye and 'grabs you for a quick question' is not straight forward (pinging dozens of people to say 'hey, anything up' throughout the day is just bothersome.) Likewise, the simple act of observing team dynamics becomes hard because lots of communication is happening in un-observable private communication channels.<p>It maybe that the WFH model really is better for everyone, but I think managers are simply in for a bigger change to how they work and it's therefore simple to understand why they are more hesitant.