2144478 - Preparation for Mid-Year and Additional Cycles - Performance Management

SAP Knowledge Base Article - Public

2144478 - Preparation for Mid-Year and Additional Cycles - Performance Management

Symptom

Clients focus greatly on annual performance and talent cycles, but there are often additional cycles added – such as a mid-year review process.  This Knowledge Base entry focuses on preparation and tips for these additional shorter cycles.

Question

How should I plan for an upcoming cycle that may not get as detailed a workplan as a formal, annual process?

Environment

  • Performance Management

Resolution

Which modules typically have short cycles?

Compensation:

  • Compensation Managers aren’t engaged with the SF application throughout the year
  • Experiences and system knowledge is fresh immediately following cycle, some organizations even request feedback from Planners or HR team
    • Recommendation:
      • Customers are encouraged to begin their planning immediately following the annual cycle

Multi Rater 360 Review:

  • The frequency of 360 will vary, keep in mind that people need time to make changes and time before other perceive that change. In general 9 – 12 month intervals are most common frequency rate for conducting 360s.
  • Recommendation:
    • Customers should start planning 12-14 weeks before their launch date

Performance Management:  Mid-Year or Quarterly Evaluations

 

What tips should you be on the lookout for?

  •  Update your Dashboard process to include form templates for your additional cycles.
    • You may want to set up separate processes so that these forms are kept separate from others in a reporting standpoint. 
    • You can then monitor your dashboards to get visibility into what forms are in what step.
    • Form list details from your Dashboard can be leveraged to get further insight into forms that are behind on due dates.
  • Update due dates within your route map steps.
    • Remember to create separate routemaps for your additional cycles, which can then have their own due dates.
    • You can then run a Performance Management ad-hoc report to see what forms are in the current step, and which ones may be behind schedule.

 

Recommended Planning Example:

Minimum 12 Weeks Before:

  • Hold cycle planning call (or use regular weekly meeting) to discuss preparing for upcoming cycle
  • Customer to begin documenting needed configuration changes (if any) for PM/GM/Comp form template (s) on CCOR
  • Customer starts case for PM/GM/Comp template changes

10 Weeks Before:

  • Ensure completed CCOR has been submitted for any form template changes (configuration change requests could take up to 2-3 weeks to complete by TSE team)
  • Ensure discovery call takes place
  • Ensure it is specified in CCOR whether form template is going to be loaded into test first, then production or directly into production.  If template is being tested first in the test environment, customer will need to build time into the process for testing in BOTH test and production, and form will need to be migrated into production by TSE team as well
  • Customer to ensure that test users set up to test form in both test and production

8 Weeks Before:

  • If updated templates are completed, customer begins thoroughly testing updated form template (testing checklist can be acquired by contacting Customer Success)
  • Customer should test reporting outputs as well (included in testing checklist)
  • Customer should test routing map (updating dates if applicable) and permissions
  • Customer should have TSE migrate template to production if it was initially only loaded into test

4 Weeks Before:

  • Customer should have a plan for launching forms and all data filters should be set up correctly for a mass-launch
  • Customer Success will check in with customer on testing progress; note that if any additional configuration changes were discovered, these need to be submitted ASAP at this point to ensure adequate turnaround time
  • Customer to consider any changes in scheduled job (Quartz) settings as well for document transfers
  • Customer should also take a look at form template settings under admin tools and update these accordingly

2 Weeks Before:

  • Customer Success to check in with customer on testing progress (testing should be close to complete at this point)
  • Review launch plan
  • Customer Success to inform customer of any scheduled maintenance activities that may be occuring during launch as you become aware of them

One Week Before

  • Use weekly meeting (or schedule a meeting) to review launch plan
  • Customer Success to answer any questions customer may have regarding launch

Keywords

KBA , LOD-SF-PM , Performance Management , How To

Product

SAP SuccessFactors HCM Core all versions