SuccessFactors is an incredibly vast and versatile tool.  For most customers, the reality is that the simplest implementation of the tool is rarely the path you're able to choose.  Once your customer starts really using the tool and asking questions, that's when you start seeing how your implementation really needs to designed.  A great tool like SuccessFactors, in the right hands, is generally almost always able to satisfy the need, or something close to it.

​

That said, with a tool this versatile, there is rarely only one way to accomplish the same task.  The way I suggest to solve a certain issue is in not always going to be the only way to solve that problem.  Similarly, SuccessFactors is always evolving with releases and improvements.  As times change, so too do our abilities to handle requirements.  So what was once a valid solution to fix a problem, may eventually be solved another way. 

​

Finally, someone may tell you that fixing a problem this way or that way is “best practice” or “leading practice”.  Best practice is in the eye of the beholder, and is a term that can be misued by someone who wants to steer you to whatever way they know to handle an issue.  If we were to describe the best practice for staying in shape, it would be to eat right and exercise, but that answer is hardly of any use to someone who needs to actually do the work.  To me, a best practice is whatever turns out to be the least invasive way to truly solve your customer’s issue.  My opinion of what is a best practice for your issue may differ from yours as well as the person who designed the software as well as the person who coded it as well as the person who answers support tickets for it.  It’s subjective. So if you see something I suggest and say “I was told that wasn’t best practice” then it’s up to you to decide if what's best for your situation.