Usability is one facet of UX design, but it isn't the whole story. As your own example shows, sometimes making something easy means making it excessively dangerous.
If your *real* goal is to create a great user experience, then you need to ask yourself about what the best possible experience looks like (or, even better, run a usability test to find out for sure). It's unclear from your short description, but if the action could cause data loss or some unexpected side effect, then it certainly would make sense to put up some level of barrier to the user committing that action.
That doesn't mean you should hide the function or make it confusing. Maybe just use a confirmation dialog, or explain the potential downside before letting the user complete the action.
Slashdot Mirror
Usability is one facet of UX design, but it isn't the whole story. As your own example shows, sometimes making something easy means making it excessively dangerous. If your *real* goal is to create a great user experience, then you need to ask yourself about what the best possible experience looks like (or, even better, run a usability test to find out for sure). It's unclear from your short description, but if the action could cause data loss or some unexpected side effect, then it certainly would make sense to put up some level of barrier to the user committing that action. That doesn't mean you should hide the function or make it confusing. Maybe just use a confirmation dialog, or explain the potential downside before letting the user complete the action.