EA – How to identify an organization’s vision and direction

Enterprise Architecture is about creating orchestrated change.  Understanding the vision and then designing a plan for how to move the organization from the current state to the future is one of the main objectives of an Enterprise Architect.

 The only way to do this is to understand the senior executive teams’ visions, priorities, and appetite for change.  Senior executives are the ones accountable and liable for the organization and for this “change” to be successful there must be one clear vision and direction endorsed by the FULL senior executive team. 

Time and time again I am asked… How do you get the senior executive team to land on one clear direction and more importantly how and what do you get them to prioritize?  My response to questions like those is… How much time do you have?

Every organization is different, and the answers depend on the environment and the people within it, there is no way to just give one answer to those questions.  What I can do is walk you through the process that I take to come up with the answers and along the way explain some of the hurdles I have run into.

I land on the vision by focussing on:

  • what the business of the organization is and what it should be,
  • the systems, both processes and applications within the organization and are they following industry best practices,
  • the strategic areas of change and what they mean to operations and
  • each of the individual senior executives’ thoughts and goals. 

I bring the full senior executive team together and challenge them on aspects of the four focus areas mentioned above, we explore status quo versus eutopia type scenarios.  Taking this approach will get discussions going and will lead to the best decision for the full organization with the one leader typically the CEO making the final decision.

I land on a prioritization by focussing on:

  • business capabilities or the functionality it takes to perform the business activities and
  • potential risks which includes such things as manual errors, inefficiencies, data integrity, safety, reputational and litigation to name just some.

Knowing that priorities must be driven from a risk, liability, compliance, value add and modernization perspective I apply potential risks to business capabilities. I then present them to the full senior executive team during a prioritization exercise where we explore what was observed during job shadowing sessions.

For a step by step guide demonstrating my approach using a fictitious organization – How to “DO” Enterprise Architecture – Part I – Creating the Consolidated Roadmap.

Published by

Lisa Pantuso

Lisa spent almost 30 years working in both the private and public sectors, and has a reputation for getting things done. As the Government CIO Senior Information Architect she led a cross government Enterprise Content Management initiative. The Provincial ECM Strategy was published in 2012 and recognized as the first Provincial Strategy to be endorsed by all Ministries. In 2020, Lisa left to start teaching others the approaches and techniques that have set her apart.