This article explains the content provided in the Hierarchy Cleaning pack, showing how it is used to:
- Identify nodes which are disconnected from the reporting structure
- Understand why they are disconnected
- Establish a single hierarchy for org analysis and modelling
- Access a record of any edits and corrections so these can be corrected at source
The link provided at the end of this article explains how to access the pack.
Slide 1: Hierarchy assessment summary
This slide provides an overview to understand the overall completeness of the hierarchy
Zones 1 and 2 show the number of nodes in each category:
- The Deepest Hierarchy: The main hierarchy, identified by the total number of layers
- Orphan Sub Trees, and the size of each sub-tree. Smaller trees which are disconnected from the Deepest Hierarchy due to the most senior node being an orphan.
- Orphan Leaves. Orphans which are individual contributors.
The reason for nodes being disconnected from the Deepest Hierarchy (‘Orphan Reason’) can be seen from the information provided in Zone 3:
- Blank Parent IDs: the Parent ID value is missing.
- Missing Parent Node: the node of the Parent ID value does not exist within the dataset. In contrast to the Blank Parent IDs, a value for the Parent ID does exist.
- Circular references: the IDs for the node and parent refer to each other. The structure is broken as the parent of a node has the child as their parent.
Slide 2: Hierarchy assessment
This slide provides detail to identify each Orphan Sub Tree and each Orphan Leaf. There is also the opportunity to ‘reparent’ orphans by dragging-and dropping to the Deepest Hierarchy.
- Nodes are color-coded to identify the category (see definitions above). This is also included on the card
- The ‘Orphan Reason’ (see definitions above)
- The total number of positions included in the sub-tree
- The number of parents in the sub-tree (see note **, at the end of this article)
- The number of leaves in the sub tree (see note **, at the end of this article)
- The number of positions at each depth (layer) in the sub tree
You can expand the number of organizational levels shown using the control highlighted in the illustration above. For example:
- To explore beyond the top-level node of each sub-tree and identify who is located at lower levels
- To reparent orphans into the Deepest Hierarchy (instruction below)
Reparent by orphans by dragging-and-dropping
- Drag an orphan to the position in the Deepest Hierarchy it reports to
- Select ‘Child of’ and ‘Preserve children’ (these are the default options)
- Select Apply
Slide 3: Orphans Review
This slide is similar to slide 2 and can be used in the same way to identify and reparent orphans.
Slide 4: Orphans Detail
This slide lists all Orphans in a worksheet slide. This slide type is useful if you need to export a list detailing all the hierarchy issues to share with colleagues.
- If more information is needed (for example, the function or location of the orphan), additional columns can be added by selecting the “Add Property” icon in the ‘Columns’ section of the slide pane
- Select the ‘Export Canvas Content’ icon to download the worksheet
Slide 5: Outgoing Count Heatmap
This slide shows the organization landscape, color-coded by Outgoing Count (the number positions reporting to each position). This provides a great way to identify data quality issues which would not have been identified through the earlier slides which identified orphans. For example, in the illustration below, it would be beneficial to check whether there really are three managers with more than 20 direct reports.
TOP TIPS:
- Filter with the colour legend to identify where these managers are in the structure
- Use this slide to reparent nodes to the correct manager (see instruction at Slide 2, above)
Slide 6: Changes Record
The final slide provides an automatic record of changes made. This information can exported and passed to whoever is responsible for managing your company’s data to have it fixed t source.
Note:
- The changes included in the report are limited only to those which have been made since the last time your data was saved, unless you are working in a draft.
- It is important to be aware of Saving your data: Datasets versus Drafts when making changes and using a Changes List slide.
- This slide has no content until changes are made
Slide 6: Changes Record – Before any changes are made
Changes Record – After changes have been made
See how to Access the Hierarchy Cleaning Pack.
Comments
0 comments
Please sign in to leave a comment.