EA value measures ? who cares?

Graham,

> I am not convinced that EA has much input to strategy as currently
> deployed by most companies , the savings come frequently from IT,
> such as server or applications consolidation , none of which is
> actually business strategy. Business is comprised of several
> disciplines such as Strategy, Planning , Operational execution ,
> Resource management , finance and more latterly Information
> technology . EA rarely addresses any of these , its simply an
> enabler in one or more of them.

As currently practised, EA does not have much input into strategy. In a ideal world, strategy would be formulated based on EA recommendations. But, EA needs to mature and move up the food-chain for that to happen. As I see it, EA seems to be getting dragged into creating lower and lower level details, possibly because it is trying to be everything for everyone.

One of the goals of EA is to increase the Operational Efficiencies, and for that EA needs to focus on where the bulk of the expenditure (CAPEX, OPEX,...) is spent on. Guess where that might be? That is probably what needs to be sorted and where massive savings could be gained.

From what I have seen, EA would always be an enabler! If I could *tell* my CEO to do something, then I become more than an enabler... But, I guess, I am a long way off from there... Others might be in much better positions?

Best regards,
Joseph

On 6 June, 20:12, Rheinlander Kirk wrote:

> As the organizations create the content of the enterprise
> architecture, by default, they agree to it.
> EA just allows communication and coordination across the boundaries,
> so they know the right things to do.

> Yes, I cut and pasted a relevant paragraph, rather than retyping the
> text again, as it had meaning in both contexts.

> On Jun 6, 2009, at 3:43 AM, C Johnson wrote:

> > I know where you are coming from, however for this context, if one
> > does not have a view (or baseline) of the organisations
> > architecture, then one cannot govern it... where the EA team owns
> > the process or references it, the business still need to understand
> > and agree that the architecture follows what they have and what they
> > see for the future (i.e. objectives, goals)