1. Common Mistakes Salesforce Admins Make

2. Jared Miller @jaredemiller
VP, Service Delivery
10K Advisors

4. Hearing vs. Listening
Image from - Public Speaking: Practice and Ethics

5. How to Listen Effectively
Ask, “Why?” And don’t be afraid to dig deeper
Why are you asking me for this?
Why is what we already have not working?
Deliver mock-ups to the user
Excel, LucidCharts, Balsamiq, Bar napkin – just do it!
Help them understand what you are ‘hearing’
More importantly – help them understand what they are asking for

6. Understanding Input and Output in a Solution

7. What do I mean by ‘Data Input’
Clicks and Scrolls and Fields, oh my!
Sometimes creating a solution will be more work than the manual way
Sometimes creating a solution delivers so much data that your users are scrolling
Sometimes creating a solution requires the creation of too many fields
Sometimes simple is the best answer!

8. How do we stay simple with our ‘Data Output’?
Understand how the data will be used
What is the expected result of the data input?
“I want to calculate if this is a good deal?”
“I would love to tell if I have a good customer or not.”
Sounds like a formula field to me! A picture is worth a thousand words

9. How do we stay simple? What is the expected action of the data input?
“I want to see the grade of everyone’s accounts.”
“It would be great to see how much our customer spends.”
Sounds like a report to me!
Or, embedded analytics!

10. Data Imports Don’t “Dump it in Salesforce” Have a Plan
Why are you importing said data?
Who can import data?
What are your standards for importing data?

11. Data Import – SHUT OFF AUTOMATION, YO!

12. Data Import – Dupes Happen
Define duplicate risk/mitigation
Pre-clean data
Post-clean data
Don’t ignore the reality of duplicates
Don’t “deal with it later”
Test in a Sandbox!

13. Field Level Security – No Cruise Control!

14. Field Level Security – Wizard Redux
Thankfully this button exists:
Which gives us this:

15. Field Level Security – Fields Required
Required at Field Level
Required via Validation Rule
Required on Page Layout
Red = Tread Softly!

16. Field Level Security – Read Only
Read Only Page Layout
Read Only Profile Level
Don’t forget to uncheck
Read Only Validation Rule

17. Too Many Profiles!

18. Reduce Profile Sprawl Clearly define roles or “buckets” of users
Utilize Permission Sets
User B is like User A but can modify Accounts
Grant granular CRED when needed
Perfect for “Temporary” Assignments

19. WHAT WE’VE GOT HERE IS …
A FAILURE TO COMMUNICATE!

20. Managing Change Symptoms Solutions Poor Communication Lack of planning
Planned releases
Constant communication s
Newsletters
Chatter

21. Summary Don’t take user requests at face value. Dive deeper.
Understand how your users will consume data.
Determine how a request meets a business goal.
Don’t always look for the shortcut.
Find a common denominator.
COMMUNICATE!

22. Q & A

24. Design Elements
Animals (Animals should always be smaller than the official Mascots)
Nature
Housing
Transportation
Equipment
Lighting
Shadow
(Resize and layer as needed)