Tom's latest eBook has been released on Amazon: "The 7 Myths of IT Integrations". Tom is also a Program Director for a large Midwest corporation and has been an adjunct faculty member at Walsh College. He has managed global web initiatives, data center moves and large multi-million dollar programs.
I often like to attend classic car shows and look at some of the old classics from the 1940s and 1950s. In looking at a 1957 Chevy, arguably one of the most popular models of that era, I was struck by how simple and direct its dashboard was.
When electronic dashboards were the rage in cars almost 20 years ago, it seemed the car manufacturers were cramming more and more information into the driver’s view and overusing the technology simply because it was available. Yet to drive a car from Point A to Point B, that 1957 Chevy dashboard was brutally effective and elegant: gas, temperature, speed and gear.
Project portfolio dashboards sometimes take the overly complicated view of the world as well. Many reports generated by some of the packaged applications on the market sometimes obscure the key messages in a bevy of details. Here is a fresh and simple take on what needs to be delivered in a portfolio dashboard to enable communication and highlight serious roadblocks. Think of it as the “Bel-Air” portfolio variety.
Similar to the 1957 dashboard, portfolio dashboards should be simple and ideally fit on one page. Everything should be easily visible at a glance. In short it should be intuitive.
Project Schedule
My preferred schedule is a simple Gantt chart. With each major project within the portfolio represented as a single