How to Document your Salesforce org
As we’ve mentioned in previous blog posts, Documentation can be google docs, word documents, zoom recordings of strategy sessions, pictures of a whiteboard showing technical design sketches, and even internal chats among the Salesforce team.
Basically, anything that helps illuminate why a certain part of the system was built the way it was, how it interacts with…
Top 5 reasons why you should document your Salesforce org
1) To make your job easier.
With good documentation to reference, you’ll be able to make changes to your org faster and with more confidence (and make the right changes).
Let’s say for example a user from Marketing is asking for a new field to “score” a prospect. You know from past projects that some other groups are also using scoring, but you aren’t sure if they are the same…
What is Salesforce Documentation?
Documentation in its simplest form is anything that helps explain why a technical system was built a certain way, how it interacts with other parts of the system, and possibly who to talk to in the event there is a question.
What we are really trying to get at is: what is the underlying business need that led to this build, what was actually built, and what information should a future admin / project manager / developer (or a future you) know?
What is Salesforce?
The best known product of Salesforce (and where its namesake came from) is its Sales Cloud platform.
It’s a website you sign into and you can store all of your company’s sales deals, notes, and contacts. It allows a company with very little effort to completely move off of Excel spreadsheets and allow them to track their open sales deals in a centralized place. As a user, you login and begin entering details…