Roadmap examples

I’ve written quite a few words concerning Decision Driven® Strategy roadmaps in the past week, so here’s a few pictures to illustrate important concepts.

Here’s a roadmap for an example water filter company that highlights their decisions concerning possible futures (alternatives across multiple decisions); the roadmap bars/text colors are controlled by the Preference (aka commitment level, decidedness) attribute:

Strategy Roadmap to communicate Preference - Commitment Level

Strategy Roadmap to communicate Preference – Commitment Level

Here’s the same roadmap that communicates Implementation Status based on colors:

Strategy Roadmap to communicate Implementation Status

Strategy Roadmap to communicate Implementation Status

Now I’ve focused on a specific alternative “bar” and run a View Links “traceability” analysis.  I’ve used the results of that analysis to produce a filtered roadmap that shows just the decisions/alternatives linked to/from the selected alternative.  These filtered roadmaps are very useful for communicating “what-ifs”, aligning dates and highlighting problem areas that could cause slippage of a key capability or product.

Filtered Implementation Roadmap – with View Links Trace

Filtered Implementation Roadmap – with View Links Trace

I’ve built-in the ability to filter the roadmap view based on existing linkages or based on manually-selected decisions; this enables the user to create a wide variety of composite roadmaps to communicate strategic alignment status and challenges.

Build your Decision Roadmaps in the Decision Driven® Solutions Framework (DDSF) Roadmap tool to visualize their evolution over time. Start a DDSF trail today by contacting the Decision Driven® Solutions team at trial@decisiondriven.com or solutions@decisiondriven.com.

About decisiondriven

Innovator in Decision Management, Systems Thinking and System Engineering methods and tools
This entry was posted in Decision Concepts, Decision Driven Innovation, Decision Driven Life, Decision Driven Product Development, Decision Driven Strategy and tagged , , , , , , , , . Bookmark the permalink.

4 Responses to Roadmap examples

  1. Roberto says:

    what is the software you use for these roadmaps?

  2. decisiondriven says:

    Roberto,
    These roadmaps are created within my Decision Driven(r) Strategy web application; a subscription based web service. You can sign up for a free 30-day trial by following the Decision Driven Website links on the left side of this page. The roadmap is one view of the strategy decision pattern that is provided within the application; roadmaps are just decisions “put to time”.

    What types of roadmaps are you creating?
    John Fitch

  3. Rafael Guber says:

    Your blog is very impressive, but I am more conversant in the language of history than I am in the language of technology.

    I have created a series of intense historical role playing games – imagine getting sucked into a illustrated history – “coffee table book” that you have to work your way through to get out. While eventually these games can be produced in computer versions, my first foray will use the traditional board game delivery system. As product road maps are usually associated with technology (correct me if I am wrong), what is the equvalent of a road map for someone in my situation?

    Any advice would be very much appreciated

    R.G. Guber

    • decisiondriven says:

      Rafael,
      You can roadmap (aka fast-forward) any decision related to the design of your games. They are products, even if their current technology is “low-tech”. All the decisions under the Product Concept decision pattern (search for this in the blog) will have a answer (a committed alternative) even in your first version. As you contemplate future versions of your first board game releases, new and more advanced games and eventually moving them to a software delivery platform, these answers (alternatives) will evolve; the questions (decisions) will stay the same. The evolving alternatives for each decision form a roadmap.
      Some of the key decisions to consider are:
      1. Use Case(s): In what scenarios will the games be played
      2. Value Proposition: For each use case/scenario, how will the game deliver unique value “wow!” to the players.
      3. Functional Model: How will the game flow?
      4. User Interface Concept: How will the user interact with the game? How will control data (instructions, it’s your turn, etc.) and content information (clues, results of user actions) be presented?
      I’d encourage you to start a free trial of the Decision Driven(r) Strategy web service to help you frame out your ideas and the business context for your products. I usually recommend a quick decision blitz (snapshot) to capture your current thinking on each decision and then a second pass to brainstorm future alternatives for each decision from which you can create various roadmaps of your future.
      It sounds like a fun project. Feel free to keep me informed.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s