Author

Roger Evernden

avatar

Roger Evernden is a Senior Consultant with Cutter Consortium's Business & Enterprise Architecture practice. He specializes in the highly practical use of EA to manage organizational transformation. Read more ...

EA Myths

 Posted by on Jul 2, 2013  15 Responses »
Jul 022013
 

A recurring theme in enterprise architecture forums and debates is: “How do we demonstrate the value of EA or justify architectural overhead?” Some may view these discussions as academic, which compounds the problem, because it supports the idea that enterprise architects don’t really understand their role, that they don’t have a common definition of enterprise architecture, and that we consequently don’t need them! By far the biggest problem is a mind-set that perpetuates certain misconceptions about EA. All too often the rewards from architecting are seen as long-term outcomes, EA is not regarded as an essential element in enterprise transformation, and the value from EA is not measured effectively. The first myth is that EA Read more

Apr 092013
 
Marketects: Delivering Good Enterprise Architecture

Good architects also need to be good “marketects”: they must be able to sell and promote their cause as well as publicize their achievements, outcomes, and results. But how do they do this? What tips and guidelines from the world of marketing can architects adopt to their advantage? First of all, what do we mean by “marketecture”? With a cynical hat on, some might argue that marketecture is about selling something that you don’t really need. In a Dilbert cartoon from 2009, the Director of Marketecture says that “it is better to seem good than to be good. A misleading benchmark test can accomplish in minutes what years of good engineering can never do.” In Read more

Dec 192012
 
Enterprise Architects Will Need To ...

Like last year, I focus my predictions on how current trends will impact Enterprise Architecture in 2013. I see three things coming: 1. Make sense of big data. Big data will continue to get a lot of press, and vendors will be keen to show off new tricks with data integration. The enterprise architecture teams need to beef up their information architecture capability and develop appropriate Enterprise Patterns to participate in this debate and to be able to respond intelligently to this pressure. 2. Mobilize for mobile. The EA team need to expand application patterns to show how a multitude of disparate apps work in conjunction with a more traditional legacy application landscape. 3. The forecast Read more

Nov 202012
 
The Business of Understanding

Contrary to popular belief, the term “information architecture” is not synonymous with designing and structuring websites or developing an Internet-based information base. The phrase was first introduced in 1975 by Richard Saul Wurman, who is probably best known for founding TED Conferences and TEDTalks. When he introduced this concept, Wurman was thinking of information in a broad sense. He was one of the first to recognize that modern technologies were likely to produce “a stream of bytes that leaves us inundated with data but starved for the tools & patterns that give them meaning. In reality there has not been an information explosion, but rather an explosion of noninformation, or data that simply doesn’t inform” (Information Read more

May 212012
 

Products and processes are two of the most vital components of a successful business. Useful, relevant, or innovative products are important for attracting and keeping customers. Efficient and effective processes are crucial to making the customer experience enjoyable and worthwhile. Product and process should therefore be included as key components in any business architecture. But, too often, product and process are not given the architectural priority they deserve. While physical products such as cars or planes are highly engineered, enterprise architects tend to overlook the architecture of information-based products and view them instead as the domain of business managers. (Note that physical products, such as the engineering of cars or computers, are more likely to Read more

Dec 122011
 
A Focus on Environment — not Enterprise — as the Context for Architecture

I have three related predictions for Enterprise Architects in 2012. Actually they are more like ongoing trends, but they are the ones that I think will be most relevant when making architectural decisions next year. All three could be summarized as a need to focus on environment as context, rather than enterprise. Enterprise Architecture puts IT systems in the context of how IT supports business and management needs, and it places business processes and products in the context of the organizational structure, its strategies and capabilities. But enterprises don’t operate in isolation, and increasingly their architectures need to be defined in the context of the broader environment. I see three reasons for organizations to start Read more