We all agree that folders are bad, right? They only make sense at a certain point in time and only mean something to the person who created them. Everyone hates the folders in SharePoint which someone else created, but I find the majority of people still organize their personal OneDrive for Business files within folders.
The problem with this is that OneDrive for Business screams and begs for you to share those files with others, so users create folders as a mechanism to define who has access to sets of data. Folder names like the built-in "Shared with Everyone" or "Shared with Team X" become the ACLs which makes sense for a specific project, but that concept quickly detoriates when project members change or someone else needs access to a subset of content within that folder.
I was guilty of the same crime for a long time, but have recently adopted a new technique I think works really well. It goes like this:
Store all your files in a completely flat structure within OneDrive for Business, and set permissions only at the file level. No folders allowed. Sort the view by Modified Date for an extra boost because this way everything you're actually working on is front and center, similar to a "Recent Documents" view.
If a group of files lend themselves to being shared together, put them on SharePoint or in an Office 365 Group. Your personal OneDrive for Business isn't the best fit for a set of documents which are related. You should set up a document library, team site, or Office 365 Group to move that effort forward. Sync that location to keep a local copy handy.
Create a single folder called Archive. Similar to mail archive concepts the only thing that goes in here are files you haven't accessed in a really long time and need to keep around for reference.