Professional Documents
Culture Documents
The ARC Integrated Planning Process: May 2003 Washington DC Carol Puzone and Jackie Greene, Facilitators
The ARC Integrated Planning Process: May 2003 Washington DC Carol Puzone and Jackie Greene, Facilitators
May 2003
Washington DC
Carol Puzone and Jackie Greene, Facilitators
Introductions
• Group
– Name
– Position
– Expectations for workshop
• Facilitators
– Name
– Position
– Expectations for workshop
Ground Rules & Format
Needs Interests
Plans
Capacity Resources
ARC ISD Core Competencies
Project Planning
Estimating Time and Staff
Requirements
Primary ARC Planning
Responsibilities
• Development:
– Region/Country
– Planning Team
– Others
• Approval:
– ARC HQ Senior Management
• Support:
– HQ and TAPE
Planning Teams
ENVIRONMENTAL SCAN
INTERNAL STRENGTHS AND WEAKNESSES EOA
EXTERNAL OPPORTUNITIES AND THREATS
MISSION AND VISION
PROBLEM ANALYSIS AND STRATEGIC GOAL STRATEGIC
PLAN
STRATEGIES AND STRATEGIC OBJECTIVES
STAKEHOLDER ANALYSIS AND BUY-IN
ACTION PLANNING
Strategic Plan vs Business Plan
? Customize or no?
EOA ANALYSIS AND
RECOMMENDATIONS
•What do the data tell us?
•Where do the needs interests, resources and capacities
converge?
•Do the needs match our core competencies?
•Are the recommendations within our manageable
interest?
•Do the recommendations match the ONS strategy?
•Does this adequately represent the country?
•Are the recommendations actionable?
TOOLS FOR EOA ANALYSIS
• External Assessment
– Opportunities
– Threats
OPPOSITES
Strength : Weakness
Opportunity : Threat
• Internal/External
• Point of Origin (?)
External Opportunities and Threats
BRAINSTORMING EXERCISE
WHEN ARE THESE A STRENGTH OR A WEAKNESS?
Staff capabilities
Financial resources
Management systems
Office facilities and equipment
Stakeholders’ perceptions
Program impacts on participants
Programs via cost/benefit analysis
Previous programs
Organization’s reputation
Program fit with core competencies
SIMILARITIES
Strength : Opportunities
Weakness : Threat
• Internal/External
• Point of Origin
SWOT STRENGTHS vs OPPORTUNITIES
(Similarities)
Strength = ARC or ONS capacities or abilities
• EOA Analysis
• go/no go decision
Problem to
Community target
Interest
Operating
National Stakeholders
Society
American Red
Cross
Problems, Causes, and Consequences
• Problem – A specific negative situation related to the
human condition:
Note: this is not the absence of a solution.
• Cause – Underlying factor(s) that exist in the
household, community, organization, or external
environment that contribute to or cause the problem.
• Consequence – Social, environmental, political or
economic condition(s), usually negative, that result
from the problem.
The Program Hypothesis:
The Relationship between the Problem Analysis and the
Program Hierarchy
PROBLEM GOAL
Then Then
CAUSES OBJECTIVES
If If
Turn the Problem/Causes into Goal/Objectives
Characteristics of a Good Objective Statement
Strategic Objectives:
Critique:
Is this phrased as a result?
Is it unidimensional?
Is it measurables and objectively verifiable?
Better:
Source: Fred R David, Strategic Management Concepts and Cases, 7th Edition, Prentice Hall, 1998
Example Use of SWOT Matrix:
Wat/San Strategy in Country X
Strengths – S Weaknesses – W
1. Expertise, experience in 1. High staff turnover
water/sanitation projects 2. No geographic focus in-
2. Long history working in- country (too dispersed)
country
Felt Needs:
– Needs based on beneficiaries’ perceptions and attitudes.
Relative Needs:
– Need in the project area in comparison to the same need in other
communities, locations, or even points in time.
Normative Needs:
– Professional, expert, or policy judgement regarding desirable conditions.
Mediating Different Types of Needs
• Transparency
• Prioritization
• Participation
• Strategic Plans
• Partnerships
Problem Analysis
Problem to
Community target
Interest
Operating
National Stakeholders
Society
American Red
Cross
Phrasing Problem Statements
Problem
Condition Condition
Behavior Behavior
Co Co
C C
Assessing and Interpreting Problem Trees
Is each cause-effect link logical? Are they necessary and
sufficient?
Can causes be identified at each level in the problem analysis
hierarchy?
What is the relative contribution of each causal stream to the
problem? How might this affect the ability to achieve impact?
Do some factors appear as causes in more than one causal stream?
Which ones are they, and what is the significance of this?
Use this information to help decide which causes should ultimately
be addressed? What should the criteria for this decision be?
Two Part Small Group Exercise:
Differentiating among Problems, Causes and
Consequences
I Determine what you believe to be the problem (P), causes of
the problem (CA), and consequences of the problem (CO).
There is only one problem.
1. Most people in the village have a very low income.
2. Men and older children have access to more nutritious
food than women and young children.
3. Most children in the village are malnourished.
4. There is no nutrition education program in the village.
5. Young children become susceptible to infectious disease.
6. Many of the men buy alcohol instead of food for the
family.
7. Children do not develop normal cognitive skills.
II Create a Problem Tree
Intervention Strategies
Partnering with
ONS, other
NGOs
Donor Interest
Best
Past Interventions
Experience,
Core
Competency Community
Needs
Synergy or Leverage
Intervention Options Example:
Reduce Malnutrition
Problem: High levels of childhood malnutrition
Cause (one of many): Inadequate diet provided to children
Possible Interventions:
Community-based nutritional education for young mothers
Billboards and radio spots promoting proper nutrition
Promote high yield sustainable agriculture practices
Distribute agricultural inputs
Physical growth monitoring and counseling
Direct food distribution
Income Generation Activity (IGA) promotion
Reconfirm/Adjust the Project Hypothesis
• In the course of defining various interventions
and selecting the ones to implement, you may
have changed the original project concept
• In order to confirm that the project hypothesis is
still satisfied, restate the hypothesis in terms of
the new interventions and reconfirm that it is still
valid
• At this point we have set the stage for designing
our project
Project Hierarchy:
ARC Terms and Definitions
GOAL:
Sustainable improvements in human conditions or well-being
OBJECTIVE:
Changes in utilization/behavior/practices, household resources
OUTPUT:
Results of project interventions, i.e., sets of activities
ACTIVITY:
Actions carried out as part of an intervention
INPUT:
Resources used by an intervention
Project Goal
• The ultimate aim or purpose of the project, written to reflect a
sustainable improvement in human conditions expected to take place
in a target group.
• The goal presents the anticipated improvements in some aspect of the
lives of the target population, and it describes what you expect the
project setting to be like after interventions have been completed.
• Note that the Goal may not be fully reached during the life of the
Project, but it must be measurable
• The Goal can be constructed as the inverse of the problem
Objectives
• Objectives should reflect the intended changes in
systemic conditions or behaviors that must be
achieved in order to accomplish the goal.
• Their statement should indicate what behaviors and
practices will change, and how and when foreseen
systemic, and/or behavioral changes will take place.
• Achievement of objectives must be verifiable at some
point during the execution of the project.
• To support a sustainable project goal, objectives
should continue to be met even after project end.
The Project Hypothesis:
The Relationship between the Problem Analysis and the
Project Hierarchy
PROBLEM GOAL
Then Then
CAUSES OBJECTIVES
If If
Interventions must be selected that address Causes
that lead to Objectives that satisfy the Project
Hypothesis
Outputs
Assuming wh at ?
Objec t ives
Wh at e ls e ?
Assuming wh at ?
Out put s
Wh at e ls e ?
Act ivit ie s
How?
Project Results Framework
Ob jectiv e Ob jectiv e
[Intended MeasurableChan gein [Intended MeasurableChan gein
Uti lization /Behavior/ Pra ctice] Uti lization /Behavior/ Pra ctice]
Key In dicator(s): Then Key In dicator(s):
If t his
and and
Ou tp ut Ou p ut Ou tp ut Ou tp ut
[Intended MeasurableChan gein [Intended MeasurableChan gein [Intended MeasurableChan gein [Intended MeasurableChan gein
knowledge, atti tudes, beli efs, availabilit y knowledge, atti tudes, beli efs, availabilit y knowledge, atti tudes, beli efs, availabilit y knowledge, atti tudes, beli efs, availabilit y
ofservices, accesstosystems/services] ofservices, accesstosystems/services] ofservices, accesstosystems/services] ofservices, accesstosystems/services]
Key In dicator(s): Key In dicator(s): Key In dicator(s): Key In dicator(s):
What changes/ r esults are necessary and Causal r elationships between results neednot always be strictlyhierarchical; i.e. , an
sufficient toget to the next “higher” level ? objective on one “level” can contribut e to the achievement of an object ive on two or mor e
How do you achieve the “higher” level of results ? “levels .”
Plenary Discussion:
Advantages and Disadvantages of
Logframes and Results Frameworks
Indicators
•An Indicator is a measurement used to
determine the degree or extent to which an
objective has been achieved, change has
occurred, or an intervention target reached.
•Indicators can be used to measure progress
for both outcomes and outputs
•Indicators are the variables that are measured
to determine the extent to which the project
interventions are producing the desired outputs
and having the desired outcomes
Characteristics of Good Indicators
INDICATORS:
• Average number of different food groups represented by foods
eaten by beneficiary families in the last 24 hours
• Average number of meals eaten by beneficiary families in the last
24 hours
•Average number of times vegetables were eaten by beneficiaries last
week
Example of an OD Goal, Objective
and Related Indicators
GOAL: Increased numbers of beneficiaries participating in
projects by increasing the financial capacity and sustainability
of the ONS by 2005.
INDICATORS:
• % of branches that have increased their total revenue by at least 35% by
2005
• % of branches that by 2005 have received revenue in one year from at
least three different sources
Examples of Poor Indicators
Monitoring
– Tracking progress towards achievement of outputs and
objectives
– Tracking basic information about the interventions over
the life of the project
– Providing management and the communities with
status updates on that progress and necessary actions
– Ongoing oversight of project implementation
Integrated Monitoring and Evaluation
Evaluation
– Assessing progress towards reaching the
project impact (goal) and objectives
(outcomes) over time in comparison with the
baseline
– Assess the outcomes and impacts of project
interventions over time in comparison with
the baseline
What Are (some of) the Key Questions?
• Monitoring:
– Determine whether or not the project is doing
what it proposed to do; i.e., has the project met its
contractual obligations? Is it within budget and on
schedule? Are the planned outputs being produced?
• Evaluation
– Address whether or not the project is having the
desired impacts and outcomes; i.e, what
difference has the project made in the lives of the
beneficiaries?
Monitoring and Evaluation Supports
Better Management Decisions
Graphic from: Results-Based Management in CIDA: An Introductory Guide to the Concepts and Principles, Canadian
International Development Agency, 1999
Proposed ARC Evaluation Guidelines
A project proposal is
NOT
a valid substitute for a project design
Preparing an ARC Proposal
We are part of a unique Movement. Make sure our proposals emphasize that
comparative advantage!
Tips for preparing your proposal:
• Plan ahead and allow sufficient time to do it right
• Build on the concept paper process
• Keep to a manageable project design – use the structured design process
• Ensure that the budget and schedule are realistic
• Assign roles and responsibilities to proposal team members
• Ensure ONS participation and partnership with ARC
• Be factual and specific, using clear, concise language
• Clarify project roles and responsibilities with Partners before you submit
your proposal
Preparing an ARC Proposal
IX Major Challenges
– Major challenges and risks to achieving objectives, goal
– Project plans to overcome challenges and risks
X Monitoring and Evaluation Plan
– Logframe/results framework
– Monitoring plan to link outputs, activities, budget
expenditures on (at least) quarterly basis
– Plan for determining whether desired outcomes (goal,
objectives) are being met
– How this information will be used to improve project
performance
XI Capacity Building
– Capacity needs of implementing partner(s)
– Capacity needs of ARC as a supporting partner
ARC Proposal Template (cont’d.)
XII Sustainability
– Project components to be sustained after end of project
– Sustained components: financial, organizational, service delivery
XIII Project Team
– Project organogram
– Key staff CVs, project responsibilities
XIV Relevant Experience
– ARC experience in the same sector, interventions,
– ARC experience with project partners
XV Project Price/Budget
– Detailed cost projections and annotations
– Addresses personnel, operations, travel, consultants, misc
ARC Proposal Template (cont’d.)
XVI Schedule
– Project timetable
– Milestones
– Task interrelationships
XVII Appendices
– Detailed technical data
– Supporting documents
– Use to avoid obscuring the proposal main message
Timeline for Proposal Writing
• See Handout
• Depends on scale of project
• Work backward from donor deadline in
planning timeline
• Leave time for review
• Find out if/when donor will answer
questions
Proposal Analysis Committee (PAC)
Process
• The mechanism for project design and proposal
review
• Formal review of the proposed project
including design and management issues
• Contributes to design and proposal
improvements
• Same planning team for each country
• Proposal review brings in other reviewers
(especially sectoral and regions with prior
experience in similar projects)
Small Group Exercise:
Selling Your Project
• Use your Project Concept and (partial) Logframe or
Results Framework as aids to writing up an Executive
Summary of your project
• You are holding your Executive Summary, standing in
ARC HQ elevator, when the President of ARC enters
the elevator and asks you what new projects you are
thinking about for your country
• You have 60 seconds to sell your project idea and gain
visibility for your project and your country
• Go for it!!
The Bottom Line…..