Saturday, September 25, 2010

A new context for EA: The Enterprise: An eco-system of Values and Value

Reflecting on recent discussions, Tweets and other online threads, there seem to be two reoccurring and related topics:

  1. Making Enterprise Architecture valuable
  2. Selling the need for Enterprise Architecture practice to CxOs.
Recent discussions with the OMG EAC2010 Working Group, Brenda Michelson, Sally Bean, Verna Allee, Chris Bird and Chris Potts are shaping a ‘Next Practice’ point-of-view for Enterprise Architecture. All seem centred around values and value:

Values = ‘The things cared about”

Value = “The worth of an interaction between Systems”.

How do the V’s apply across an Enterprise? My definition of Enterprise includes the subject organization’s relationship with customers, markets, and trading-partner communities.

Value Network Analysis seems to provide one of the simplest ways to represent these relationships, in this System-of-systems, we call the Enterprise. Value Network Maps are a representation of the Roles (sub-systems) and the interactions between them. Each Role has a set of dominant Values (things-they-care-about) and a number of ‘transactions’ that produce and consume tangible and intangible value with other Roles.

Click here for examples of Value Network Maps.

I believe understanding “The Enterprise” as a complex system of interacting Values and Value-Transactions is fundamental to selling the need for Enterprise Architecture as a practice (note: whether or not someone carries the title ‘Enterprise Architect’). A recent LinkedIn discussion with Verna Allee helped clarify this perspective:

“… value network mapping indeed provides an overlay for business processes. … This gives you a "process" view, but it is one with all of the key intangible interactions built into the process and not mysteriously hanging outside. At Boeing VNA is their Lean + tool and they use it extensively prior to doing the deep dive into process modeling. It serves as that reality check to be sure that a) all of the critical interactions are addressed and b) the processes do not become over structured in contrast to what is most essential.

The discovery, and the concise abstraction of ‘The System-of-Values’ across the enterprise, seem critical to understanding the style of EA required and its “Worth” to the subject organisation.

The ‘Systems-Of-Values’, will vary, sometimes dramatically, from company to company and will change over time depending on all sorts of factors from market demand to changes in leadership.

Brenda Michelson recently commented that she always does anthropology before architecture; I believe this exploration of the ‘V’s’ aligns with that thought. I also believe, that it is possible to create a usefully abstracted, values-based reference model of the enterprise that acts as a grounding-point subsequent views of EA (e.g. process, information and technology).

This worldview of EA seems all the more important as governments and businesses need to become more connected to external organisations to stay relevant and aligned with the values of their citizens, customers and trading-partners.

1 comment:

David Meggitt said...

Nigel, I approach the EA concept from the value network perspective that you mention in this post.

It is, indeed, important that the EA movement reflects deeply on the outcomes of its contribution to Government IT success in the UK. There is growing realisation that current UK Govt. procurement policy, influenced by EA, needs a radical review.

Your contribution, here, is a most welcome start, even if it only opens up that glimmer of understanding that it is people ultimately that drive performance, despite the systems and formal processes, underpinned by IT, that operate in parallel with the informal networks that are undrpinned by trust.

Following our meeting with Sally Bean in May 2009 I mapped out a rudimentary set of connections between the value network approach (VNA) ( see open respource site at ) and the EA VPEC-T

You can find it in a Google doc spreadsheet here ....
Maybe, better late than never!

The last row, "behaviour," in the spreadsheet, is not strictly a classic VNA factor, but one that is implicilty connected to it and which appears in the original VNA object model. Behaviour in this context is principally about how people behave / act in the roles they play and how they develop relationships.

In the latter, we can see the link to the VPEC-T Trust. Accordingly, it is quite wrong in my view to refer to "relationships" between Roles.

Admittedly, we do refer to patterns of relationships when examining organisational configurations, but the heart / soul is missing... the essence of human interaction. A "role", in UK English, is possibly best viewed as a script that real people follow as they participate and contribute to the activities that transfer, enhance, create, co-create value to deliverables, both tangible and intangible, formal and informal within the whole... and Trust is key in this.

VPEC-T resonates well with VNA and I look forward to the results of your continuing discoveries.

Best wishes, David