Communication & Relationships

As mentioned earlier, the architectural / solution design should have enough detail to permit the key stakeholders to make decisions without extensive dialogue:

• The customer (or client) needs to be able to appreciate that the design will deliver the product or solution they desire
• The project manager needs to know which constructor teams to engage & include in the project team and compile a project plan (with estimates from the constructors)
• The constructors need to be able to estimate the effort & cost of building the design for the project manager

Therefore, the package of an architectural design must service these three key perspectives, requiring the Solution Architect be eloquent to these audiences.

Also, since an architectural design typically spans two or more constructor teams & often building with different technologies, the architect will need to be able to communicate the design in the context of each constructor without introducing incoherency or ambiguity to the overall design.

Since we're all human (I hope!), relationships factor greatly in ensuring effective communication. Therefore, Solution Architects should possess excellent relationship building & management skills, regularly engaging in direct dialogue with each key stakeholder.

Egos often do get in the way, especially in a large corporate environment where recognition for high-profile initiatives is a high-value currency. Therefore, good Solution Architects will have honed excellent diplomatic skills and maintain a focus on their objective ... facilitating the implementation of the selected solution.

Creativity

This is important; Solution Architecture is a creative profession that utilises technology to realise design. Frequently, the assumption is that, being in 'IT', a Solution Architect will be highly technical, wear socks with sandals and be incapable of communication without a keyboard.

Personally, I'm not the most numerate, prefer talking to people than sending emails, have never worn socks & sandals (no beard either!) and use an A3 pad whenever I start a new design concept.

There's no formula to being a Solution Architect, but the most effective are those who are highly creative since, from creativity springs design. There's no use in possessing deep technical knowledge if that cannot be translated to a creative design inspired by real needs. Creativity consumes knowledge; nothing good comes of the converse.

Multidisciplinary

Regardless of the importance of creativity in Solution Architecture, the materials used in realising design are technical in nature, creating opportunity for various levels of specialisation by technology & domain. The effective Solution Architect will have, at least, a detailed appreciation of the nature of the materials at his / her disposal.

Frequently, solution architects are specialised in either or both of the following categories:

• Vendor-specific technology (especially the integration of the technology with other technologies or the business / user)
• Architectural domain (e.g., software, network, security, information, etc.)

The more experienced an architect is, the broader the set of disciplines s/he will have and, as a result, the more rapidly a design is likely to be reached.

In my opinion, a Solution Architect usually will design end-to-end solutions spanning multiple domains / technologies. Where the subject of design is specific to a domain or technology (e.g., software architecture), the appropriate title should be used for no other reason than the title quickly identifies what the architect is designing.