Below is a smorgasbord of all the things I consider for an improved cad system - click the title for more details.
Some you may already have, some you may want, and some you may disagree with. That's fine - these summaries are just what I've found to be best practises but not always applicable to every office.
The particulars of your projects, your clients, your IT system can bring other constraints or ways of working - projects are rarely a carbon copy of the last.
Either way, these discussions are useful to nail down the pros and cons you can get from your system, so addressing any aspect contributes to a better system with time-money savings for your team and the business.
Layer naming - That old chestnut
Using most of the swatch - Use the range to differentiate architectural elements
Color + Monochrome - Separate and accommodate the two needs
CTBs for printing - Control lineweights without changing the drafting
Printing - Filter the options to avoid mistakes
Menus - Still hugely useful and the go-to for all users
Ribbon - horrendous, but the younger generations seem to like it
Customising keyboard shortcuts - will always beat point-and-click for speed
Onscreen info - doesn't print and like adding notes to the design
Optimize settings - for faster drafting and dependability
background colours, scroll wheel for zoom, pickbox for selecting
Simple blocks - the original is still good for cookie-cut elements and context
Dynamic Blocks - even the smallest use of dynamics can make a massive time saving for users
Composite Blocks - nest blocks in blocks, both simple and dynamic, to cover everything
Automated drafting using blocks - the absolute zenith of using dynamic blocks
Block libraries - a pain to maintain and ignored by the team, so here's an alternative method
DWT templates - Start every drawing with dependable settings and key ingredients
Metric linetypes - Stop fussing with Linetype Scales and remove the frustrations
Hatches -
Fonts - If you want more space for text then stop using Arial
Tools for Good housekeeping - When things go awry, have some tools to get things back in line
Folders and flow - No more empty folders and a clear hierarchy enables xrefs
Modelfile naming - AutoCad dwgs are not drawings
Plotfile naming -
Composite naming - When a 'study' breaks the rules, where does it go and what is it called?
Menu macros - Lightning fast, but hardcoded
Composite commands - If one thing is usually followed by another then lets do it
Scripts for automation - Deaf dumb and blind, but simple and fast
Redefining AutoCad commands - Let the team use what they know but steer them to better
Removing problematic commands - Splines, Base, and other bad apples
Custom built software - When the native stuff can't do it, get under the bonnet of AutoCad