As the flexibility of a system increases, the usability of the system decreases.
The flexibility-usability tradeoff is related to the well-known maxim, jack of all trades, master of none. Flexible designs can perform more functions than specialized designs, but they perform the functions less efficiently. Flexible designs are, by definition, more complex than inflexible designs, and as a result are generally more difficult to use.
Enterprise software configuration settings is a prime example of this maxim as demonstrated below with salesforce password configuration:
Without delving too much into the details, flexibility in this case is a business goal but users end-up paying the price..as UX designers we sometimes have limited leverage in changing this so in my opinion the best approach is to try and mitigate usability risks .
So my question is : would it be ok to recommend a specific security settings that will minimise user frustration?
I am thinking that these recommendations should be embedded next to configuration parameters so users can make an informed decision.
A good example here is to have default settings that never allow passwords to expire but also explain why it is also recommended to keep it this way.I want to show whoever is setting these parameters the human factor involved