User acceptance testing: Difference between revisions
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 5: | Line 5: | ||
It is not called “[[user appreciation assurance]]”, or “[[user experience enhancement]]”, or “[[user productivity maximisation]]”, for a reason. | It is not called “[[user appreciation assurance]]”, or “[[user experience enhancement]]”, or “[[user productivity maximisation]]”, for a reason. | ||
It is not about the ''[http// | It is not about the ''[http://tron.wikia.com/wiki/User user]''. | ||
Revision as of 12:48, 11 May 2017
UAT, or “user acceptance testing” is the process whereby an IT department experiments on its workforce the way scientists experiment on mice. It is designed to make sure new software it would like to impose on the workforce but which users neither want, understand nor care about, will not be so disruptive, annoying or useless that users rise up in outright rebellion.
“Acceptance” implies tolerance, not enjoyment. Forbearance. Sufferance. Coming to terms with a generally unsatisfactory circumstance. Sacrificing individual freedomeand preference for “greater good”. When one says “I have accepted my fate” one does not necessarily mean one is happy about it. So it is with user acceptance testing.
It is not called “user appreciation assurance”, or “user experience enhancement”, or “user productivity maximisation”, for a reason.
It is not about the user.
See also
Dramatis personae: CEO | CFO | Client | Employees: Divers · Excuse pre-loaders · Survivors · Contractors · The Muppet Show | Middle management: COO · Consultant · MBA | Controllers: Financial reporting | Risk | Credit | Operations | IT | Legal: GC · Inhouse counsel · Docs unit · Litigator · Tax lawyer · US attorney Lawyer | Front office: Trading | Structuring | Sales |