The Next Generation CTO and a pragmatic view of Future Tech

I created this blog to share my thoughts around the evolving roles of the Chief Technology Officer (CTO), Chief Innovation Officer and Chief Strategist. Please click on the 'subscribe' button to receive email notifications when articles are posted. Thank you for  contributing to this very important topic and don't forget to view my intro video  which attempts to articulate the reasoning behind the blog's creation. Phil West Here is more information about me. NOTE: If viewing 'full screen' on a PC, please ensure video playback is optimized by clicking on the YouTube settings icon and changing the Quality to 1080p Video Transcript As a technologist, I have always been fascinated with trends in technology and how businesses exploit these trends to create new markets or enable a competitive edge within their existing market. I believe that in this rapidly expanding, technology-fueled world of ours, the role of the CTO is becoming even more critical in

Before we dive into why I believe Enterprise Architecture (EA) and Technology Strategy should belong within the same organization, I would like to take a moment to review some definitions. There are many ways to define these two functions based on how they are deployed within an enterprise and the problems that they are designed to address. My attempt here is to keep the following descriptions at a high level to incorporate all the common variations of Enterprise Architecture and Technology Strategy. What is Enterprise Architecture? Enterprise Architecture, at its core, focuses on ensuring that technology is aligned with business strategy and applied or adopted in such a way that technical debt is minimized. Additionally, functional, and technical fitness is measured along with the level of compatibility with existing technical architectures. The artifacts of EA include a view of the entire enterprise in the form of Business Capability Models and Architectural Models that represent eve