Hi,
I had similar problems with my users.
We created and enforced policy (this required, not only distribution of the policies but also train the users)
We also developed script to automate/simplify certain tasks.
For instance on Relation Parameters, we created what we called Embedded Parameter Creator. It was based on weblink and was an interface in the embedded webbrowser. What it did was to provide selection of parts we make and the list of parameters such parts had to have. Users could launch also the script when using existing parts, The tool highlighted if certain parameters or relations were missing/wrong according to the part opened. It has helped a lot with data cleansing (we do a lot of Save As)
You can also force the users by a WC setting to remove from WS when data are checked in. But this may not be applicable for your users.
We also replaced the OOTB Regeneration buttons by our customer ones. As some of our models needed to be regenerated twice to get the green light (most users regenerated once and never checked the green light).
Generally from my experience, admin must fight on several areas, Policy but also system configuration so either policy is used automatically by the system (eg for us if parameters were missing you could not check in, or if Model Check returned certain types of error). And train the users, provide consolidation training. A lot is down to education.
For large assemblies, we trained the users to breakdown their top level assemblies in sub assemblies and used simplified reps
For workspaces, we also included Views to supposed to be good for the users while not taking too much resources.
We also set a preference so by default only the new/modified/checked out objects are displayed rather than all. This is the As Featured Objects
Generally, best practices is down to how you want to use the system.
hope this helps. don't hesitate to ask 🙂
