I recently started using Processing (processing.org) at the CBC to visualize the dependencies of the content areas on projects being built by Media Ops & Technology (MO&T). Roughly speaking, MO&T builds out platform related projects and the content areas leverage the functionality of those projects to build out their sites. The previous post here was a first sketch in chalk of how a tool to visualize these dependencies might end up looking. Turns out I wasn’t too far off.
These screenshots below show the hightlighted and un-highlighted views. What isn’t shown is the interactive component that enables users to pick which content areas they want to see and then the ability to select individual projects and highlight their dependencies.
The next visualization focused on displaying the content area’s over all dependency on each Media Ops project and then normalizing the relative impact based on audience or revenue. Below is the baseline view before audience and revenue adjustments are applied. One of the benefits of this view is that it makes it easy to see where the content areas aligned in their dependence on different Media Ops projects.
There are more projects underway to help inform discussions about where and how we expend our resources.
A big thanks goes out to everyone involved in the Processing project!