Blog post

Enterprise Architecture and Scenario Planning

By James McGovern | April 28, 2017 | 3 Comments

I am conducting research into the best practices in how Enterprise Architecture teams perform scenario planning. Enterprise architecture teams are the group to answer questions such as:

  • What happens if the business adds a new sales channel?
  • What impact does latest technology widget XYZ have on our technology ecosystem?
  • How do we ensure that security and compliance is built into new enterprise applications on day one?


I have observed differing practices for arriving at how the answers to the above questions are formed across Gartner clients . I would like to identify both commonality across organizations as well as novel ideas/techniques used arrive at an answer. I am especially curious to know how enterprise architecture teams are preserving the answers to this questions in some form of body of knowledge and how they might be represented in application portfolio management tools.

Got any thoughts you would like to share?

Leave a Comment


  • AS says:

    Q3 – “The enterprise architecture pattern Security, Risk and Architecture Mixture (SRAM)”

  • For EA, it is generally enough to gather all the uncertainties, select those that would have gone into a full scenario planning exercise and then tell the organisation that they have to design ‘robust under these uncertainties’. The EA governance guards that.

    See Chapter “The Future” from “Chess and the Art of Enterprise Architecture” or watch (approximately the keynote given at EAC Europe 2016).

  • Hi James,

    We have researched this exact topic for 20+ years (my Phd was on it) and we have incorporated advanced scenario planning via multiple architectures into our tool ABACUS.

    Exactly what you describe above and show in your graphic is what we call a Type 4 roadmap.

    DM me and I can share case studies and background.