It contains no cause, no specific behaviour, no consequence and no group. It cannot be assessed for likelihood, cannot be assigned to anybody meaningfully, and cannot be closed except by assertion.
A usable acceptance risk states three things. The cause: something identifiable about the design, the process, the environment or the distribution of burden. The behaviour: what people will actually do, described concretely. The consequence: what that behaviour costs the organisation.
Written that way, a risk becomes arguable. Somebody can challenge whether the cause is real, whether the behaviour follows, or whether the consequence matters. All three challenges are useful.
Nothing useful can be said about “users may resist”.
The entry matters more than it looks, because it is where an organisation decides in advance whether it is going to investigate a problem or explain it. A register full of anxieties has already chosen.
Chapter 7 of Built to Be Used works through what an acceptance risk has to contain, and includes a register you can use.
#RiskManagement #ITimplementation #ProjectManagement
It contains no cause, no specific behaviour, no consequence and no group. It cannot be assessed for likelihood, cannot be assigned to anybody meaningfully, and cannot be closed except by assertion.
A usable acceptance risk states three things. The cause: something identifiable about the design, the process, the environment or the distribution of burden. The behaviour: what people will actually do, described concretely. The consequence: what that behaviour costs the organisation.
Written that way, a risk becomes arguable. Somebody can challenge whether the cause is real, whether the behaviour follows, or whether the consequence matters. All three challenges are useful.
Nothing useful can be said about “users may resist”.
The entry matters more than it looks, because it is where an organisation decides in advance whether it is going to investigate a problem or explain it. A register full of anxieties has already chosen.
Chapter 7 of Built to Be Used works through what an acceptance risk has to contain, and includes a register you can use.
#RiskManagement #ITimplementation #ProjectManagement
This article accompanies the book Built to Be Used.