Podcast on the Enterprise Architecture profession–Interview with CIPS’s Stephen Ibaraki

Way back in April, I announced the first of two podcasts with the Canadian Information Processing Society.  I just realized this weekend that I had not announced the availability of the second of those podcasts.  Error corrected.

The second podcast, once again hosted by the inimitable Stephen Ibaraki, focuses much more on the growth and progress of the Enterprise Architecture profession itself.  Specifically this podcast reflects upon:

  • The role of Business Architecture in Enterprise Architecture?
  • Does an Enterprise Architect have to be able to discuss technical issues like cloud computing?
  • How would you define Enterprise Architecture?
  • The value proposition of the Enterprise Architect?

 

For full details, and a link to the podcast, visit the Canadian IT Manager’s Connection, a TechNet site. 

Why Most Organizations Have Weak Visions

We do a lot of strategy work with organizations big and small. It is very curious to me that few organizations create strong vision statements. A powerful vision statement clarifies management’s aspirations. It sets broad direction and inspires people to go beyond the norm. If you create a set of reasonable goals people will meet […]

Why the CIO Should Heed Stephen Covey’s 7 Habits

Steven Covey, author of the highly acclaimed management book, “The Seven Habits of Highly Effective People” passed away recently. I’m dedicating a post to him because his book and teachings were memorable during my early management training and his simple, but profound principles are particularly timely for CIOs today. When I look back at Covey’s legacy, two overarching themes come to mind: working effectively with others and time management. Both are interrelated and incredibly relevant […]

If you liked this, you might also like:

  1. 5 Steps to Brighten Shadow IT

5 Steps to Brighten Shadow IT

With the popularity of public cloud offerings, BYOD and personal productivity apps, rogue technology acquisitions (at least from IT’s perspective) are more pervasive than ever, creating a new focus on “Shadow IT.” Our 2012 Digital IQ study of 489 executives found that 30% of technology procurement is outside the CIO’s budget. A wise proverb says: “If you want to go fast, go alone. If you want to go far, go together.” What if you need […]

If you liked this, you might also like:

  1. 6 Steps to Close the IT Skill Gap
  2. 4 Steps to Manage Your Technology Portfolio
  3. Why the CIO Should Heed Stephen Covey’s 7 Habits

Should the CIO Ban Email?

I was at a conference last week where I heard about a CIO who is banning email. Looks like we’re not finished having a conversation about how email is hampering employee productivity. What tools and techniques can CIOs employ to improve enterprise communications in the face of a proliferation of channels? Is trading email for social collaboration tools the answer or do we need to change employee behavior? How about using the right tools at […]

If you liked this, you might also like:

  1. BYOD and Your CEO
  2. Time is Running Out for the CIO to Lead on Social Media
  3. How a CIO Can Help Improve America’s Education

THE FIVE “Vs” OF LEADERSHIP

There are lots of models around describing leadership characteristics and roles. Here is one I have been using for a number of years to introduce the role of the leader. While not a complete model, it does get across some of the more important attributes of excellent leaders. VISION – One of the first roles […]

Positioning an Enterprise Architect for Success

As I found in our Enterprise Architecture team in Microsoft, each time an Enterprise Architect is assigned to a specific area of the business, each one has a unique “engagement” with their stakeholders.  In very large organizations (like mine), there may be many different IT units as well as many different business units, all involved in a particular strategy.   Each situation is different.   This leads to a common problem that can framed with two questions:

  1. So how do you know if your Enterprise Architect is doing a good job?
  2. How do you set the right expectations to position that Enterprise Architect for success?

A Model for Positioning an Architect

We developed a simple grid that helps to position the EA with respect to a specific area of the business.  The two axes of the grid are: Architectural Maturity of the “segment” and Maturity of the Architectural Engagement itself.  Within each cell, we put a description of “what we want the EA to do” if they find themselves in that position.

Note that maturity of the engagement is a measurement of a relationship: specifically the relationship between the “business customer” and the Enterprise Architect.  Architectural maturity of the segment is measured against both the business area and the IT groups that they use (see below).  You need to measure the maturity of BOTH variables in order to understand what an Enterprise Architect will need to do to be effective.

image

Note that the Architectural Maturity axis has four levels, cryptically described as “Level I” through “Level IV”.  This is a reference to our internal maturity model, which I’m not at liberty to share in detail. 

The broad strokes are:

  • Level  I – architecture is not a trusted and well-understood role in business change or IT programs.  (This includes business, information, solution, and technology architecture).
     
  • Level II – architecture is used and their processes are defined, but not consistently and not well. 
     
  • Level III – architecture is performed consistently and is part of governance as well as some portfolio planning activities.  The business stakeholder does not take ownership of driving the funding and execution of the roadmaps developed by the Enterprise Architect.
     
  • Level IV – architecture is performed consistently and is involved in planning and governance.  The business stakeholders involved in funding and overseeing the business changes themselves are engaged with enterprise architecture, have been key in developing the roadmaps, and follow through with regular updates to the future state models and the roadmaps.  In addition, they decide on which initiatives to use BASED ON the content of the roadmaps. 

 

