I use folders and have folders inside folders. I also, started to do with the naming of the survey is to add the semester and year, project numbers, dates of the courses to the title.

Adding prefix to your projects is a must if you need to share with a team (because folder organization is individual )

I also add my firstname to all the project I build.
This help us to know who is responsible when we try to do some cleaning in the mess of projects !

Also, if you work with workflows make sure that you name them instead of leave it say new workflow because I have thousands of them name new workflow and that does not help when you are trying to find workflows and transfer them.  Also, if possible have the owner of the survey with workflows start the workflows or the person that creates the workflow will be the owner of the workflow and it will become a mess.

I name the workflows what it does but also need to add the survey if you can.

There is functionality around Programs that has been released recently. We’re not using it yet but I am keen to play with it in the future to group surveys and dashboards together.

We use numbering to distinguish between surveys but also wherever possible try to minimise the number of surveys (e.g. we have a single survey project that has been used for surveying in our major semesters for the past 3 years), we just make modifications as required and use embedded data for additional functionality where needed to customise. This helps to reduce confusion around which survey project we should be using. For some surveys, we keep a master copy and then generate specific copies for an individual instance if we need to, although we try to minimise this.

We also use folders and subfolders.  We do have a standard naming convention of starting with the Academic Year, then Class Year (if applicable), Type of survey (course, faculty, research, program), Name.