Salesforce Admins are the protectors of a streamlined and effective org. Before you agree to “just add a field”, you need to ensure it truly adds value and doesn’t lead to unnecessary work. Vanessa shares how to avoid a ‘Pandora’s box’ of complications down the line. https://lnkd.in/dgQbwQ6m #Salesforce
One question... "Can you show me on this process map where Salesforce hurt you"
Brb just putting on my BA Hat 🤠
You forgot to ask “Who is paying for this field (both and tomorrow)?”…. And therein lies the problem, if it’s deemed free, it will be taken advantage of at the expense of the project or admins
It might seem silly, and you might receive some push back from the person requesting the "field" but these questions usually uncover that the requirement is so much more than just a field. But sometimes it is super simple and that's a win!
Unless, of course, after all the questions and suggestions, the client demands the field anyways, with the same label as a standard field, with mostly the same values as the standard field, to appear on the screen instead of the standard field. I swear, being an admin isn't a feat for the weak of heart 😬
Come on it is just one field and the business really wants it really really bad…how could it hurt? - fast forward 3 years and 200 new fields later. 😂
...and suddenly it is not the field the user needs but a whole new process 😅
My first question is always "does this other field I found have what you need already?" The cheapest process to build is one that doesn't need to be built.
Useful tips
VP of Product Management - Acxiom
4moYou forgot one- “Does an existing field already contain the data you want to store in this new field?” 😀