I don't want to demonstrate, in general, that there is a wrong approach or a good approach .
I'm working on a framework to build web-banking apps.
Our goal is to provide components (we are developing according atomic design approach) that allow internal developers and third parties developers to build views and pages following a standard UX logic.
For instance one UX KPI are performances. The back navigation costs a lot (especially when we have to build the user journey within different app sections) in terms of performances, to our architecture, if users do not use such feature we do not want to deliver it.
This is the reason why we run usability test (qualitative and quantitative) with customers. We want to highlight the "most wanted" feature and try to simplify the full framework providing standard and common patterns.
I hope now is much clear the full context