I am gathering the considerations that should be taken into account to build a hierarchy based on levels and parent-child. From your experience, I would like to hear your opinions and recommendations on this matter.
EX Hierarchy considerations
Userlevel 5
+17
Hi
you may check this article:
I think it strongly depends on how your organization is set up.
In regards to level-based: “This data format is often more common with companies that organize employee data by distinct levels, location, or functional breakout.”
If you have the org hierarchy levels (e.g. departments) available as metadata, I would prefer the level-based hierarchy. If you have information about who is manager for the appropriate levels, this would be even better to reduce manual effort.
Best
Christian
+5
Hi
I can provide you with some of the best practices to follow when working with hierarchies.
Understanding Different Types of Hierarchies
Before creating a hierarchy, it's important to familiarize yourself with the different types of hierarchies available. This will help you determine which type is best suited for your organization's structure. The three main types of hierarchies are:
-
Parent-Child Hierarchies: This type of hierarchy represents a traditional hierarchical structure, where each member has a direct parent and can have multiple children. It is commonly used in organizations with a clear reporting structure.
-
Level-Based Hierarchies: In a level-based hierarchy, members are organized into different levels or tiers based on their position or role within the organization. This type of hierarchy is useful when there are distinct levels of authority or responsibility.
-
Ad Hoc Hierarchies: Ad hoc hierarchies are flexible and can be created on the fly to meet specific reporting or analysis needs. They are not based on a predefined structure and can be customized as per the requirements of the situation.
Preparing Your Participant File Correctly
Once you have chosen the appropriate hierarchy type, it's crucial to prepare your participant file correctly. The participant file contains the necessary metadata for your hierarchy, such as employee IDs, manager IDs, and organizational unit IDs. Here are some key points to consider:
- Ensure that the participant file includes all the required metadata fields for your chosen hierarchy type.
- Double-check that the employee IDs, manager IDs, and organizational unit IDs are accurately recorded in the file.
Limiting the Number of Hierarchies
In your project, you can have a maximum of 10 hierarchies. However, it is advisable to keep the number of hierarchies to a minimum to avoid complexity.
Using Advanced Options
When creating a hierarchy, you have the option to use advanced settings to customize the inclusion of people or add additional metadata. Here's what you need to know:
- Advanced options allow you to limit the individuals included in the hierarchy based on specific metadata values.
- You can also add unit-specific metadata to provide more detailed information about each organizational unit.
Updating Your Hierarchy
If you have already uploaded your participant file and collected data but need to make changes to your hierarchy, you can do so without manually moving units. Here's how:
- Make the necessary changes to your participant file, such as updating employee IDs or manager IDs.
- Upload the updated participant file and update your participant list with the new file.
- This will automatically reflect the changes in your hierarchy without the need for manual adjustments.
Remember to always double-check your participant file and hierarchy settings to ensure accuracy and consistency in your org structure.
For more information: You can refer to this page: https://www.qualtrics.com/support/employee-experience/creating-ee-project/participants-tab/org-hierarchies/generating-hierarchies/generating-a-level-based-hierarchy-ee/?b_no_inline=1
Leave a Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.