Many of these will come off as frustrating and manipulative. When I, a manager, ask “what is the biggest obstacle facing you and how can i remove it,” I’m offloading the manager-level work of identifying blockers for my team on the individual. And hey, that might work, your teammate might have an insight you’re missing. But then, if they do have that insight, you’ve volunteered to do a shitload of work for your team.…
That gets a bit circular. In my mind, "asking my team members" is THE number one method of "identifying blockers for my team". Think about it - if a manager didn't ask for input from their team members, and instead assumed they can identify blockers, on their own and in vacuum, how would we portray such a manager? :-)
>> ive never had a manager that was willing to actually do the work when they asked the questions on this list
That is indeed the crucial second part; works for anything though - whether it's "lessons learned" at the end of the project, or "requirements gathering" from the client/user-base, or "soliciting feedback" from team members - obtaining information is critical #1 step; only useful if you then action it.
Just because both effective and ineffective, willing and unwilling managers ask questions, doesn't make questions themselves bad. It does depend on the actual manager and the relationship they have with a team member.
So I'd say such questions are "necessary but not sufficient" criteria for managerial success, and having a list is similarly "useful but not sufficient" :)