There is a difference between design that tries to prevent someone from shooting themselves in the foot (designing around how users interact), and design that seeks to influence or limit their behavior. The former is safety, the latter is manipulation or restriction.
Giving system owners RBAC controls so they can choose who is an admin, versus not giving system owners admin privileges at all.
But more importantly, the point of my comment is that the axiom that everyone thinks themselves competent enough, is true at every level of risk. No matter how low risk something is, someone can and will still overestimate their capabilities and muck it up. If we're using that as justification to impose restrictions, there would be no actions that someone could not justify restricting.
Giving system owners RBAC controls so they can choose who is an admin, versus not giving system owners admin privileges at all.
But more importantly, the point of my comment is that the axiom that everyone thinks themselves competent enough, is true at every level of risk. No matter how low risk something is, someone can and will still overestimate their capabilities and muck it up. If we're using that as justification to impose restrictions, there would be no actions that someone could not justify restricting.