Implementing dotted (multiple) reporting lines

Organisations can be messy and matrix or dotted line reporting is common. Luckily, OrgVue has a couple of ways of visualising your org charts even when there’s more than one manager per employee. All you need for both methods to work is to have a second parent ID field in your data (e.g. Reporting Manager ID and Regional Manager ID).

 

Option 1: Switching the 'Parent by' between different Parent IDs

Here is a hierarchy in which the nodes are parented by the Reporting Manager ID : -

mceclip0.png

 

Changing the 'Parent by' setting to the Regional Manager ID results in this : -

mceclip2.png

Note how the three Service Operatives have moved to their respective Regional Manager.

 

Option 2: Team View

Reverting back to parenting by the Reporting Manager ID and then viewing the Team View dashboard

you will see this : -

mceclip3.png

Setting the Matrix links option in the Side panel to 'Regional Manager ID

mceclip6.png

results in this : -

mceclip5.png

The existing hierarchy (based upon the Reporting Manager ID) remains intact but to the right of the canvas you now see the list of direct reports of the top node of this hierarchy using the Regional Manager ID as the parent. In this instance, there is no difference between these two hierarchies. To view the changes you need to drill down by clicking on the relevant manager node : -mceclip8.png

This places this manager at the head of the displayed hierarchy and shows the nodes that report in to it (with the current Reporting Manager ID set as the parent by) on the left, and the nodes that report into it when the Regional Manager ID is considered on the right : -

mceclip9.png

Note that the three regional Service Operatives are not showing in the list on the right.

You can navigate back up a level by clicking on the 'Global Lead' link : -

mceclip10.png

From there, clicking on 'Regional Lead (Region 1)' : -

mceclip11.png

shows this manager's responsibilities : -

mceclip13.png

This shows nothing to the left of the vertical text which indicates that the Regional Lead (Region 1) only has any responsibilities when the hierarchy is based upon the Regional Manager ID being considered as the parent. Where the Regional Manager is considered as the parent we can see that Regional Lead (Region 1) has one direct report (Region 1 Service Operative).

 

If your data doesn’t already contain a second parent_id, you can create one easily. Make a property to hold the dotted line manager id, and then “Parent By” that property. Your hierarchy will disappear and all your nodes will be orphans. However, when you drag and drop nodes in tree view to start building your matrix[1] reporting structure, the correct values for parent_id will be generated in the newly created property.

 

If your organisation is too big for this to be feasible, we've developed a custom online form that you can instantly email to your employees and prompt them to fill in the email address of their manager(s). This can be used to automatically generate a hierarchy by crowd sourcing. Get in touch with one of our consultants for more information.

 

 

Best Practice Option: Linking people to positions

Sometimes neither of the above options is sufficient because either reporting relationships aren't clear, or change regularly. This is especially true in professional services and healthcare, where having 3+ managers, employees reporting outside of their own company, skip level reporting and shift managers are common.

 

A good way of capturing this is to have a standard org chart of roles that remains fairly static, and a flat list of people that changes regularly. You can then link people to their current role(s) and capture some of these complex many-to-many relationships.

Have more questions? Submit a request

Comments