Using the Business Map

Directing System Development

The map is used to control and direct all system development. It acts as the 'conscience' of the system builders - what the business would have if there were no constraints of any kind. It is used in many ways:

• To scope proposed systems - by specifying which business processes are within the scope, and by collecting objectives and problems associated with each process.
  
  
• As the basis of business transformation studies. The map itself is stable - it represents the what. Using it creatively helps you explore ideas for transforming or simplifying the business.

• As a way of enabling you to implement solutions, either as one large 'chunk' or as separate sub-projects. You can safely develop the urgent parts of the solution, knowing that the underlying map means the resulting parts will all fit together.

The map can be used in other ways as well, to help evaluate packages, identify constraints in existing systems, act as a first pass database design, and help the business exploit new technologies such as Client/Server.

But it should be remembered that many business people find the building of the modela vauable exercise in its own right. 'Gave a common understanding of the business' and 'Highlighted business issues' are quotes from workshop participants. We hope these notes help you appreciate and support the business mapping approach.