Road Maps Are Powerful When Linked To Business Outcomes

The use of road maps to illustrate technology plans is fairly widespread. Whether it's a vendor explaining its product plans or a technology architect showing the evolution of a particular area of the infrastructure, road maps are great for communicating what happens when. And when plans as illustrated by the road map get sign-off, they can become a useful tool in change management as well. Someone wants your key resources for a special project? Fine, but all the dates on that road map they just approved just shifted six months to the right. Road maps tell the story of what to expect an organization to accomplish for the foreseeable future, and that's what makes them powerful. 

That's why road maps that link traditionally difficult-to-explain areas of technology, such as those related to information management, to specific and highly desirable business outcomes can be a major win for architects looking to communicate what they're doing and why. There's always been a Catch-22 about explaining the value of complex technologies to audiences with no appetite for technical complexity -- but with needed sign-off authority for key resources (like funding). If the EA team has credibility (OK, that can be a big "if"), just showing the interrelationships between business outcomes, business capabilities, IT projects, and required activities in the various EA domains can satisfy the need for "explaining" that complex technology. Or for explaining the need for that not-well-understood architecture process that requires business involvement, such as information architecture development or governance. 

Here's a rough example. Other detailed views can supply supplemental information, but this summary view tells the story of how the business goals and strategies drive changes to how business capabilities are instantiated in the application/information/technology architectures. 

 

Road Map With Linkage To Business Outcomes

I was working with a client recently who was having trouble communicating to non-architects in the business as well as in IT about what the EA team was doing. They wanted a graphic that captured their planning in a compelling way but rejected conceptual graphics like enterprise operating model diagrams. I showed them this type of road map and it clicked immediately. 

What works for you? Has EA's broadening scope into business architecture provided the info you need to finally provide a comprehensive view of how the enterprise architecture will evolve? Do you have another way of showing it? Please share!

Comments

Gene, Thanks for the post. I

Gene,

Thanks for the post. I like the diagram and would be interested in seeing the differences in the representation of the roadmap for each of the phases shown on the diagram. I use a diagram that would work well as a drill down from this diagram. I relates the linkages for a single project to strategy, business and technology.

I will attempt to build one of these diagrams for a university and see how it resonates with our senior staff as well as our business and technology line staff.

Thanks, Leo

An idea - the WHY Code

Thanks for this post Gene - its good to read articles that focus our work on what's important.

The business outcomes / goals should be the starting point for any project road-map. It helps to ensure that all your people share a common understanding of the projects purpose.

I'd like to introduce you to the WHY Code - if you're receptive - as a way to focus people and information around the key questions: What are we trying to achieve? WHY? and How shall we go about it.

An example "Strategy WHY Map":
http://www.knowledgegenes.com/home.aspx?kgid=21795&t=moretext

Please send me a mail if you've the time to explore more,

Cheers for the good article.