I disagree. Your description of an architect sounds to me like an artifact of current workplace trends - which are to punt managerial duties and responsibilities to people as they get promoted, without giving them corresponding authority.
Architects should architect. There are some social skills requirement that come with any collaborative position within a company, but I see no reason why an architect should be expected to have managerial-level social skills, vs. senior-developer-level ones. There's nothing in the actual job of architecting software systems that requires it.
But to be explicit about my original point: managing is a completely different type of job than writing code or architecting systems. It's a whole specialty on its own. Not everyone has the necessary organizational and social skill set. It's learnable to a large degree, but that takes time. Just because someone sucks as a manager doesn't mean they're a bad employee or a bad human in general - it only means they don't have the specialized skills necessary for that particular role.
Architects should architect. There are some social skills requirement that come with any collaborative position within a company, but I see no reason why an architect should be expected to have managerial-level social skills, vs. senior-developer-level ones. There's nothing in the actual job of architecting software systems that requires it.
But to be explicit about my original point: managing is a completely different type of job than writing code or architecting systems. It's a whole specialty on its own. Not everyone has the necessary organizational and social skill set. It's learnable to a large degree, but that takes time. Just because someone sucks as a manager doesn't mean they're a bad employee or a bad human in general - it only means they don't have the specialized skills necessary for that particular role.