Monday 18 October 2010

Assumption Mapping

In the story about the aspiring Dutch musician, it is clear that questioning  assumptions is a key part of dealing with difficult problems.  One way to analyse assumptions is 'Assumption Mapping', which is one of a number of ‘qualitative mapping’ techniques that can be used for dealing with difficult problems.  Its purpose is to;

1. Make you vocalize your assumptions, and hence communicate them with others.  This may create a discussion about the assumption, or prompt other less obvious assumptions to be stated.

2. Sometimes, useful information can be gained from observing the relationship between assumptions, for example certain types of assumptions may be grouped together or separated from others - why?

Knowledge about the problem can be gained by exploring the background.

Assumption Mapping begins by asking the stakeholders concerned to identify as many assumptions about the problem as they can (this may be helped by identifying the needs/conclusions/outcomes and asking  'on what assumptions are these based?').  We then map these assumptions according to;

1. The certainty of belief in the assumption.
2. The relative importance to the problem.



We then look to see what ideas or conclusions can be drawn from the mapping of the assumptions.  Usually, the most interesting quadrant is where the assumptions are thought to be important, but there is some uncertainty in this belief. 

Another approach is to think about how you could change the criteria that define the axes of the matrix (eg. how you could make it more or less important) -  and how that would affect the problem? 

A different approach may be to ask why certain stakeholders make similar (or dissimilar) assumptions.

The goal of this is to gain an insight into the problem by questioning your assumptions, and it is NOT about being logical, it is about asking unexpected questions that give you a new perspective on the problem.

New perspectives give you new insights into the problem and hence ideas about possible solutions.

No comments: