Monday, February 23, 2009

Solution Architect Competencies - Part I


Solution Architect Competencies - Part I

Alik Levin 


  Now that I know what Solutions Architecture Foundations are and what the Solution Architect And Enterprise Architect Do it's time to learn what competencies the Solution Architect must possess in order to build solid solution architectures. I found it in Solution Architect Competencies that includes (but not limited to) these:

  1. Leadership (covered here)
  2. Communication (covered here)
  3. Organizational dynamics (covered here)
  4. Strategy
  5. Process and tactics
  6. Technology breadth
  7. Technology depth

by aloshbennett

In this post I am mixing the content from the resources on MSDN with my own take on each competency expressed by links to my original posts on


From Lesson 3: Leadership:

Leaders and Managers: Leadership is managing yourself and leading others. Managers do and leaders guide, even when they don't have power. A solutions architect must not advocate or tolerate “Technology for technology’s sake.” Technical leadership means getting all team members to align their actions with the needs of the project.

Leadership Models:

  • Situational Leadership – advocates adaptive leadership based on the situation at hand.
  • Servant Leadership – This leadership approach is one of stewardship.
  • Thought Leadership – this leadership approach is one of education.

From Lesson 1: Listening and Communication:

What’s important is that you remain open to surprise: Recognize that other people have information or opinions that will be different than your own, but will enhance the value of your outcomes.

  • Self Awareness: Recognize your own style or type and how it can affect your listening style, assumptions, and ability to achieve empathy.
  • Be Aware of Others: Each person has a different personality. This leads to differences in how each of us best understands and communicates.
  • Ask Open-Ended Questions: Questions like: "Tell me about...?" "What do you do when…?” and "What do you think about...?" get people talking.
  • Make Connections: Coordinate efforts with work partners to get their help in understanding.
  • Make Time to Listen: Make certain that your conversations are dialogues, not monologues
  • Set the pace: In meetings, encourage team members to "check in" by repeating in their own words, summarize, and clarify.
  • Close the Loop: Follow up your meetings with written notes to the audience.
Organizational dynamics

Got resources of your own? Please share!

Related Materials

This post is made with plugin for Windows Live Writer

Published 23 February 09 06:57 by alikl

Alik Levin's : Solution Architect Competencies - Part I

No comments:

Blog Archive