Common Mistakes Salesforce Admins Make - #DF13
Download as PPT, PDF1 like160 views
Salesforce admins commonly make mistakes around data management including not cleaning data before and after imports, not planning for duplicate records, and having overly permissive field level security. Other common mistakes include having too many custom profiles, not managing change effectively through communication and planning, and not understanding users' needs by failing to ask questions and validate requirements.
Common Mistakes Salesforce Admins Make - #DF13
- 1. Common Mistakes Salesforce Admins Make Mike Gerholdt, Red Argyle, Dir. Client Engagement @MikeGerholdt Garry Polmateer, Red Argyle, Partner @DarthGarry Jared Miller, Configero, Sr. Project Manger @JaredeMiller
- 2. Safe harbor Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include β but are not limited to β risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
- 3. Mike Gerholdt Director of Client Engagement, @MikeGerholdt
- 4. Garry Polmateer Managing Partner, Red Argyle @DarthGarry
- 5. All about Red Argyle Red Argyle is a Salesforce consulting and ISV partner that focuses on bringing Tailored Goodness to the Salesforce Platform ο§ Custom Development β Enhance Salesforce or build products ο§ Consulting β New Salesforce implementations ο§ On Demand Administration β Small business scalable support ο§ Products β Several free and paid offerings on the AppExchange
- 6. Jared Miller Senior Project Manager @JaredeMiller
- 7. Configero At-A-Glance 400+ CRM Projects 250 Custom Apps 7 Force.com Apps Configero is a leading provider of Salesforce and cloud computing solutions and services Proven Experts Clients/Expertise
- 9. We were all in your shoes
- 10. Question What is the worst Salesforce mistake youβve ever made? Post your answer to Chatter with the hashtag #WorstMistake
- 11. Hearing vs. Listening Image from - Public Speaking: Practice and Ethics
- 12. 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
- 13. Understanding Input and Output in a Solution
- 14. 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!
- 15. 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 the viability of a 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
- 16. 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! (shout out to Winter β14)
- 17. Want more βSimpleβ from Winter β14? β’ Publisher Actions β’ Available in PE! β’ Chatter Groups β’ @mentions β’ Publisher actions β’ Historical Trending
- 18. 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?
- 19. Data Import β SHUT OFF WORKFLOW, YO!
- 20. 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! (EE +)
- 21. Field Level Security β No Cruise Control!
- 22. Field Level Security β Wizard Redux β’ Thankfully this button exists: β’ Which gives us this:
- 23. Field Level Security β Fields Required β’ Required at Field Level β’ Required via Validation Rule β’ Required on Page Layout Red = Tread Softly!
- 24. Field Level Security β Read Only β’ Read Only Page Layout β’ Read Only Profile Level β’ Donβt forget to uncheck β’ Read Only Validation Rule
- 26. 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
- 28. Managing Change β’ Symptoms β’ Poor Communication β’ Lack of planning β’ Solutions β’ Planned releases β’ Constant communication β’ Emails β’ Newsletters β’ Chatter
- 29. 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!
- 30. Mike Gerholdt Red Argyle, @MikeGerholdt Garry Polmateer Jared Miller Red Argyle, @DarthGarry Configero, @JaredeMiller
Editor's Notes
- #8: Out of nearly 5,000 partners worldwide we are in the Gold level only about 30 companies have this distinction
- #9: Mike
- #12: Jared
- #13: Jared Bring up GK talking in scenarios
- #14: Jared
- #15: Jared
- #16: Jared
- #17: Jared
- #18: Jared
- #19: Jared
- #20: Jared
- #21: Jared
- #22: Jared
- #23: Mike
- #24: Jared
- #25: Jared
- #26: Mike
- #27: Mike
- #28: Mike
- #29: Mike