People in an Information Supply Chain perform an Action that creates Information as shown here:
LINQ captures a person's role in an Information Supply Chain through this relationship of a Person performing an Action. The People Dashboard can then pivot a view around that Person to create a view like this one:
In the table, it appears that Hilary works a total of 1,678.25 hours a year. She's a full time employee whose contract is for 2,000 hours a year. So does this mean that Hilary has spare capacity of 321.75 hours?
No! It's important to appreciate that LINQ only captures the work of a person that relates to their work processing Information in an Information Supply Chain (ISC). In Hilary's case, she also has a leadership coaching role which takes 4 hours a week and the company also has a policy of only loading people to 80% of their capacity to allow time for professional development. So how can we represent the 200 hours of coaching time and the 400 hours of professional development time?
This can be done by creating separate Action nodes that represent non-ISC Actions. In this case 'Professional Development' and 'Leadership Coaching'. The durations are set to 400 and 200 hours respectively and Hilary is connected to those Actions. This appears like this in the Canvas:
Now, when the People Dashboard is displayed, it appears like this:
The two non-ISC Actions appear in the spider diagram with no Information being produced; this is appropriate. And note that the table is now showing that Hilary is actually working 278.25 hours over capacity. This makes it likely that Hilary is at risk of becoming an information bottleneck.