Files and folders are already a helpful metaphor taken from paper based office work. You have container folders and you can put different files (pieces of paper) into different folders. The thing thats a bit conceptually hard for regular people is the nesting, that folders can contain folders can contain folders. The real world has some nesting too, like putting folders in drawers but it's more limited in number of levels. This tends to be the thing that supposedly "more user friendly" apps remove and only allow two levels or so. Basically collections or lists, eg playlists. Or tags. But once you understand nesting, files and folders are quite intuitive.

Without the helpful abstraction of files and folders, all we'd have are bytes stored at various addresses or sectors of the hardware.

This is actually an interesting example. To me it sounds like it actually should be less confusing to a person who has no preconceived notion of what a file should be, and only wants to save their work and reopen it later, not worried about what shape the saved object takes.

On that note, I remember how absolutely ecstatic I was when I first set up Sublime Text and discovered that unsaved editor tabs always reliably survive restarts; it essentially flips the script, whereby I've lost multiple saved files by accidentally deleting them, but I've never accidentally lost work in unsaved tabs, and I've never actually had any interest in figuring out where and how these tabs get persisted - it just works.