I feel like this analogy is perfect, but not just for the reason you used it.
Car manufacturers making cars easier to use and require less maintenance is great. Your point in regards to people just not needing the old skills because of that is spot on.
But car manufacturers have also been making intentional design decisions to make accessing things under the hood require speciality tools or needlessly complex when it is needed. There are cars where you can't replace headlights without removing the whole front bumper assembly. That isn't the fault of the owner/user, and it's not a case of "improvements make old skills obsolete". It's design intentionally hostile to the goal of allowing owners to even attempt it themselves. Scummy as hell, and we should be holding these companies responsible.
Google has done and is doing the same thing with Chromebooks and Android. File system? Folders to organize my files? What?
And now we have people who don't know how to operate their car's headlights, and people who can't find files if they aren't in the "recent documents" list.
Edit: This came off intensely aggressive. Sorry.
I'm looking down the barrel of a massive project to shift all of our departments away from network shares to SharePoint. Simultaneously, my team is going to stop supporting "special" permissioned sub-folders, like share/Facilities/Managers/ so people can't see their co-worker's yearly review. Each Sharepoint site's "owner" (read, department manager) will be responsible for access management in their own site.
Also, knowing some of these departments, they will absolutely run up against the limit on amount of files in a single Sharepoint site. My boss seems to refuse to believe that's possible.
This is going to be such a clusterfuck. I am afraid.
Original comment:
Sincerely: How the fuck are your users utilizing Sharepoint that they don't need to navigate the file/folder structure concept? Just using the search bar every time? Maintaining a list of shortcuts or browser favorites?
How does a file being shared from another user's storage invalidate the need to still know how to get to it?
I can't speak to Google Drive, as I've only used that minorly as an end user. Object based storage is an entirely different use case than document/data organization.
File names and tags with shit chucked in what is effectively a root folder are not adequate for most companies' data organization and "securing so only the right people have access" needs.