Since we don’t know what we don’t know about EA, the first step would be to get to know what we don’t know. Only then we can the right questions.
Given the EA state today, an EA architect should first create and employ own methodology to model the integrated blueprint of the enterprise and guide the transformation.
Too often the “Enterprise” in the EA term translates into experience in the enterprise IT, while “Architect” into a senior IT employee.
Here is another of my favorite Richard Feynman stories (and fitting to honor the memory of Feynman today, for it is 25 years since the day he died): “When I was a kid growing up in Far Rockaway, I had a friend named … Continue reading →
Still on the theme of mastery, and further exploring attention and perception, here is another story I like to tell alongside the Master Butcher and the Agassiz fish tales. It is one of Richard Feynman’s stories from his childhood: One job … Continue reading →
As we start to navigate our way into this topic of mastery, I’d like to explore attention and perception further. Louis Agassiz became known well beyond his own field for teaching observation, and many of his students relay similar stories of how he imbued this … Continue reading →
To launch this series of posts, I thought it would be useful to convene a discussion of the role of the architect and mastery. Talking about Conceptual Architecture several years ago, Dana Bredemeyer relayed the story of the Master Butcher. … Continue reading →
Playing with a “learning chemistry” metaphor: Essentially the idea for this blog is to create an architect’s learning lab of sorts, where we create new insight compounds by tossing a starter into this learning crucible for discussion, so that we can all … Continue reading →
Next to the perennial favorite “What Enterprise Architecture is and/or is not,” I’m inclined to believe debates over frameworks are the hottest debates going right now. Why is that?
What is the future of Enterprise Architecture?