Enterprise Architecture

A kind of manifesto (short version)

by

Enterprise-architecture is dead; long live the architecture of the enterprise? Or something like that, anyway… Time for a kind of manifesto, I guess? As is perhaps too usual in my writing, the full-length version of the ‘manifesto’ ended up, uh, kinda long……

A kind of manifesto

by

Enterprise-architecture is dead; long live the architecture of the enterprise? Or something like that, anyway… So, what next? Time for a kind of manifesto, I guess? At the least, time for a fairly major paradigm-change in how we view the…

Zachman Ontology, not Framework?

by

Time to rename it?There is an interesting discussion on the Zachman Framework LinkedIn group, about the practical use and tool support for the Zachman Framework. I’ve put up a couple of comments because the Zachman Framework is not a good basis for a practical EA use or tool support, and it is about time that…

Related posts:

  1. The Gill Framework: Do We Need Another EA Framework? We already have too many predefined frameworks for enterprise architecture,…
  2. Zachman Version 3.0 John Zachman recently announced a new version of his framework….
  3. Architecture Frameworks – too complex and multi-dimensional? Following the recent The Open Group’s “Business Transformation in Finance,…

Crystal Ball Time

by

Each year, Anne Mullaney, sets a challenge to the Cutter consultants: to look into their crystal balls for the annual Cutter Predictions campaign! This year I’m predicting more stealth enterprise architecture! I’d like to say that I invented this phrase – but I’ve found at least two previous uses – one in a comment by Peter…

Related posts:

  1. Building planes in the sky EA is like building planes in the skyEnterprise Architects are…
  2. Special Complimentary Offer – Enterprise Patterns Executive Report Follow this link to receive a complimentary copy of an…
  3. Social Architecture In 3 Minutes Social Architecture is an exciting application of architecture techniques. It…

Stop talking about enterprise architecture. Go solve a problem.

by

Many years ago, as a newly minted lead architect, I had a memorable initial 1×1 with our organization’s CIO. After reviewing my hand drawn (pencil on paper) application and information landscape, and hearing the CIO’s vision for common front-ends across retail, catalog and (burgeoning) web channel, we discussed the state of the union, and the inevitable gap from here to there.

After I listed ten or so gap items, I looked to the CIO for verification and prioritization. Instead, the CIO said, “I don’t care what you do, just do something.”

I admit. I was taken aback by the CIO’s response. Afterwards, I sat in my cube wondering why the organization created this new (enterprise architecture predecessor) position, if the big boss didn’t care what I worked on.

Then though, thankfully, I interpreted the CIO’s message differently, correctly. The CIO didn’t care which of the litany of items I picked, because tackling any item would move us closer to the ultimate, customer-centric vision.

This is the perspective I draw from as I advise architects and enterprise architecture groups who struggle in starting, or revitalizing an architecture practice. To get traction, don’t get tangled up in a framework or methodology, go solve a problem.

The problem doesn’t even need to reside in the (traditional) enterprise architecture domain. Nor does the solution have to be perfect, or in classic form. Just move your organization closer to there, from here. Repeat as required.

While this problem-solving, action-oriented approach can slow-down the generation of traditional artifacts and processes, it does accelerate value generation, and really, isn’t that the point.

Need to grow your architecture practice and credibility? Go solve a problem.