Best practice: display and output optimisation

Scenario:
    
As I’m sure you have seen many time before, we are experiencing difficulty in getting the optimal scale and display in the automatically generated org charts. Where in manually generated charts, we would roll-up identical rolls and neatly arrange ‘child’ nodes on the page, it seems OrgVue spreads things out a bit more, so that some larger organisation charts become illegibly small. Outside of leveraging the predefined view types (e.g. ‘wide tree’, ‘compact tree’ etc.) is there a way of optimising the display?

 

Practice:

OrgVue does a pretty good job in maximising space when creating organisation charts using algorithms but inevitably, a bespoke chart will always be able to squeeze more material in.

It is a good idea to spend time getting a single format that works 95% of the time.  We would recommend:

  • Use the Sunburst or icicle view for an overview of the whole organisation
  • Restrict all charts to three levels-assuming an A4 slide.
  • Have a custom property that rolls up the total level of descendants so positions cut off the chart are still indicated.
  • Embed a .pdf of the full chart so that the client can “double click” if they want to see the detail beneath-it looks quite good if you do that as an icon.
  • Depending on the Org, I usually found that two sets: layers 1-3 and 3-5 were sufficient if the descendants property and detail were included in the pdf.  Occasionally I would do a 5-7 for very deep/populated areas of the org chart


We are also considering adding a capability to “collapse” an org chart to only include parents and teams of leafs which would simplify the chart.  The same effect can be achieved today using the descendants property and filtering out leaves.

 

 

Have more questions? Submit a request

Comments