“Direction” is a fancy way of putting it ☺

I’ve just adopted this initiative as one of the things I’m driving this year, being supported by our Data Standards Committee (and Subject Matter Experts in our different business units). We have started simply with a Google sheet. I set it up by saying: If you were to win the lottery tomorrow and never show your face back at work again, what processes in/connected with Salesforce would need to be documented so that we wouldn’t miss you?

So, this Google Sheet has who, the department, high level description of the process to be documented, Y/N has it been documented, if so, we have a Google Drive folder sorted by product and department where they’re storing the document (most are quick reference guides (QRGs)), the date it was last reviewed/updated, and who (ideally a person but can be a department) will take ownership of this process document moving forward. We have provided a QRG template in Google Docs with a Table of Contents, etc. People don’t HAVE to use it or follow our guidelines, but we’re suggesting they do.

That seems to be going well so far. We are hoping to have all of the documents documented (see what I did there?!) by September, then we want to compile all of them into one HUGE ‘dictionary’.

NEXT Fiscal Year, I want to budget to purchase and supplement this with something like Configuration Workbook, Spekit, or we may be able to use components of Elements.Cloud we aren’t already using, to simplify the end-user’s experience in Salesforce so that they have our org-specific help text and QRGs as they work in our org.

That’s our direction so far. Hope this helps!