We surface assumptions by reading the arrows. 

Horizontal arrows:

In order to (have tip of the arrow), I must (have tail of arrow), because...'

The conflict arrow:

'(D) is in direct conflict with (D’), because...'

And we fill in the 'because', which is the assumption.

Copy your core cloud while making amendments to add clarity and precision.  Surface major assumptions leading to the mandatory requirements for each one of the entities.  Record the important ones on the cloud.

If you are unable to surface assumptions by reading the arrows as outlined above, then the 
following guidelines may prove helpful:

For Horizontal Arrows: 

1. Think of a comparative environment in which the tip of the arrow still exists, but the tail is not relevant.
2. Identify what the difference is between the comparative reality and the system you're analysing. 
3. The difference between these two systems highlights a hidden assumption of your reality that causes the need for the tail of the arrow.
4. State the assumption as generically as possible.

For Conflict Arrow:

1. Think how there might be some overlap, or commonality, between the two ends of the arrow.
2. Ask yourself what exists or is missing in the environment that allows the conflict to continue to exist.

Related subjects

How to select a core problem