Split enterprise architecture into five or more specialities: proposal

Split enterprise architecture into five or more specialities: proposal

Summary: The medical profession has a lot of specialties to tackle complicated problems. Why not enterprise architecture?


Is enterprise architecture trying to take on too much?  Enterprises are complicated organizations after all, to which we're trying to apply complicated technology.

Nick Malik, for one, proposes that EA actually be subdivided into five specialties, to address different business IT problems. In the medical world, there are specialties for each type of condition (ENT specialists, heart specialists, neurologists, and so forth). Here are Nick's proposed EA specialties:

Alignment or Business Architects: "Focused on interpreting strategy, making it actionable, and using it to scope and define business change initiatives.

Application or Enterprise IT Architects: "Implement successful enterprise applications or enterprise systems."

Information Architects: "Manage information assets at the enterprise level in a consistent way

Process Architects: "Improve business processes or reorient business processes to place the customer first."

Strategy Architects: "Help business leaders create new strategies, open new markets, develop new products."

Does such a line-up make sense?

ebizQ colleague Peter Schooff recently posted Nick Malik's proposal, and generated some interesting discussion. Forrester's Gene Leganza, for one,  posits that "most EA programs are already highly dependent upon specialists." However, JP Morgenthal says anytime someone that proposes fixing what ails enterprise architecture "should be seen as a major red flag." A better term for EA would be "multidimensional architecture," since "it's really about applying multiple disciplines in a holistic manner toward a particular scope, which may not be enterprise."

Topic: CXO

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


1 comment
Log in or register to join the discussion
  • RE: Split enterprise architecture into five or more specialities: proposal

    Most large Enterprises already have teams or functional units that split into there own specialties and that creates silos to make any implementation of even the simplest software or network service very difficult. The best way IMO is to have more multipurpose groups. You can combine Desktop support, Windows and Linux user management teams into one group. You create a very dynamic team that will cross train each other and better serve the end user. DBAs and developers should be one group that way projects that need DBA's and software development can work as a team. This group will also do some cross training and problems will be discovered much earlier in the development process. and Networking, server and operations should be one group for all of the same reason, they will cross train and notice problems that normally would be hidden because the silos that are created when you have multiple specialty groups.