I recently posted on social media asking other Salesforce Admins to share their thoughts on how they would complete the following sentence:
“You know your Salesforce project is in trouble when…“
If you’re relatively new to managing Salesforce projects you might find the list below enlightening (maybe even shocking).
If you’re an experienced Salesforce Administrator, the list below might induce some reflective laughter, moments of shock and perhaps even a bit of post traumatic stress.
You Know Your Salesforce Project Is in Trouble When..
- Nobody is willing to provide requirements and business team suggest that Salesforce implementation should be an exact replica of legacy application.
- Instead of participating in business requirements gathering, senior leaders within the organization insist on saying “Just turn it on! Just set it up so that we can log in!”
- Your company’s founder says, “it’s just a database with a fancy GUI, how hard could this be?” and decides they can do all the configuration themselves.
- Nobody knows what fields are needed or where the data is coming from!
- Your team has an “Apex First” mindset.
- You get your quarterly invoice and you balance it against the competition pricing.
- The client asks why opportunities are needed, let’s just record everything under account notes.
- Senior Management wants to run the business on the Opportunity…with 500 fields, and everyone needs to see all the fields.
- Salesforce certifications means nothing and experienced certified team members are treated as “Level 0” support.
- There is no clear business process to configure and the expectation is that Salesforce will fix that.
- The organization has more profiles than roles and every profile has just one users and the name of the profile is the name of the user.
- Client doesn’t have someone who “owns” the Salesforce project from the business side.
- The business is unable to identify consistent business requirements.
- Each question asking for clarification on business requirements results in senior leadership cc’ing 5+ new people who were never previously identified, without identifying who within the organization is the subject matter expert to give the clarification needed to proceed.
- The data quality is horrible and no one feels accountable to clean it and everyone assumes that “the system” should have a feature to clean the inaccurate data itself.
- There is lack of vision by the management to understand how to leverage the Salesforce platform to streamline and automate processes – instead of simply replicating the same backwards manual way things have always been done….in Excel.
- The wrong people do the analysis, resulting in non-usable business requirements.
- There is no governance or stewardship.
- No one wants to dedicate any time, resources or any effort at all into training end users on how to use Salesforce once we go live.
- There is no plan on how we are going to maintain Salesforce once we go live.
- Management thinks that Salesforce is simply “ONE OF” the other systems that we have (resulting in siloed data being dispersed across multiple systems throughout the organization, making 360 degree reporting practically impossible).
- The organization cannot articulate their current or future state business processes.
- Middle management within the organization is VERY middle/low (with no authority, minimal experience and incapable of helping to implement any change within the organization).
- The team insists that they can’t log into Salesforce (because they aren’t technical, refuse to remember another password, it’s beneath them, or some other lame excuse)…so they would rather just keep entering their data in Excel expecting it to be automatically imported into Salesforce every night.
- Business leaders insist that they need “to see all fields for all records” on the homepage.
- Stakeholders try to build “Salesforce-based Excel” with Lightning.
- Business participants trivialize User Acceptance Testing, insist that everything should “just go live” and then come up with new business requirements (never documented or agreed-to previously), arrogantly screaming that since their (new) requirements are missing, the project is a failure and they will just use Excel instead.
- The “Salesforce Admins” or “Power Users” don’t know the difference between a tab, a field, record type, object or record.
- The “Salesforce Admins” keep insisting that Lightning is a whole brand new database and an entirely new platform.
- Business users keep insisting on replicating the same fields on multiple objects, without any comprehension that users will vomit when they see several hundred fields on each screen.
- After business requirements gathering, configuration, user acceptance testing and end user training, the team expects an integration (never before discussed) should “just be there!”