How many COEs, HR services do you have?

[JuliaA]

We are implementing service now (kicked off yesterday woohoo!) and are coming from another case mgt. system where we had 50 topics, 200 categories, 350 sub categories.  Clearly too many.  We know we need to slim it down, but are struggling to identify the HR Services that matke sense to an employee and get HR what they need. Is anyone willing to share their hierarchies or lists of HR Services that are working well for them? Or even just how many you have to compare? This is a tough exercise for us...I know it will be iterative but any help is appreciated! 

[Hendrik Kuehl]

Hi Julia,

I think this really depends on your HR service scope and there is no standard solution. Below is our catalog, which is fairly short and simple. One thing we made sure is that we use the same categories and sub-categories for the HR Service Catalog as well as for the HR Knowledge Base(s) - as a common reference framework.

Category	Sub-Category
Recruiting & Onboarding	Recruiting
	Onboarding & New Joiner Integration
	Employer Branding
Learning & Development	Training
	Leadership Development
	Vocational Training
	Talent Management
	Organizational Development & Change Management
	Succession Planning
Performance  Appraisal	Performance Appraisal
Compensation, Benefits & Pensions	Benefits
	Bonus
	Compensation
	Pensions
	Payroll
	Employee Suggestion Program
	Grading
Personal Data	Certifications & Reference Letters
	Employee Data Management
Time & Absence	Leave & Absence Management
	Time & Attendance Management
Transfers	International Transfers
	National Transfers
Health & Wellbeing	Employee Assistance / Social Services
	Occupational Health Management
	Workplace Health Promotion
	Medical Emergency Management
Labor Relations Management	Social Benefits
	Employee Handbook
	Settlement of Interests
	Workers Council
HR Internal Services	HR IT
	Governance & Compliance Management
	Labor Law
	Project & Program Management
	HR Case & Knowledge Management
	Process Management
	Organizational Data Management
Reporting & Planning	Workforce Planning
	Reporting & Controlling
Leaving & Off-boarding	Retirement
	Leaving our Organization

Regards,

Hendrik

[Hendrik Kuehl · Accepted solution]

Table now with borders...

And I forgot: we have started with only one COE (HR Core) - to keep it simple. Will add more COEs once we see a real need for it.

Category	Sub-Category
Recruiting & Onboarding	Recruiting
	Onboarding & New Joiner Integration
	Employer Branding
Learning & Development	Training
	Leadership Development
	Vocational Training
	Talent Management
	Organizational Development & Change Management
	Succession Planning
Performance  Appraisal	Performance Appraisal
Compensation, Benefits & Pensions	Benefits
	Bonus
	Compensation
	Pensions
	Payroll
	Employee Suggestion Program
	Grading
Personal Data	Certifications & Reference Letters
	Employee Data Management
Time & Absence	Leave & Absence Management
	Time & Attendance Management
Transfers	International Transfers
	National Transfers
Health & Wellbeing	Employee Assistance / Social Services
	Occupational Health Management
	Workplace Health Promotion
	Medical Emergency Management
Labor Relations Management	Social Benefits
	Employee Handbook
	Settlement of Interests
	Workers Council
HR Internal Services	HR IT
	Governance & Compliance Management
	Labor Law
	Project & Program Management
	HR Case & Knowledge Management
	Process Management
	Organizational Data Management
Reporting & Planning	Workforce Planning
	Reporting & Controlling
Leaving & Off-boarding	Retirement
	Leaving our Organization

[JuliaA]

Thank you! This is really helpful. Did you start with one COE because your case form, assignment groups and workflows are the same for each? Or because you are converting from a previous SNOW version? 

[Hendrik Kuehl]

Yes, we decided to start relatively simple with just one COE and case form - and to add more later when really required. We have +50 assignment groups and use assignment rules to allocate cases to them based on HR / user criteria.

We implemented only a small set of standard workflows used primarily for approvals. Generally we try to keep the configuration as simple as possible to minimize our release upgrade effort. We had to customize the solution slightly to meet data privacy requirements (we're based in Germany) but generally try to stick to the standard as far as we can.