Developing the Goal Components of the Plan Baseline Data

Each Goal includes Baseline data that defines a starting point for the Goal. A defined starting point is essential to determine how much realistically can be accomplished during the Timeline that is established. Without a starting point, defined by data, it is not possible to strategically figure out how much can get done, how long it is likely to take and what resources will be needed. A defined starting point provides a clear, specific gauge to determine how close or how far away the Team is from the end point, which is defined by the Progress Benchmark.

Baseline and Progress Benchmark data useful for decision making is referenced to the Goal, and NOT to individual strategies within the goal. Teams may want to also keep track of progress toward accomplishing some of the individual strategies. Data tied to strategies in itself does not illustrate progress toward the Team’s Vision; it does indicate task completion necessary to implement the strategy. Baseline and Progress Benchmark data referenced to Strategies can provide an important record of the details connected to implementing the goal. This data could assist the Team in revising a strategy to be more effective and in replicating a particular event or activity. But data tied to individual strategies is not as useful for data-based decision making. Review the Goal-Vision discussion for more information.

Baseline data for the Goal may already exist, or it may need to be gathered before the details of the goal and strategies can be developed. When this happens, the Team first gathers and analyzes the data then updates the plan with Baseline data. Here are some guidelines for establishing baseline data:

Read the Goal statement carefully to identify the specific action the Team intends to implement. (See the SMART Goal criteria for more about the qualities of ‘action-oriented’ and ‘specific’). Then use questions to discuss data that would define the starting point or baseline for the current level, quality, quantity or other attributes of the action. This helps to define the size or scope of the proposed action.

If the action is not readily apparent, or Team members understand it in different ways, have a discussion to sort out any disconnects or imprecise language. Sometimes, the different understandings are because of vocabulary or terminology used differently by various agencies. Keep in mind that for a Multi-Agency team to get and stay on the same page, wording and the words chosen matter! Across systems, sometimes the same term means different things and, conversely, different terms can mean the same thing. The Team must have an openness with each other that makes it comfortable to ask questions and clarify language and meaning.