I strongly believe that Leadership is a critical competency for successful Enterprise Solution Architects. To some, that statement may seem bold. To others, its obvious. for those that this seems bold, I hope this blog post helps explain why Enterprise Solution Architects have strong Leadership competencies. For those that this statement seems obvious, I'm simply attempting to refine this concept to bring it to a more mature level.
A bit of my background leading to thoughts on strengthening Leadership competencies as an Enterprise Solution Architect
During my career as an IT guy, I've always been laser focused on my career mission "Improve IT's business value proposition". This is my passion and it is my guiding principle for making career choices. It's worked well for me probably because there always seems to be new opportunities to explore and deliver more business value such as; exploring different software delivery models, exploring different software design processes and techniques, implementing new and exciting technologies, engineering business architecture, and scaling to enterprise-level constructs like enterprise architecture frameworks and organizational dynamics. In fact, I feel lucky to have been able to achieve so much and still be totally inspired to learn and grow more.
My career has taken me through many IT roles gaining experience as an IT software engineer, tester, business analyst, project/program manager, and solution architect. I've carried pagers while in IT operations support roles. I've spent time in sales selling software solutions and I've spent time as a consultant delivering software solutions and coaching customers and partners how to deliver software solutions. Because I've always had a hankering to make bigger, broader, enterprise-wide business value from IT, my career has led me to where I sit today, an Enterprise Solution Architect.
Enterprise Solution Architects require Leadership skills the most
I think that all Architects require Leadership competencies to some degree but one Architect type that stands out as being the most dependent on Leadership is the Enterprise Solution Architect. Because I haven't seen an attempt to articulate the Leadership abilities in the context of the Enterprise Solution Architect role, I thought I'd share my opinion of what they might be.
So, here's how I think of Leadership. Leadership is a competency and it can be decomposed in a number of ways; leadership principles, habits, values, emotional intelligence abilities, leadership imperatives, frameworks, competencies, et al. All are valid and often share the same semantic meaning but conveyed in different terms and constructs giving us lots of choices to find the one that resonates with each of us individually.
Daniel Goleman's Leadership model as the base construct
One such Leadership model that resonates with me is Daniel Goleman's Emotional Intelligence (EI) abilities organized by the domains Self-Awareness, Self-Management, Social Awareness and Relationship Management. The complete list of Goleman's EI abilities with definitions are located at the end of this blog.
This is an Architect's blog post, so I created some views of the EI domain model as well as the actual model using UML notation for those who like to read models:
Relating Goleman's Leadership Competencies to the Enterprise Solution Architect
So, how does this all relate to the Enterprise Solution Architect role you say? Well, I think that this is where things get fascinating. Below is an attempt to describe how Goleman's Leadership abilities relate to the Enterprise Solution Architect role. It is very rough but my hope is to mature the thinking to the point we can manage Leadership abilities like we can with other Architect skills like I described in this blog post regarding growing Solution Architects.
It should be noted that the Enterprise Solution Architect's Leadership competencies are required or be the highest maturity achievable. The aim of this blog post is simply to describe the relationship between Leadership competencies and the Enterprise Solution Architect role.
|Leadership Competency||Narrative description how Enterprise Solution Architects use the Leadership Competency|
|Emotional self-awareness||This is one of the more critical competencies that Enterprise Solution Architects have. We are often engaged in discussions that are extremely complex with very senior leaders when suggestions are asserted which unintentionally break the integrity of the enterprise architecture we have so carefully nurtured. Enterprise Solution Architects must have self-awareness competency to inject architectural integrity back into the discussion without sacrificing relationships or, as Goleman might say, "emotional capital".
Take for example the situation of enterprise planning. There are times when senior leaders suggest major platform consolidation decisions while, unintentionally, grossly oversimplified the engineering rigor involved in defining shared software platforms. Instead of bursting aloud and delivering 'an education' to the group, Enterprise Solution Architects might choose another route. Perhaps s/he might respectfully acknowledge the leadership's role and compliment the suggestion with the option of off-lining that decision to allow time to review impacts and return with their analysis results.
Because Enterprise Solution Architects interact at all organization levels in the business and IT organizations, they become acutely aware where they must grow and improve in order to be more effective. The best Enterprise Solutions Architects, therefore, seek mentors and coaches, join networking clubs with a passion for self-improvement. This is one of the reasons why find themselves at networking events and sharing experiences at enterprise architecture conferences.
Enterprise Solution Architects are some of the most psychologically mature Architects an organization has. They are often "the rocks" within the most complex, high-profile IT projects a company has. They are masters of self-control for the project team and in planning teams. Their decisions carry weight both in the eyes of the business and IT and any wavering can cause ripple effects strong enough to cause doubt and ultimately shake the foundational confidence of a project.
|Transparency||Transparency is a major part for gaining a Trusted Advisor relationship with senior business stakeholders and engineering teams. Often, the Enterprise Solution Architect must deliver messages that are not what stakeholders want to hear so setting expectations early and being transparent to the decision-making stakeholders is critical.
Take for example the situation where Enterprise Solution Architects coordinate the support for a shared enterprise-wide software platform. Enterprise Solution Architects must be able to gain support from several Lines of Business and engineering organizations to commit to the software platform. This is a tremendously complicated task that can be thwarted from several angles. Enterprise Solution Architects provide a Leadership role through this process and the great ones build Trusted Advisor relationships through transparency.
Adaptability is a core competence of the Enterprise Solution Architect because of the diverse situations and audiences they are faced with on a daily basis.
As an example, I once led a highly complex software design discussion with highly-talented and, should I dare, 'critical' engineers involving system integration modeling of our Microsoft Online Order Management systems in the morning, sat with business leads to brainstorm licensing business logic for our to-be-released Online Products over lunch, and delivered an architectural brief to a group of Business and IT Vice Presidents on the impacts to our enterprise for our S+S company strategy all in the same day.
|Achievement||Enterprise Solution Architects are measured by adoption. Everything they are set out to accomplish is carefully prioritized and burned into the forefront of their consciousness. Think of Stephen Covey's second habit of highly effective people "Begin with the End In Mind". The 'end' for an Enterprise Solution Architect is the delivery of change whether it be decisions on which software platforms are to be built and how they are designed, delivery of enterprise-class software solutions, optimization of the application portfolio, enabling IT with the right architect to deliver faster, efficiently and cost-effectively.|
|Initiative||Enterprise Solution Architects have the opportunity to view broadly across the company and often are quick to see opportunities for progressing the advancement of the enterprise architecture. They look for ways to gain adoption quickly and often are able to provide feedback to IT process owners or organization designers on observations made that potentially can improve the organizational effectiveness in terms of improved delivery to the business.|
|Optimism||Enterprise Solution Architects know that no one want's to work with pessimistic wet blanket. Gaining momentum is critical to the success of delivering large-scale initiatives and, therefore, optimistic leaders help carry the momentum. Not all Architects can perform the Enterprise Solution Architect role. It is mostly a thankless job and often highly criticized. I'm sorry if this sounds like a bleak picture for the Enterprise Architect but to be honest, we must be optimistic to try, try again.|
I just love this Leadership ability because it is often so sorely lacking in the IT industry, thus representing a great opportunity to apply focus and get huge improvements. Engineers often don't have the training or basic social skills to have a positive dialogue. All the more reason why the Enterprise Solution Architect has very mature empathy abilities so as to resonate and get decisions made to rapidly enable change. I can't put it better than Jack Welch's "Three S" approach to Leadership; Self-Confidence, Simple, Speed. I've created a conceptual model of the "Three Ss" concepts and added a couple of new one's taken from anecdotal mentions from Goleman for another View to help describe the concepts.
Here's how to relate Empathy to the Three Ss concept. Through Empathy, an Enterprise Solution Architect can identify a Simple message that resonates with others allowing them to act on the message with speed.
Enterprise Solution Architects often find themselves in organizations that lack fluid understanding for involving enterprise-wide concerns. This is common and natural. For example, large companies often have several business strategies that are not in-sync eventuating in siloed supporting IT systems. Enterprise Solution Architects must be able to understand who to influence in order to contribute due diligence efforts for deliver solutions to enterprise concerns such as application rationalization, delivery of shared enterprise software platforms, software platform designs built for flexibility, reusability and availability.
Now, I would like to make a distinction between Organizational awareness from a Machiavellian politician who studies organizational dynamics and manipulates and drives their self-interests. Like Goleman, Stephen Covey and Jack Welch note often, "those individuals are a bore and bring down organizations." I'm in complete agreement.
|Service||Service is one of the most important competencies Enterprise Solution Architects have. We are humble and serve our business partners and teammates to achieve our goal, adoption. I described tips for gaining adoption in a previous blog - see here. Enterprise Solution Architects fill the gaps and complement the team's plan directly or indirectly through encouraging the appropriate role owner to pick it up.|
|Inspiration||When Enterprise Solution Architects discover business problems that cross several Lines of Business and engineering teams, they have a tough challenge ahead of them. Often, Enterprise Solution Architects make all groups aware of the problem and inspire them to collaborate on solving the problem together, thus bringing synergy to the organization.|
|Influence||In the software industry, if you are not directly writing source code you are in an influencer role. I cannot stress the importance Enterprise Solution Architects place on this leadership competency. It is critical to the success of gaining momentum for software initiatives and truly delivering in a Trusted Advisor capacity.|
|Developing others||Goleman often cites statistics that the IT Business sorely lacks this competency. Goleman believes that this is likely due to the fact that engineers focus on improving one's technical skills rather than focusing on improving other people's skills. He's got a great point.
Enterprise Solution Architect's understand that no single role will be responsible for improving IT's value proposition to their business stakeholders. We spend a lot of time growing an organization's competence. The best Enterprise Solution Architects I know, dedicate time to mentor others, contribute to skills discussions and often express their ideas in broad audiences all with the intention of helping grow the discipline in the direction of improving IT's value proposition to the business.
In fact, Developing others is why I blog (and I wish I blogged more often), mentor aspiring Architects in and outside of Microsoft and one of the sole reasons I choose to be an Enterprise Solution Architect within Microsoft.
With this blog, my hope is that I catch the attention of another Architect to investigate and learn more about leadership competencies and contribute to their growth and success.
|Change catalyst||Many esteemed thinkers in the space of Enterprise Architecture often evangelize the role of Enterprise Solution Architects as 'change agents'. This is true. Like I discussed in the Initiative item above, Enterprise Solution Architects do have an unusual position of seeing an impartial view of the 'big picture' and when opportunities for gaining efficiencies regarding re-prioritization of our business needs, tweaking our delivery process, restructuring governance models, identifying skill gaps, to drive change for improving the IT organization's effectiveness to deliver more value to the business, we do it.|
|Conflict management||I love this competency! In the IT industry there is so much social insecurity that it impairs even the most trivial discussions resulting in relationship destruction. These outcomes are unacceptable to Enterprise Solution Architects and we mitigate these outcomes by leaning heavily on our Conflict Management skills.
For example, Enterprise Solution Architects often find themselves facilitating an initiative via a virtual team of multi-discipline resources from all over the organization. Inevitably, there are pitfalls to avoid from insecurities that exist with each of the team members. Normally, insecurities manifest themselves from team members that were part of a failed project they wish to not be reminded of, or senior resources wanting to be recognized for their position by subordinates, or from highly educated individuals who want to be publicly recognized for their educational credentials, or for cultural sensitivities typical in the western and eastern cultures and the list goes on.
At the surface, one might say "why do they behave so childish?" and they'd be right if it weren't for the fact that people are very emotionally complex beings - we are not beings from the planet Vulcan where logic prevails over all social conflict. 🙂
Enterprise Solution Architects identify and respect other's underlying personal insecurities, which are often unsaid, and empathize with them in a very non-threatening manner, and usually in private. Then, suggest a simple resolution to the group that a) can progress the group's initiative, and b) does not seem threatening to any one person or the group they represent.
|Teamwork and collaboration||Enterprise Solution Architects, by necessity, have experience managing project teams, virtual teams, relationships "owners" with other organizations on behalf of their organization to deliver planning and delivery functions. We often exude the ability to create an environment with strong collaboration and do this by leveraging our Teamwork and Collaboration competency.|
Just some closing notes
There is nothing new described in this blog other than an attempt to articulate a relationship between two concepts. It is my interpretation of the fantastic work already delivered by Leadership thought-leaders in the context of the Enterprise Solution Architect role.
Acknowledgements: One of the great pleasures from working at Microsoft is the opportunity to work with unbelievably talented people. One such person is Harry Tucker and a few others whom I'm not sure I have the right to publicly identify...Jeremy, Mike, Chad and Gray. 😉 Anyway, much of what I've written below was directly triggered by their coaching and I'm very grateful to have crossed paths with these individuals.
Here are Daniel Goleman's Leadership Competencies: