Our team developed a custom report and data collector on top of the Troux transformation platform to help federal customers ingest IT investment data and understand their portfolio in the context of risk, cost, and capability. One of the hardest things to do when thinking about developing analytic components is develop the statement encapsulating the purpose of the analytic component. Our first analytic component for Federal investment portfolio managers (IPMs) is focused on helping guide the IPM’s eye to the investment that most require attention. One of the hardest things I find in developing high-level dashboards is to resist the temptation to overcomplicate or try to service a broader audience than is really intended. Our dashboard is intended for the person in charge of managing the entire IT investment portfolio.
As such, some detail that is available from more analyst-oriented dashboards is abstracted or otherwise wrapped into the presentation layer. The design tension here – between giving enough detail to support decision making and presenting a very complex information set in a manner that is accessible – was difficult. Throughout the development we focused on identifying measures and views that were very relevant to other stakeholders. In the case of this example we are going to find a great deal of information and views that will resonate with individual investment managers, project portfolio managers, project managers, and analysts. Keeping laser-focused on the objective of our high-level stakeholder was critical to ensuring the eventual success of the dashboard. In fact we ended up building many of the lower level analytics required by other stakeholders in order to understand the various components of the high level analytic well enough to understand the interplay and relationships of the various components.