##Risk Description

= Risk Description =

## Detailed description of this risk and its possible implications.
## E.g. If one of the car's tires suffers a puncture, we may run off the road.

The DOMS Meets Resistance in the Library.

Internal end users will not accept the new system, and continues to use legacy systems.

A reason for this risk could be misconceptions about what DOMS is, or a lack of influence during the DOMS design and development.

It is known that people know about DOMS, but are currently not aware of precisely what it is, which leads to misguided ideas.

== When to react? ==

## When must we respond to the risk? E.g. When the event occurs or already when we see the warning signs?
## E.g. We must react if we hear a hissing sound.

We should react to this threat by communication whenever we learn about misconceptions or initiatives that contradict the DOMS.

== Reaction ==

## Detailed description of how to react on the risk and which actions to take, if it is imminent.

## There exists 4 basic reactions:
## 1: Accept the risk.
## 2: Eliminate the cause to the risk.
## 3: Mitigate the probability or the consequence of the risk.
## 4: Delegate the risk to another party, e.g. by outsourcing it or take out insurance for it.

## E.g. We accept the risk and change the tire if we suffer a puncture.

We need to do our best to eliminate the cause of the risk, by communicating what the DOMS is widely and frequently. Communication with the internal end users of the DOMS and the DOMS collection owners is essential for a succesful system.



== Responsible Persons ==

The below persons are responsible for continuously monitoring and acting on this risk:

## Add a bullet list with links to the wiki pages of the responsible persons here:
## E.g.
## * [:JohnDoe: John Doe]