The answer depends on which dashboard you are talking about.
The DC guy replied appropriately for an internal IT dashboard, which is of direct concern to the CIO and their organization. It also is important when talking about the base budget/ outsourcing etc.
I will talk about a different type of dashboard, the information that is reported to the highest level of executive in a company. For this purpose our organization has moved away from all of the internal measures that talk about how we are doing the job of delivering. Instead we talk about what we are delivering at a very high level that is of interest to the business.
My strategic plans for the executive have been boiled down to a few items that no longer include operational details.
1) Key projects
2) An infrastructure road map
3) A data warehouse road map.
The categories reported on for each of the projects are:
Overall status
Major Issues
Schedule
Financial
Risk
Scope
For each category on the summary sheet they are marked as green, yellow, or red
Green - proceeding as planned, no issues
Yellow ? issues exist which may impact the project
Red ? issues exist which are impacting the project.
The infrastructure is really internal IT stuff. It is included for reference because if a big item comes up that will effect the next year budget then it helps to be identifying it several years out. It also provides a standing place for discussion if the executive committee wants to ask about things that would affect their desktops etc. For each item on the infrastructure road map there is a project plan associated with it for purposes of use by the Internal IT technical operations areas that have to deliver on the infrastructure plan.
Broad areas in the road map are:
Network
Security
Computer room
Applications development environment
Internet/intranet
Personal productivity/desktop
Group productivity/collaboration
For each item we keep a time line
Example:
Computer room ? storage
- Punch cards, tape, disk, RAID, SAN, future (SAN replacement/upgrade?)
Each of the above has the date that we moved to that technology or when we think we will in the future. The road map shows us where we have been and where we are going.
The data warehouse road map is really a portfolio all of its own. Each item in the roadmap is a project. In this way it is similar to the infrastructure plan. Like the infrastructure having it as an item in the highest level plan gives the opportunity to talk about it with the executive if there is a need. The contents of this item will vary according to the industry that a company is in.
All of this also ties into corporate planning and budgeting. We have two parts to our IT budget. A base budget and a one-time budget each year. The one time budget contains the items that are too big to handle with in the base. The items included in the high level summary/dash board that get discussed with the executive are the items that are key to the business or the ones that are big enough to need one time funding. We have synced up our portfolio management with the corporate planning so that what we show to the executive has a one to one correspondence to the major items in the budget brought forward by the rest of the business. Hence what we report on also matches the major items of interest to the business since almost any major business initiative has a large IT component as well.
Plan your work as part of the businesses planning cycle in sync with the rest of the company. Budget your work in sync with the rest of the company. And finally report on those key items that come out of the business/budget planning cycle, as they are both what is of interest to the rest of the company and what is important to the rest of the company.
My experience has been that if you plan in a organized way in sync with the rest of the company, including infrastructure and data warehouse, then the budgets will be there as long as your organization actually delivers what is promised in the plan. Delivery of the plan is another topic!
Good Luck
Phil