Absolutely agree on the empathetic listening. But there are definitely times when devs come to be and no amount of empathetic listening is going to get to the room of the problem. Like when things are moving slower, why dates are being missed etc. And no amount of empathetic listening is going to be enough data to go to leadership to argue why things are off, why we need to delay things (and delay other teams), and build any sort of trust that you can reasonable manage the work for the team. But this may be limited to working at a FAANG company where projects span 100's of developers and any shift needs to be backed up with a lot of data about what's going on.