Table of Contents


Roadmaps are used at a strategic level and also at product level. Roadmaps are used to declare strategy and implementation details alongside vision.

Roadmaps done well

There are many kinds of roadmap ideas and layouts and all of them are often misused. One example of this, is that a roadmap is often layed out like a gannt chart or has expectations of dependencies and deadlines. This can often muddy the water between vision and implementation detail. Typically a roadmap is not a map.

AMMERSE alternative

AMMERSE comes with huge set of benefits that do not get confused as a map or implementation details.

  • communication of strategy and vision
  • a common language for strategy
  • works at the board room level and at the key worker level
  • contains decision making heuristics
  • provides a mental model for decisions at all levels
  • no implementation details
  • works with a Maturity Index
  • can be used to measure gaps


In the featured image, you will see that a from/to for the medium term and a from/to for the long term has been developed. This means that an inspection of the current state was done and a vision for the next step was created. The values of each element shows where we should concentrate.

In the medium term, more emphasis should be placed on Minimal, Maintainable and Reachable. Why might this be?
In order for services and solutions to be effective, they need to be robust and also tweaked from time to time. In the example, we have noticed that whenever something is changed, the process of updating the product suffers from high maintenance issues. The solutions could be streamlined and more effective. Why is Minimal and Maintainable 0.5 and not 1? We realised that we have so many issues, that it would be best tp halve the vision. A value of 0.5 shows that it is important, but not that focus should be derailed only by these two values.

This strategy can be released to the product team. They can already start to think about this and what it means for their work. Scheduling a meeting next month, for the creation of a checklist to evaluate the current state (a form of capability modeling) will help us fine-tune the numbers assigned to the AMMERSE Set, giving it more legitimacy and context.


Substack Newsletter

Sign up to our newsletter and collaborate.

Join the free newsletter


Level 1

7 Principles: Agile, Minimal, Maintainable, Environmental, Reachable, Solvable, Extensible.

Level 2

The AMMERSE Set has weights assigned to 7 Principles. eg. “Enterprise Strategy”.

Level 3

AMMERSE Sets in a grouping that work together for a purpose. eg. Modes.

Level 3.1

You can extend AMMERSE by creating your own Sets and Frameworks.

Our goal is to enable business strategy, implementation and the reaching of objectives by giving you the tools to design your own methods. 

Sign up for the occasional email