Unified taxonomy for Employee Center

Dean1
Tera Contributor

Hi Everyone,

We will be shortly beginning work on the planning for the introduction of Employee Center Standard (move from Service Portal).

I am keen to get the Unified taxonomy sorted as soon as possible.

Would any of you that have already implemented Employee Center be willing to share your taxonomy in a spreadsheet format?

Our current structure for the Service Portal is quite flat, mainly focused on IT and needs a total rework. We will also be soon introducing catalog items relating to other business functions/tasks in the near future, including facilities, personal security, finance, hr etc.

Thanks 

6 REPLIES 6

MrMuhammad
Giga Sage

Hi Dean,

Here is a how the Taxonomy or child topics looks like:

Taxonomy Child Topic 1 Child Topic 2 Child Topic 3
IT Accounts and Access Account and Access Administration User Accounts
Bundled Services New Starter
Employee Exit Processing
Employee Relocation
Custom Account Access
Computing Services Desktop Computing PC Hardware
Mobility Devices Tablet
Printing Printer
End User Software PC Software 

Further, taxonomies could be HR, Procument etc that you have to identify for your customer.

Please mark this helpful/correct, if applicable.

Regards,

Muhammad

Regards,
Muhammad

Alexander17
Tera Guru

Hi,

Im looking for a similar thing but then for HR Topic. Anyone happy to share their HR topic structure?

 

thank you

Dan O Connor
ServiceNow Employee
ServiceNow Employee

Hey Dean,

 

Taxonomies are going to differ organisation to organisation. Definitely sounds like you are on the right track though thinking and talking about business functions and services. One of the big features of Employee Center is the Taxonomy, and the ability to structure that in an optimal and meaningful way for your employees. 

 

One tip I'd give is make sure/try not to just recreate your catalogs into the Mega Menu. Taxonomy structure for me is about

  • What do you think is important for users?
  • What do your users think is important for them?
  • What do you know is important for users? (Usage analytics/dashboard)

Remembering that you can give users the option to browse a full catalog or KB by adding them as Menu Items, or just quick links onto the homepage itself. 

 

So like as an example, you could structure an IT Topic like this

 

Hardware

 - Desktops

 - Laptops

 - Printers

- Accessories

 

Or you could do this

 

Desktop Services

-Desktop PC's

    - PC's

    - Peripherals

    - Monitors

     - Support

-Mobile Working

      - Laptops

      - Tablets

      - Support

- Printing

       - Printing Access

        - Supplies

         - Support

 

Point being I don't believe there is an inherently right or wrong way to structure a Taxonomy and topics, because there are so many options. But something I do try discuss with customers is looking to move away from just static labeling Taxonomies after their existing Catalog categories. Taxonomy is giving the option to move to a more tailored and better user experience, so we might as well use it šŸ™‚ 

Hi,

Do you have as well for HR examples? šŸ™‚