Why map

As a follow on from the benefits of business mapping from July, Simon Wardley has kindly used the example to explain why you map. This illustrates:

  • Needs, differentials and efficiency targets, including the operational constraints as well as hidden business components;
  • What type of focus and management can you apply to the various components based on the types of focus;
  • Ideas on measurement for different stages in the lifecycle; and
  • Where to attack the market using ¬†Innovate, Leverage and Commoditise (ILC).

My plan was to do a similar write-up, however I don’t think I’d ever explain it as well as Simon, instead I’ll work on a couple of follow-up posts that discuss integration of the business map into the Business strategy / Enterprise Architect roadmap (as opposed to just the technical roadmap) and a generic look at the cost vs. value as you move from new capability to commodity.

Thanks again to Simon for sharing his thoughts and ideas.