Overview
This page has been mothballed.
It is no longer being updated but we've left it here for reference.
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
A Workshop in Bulgaria: Options for Local Biodiversity Management in Protected Areas
8 - 10 February, 2002
The Project Proposal Session: Lessons Learned
- Clearly state assumptions about the background to a proposal (such as data on market research and opportunities).
- In addition, be explicit about other aspects of the proposal, such as feasibility, relevant activities and the likely results of these activities.
- Make the purpose and objectives of the project concise, in order to avoid attempting too much. Do not get distracted from this project purpose and these objectives.
- Involve people from a socio-economic background in devising the project.
- In tackling conflict issues, involve people; adopt clearly limited goals; identify goals which are common to all participants.
- Develop a list of simple, defined actions: this helps partnerships agree on which actions to adopt.
- Use local experience-based knowledge reflecting community heterogeneity, in order to form new collaborative approaches.
- Don't always avoid conflicts, as these inspire discussion.
- Distinguish between encouraging economic development within a park and the legal requirement to produce a management plan.
- Account for lessons from previous projects when designing new project proposals.
- Small, demonstration projects of community involvement are morel likely to receive funding than national proposals.
- The Project Proposals