We are all familiar with Organisation charts, and some of us find them useful. Well you can now build them in CRM (since CRM2015). I'm not going to write and tell you how, instead I'll just point you to Sonoma Partners blog
'Dynamics CRM 2015 Hierarchy Visualizations' for that, it's clear and easy to follow (as is all of their stuff).
How can we make use of them?
The answer to this really depends on what you do and how you use CRM. Here are some examples that I've come across:
- A manufacturer mapping outlets to distribution depots
- A software provider mapping modules to a suite
- Mapping customer organisations (Accounts) to show buying centres (think national retail chains buying products locally for each state or region)
- mapping the users to the company org chart
You don't just have to stick to system entities, you can add a hierarchy to your custom entities too, For example if you wanted to model types of financial institutions : Life, Super, Investment and their funds as a single entity type, but you also wanted to see how they related to each other, for example: ACME Investment Portfolio might be the parent entity for ACME Hedge Fund Investments and ACME Off Shore Diversified funds; Acme Off Shore Diversified Funds may be the parent entity for ACME Off Shore Europe, ACME Off Shore Middle East and AMCE off Shore Americas, etc. Using the Hierarchy feature you can quickly see where an entity fits in. Clicking on any given entity allows you to see its Parent, Siblings and Children, allowing you effectively drill down through the hierarchy.
What do I get from it?
It's not a silver bullet, it doesn't solve everything, but for visual oriented people (like me) it can be a very quick and simple way to navigate between entities.
As a management tool you can leverage it by modifying the information displayed.
For example, if you are running a helpdesk you can model your client hierarchy so that the number of help requests is displayed on the Organisation and rolled up to the parent Organisation (you'll need to do a bit of scripting for that). When you view the organization hierarchy you'll see the number of requests coming in from that particular Organisation, if it is above expectations you can simply drill down to the child Organisation until you see where the bulk of the requests are coming from (think national support desk for a large Organisation like Telstra stores, for example) and you can quickly see sibling comparisons before having to switch to the actual helpdesk module.
As a sales tool, you can use it to model the client contacts to build your own Organisation chart allowing you to see where that contact fits in to the overall structure of your client organisation. It can help in identifying the decision makers, the influencers and the decenters.
what can't it do?
Well, it only works on 1 to many relationships where each end of the relationship is of the same (entity) type. So you can't mix Accounts and Contacts for example. You are also limited by the amount of information you can display on the card (in the hierarchy), so if you want to display 20 fields on each card, this won't work for you. Overall, it's only handy if you have a use for it. There's no point creating a hierarchy because you like it or to make yourself look cool, this feature should be part of your tool kit to solve specific requests, This feature just makes it a whole lot easier.