Using this model

I’ll provide two scenarios to illustrate how this simple grid is used. 

In Fabrikam, we are Enterprise Architects.  Fabrikam manufactures and distributes consumer electronics.  There are six divisions that manufacture different kinds of products (kitchen appliances, television and radio, automotive, etc). Let’s say that we have 18 Enterprise Architects in our EA team.  Fabrikam’s EA has divided into three working groups, each with six architects.  Maria manages one of these teams, and has six enterprise architects working for her.  Her team focuses on addressing business issues related to supply chain management. 

Maria is performing an annual review for two of her architects.  They are Tomas and Jai. 

Case 1: Tomas

Tomas is working with the kitchen appliance team.  This is the oldest division in Fabrikam, and they have their own IT group that has been stable for many years.  That team has established processes for IT architecture but no business architecture.  Their architectural maturity is Level III.   Tomas just moved over to the kitchen appliance division from the television and radio division.  He is a well established architect with years of experience, but the kitchen appliance team is just beginning to get to know him.  As a result, the maturity of the engagement is “Useful.”  

The intersection of these axes has the following text:

  • Engage in existing review and governance processes
  • Engage stakeholders in cross business decisions
  • Collect current state data

Maria can set expectations with Tomas and with the Kitchen Appliance division.  Tomas will be expected to engage in existing governance and review processes.  He will be expected to work with business stakeholders in the kitchen appliance team as well as other divisions to address shared opportunities, capability overlaps, and strategic prioritization.  He will be expected to collect current state information models, system models, technology models, and business strategies for the EA repository.  He will be measured on his ability to deliver on these expectations.

Case 2: Jai

Jai is working with the automotive division.  This is the newest division in Fabrikam, and they are just beginning to roll out their first set of after-market automotive radios and CD players in the North American market.  Their IT division is small and rather chaotic.  Their architectural maturity is Level I.  Jai has been working with the automotive division for about two years, and has repeatedly earned recognition from their business leaders for his skill and depth of knowledge.  The maturity of the engagement is “Influential”.

The intersection of these axes has the following text:

  • Demonstrate EA specific methods and deliverables
  • Drive the scoping, approval, and oversight of an enterprise-relevant project

Maria can set expectations with Jai and with the automotive division.  Jai is expected to demonstrate EA specific methods and deliverables.  The teams know him and trust him.  He can demonstrate how EA can be valuable by simply doing the work and showing how valuable the results are.  Due to his level of influence, he can work with the business to invest in an area of improvement that will benefit the entire enterprise (for example, a project to improve the distribution of finished goods to retailers), and then work with the IT teams and business stakeholders involved to get the project launched and oversee its development.  Jai can be measured on his ability to deliver on these expectations.

Conclusion

In small organizations, Enterprise Architects can be “heros” and just “do what works,” but if you are trying to develop a mature EA program, each architect needs to have specific goals and specific deliverables that they will be expected to deliver.  This kind of model, we found, is useful for helping each architect to position themselves and their role in the organization.

Conversational Antipatterns on Message Boards

Architects argue.  I have, over the past year, spent a good bit of time on LinkedIn Message boards.  I’ve watched a lot of people argue.  I’ve learned a great deal about Enterprise Architecture, and a few things about myself, as I’ve compared notes with individuals who have different perspectives and motivations. 

That said, some patterns have emerged, good and bad, for conversing with other architects on these message boards.  In the spirit of the GOF Design Patterns, and the subsequent work on Antipatterns, I’d like to point out some of the antipatterns I’ve noticed repeatedly on the boards, and in each case, these antipatterns cause some level of anxiety.  This is borne out by observing the responses, where frustration is often explicit.

There are nearly always two roles in this kind of argument.  The provocateur ( a person who makes a statement that is challenging or innovative ) and the responder ( a person who responds in a way that triggers the antipattern behavior ).  

Conversational Antipatterns

  1. Don’t misrepresent me with my own words
  2. The problem with your general message is this specific use of a word
  3. If you don’t understand, you should read my published papers
  4. My argument has been validated with my years of experience, so you must be wrong
  5. My certification means more than you think it means
  6. You are using “my” terminology wrong

 

Antipattern 1: Don’t misrepresent me with my own words

In this antipattern, the provocateur will make a statement that appears to conflict with something that they said previously or said in another discussion.  If the responder points out the conflict, especially if done with a direct quote, the provocateur get’s offended and becomes defensive.  Conversation ends.

