Well, here's the rub: I generally try to avoid saying "my team", because I don't regard them as possessions.
I'll make N-way decisions between conflicting ideals when I'm invited to adjudicate, but refrain otherwise. My guidance would be to workshop apparently dissimilar preferences extensively, because 99% of the time there is a synthesis to be found, and creating a focus for conflict tends to encourage loud voices to get louder, drowning out alternatives. I'll treat any administrative decision-making as being on behalf of the team, i.e. as having been delegated the authority to do so from the members. I learned years ago that governing by consent of the governed is the only form of respectful leadership, and this extends to organisations and corporations, and it's never more apparent than when a manager switches jobs and people follow to the new gig because they liked working with you.
The most important function, in this management style, is hiring, and in some organisations, talent acquisition has been half my workload. Regarding which I was once told, "hire people smarter than you"; the only issue with this maxim being the corollary, viz. that the CEO is, by induction, the company dunce.
Interesting perspective. What is it about my team that is possessive? The work my?
Why is it that you avoid possessiveness?
I am not asking from judgement but genuine curiosity.
I think there are some valuable ideas in your post. And I generally agree with your perspective. I also think nothing about governing with consent of the governed alters the existence of an actual power structure unless you would resign in the face of a team member not consenting to your decision.
Yes. The primary meaning of "my" is the individual possessive. The secondary meaning of association, or membership, is something one cannot reliably communicate, even to oneself.
> Why is it that you avoid possessiveness?
I don't own people. They have individual agency.
> resign in the face of a team member not consenting to your decision
That's bonkers. It's still thinking in terms of a command authority. It's not me that has to consent, it's the rest of the team. Or more precisely, don't make decisions on behalf of a team if it hasn't agreed to recognising their validity in advance. The most important consent to obtain in this regard is hiring (nuance: compensation/levelling is best left to a separate corporate organ), followed by seating (yes, really) and allocation of day-to-day work.
Frankly, a manager whose team doesn't recognise the validity of their decisions, or who can't handle being challenged to qualify and explain their thinking, should go. Continuing the earlier analogy; if the band is unhappy with their manager, they can get a new one.
Command authority is for temporary dictators in situations required real-time skilled decision making, like a surgeon in the OR, or the emergency controller for a downtime incident. It is not for deciding which continuous delivery tool we'll use, whether we're including SSO in the next release, or buying standing desks, or who gets to sit next to the window, or has to refactor a problematic query.
The hardest thing to do in this context is fire someone, but then, it always is.
The easiest thing to do is actually extinguish the team, because the quid pro quo is that it spends company resources.
I'll make N-way decisions between conflicting ideals when I'm invited to adjudicate, but refrain otherwise. My guidance would be to workshop apparently dissimilar preferences extensively, because 99% of the time there is a synthesis to be found, and creating a focus for conflict tends to encourage loud voices to get louder, drowning out alternatives. I'll treat any administrative decision-making as being on behalf of the team, i.e. as having been delegated the authority to do so from the members. I learned years ago that governing by consent of the governed is the only form of respectful leadership, and this extends to organisations and corporations, and it's never more apparent than when a manager switches jobs and people follow to the new gig because they liked working with you.
The most important function, in this management style, is hiring, and in some organisations, talent acquisition has been half my workload. Regarding which I was once told, "hire people smarter than you"; the only issue with this maxim being the corollary, viz. that the CEO is, by induction, the company dunce.