A filename should help someone recognise a document without opening it. That someone may be you several months later. A small, consistent set of conventions can make a folder much easier to navigate.
Choose the information that matters most: project, subject, date and version. Use it in the same order for related files. If dates are important, a year-month-day pattern keeps the sequence understandable and avoids ambiguous day and month ordering.
Use ordinary words rather than unexplained abbreviations. A name such as workshop-agenda-2026-11-03-v02 tells a future reader more than final-new-latest. Decide what a version number means and avoid repeatedly adding the word final.
Keep the folder structure equally modest. Separate active work from completed material and put instructions in a short note if other people share the files. Extremely deep folder trees can create as much confusion as a single crowded directory.
Test the system on a small project before renaming a large archive. Check whether existing links or applications depend on current paths. A naming convention succeeds when it reduces hesitation during everyday work, not when it looks perfectly organised in a screenshot.