Earlier quoted context omitted.
At my old company it was a bit of a joke, you would repeatedly see shit managers become "architect"s. Management were too cowardly to get rid of bad managers, so they were forced to promote them to get them out of their role. So managers who were shit technically constantly ended up with senior technical titles - and everyone knew why.
Were they bad architects though? It's easy to paint bad managers as bad workers (or even bad people ) - but sometimes, they're just bad at managing. In such cases, it's better to shift them into roles they're more suited for than to fire them and hire new people for those roles - existing employees already know the company's procedures and products. Plus, it'll likely be cheaper salary-wise - in our industry, new emp…
Every skill of a good manager - having good working relationships and pleasant interpersonal relations, understanding conflicting needs from different teams, building trust, being able to schedule and prioritize work, etc. - is also a skill of a good architect. If you're off in a corner developing things by yourself, you're not an architect, you're an individual-contributor team of one (or if they're not getting implemented at all, you're just wasting the company's money). If you're actually designing architectures that other people will be following or implementing, you need to be able to work with people.
The balance of work is different, of course: for instance, architects will less often (but not never!) need to have difficult one-on-one conversations. I can understand someone preferring one role or the other, of course. I can't really understand how you can be a good architect, not just a mediocre one, if you're a bad manager, not just a mediocre one.