Related Posts
Dm for referral at adidas
More Posts
Additional Posts in Consulting
Happy fly day from DCA 🙃🙃🙃

Any Seattle tax accountant recommendations?
Best consulting firms without the massive ego?
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.






Definition of Enterprise Architect is evolving rapidly. Back in the days, EA was less about how technology works and how technology fits into enterprise and business.
In the post-Digital, post-COVID era, technology is at the heart of organizations and EA needs to be more connected to technology and architecture. Days of superficial IT capability inventory are gone.
With that background, my job everyday is more or less solving technology problems at enterprise level. You want to implement Salesforce or new custom Microservice! You need Technology Architects to design within that specific platform. However, you need an EA to design how this new platform will work with rest of the IT systems, how duties will be separated, how data will flow, and how all of this will align to business priorities.
A Technology Architect is tactical and focuses on business requirements. An Enterprise Architect is strategic and focuses on business/organizational priorities.
Yes and no. TOGAF is a good high level framework (there are others too). However, these frameworks must be contextualized for each situation in terms of their applicability. I’ve never actually used the full framework. Also, frameworks are technology and solution agnostic and a lot of actual groundwork is still up to you.
When it comes tool, there are tools for developing and maintaining artifacts and architecture dependencies. These are very useful for maintaining pulse of the architecture - however, they don’t solve the problems by themselves. As an experienced architect, you will still have to make sense of what’s captured by the tool and identify patterns (or anti-patterns more often).