A team of high-performing engineers needs something different from a manager than a team of low-performing juniors. A team building a new product in a fast-growing startup will have different needs to a maintenance team in a bluechip.
Nonetheless, I do like your thought experiment. It provides a model to think about what might be necessary.
https://en.wikipedia.org/wiki/The_One_Minute_Manager
It covers this, is very short, and (IMHO) is a good book to give all brand new managers. eg when they're promoted from individual contributors
Seems to set new managers on the right path. :)
2x2s can be really entertaining. One I've seen a lot covers the dimensions of lazy-hardworking and idiot-clever. The outcome is
* hardworking-clever: Ideal!
* lazy-idiot: don't need to worry, they'll not usually progress.
* lazy-clever: hmmm. not ideal but may still be useful from time to time.
* hardworking-idiot: bad! They can do a lot of damage
In truth there are usually more than two relevant dimensions.
https://quoteinvestigator.com/2014/02/28/clever-lazy/?amp=1
I think it requires a certain definition of "lazy" that basically translates to "delegate everything you possibly can" - which we all know can be hard work in itself.
IME they are the first people to challenge assumptions about the way things are done, and the least happy with the answer "that's just the way we do it"
Just make sure you review their code.
Spend the time that needs to be spent implementing the generalisable aspects, so that the work never needs to be repeated.
Implement the problem specific aspects (with minimal code) against those changes (and if any similar problems come up in the future, the changes can be made in minimal time and with minimal work).
I'd also say that very few people are inherently lazy, they're often just demotivated through misalignment of their responsibilities versus interests.
Captain and Commander - appropriate control and perspective, seen as that flow state in FFA chart
Micromanager - has too much control, not enough perspective, work gets out of control because it's being squeezed too hard
Crazymaker - has not enough control, but has lots of perspective. Work doesn't happen because new ideas pop up like fungus covering everything and nobody can iterate on anything because of all the context shifting.
Victim - not enough control or perspective, just responds to crises. Sounds like TFA version of the disengaged manager to me.
The thing is that the control and perspective axes change on the subject matter, so a person can be a Victim in one space and a crazy maker in another and a captain and commander in a third, at least at this point in time.
Halvorson, Heidi Grant & Higgins, E. Tory. 2013. Do you play to win - or to lose? Know what really motivates you. Harvard Business Review 117.
I did the exercise for myself, and here's what I got:
hands-on + task-oriented = micromanager
hands-on + people-oriented = professional office politician (deeply involved, but only to the extent it enables shaping the org chart)
hands-off + task-oriented = scrum master (no technical background that would allow being hands-on, but still very concerned with tasks)
hands-off + people-oriented = HR rep, I guess? Relatively distant from the day-to-day of the team, but still concerned with "people."
On reflection, maybe that last one is a bit of a stretch. But — definitely an interesting thought experiment overall.