What Does the Term “Program Alignment” Mean When Applied to Open Data Programs?

Guest Blog By Dr. Dennis McDonald, BaleFire Global.

“Program alignment” has long been a meat-and-potatoes term for consultants involved with strategic planning. The basic idea is that the initiatives you plan and carry out to support your organization's goals and objective need to be “aligned” (i.e., supportive of or in line with) your organization’s goals and objectives.

What does "alignment" mean in practice? How do you measure whether or not your activities are aligned with your goals and objectives? And what does this mean when the concept is applied to open data programs?

Here are some of the things to look for including a caveat about applying this term too loosely to open data programs.

The basic conditions for determining whether any initiative (for example, a program, a project, a purchase, a reorganization, a new product, a new hiring initiative, etc.) is aligned with your organization’s goals and objectives are the following:

  1. You know what your organization’s goals and objectives are.

  2. You know how to measure whether these goals and objectives are being accomplished.

  3. You and your management agree that your open data program supports one or more of your organization’s goals and objectives.

  4. You know how to measure the relationship between your open data program and accomplishments of your organization’s goals and objectives.

Items one and two don't have anything to do directly with open data programs. They are the basis for ensuring that any program or initiative is aligned with what the parent organization is attempting to accomplish.

If the organization is able to articulate its goals and objectives but can't measure their accomplishment you have your work cut out for you if you decide to take on both implementing an open data program as well as measuring its performance against the organization’s strategic objectives. It’s not impossible to do both but at minimum more executive buy-in and involvement – and resources - may be required.

There are many ways to measure accomplishments. Program impact range from purely qualitative to rigorously quantitative. Don't think that benefits always need to be measured in dollars and cents for management to be convinced that a program delivers useful results. At minimum you will need convincing anecdotal evidence of positive impacts that management will understand and accept.

I mentioned a caveat concerning the ability to demonstrate alignment between an open data program and a sponsoring organization’s goals and objectives.

Don't assume that you can predict, much less measure, all the uses made of the data your open data program provides. It's in the nature of open data programs to make data available for planned as well as new, unanticipated, and innovative uses. This should not deter you from proposing an open data program but instead should cause you and your organization to rethink how your organization can support accomplishments of its goals and objectives, even among partners and users with whom you may not have worked in the past.