How to avoid: People are inconsistent but believe that they are quite consistent.  If a provocateur appears to be inconsistent, the responder should simply ask for follow up details.  Don’t pounce in public.  Find out what their real underlying thinking is, rather than picking at words.  If they remain inconsistent, the responder should reach out in private.  In the private message, the responder should point out the text from the other thread and ASK them to explain how these two positions work together. 

How to address: The forum moderator should look at the value of the conversation.  Has the provocateur added useful thinking?  Has the responder?  Normally, the answer to both questions is “yes.” If so, send a warning message to both asking them to assume positive intent and consider the emotional context of the other.

Antipattern 2: The problem with your general message is this specific use of a word

In this antipattern, the provocateur will make a general statement designed to express a “grand idea.”  The  responder will either agree or disagree (usually the latter) but then point out that a particular word, in the response, was used incorrectly.  Perhaps they said “process” when they should have said “capability.”  Perhaps they said “activity” when they should have said “process, activity, and practice.”  Perhaps they said “business” when they should have said “enterprise.”

How to avoid: The responder should start by stating whether they agree with the main idea, or not.  If they disagree with the main idea, offer a reason “why” that has NOTHING to do with the detailed wording.  Take the time to think about what the big idea is, and follow up to understand it, before focusing on a word.  Disregarding a “big idea” because you disagree with a minor distinction in the wording is frustrating to everyone on the community, and stifles the sharing of ideas. 

When you get to the point where you understand the big idea, the responder can offer a suggestion to improve the understanding the idea.  For example, “I agree with your core concept.  It appears that we have similar experiences and I find your description innovative.  It may help, as you go forward to share this idea, if you are careful about the use of the word “zyzzix” because I understand that word to be a synonym of “fryzzam.”  I understand that you make a distinction between these terms, but not all of your audience may agree that these two terms are distinct.  You may find it easier to reach people like me if you use the term “golozarat” instead to refer to this muddy concept.”

How to address: Either of the participants can pull back and “get to the point” by reframing the “grand idea” and ask if the other person agrees with a simple “yes” or “no” answer.  If no answer is forthcoming, no learning is happening.  If you are asked to consider a new big idea, take some time before you respond to think about that idea.  Be willing to learn and grow, not just pontificate.  My father used to say, “sometimes, the best way to open your mind is to close your mouth.”  It’s good advice.

Antipattern 3: If you don’t understand, you should read my published papers

In this antipattern, the provocateur will make a specific statement that appears well thought out, but may be innovative or controversial.  When the responder asks questions for follow-up, the provocateur replies “I explained this in rich detail in my book” or “please read my paper in the Journal of EA Innovation, September 2005, page 14.”  This generates frustration on the part of the readers who cannot hear the full discussion because some of it exists in a book or article that they may not have access to.

How to avoid: First off, if you are an author, you must realize that publishing a paper or book does not give you the right to force others to read it before speaking with you.  You will never be out of the “business” of educating others in your ideas.  Get used to it.  Getting defensive is counterproductive.

To avoid creating frustration, it is OK to point others to your work, but then ALSO offer a summary of what you said in that work and be willing to continue to discuss the problem in the forum.

How to address: When this happens to you, it is probably safe to assume that the author you are speaking with is looking for some validation.  Compliment him or her, and ask them to provide a summary of their thoughts from the book or article so that progress can continue.  If you are a moderator, and one provocateur does this a lot, or gets defensive when others DON’T read their articles, remind them privately of this antipattern.  If they persist, suspend them from the board for 30 days.

Antipattern 4: My argument has been validated with my years of experience, so you must be wrong

In this antipattern, the provocateur will make a statement that appears to be too directive or too specific for others to understand or agree with. If the responder challenges the position, the provocateur claims that their “years of experience” have found their position to be true.  The provocateur remains unbending, and repeatedly argues against any alternatives.

How to avoid: This is tough to avoid.  People form their own mental models of reality and when challenged, they can listen to alternatives, or defend their model.  The problem with listening to alternatives is that it is risky.  They may discover that a past “success” was not as successful as it may have been.  In the words of my friend Jack, “their ears are filled with their ego.”

Often the best way to avoid the problem is to model good behavior in your own contributions.  When posting an opinion, lead with “in my opinion” or “in my experience.”  Use phrases like “I’ve found this to be true in my situation,” and then ask others to share “their situation.”  That way, when someone does respond with a statement like “you are wrong,” you can follow up with a moderation message, like “I believe that our experiences may be different in this respect. I’m glad that you shared your experience.  Can you tell me how we should reconcile our two different sets of experiences to come to a mutual understanding?”

