> did anyone actually use this? Are you me? Lol. Sometimes I use software where I wonder "am I the only one that bought this and tried to use it?" I think p

> did anyone actually use this? Are you me? Lol. Sometimes I use software where I wonder "am I the only one that bought this and tried to use it?" I think part of the issue is that requirements get written by people who have no experience. They've never done the job the software will be used to augment and they don't know anything about software development. Then the requirements are used to outsource the actual design and development. Using POS as an example (in a country with tipping culture). Imagine if a requirements document for the payment system said "must include an option to tip", but the design and development was done in a country where tipping culture isn't a thing. You'd likely end up with the "tip" option hidden away in a hard to reach place while everyone who uses the software knows it should be prominent and easy to use and could immediately tell you the design is poor.