I've known teams where the architect is integrated into the team yet still fails to own the solution, communicate the architecture, be trusted etc. While sitting in the middle of a team of developers you can still be in a metaphorical corner, isolated by your demeanour.
I'm sure I'm not alone in sometimes seeing (ok, and occasionally being) an architect that busies themself, as part of a team, with writing isolated framework code or complaining about code quality without bringing in any process to address it.
I've no doubt this is not a problem specific to architects but it does highlight that a role is often as much about temperament as it is about experience. Perhaps this is exacerbated by considering "architect" as a title of rank rather than as a role?
E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).