Is this chart an analyst’s view or a governance report?
This chart displays a real portfolio, although with disguised project names and market titles.
The chart sets up a deeper question:
“why is 50% of our spend going to only 10% of the gain?”
The chart doesn’t provide answers or recommendations. That’s why it’s an analyst’s view. And it’s a powerful view because the colors and shapes beacon the analyst to group the data into pivot tables that can drive the analysis further. That’s why PortView, the analyst’s tool that created the chart, is so helpful.
What the analyst sees is not what a governance team should see. Please don’t make your governance team create pivot tables in their heads.
The Analyst’s View
The first data visualization should help analysts probe a situation. From there, analysts should collect and review more data. The goal is to build a story that explains the situation and uses logic to recommend decisions and actions.
The analyst’s views should lead to more insightful questions and answers. The governance storyboard should communicate explanations and recommendations.
Delivering an analyst’s view into a governance meeting is a surefire way to piss off many people. You’ll find project leaders and team members at the front of the line. And right behind them will be the governance team.
Are you sharing analyst views in governance meetings?
Fill in the form below to receive information on PortView, creating analyst’s views, and crafting impactful governance storyboards.