As they put it in NLP:
"The map is not the territory, what I think being the world is my own
perception of it"
--> as many realities as there are people
while I am at it:
"Language is a secondary representation of experience"
--> information given does not reflect "subjective reality"
As there are as many perceptions as there are people, and as experience
(usually) accumulate, we are bound to live in :
- evolving and inherently subjective realities
Add the emotional component to the mix and a tendency to try to get it
"right" (which is impossible).
The question is then : "how can we build a system that satisfies the
stakeholders and users given that state of affairs ?"
Right now, a way to build such a system is in following a process that
creates "incremental buy in" by the target organization.
By that I mean that we try to lower the rejection threshold for the system.
If user representatives get invited to workshops and see their input valued,
if stakeholders are given a chance to experience what they asked in a
tangible way,
if developers see that they work for real people with understandable
concerns,
if "models" (UML or (active) sketches or data samples) are used to clear the
fog in everyone's head to a reasonable level
then
there is a chance to get the system done & accepted.
