Project information:
Project Name: “Financial integrity, anti-corruption and compliance” concentration for master students in law”
Strategic Policy Alignment (To be completed by INL):
FBS Objective(s):
ICS Objective(s):
Other regional or cross-cutting strategic alignment
Design element and Statement
Note: Goal, objective, and sub-objective statements should meet the Change and Clarity standards described in Appendix B. In brief, state the result expected, and be specific about what we should observe if the end state is achieved.
Indicator name
Note: Each design element may have no indicators, one indicator, or multiple indicators. Only collect indicators that will be useful for understanding the extent to which project implementation is proceeding as expected. Do not include indicators for deliverables. Additional indicator information should be provided in the PIRS.
INSTRUCTIONS and DEFINITIONS
Purpose: The primary purpose of the Change Map is to link the work plan (goals, objectives, sub-objectives, and activities) to the monitoring plan (indicators). INL emphasizes “Change” in the title because the work plan should describe what changes the project intends to achieve (i.e., the goals, objectives, and sub-objectives) and how the project will achieve them (i.e., the activities). There should be more detailed information about the work plan in the project proposal; and more details about the indicators in the Performance Indicator Reference Sheet (PIRS). This document serves as a “mapping” between the two, by showing which indicators will be used to monitor progress toward which goals, objectives, and activities. It also functions as a high-level summary or “cover sheet” of the project that describes the specific results the project intends to achieve and how it will achieve them.
Roles and Responsibilities: INL staff are responsible for filling in the strategic alignment section. Implementing partners generally create the initial draft of the main Change Map table. INL staff provide feedback and eventually approve a final version. INL staff and dedicated M&E specialists at Post or in Washington can work with implementers in a consultative capacity to ensure that goals, objectives, and indicators meet INL design and monitoring standards.
Requirements: The change map must include the strategic alignment section; goals, objectives, sub-objectives (if applicable), and activities—all in the first column; and indicators in the second column. The vision section and associated indicators are optional.
A note on indicators: More is not necessarily better. Data are costly to collect and analyze; and too many indicators can result in focusing on minutiae at the expense of answering the most important monitoring questions, namely: 1) are major project activities going to plan; and 2) is the project achieving the expected immediate results.
A note on indicator terminology: INL uses the following indicator terminology:
Output indicator: A measure of the expected result of an activity Outcome indicator: A measure of the expected change defined by a goal, objective, or sub-objective statement Vision: Changes that are expected to occur after the period of performance ends, or only in combination with other projects
Strategic Alignment: INL will complete this section. All INL projects should align to strategic goals and objectives laid out in strategy documents such as the Functional Bureau Strategy (FBS), an Integrated Country Strategy (ICS), or an Issue-Based Strategy. The Strategic Alignment section indicates which strategic objectives the project is intended to advance.
Vision: A vision statement describes the results that a project contributes to but is not expected to achieve during its period of performance. The vision may be broad (“reduce the flow of illicit narcotics through Freedonia”) or more specific (“increase arrests related to methamphetamine production sites in Freedonia”). The vision statement is optional because achieving a vision-level change is often the result of multiple interventions and lines of effort, over an extended period of time, in which INL is not the only actor.
Goal: A goal describes the highest level of change that a project expects to achieve as an immediate result of its activities, during the project’s period of performance. Projects may have one or multiple goals. Goals must meet the “change” and “clarity” design standards. See Appendix B below (Design Work Aid) for more explanation and examples.
Objective / Sub-Objective: Similar to goals, objectives and sub-objectives describe changes that the project expects to achieve during the period of performance. Objectives are mid-level changes that, if achieved, should result in the achievement of a project goal. Sub-objectives are the smallest level of change that, if achieved, should result in the achievement of an objective. Note that many objectives may not require sub-objectives.
Activity: An activity refers to the things that INL or the implementing partner are doing to cause the changes described in the goal, objective, and sub-objective statements, such as training, development of guidance documents, and equipment donations.
Indicator: An indicator is a statistic (or metric) used to measure progress toward accomplishing the activities or changes described in the goal, objective, and sub-objective statements. Indicators should answer the question: to what extent was the associated activity, goal, or objective achieved? Note that indicators associated with activities are generally output indicators (e.g., # trained, $ value of equipment donated), while indicators associated with goals, objectives, and sub-objectives are outcome indicators (e.g., changes in knowledge or behavior as a result of training). See the Indicator Work Aid, a tab in the Performance Indicator Reference Sheet for more explanation and examples.
Design Work Aid
Introduction:
To improve project design, INL is focused on two of our design standards: change and clarity. To meet the change standard, goals and objectives should be expressed as the expected results, or desired end states, of the project, not as the activities that INL or its implementing partners undertake to achieve those results. To meet the clarity standard, goals and objectives should be specific about the expected results. What exactly should we expect to observe if the project achieves the expected result?
This document provides quick tips on how to meet each of these standards, examples of what meeting them and not meeting them looks like, and why meeting them matters.
How to Meet the Change Standard:
The key to the change standard is the actor: are we describing what will be true for our partners at the end of the project or are we describing what INL or our implementers will do during the project? The first is a change, the second an activity. For example, INL might train police. Running the training is our activity. The desired change is what the police learn or, in combination with other activities, the change in their behavior. A training project’s goal should be about what the police learn or do.
To be sure you’ve met the change standard, always write goals to include the subject (the person performing the action) and check that the subject is not INL or our implementing partner.
Examples of Common Mistakes and How to Fix Them:
Why Change-based Goals Matter:
Congress entrusts INL with taxpayer funds for the purpose of making a difference on the ground, not funding the existence of foreign assistance implementing organizations. Setting change-based goals and objectives is important for two reasons. First, what a project monitors depends on its goal. If we want to know if our projects are making a difference on the ground, we need to set goals focused on that external difference. Second, it sends an important message about what we are collectively responsible for accomplishing. It is not enough to execute an activity. We are also responsible for understanding if that activity resulted in the desired change so we can adjust future activities if needed.
How to Meet the Clarity Standard:
There are three components to clarity: (1) be consistent in describing the most significant change the project seeks to achieve, i.e., the goal; (2) the goal and objectives should be precise about what will be different as a result of the project; and (3) project documents should define ambiguous terms.
Each is elaborated below.
Consistent goal: When projects are described in narrative form without a change map, they often articulate a range of aspirations, some of which the project actually intends to bring about and others to which the project might contribute in a small way but that are much bigger than what one project can reasonably expect to accomplish. It is not always clear, however, which the project seeks to catalyze and which are aspirational. A good way to avoid this problem is to use a change map and to be clear that a goal is a change the project expects to achieve, not a visionary purpose for pursuing a project. (Note: different organizations use terms in different ways. Some use the word goal to mean visionary purpose. That is fine so long as the project document clearly identifies the most significant change the project expects to achieve.) Precise changes: It is very common for a project to know a desired end state but one that is not attainable as the result of a particular intervention. In these cases, INL often articulates goals that indicate progress toward that desired end state but do not specify how much progress to expect from the particular project. Goals like this use words like build, enhance, increase, or strengthen. This can mask a superficial understanding of what is causing the problem INL seeks to address and how much of that can be addressed given context and resources. When working on challenging issues with limited resources, it is imperative that we understand all the main causes of the issue in question, which of those are the most important to address and in what sequence, and who has the power to address them. Being disciplined about writing goals and objectives that state who will be different in what way as a result of our activities drives deeper analysis that allows us to design more effective interventions. One tip for avoiding the fuzzy thinking pitfall is to design with a partner. It’s fine to start with the general statement that we want to, for example, improve border security. Then talk with a partner about follow up questions like: what are the main problems with Freedonia’s border security now? What’s causing those problems? What would it take to address those causes? How much of that can we afford to take on? In most cases this will lead to identifying a particular way in which the project will improve border security. Occasionally, however, INL is truly seeking to chip away at a problem it does not make sense to break into its component parts. In these cases the goal/objective can call for “improving” but should include a target to make clear by how much. Define terms: There can be a surprising number of words that mean different things to different people. Two common categories that benefit from definitions are target groups and words that describe doing something to a certain quality marker. On the former, for example, a project might state that it seeks to target police leadership. If someone said INL leadership, would you understand that to mean the Front Office, Office Directors, or some other grouping? Similarly, police leadership can mean different things to different people and knowing which we’re talking about is important for how we scope and approach activities. On the latter, words like “appropriate” or “effective” can mean different things. If our implementing partner has a very different understanding of what an “effective” prosecution looks like, they are likely to execute activities that emphasize points we don’t prioritize. As with articulating precise changes, a good approach for making sure we define ambiguous terms is to talk about our project plans with others. It’s fine to have short goal statements (e.g., the police investigate effectively) and provide the necessary definitions as footnotes.
Examples of Common Mistakes and How to Fix Them: