I know some great architects who have very limited social skills but sound confident (read cocky) when they talk about technology and you can tell they know what they are talking about. This sort of attitude often times instills confidence.
I think it is important for anybody to have good social skills. But how important are social skills vs technical skills to a software architect 10/90, 20/80, 30/70?
Soft skills are important for any developer -- if you cannot communicate, your value is diminished. For someone working at the architecture level, it's even more important as communication of ideas is a large part of the job. The "smartest" architect is useless if all he or she can do is think great thoughts and keep them to themselves.
Being able to express your thoughts clearly is different from having good social skills. In fact, most of architects that I admire have extensive vocabularies and presenting skills.
Sometimes I am worried when we have to take architects on customer sites because they can come across as cocky and patronizing. But surprisingly such behavior seems to make customers feel more secure.
I better get a copy of your book and see how this outcome can be achieved through other types of behavior.
The current Software world becomes very DYNAMIC today because of the volatility in the current market due to globalization and users become very much choosy because of this. Due to this most of the projects follows AGILE technology now a day. In this scenarios user requirements are not fixed and keeps changing during development cycle of software. In these scenarios Software Architect should have Social Skills which are equally important to Technical Skills. Social skills play important role in below scenarios.
1. Software Architect need to understand the client requirement and need to judge whether it is Achievable or not and need to communicate the same to the client with proper justification.
2. Software architect need to involve in negotiation with the client to get the project work.
3. Software Architect needs to put his technical thoughts properly on document and need to communicate the same properly to Project members. It helps to reduce the requirement gaps in future of the project and helps to achieve the project in planned budget.
4. Software architect should also be good in Domain knowledge. It helps to raise the proper queries to the client during the requirement gathering .Hence social skill help here to communicate the queries in efficient ways to the client at proper time.
5. Software Architect should also have good flexibility of mind which helps him to take proper decisions on behalf of project if someone responsible from the team fails to do so.
As per my understanding 12 Essential Skills for Software Architects book will really help to understand Social Skills which need to be deliberately cultivated by each Software Architect in order to get more hold on current business, project and market scenarios to develop and deliver more robust software.
More than simply Domain knowledge, I feel it helps significantly when an Architect has some level of business savvy. To some degree I suppose this encapsulates a level of social grace, though I don't know that acquiring those soft skills is the point of having a "head for business".
Sometimes an architectural decision can be made that is perfectly sound from a technical perspective and it even seems to fit the business needs - those needs, as stated by the business, often carry an implied level of knowledge that isn't captured in a requirements document or visible as an artifact of the business itself. There is a reason why the perception of IT project failure rates hovers in the 50% range at any given time, and I wouldn't be surprised if this has something to due with the that lack of "insider knowledge" and general understanding of business exhibited by some Architects.