Sharing the Solution Domain Taxonomy

Sometimes, Enterprise Architecture efforts fail.  This is no surprise to folks in the EA business.  This failure occurred slowly, back in 2007 and 2008.  But it did occur.  It took me a while to realize it.  I had developed a method useful for Application Portfolio Management as well as for Service Oriented Architecture called “Solution…

2

How brand-thinking can kill you, and capability thinking can save you

I guess it shouldn’t surprise me that business strategy work is often about constrained thinking.  Thinking “inside the box” is nearly always rewarded well.  After all, the person giving the rewards lives in the same box.  One of the most pernicious kinds of constrained thinking is “brand thinking.”  That is the notion that the value…

6

Moving Towards a Theory of Enterprise Architecture

I’ve been asked a number of times over the years if I can explain the theory of Enterprise Architecture.  I decided recently to reopen that idea.  It’s not a new discussion.  I refer to Tom Graves post on the Theory of EA from 2012 where he posits that the theory of EA, if one were…

17

Do you perform Information Architecture or a Data Architecture?

So, full disclosure, I care about Wikipedia.  Call me dumb, I know.  Wikipedia has been described, alternatively, as the best platform ever invented for fostering useless arguments among ignorant people /and/ the most successful encyclopedia effort of all time.  The truth, as always, lies between these extremes. Well, I’m part of a small team that…

11

The Architecture Manager – the Forgotten Enterprise Architecture Role

I’ve met many Architecture Managers over the years.  Sometimes they go by the title of “Chief Enterprise Architect” or “Chief IT Architect” and other times, the title is “Vice President of Architecture and Strategy” or some variant.  The men and women called to serve in this unique role have a distinct, and uniquely important role…

6

When does EA start to care about sociocultural influences?

Organizations do not work, in real life, like they work on paper.  On paper, there are departments (all shaped like a neat rectangle) and business processes with neat inflows and outflows of responsibility and information.  On paper, you improve things by modeling things on paper, and then moving things around, on paper, then teaching people…

4

Being Forgotten in the Internet of Things

We all know that Google lost a landmark legal case recently.  As of now, a citizen of Europe has the “right to be forgotten” on the Internet.  As of now, a citizen of Europe can ask Google to “forget” them, so that a search of their identity will not return embarrassing information from the past. …

0

EA Debt

(Note: I’ve added an addendum to this post) It has been many years that we have lived with the concept of technical debt.  Martin Fowler did a good job of describing the concept in a 2003 article on his wiki.  Basically, the idea is that you can make a quick-and-dirty change to software.  You will…

4

Climbing the ladder from EITA to EA

One of the most common problems in Enterprise Architecture, and one I get asked about routinely, is the “ladder” problem.  Many Enterprise Architecture teams are formed by assembling a group of talented technologists into a team and giving them a charter to “go do EA.”  The problem is that most of these teams have no…

3

The Purpose of an Enterprise Architecture Framework

Can Social Media create new ideas?  Here’s an example where the answer is “yes.”  I recently blogged about EA models, and what makes them interesting.  I was thinking about providing insight to people who were in the mood to send me updates to the EBMM… a rather tactical post to deal with a rather pedantic…

2