Yeah maybe not the whole project structure, but that Ice_Assets folder is a perfect example of what I’m describing and have done. Inside Ice_Assets folder you find all the content related to the meshes categorized in sub folders. That’s literally the kind of setup I have without having looked at that demo and getting turned down for being more organized is a little disappointing. Thanks @ for providing an example along with images.
As the content grow larger in volume, such localized structure greatly helps keeping track of what you’re doing, what is where, what are all the dependencies of an asset, iterate on them faster and so on and that is exactly why they naturally follow that kind of structure when they create those projects. Imagine breaking all the content from Ice_Assets folder and spreading it in 5 different paths across the project, that really hurts the overall experience as you should constantly switch between folders and look for the right files instead of spending your time on using them in the viewport.
There’s gotta be a way we’d be allowed to switch to the better hierarchy. It seems reasonable to keep the current structure, until it doesn’t. Like with the Metallic issue, I really hope you consider the new structure @MikeViolette, maybe even ask for some opinions from the art department internally. Thanks. 
Edit: Basically let’s imagine a project that contains 1 piece only.
Current setup:
Content>Meshes>
Content>Materials>
Content>Textures>
Content>Animations>
Content>Effects>
^ You’d constantly go between these.
Preferred setup:
Content>Meshes>>(mesh here)
>Materials
>Textures
>Animations
>Effects
^ Everything is close together. It’s organized, easy and fast to find/access.