9 Important Factors to Consider When Implementing Employee Central Globally
- by Prashant Rastogi, Associate Manager, Accenture
- November 12, 2015
Take a look at nine important, but often-overlooked, factors to consider when undertaking a SuccessFactors Employee Central implementation. The reason they are ignored is that often companies think they can be dealt with after the project has been started. This mind-set leads to longer implementation cycles and creates tension between the company and its implementation partners. These helpful tips help you avoid these and other common implementation issues.
After reading this article, you will:
- Understand some of the important factors that tend to be overlooked during global Employee Central implementations
- Understand key considerations that can help project teams avoid making big mistakes
SuccessFactors Employee Central is SAP’s HR information system (HRIS) cloud solution. Many companies—large and small—have begun implementing SuccessFactors Employee Central in place of their homegrown or legacy systems.
Being on the cloud gives many advantages to companies running SuccessFactors. Faster implementation is one such advantage. However, in their haste to finish implementing SuccessFactors quickly, companies often overlook some essential considerations. Each one of these factors has the potential to derail the implementation cycle and can endanger the fate of whole project.
In this article, I look at nine important factors that are commonly ignored in SuccessFactors Employee Central implementations. Many companies wrongly assume that these can be figured out further down in the planning process, only realizing later, when it’s too late, their true importance. Not considering these important tasks, and their outcomes early in the implementation process not only leads to an increased implementation cycle, it also causes friction within the company.
Factor #1: The System Landscape for SuccessFactors
In IT project terminology, the system landscape refers to the strategy for moving the configuration across various phases of the project (for example, development, testing, and production). The greater the number of instances you have in your landscape, the greater the level of effort for:
- Keeping the instances synchronized with production
- Moving the configuration from one instance to another (this is discussed in more detail in Factor #7)
Would you like to see this full item?