One of the manifestations of the mid-Level 2 sticking point referred to in an earlier post is around Enterprise Architecture (EA). At the risk of over simplifying, way back, most IT shops had some kind of Technology Architecture (TA) capability - usually focused on selecting and enforcing standards, providing an overall schema and logic for physical hardware, networks, and perhaps delivering technology roadmaps (e.g., what gets retired, what replaces it, how). Typically, as TA evolves (matures?), there is an increased focus on the information and data domains, and TA becomes Information Technology Architecture (ITA). Note: sometimes the labels don’t properly align with the reality, so we find Technology Architecture efforts referred to as ITA, but they really do a poor job of addressing the information domain, and ITA efforts referred to as EA that do a poor job of addressing the business process domain. The next shift is when ITA evolves into Enterprise Architecture - and the really ...