How to address: Usually the best way around this is to respond as above, asking for a common understanding.  However, if that doesn’t work (and it often will fail), then you have no leverage to “require” someone to change their opinion.  Ask if it is OK for the two of you to “agree to disagree” and move on.  There is no point in discussing the same issue over and over.

Antipattern 5: My certification means more than you think it means

In this antipattern, the provocateur will state that a concept that he or she is fond of, applies to the discussion at hand.  When the responder questions the concept, the provocateur responds that they are “certified” or otherwise demonstrably educated, and their certification tells them to use that concept.  Upon inspection, it is clear to all that the certification in question does not cover the same scope as the provocateur claims it does.  An example would be an IT person, certified in the development of software interfaces called “SOA Services,” claiming an understanding of business services or customer services.  Another example would be a person with substantial training in financial risk management claiming that all business decisions in the enterprise begin, and end, from a risk management viewpoint.

How to avoid: As with most of these antipatterns, we have a situation where the ego of one or more of the people may be getting in the way of open communication.  The “certified” individual may, in fact, have broader experience than their certification prepares them for.  However, there is often a predisposition, among those that have been formally trained in a field, to believe that the training describes the world “as it is” rather than the world “as it should be.”  More often than not, the training is simply out of sync with the reality on the ground.

As a result, of the “ego factor,” this antipattern is somewhat inevitable.  It will occur more in some areas than in others.  Unfortunately, in the EA field, it occurs often because of the explosion of certifications and the lack of consistency among the field participants.

How to address: One good way that I’ve found to address this problem is to point out your own experiences, using words that reflect that you are not dictating some universal truth but rather the experiences you’ve actually had.  Use first names of people (replace the actual first names, to protect your friends), and explain how they used the terms and concepts of the space.  Then describe how you worked in that situation.  Try to use successful scenarios to lend credibility to your position.  You want to help them to see that their position may not be universally true.  You don’t want to prove them to be wrong, because that would simply be your ego trying to stomp on theirs.  There are names for this kind of ego-vs-ego behavior.  Avoid it.  It hurts your credibility to engage in it.

Antipattern 6: You are using “my” terminology wrong

In this antipattern, the provocateur will state that a concept has one, and only one, meaning.  The responder suggests an alternate meaning, and the provocateur responds defensively, citing sources for their definition of the term.  This is where you see a “dictionary grudge match” where someone cites a definition from an authoritative source, and another person responds with either ridicule of the source or, even better, another authoritative source with a conflicting definition.

How to avoid: Firstly, if someone questions your use of a word, don’t immediately go hunting for a reference definition.  In other words, model good behavior.  Admit that your definition, regardless of how well sourced it is, was created by other (fallible) people with a particular context in mind. It is entirely possible that the provocateur also has a different context than you, and that the author of the definition that you are painstakingly citing would have created a different definition if he or she had the same context as the provocateur.

Of course, if someone asks you for a reference, it is perfectly appropriate to give one on a message board.  In writing a research paper, you would assume that the reader wants to know your sources, and you would always provide them, but for conversation on a message board, you should wait to be asked.

Secondly, don’t be “possessive” about the terms that you use.  Your openness will reduce the likelihood that others will be possessive about the terms that they use.  If someone wants to use a synonym, agree. 

How to address: One good way that I’ve found to address this problem is to ask the provocateur for their help in explaining their terminology to you.  Most people will be flattered by the request, and will go out of their way to describe what their use of a term means.  If you respond by “reframing” their statement, using a smattering of your own terminology, then you will quickly discover whether that person is interested in conversing with a shared set of terms, or if the conversation can only proceed by acquiescing to their use of language.  If the latter, it becomes a judgment call, on your part, about whether you should continue to interact at all.  It is better to end a discussion on a good note than to fight on forever over the meanings of words.

—-

That’s my list.  I’m sure that there may be more, but these are the ones that crop up often enough for me to want to write about them.  I hope this is helpful for folks who want to discuss things on message boards, like LinkedIn, without becoming entwined in endless arguments.

Six Attributes of a Powerful Business Architecture Practice

Business architecture is still new enough that highly successful practices are difficult to find. Most organizations are struggling to get off the ground and gain traction. However, we can learn a lot from the currently successful trail blazers. Powerful business architecture practices – those making a significant difference in their organizations: Offer a strong value […]

Shhh…. I’m talking, listen to me!

I just want to be heard. And, OK, maybe understood a little. Agreeing with me would be nice too, but honestly, most of the time I would be content with just being understood. And isn’t that what we all want – to be heard, really heard. The problem is, so few people know how to […]

Wicked Problems

In last week’s post ,The problem With Problems, I presented a framework for defining and solving problems. I described how symptoms are often presented as problems, how the immediate situation exacerbates the problem, and how the context provides fuel to keep the problem nourished and growing. Three types of problems live within this framework: simple, […]