Showing posts with label John Zachman. Show all posts
Showing posts with label John Zachman. Show all posts

April 25, 2008

Self-Determination and Enterprise Architecture

There is an age old question whether we make our own fate or whether it is predetermined.

For thousands of years, people have turned to prophets, fortune tellers, mystics, and star gazing to try and divine their futures. Yet, at the same time, we are taught that every child has the opportunity to become the President of the United States or an astronaut, or whatever their hearts desire; that laser-like focus, discipline, repetition and determination breeds success. Haven’t we always been taught to always try our best?

Surely, this is one of the irresolvable conflicts that philosophically can never be truly resolved: If the future is already predetermined, then how can we affect it? Further, if our actions can impact the future, then how the future be predetermined?

The way ahead is to work to influence our future, knowing full well that many things are indeed beyond our control.

From an organization perspective, there are no guarantees for the future, so we must take the reins of change, plan and manage it: one way we do this is through enterprise architecture.

In Fortune Magazine, 5 May 2008, in an article entitled, “The Secret of Enduring Greatness,” it states that “the best corporate leaders never point out the window to blame external conditions; they look in the mirror and say, ‘We are responsible for the results.’”

The future of our organizations are not static and so our leadership cannot rest on its laurels, rather we must continually plan for and execute innovation and transformation.

If we look at the largest corporations in America, the Fortune 500, we see that companies rise and fall to/from prominence with almost unbelievable speed. Here are some examples:

  • “The vast majority of those on the list 50 years ago are nowhere to be found on the current list” (only 71 of the original 500 companies from 1955 are still on the list today).
  • “Nearly 2000 companies have appeared on the list since its inception.”
  • “Some of the most powerful companies on today’s list—businesses like Intel, Microsoft, Apple, Dell, and Google” didn’t even exist in 1955 and conversely, “some of the most celebrated companies in history no longer even appear on the 500, having fallen from great to good to gone.”

So if the tides start to turn down for a company, what are they to do—simply accept their fate, and perish like so many of those that came before them or do they fight to survive, knowing full well that they may not or will likely not succeed?

I say we fight to survive—we plan and execute change—we transform, and we live to fight another day.

“Just because a company stumbles—or gets smacked upside the head by an unexpected event or a new challenge—does not mean that it must continue to decline. Companies do not fall primarily because of what the world does to them or because of how the world changes around them; they fall first and foremost because of what they do to themselves.”

One example is IBM that stumbled in the late 1980’s in relying on what was becoming commoditized hardware, but transformed themselves in the early 1990’s to a software and services juggernaut. Similarly, Apple transformed from a niche computer manufacturer to a consumer electronics dynamo with their innovations such as the iPod and iPhone.

Essentially it comes down to the ability of the organization to manage change and complexity (as John Zachman stated) to adapt and transform, and we do this through enterprise architecture


Share/Save/Bookmark

March 4, 2008

John Zachman and Enterprise Architecture

In the Journal of Enterprise Architecture, February 2008, John Zachman, the father of EA, talks about core definitional elements of enterprise architecture.
  • Enterprise versus IT or Applications Architecture—”First Enterprise Architecture constitutes a paradigm shift and many people have not yet been inclined to make the mental, cultural, and behavioral adjustment to engineering and manufacturing the enterprise” and I love that phase—engineering the enterprise!

“Because…many of the skills required to the work of enterprise architecture are typically found in the Information Systems community, some people misconstrue the Framework intent as an Information Systems schema rather than its true intent as an ENTERPRISE schema.”

And not only is the Zachman Framework misconstrued as an Information Systems schema, but many people mistakenly confuse the whole EA with IT or applications architecture. But EA is not focused on IT or applications, but rather on the overall organization—the enterprise.

  • Lexicon—“As global communication and collaboration expands, there is an increasing requirement for semantic coherence. If people’s words do not mean the same thing, there is neither communication nor collaboration”—another good one, semantic coherence!

Without a lexicon with common definitions and standards for usage, we will not be talking to each other, but past each other.

Moreover, if we can’t even define EA elements in a common way, then how can we ever make them interoperable?

As Zachman says, “The underlying classification and components of architecture must be consistent for any interoperability (internal or external) to be effected.”

  • Classification, Taxonomy, and Ontology—“Enterprises are complex. Managing the knowledge base of the enterprise that is required for enterprise operation and change is complex. The key to managing complexity is classification.”

This is so true. We need to categorize and relate items to make sense of them. Moreover, I would say we need to roll this information up to what I call the profile level—the big picture, strategic view using information visualization—so that our executives and decision makers can quickly understand the information and come to a decision point.

“Humanity for seven thousand years has found no mechanism for accommodating complexity and change other than architecture,” says Zachman.

EA is the way to plan, manage, and measure change in our increasingly complex world. And if we don’t take control over our enterprises and their future destiny, then we will be controlled by them.


Share/Save/Bookmark

October 27, 2007

Lecture by John Zachman on Enterprise Architecture

John Zachman Lectures on Enterprise Architecture:


Share/Save/Bookmark