A frontend team can spend an entire meeting deciding whether a component belongs in components/ , features/ , or modules/ without making the system easier to change.
The folders look cleaner afterward. The checkout page still imports pricing rules from the catalog. Three teams still edit the same customer model. A small product change still requires coordinating several releases.
Folder structure makes architecture visible. It does not create the boundaries that architecture needs.
Start with a change, not a directory
Consider a storefront with catalog, cart, and checkout capabilities. Suppose checkout needs to support a new delivery option.
A useful architectural question is: how far should that change travel?
Ideally, checkout owns the delivery selection flow and its presentation. It consumes a shipping quote through an explicit contract.…