| Literature DB >> 30174742 |
Julia Leventon1,2, Luuk Fleskens2,3, Heleen Claringbould4, Gudrun Schwilch5, Rudi Hessel6.
Abstract
In this paper we present a novel methodology for identifying stakeholders for the purpose of engaging with them in transdisciplinary, sustainability research projects. In transdisciplinary research, it is important to identify a range of stakeholders prior to the problem-focussed stages of research. Early engagement with diverse stakeholders creates space for them to influence the research process, including problem definition, from the start. However, current stakeholder analysis approaches ignore this initial identification process, or position it within the subsequent content-focussed stages of research. Our methodology was designed as part of a research project into a range of soil threats in seventeen case study locations throughout Europe. Our methodology was designed to be systematic across all sites. It is based on a snowball sampling approach that can be implemented by researchers with no prior experience of stakeholder research, and without requiring significant financial or time resources. It therefore fosters transdisciplinarity by empowering physical scientists to identify stakeholders and understand their roles. We describe the design process and outcomes, and consider their applicability to other research projects. Our methodology therefore consists of a two-phase process of design and implementation of an identification questionnaire. By explicitly including a design phase into the process, it is possible to tailor our methodology to other research projects.Entities:
Keywords: Interdisciplinarity; Participation; Soil degradation; Sustainability
Year: 2016 PMID: 30174742 PMCID: PMC6106094 DOI: 10.1007/s11625-016-0385-1
Source DB: PubMed Journal: Sustain Sci ISSN: 1862-4057 Impact factor: 6.367
Case study sites in the RECARE project
| Case study | Primary soil threat | Location | Country |
|---|---|---|---|
| 1 | Erosion | Frienisberg | Switzerland |
| 2 | Erosion | Caramulo | Portugal |
| 3 | Erosion | Peristerona watershed | Cyprus |
| 4 | Salinization | Timbaki, Crete | Greece |
| 5 | Compaction | Aarslev | Denmark |
| 6 | Soil sealing | Poznan and Wroclaw | Poland |
| 7 | Desertification | Canyoles River Basin | Spain |
| 8 | Desertification | Gunnarsholt | Iceland |
| 9 | Floods and Landslides | Vansio-Hobol Catchment | Norway |
| 10 | Floods and Landslides | Mjava Catchment | Slovak Republic |
| 11 | Loss of organic matter | Veenweidegebied | The Netherlands |
| 12 | Loss of organic matter | Broddbo | Sweden |
| 13 | Loss of organic matter | Olden Eibergen | The Netherlands |
| 14 | Loss of organic matter | Veneto Region | Italy |
| 15 | Contamination | Guadiamar | Spain |
| 16 | Contamination | Copsa Mica | Romania |
| 17 | Loss of soil biodiversity | Isle of Purbeck | United Kingdom |
Fig. 1The RECARE methodology for identifying stakeholders for transdisciplinary research, highlighting the phases and steps of the methodology, the people involved, and the purpose of each step. Researchers are shown as blue squares; stakeholders are red circles; and the core team (paper authors) are shown as yellow triangles
The purpose of the constituent parts of the questionnaire
| Questionnaire section | Purpose |
|---|---|
| Part 1: characterising the stakeholder | |
| 1A | Basic information on the stakeholder, including their size and location |
| 1B | Checks if stakeholder is actually multiple stakeholder, for example if there are local and national branches with different functions |
| 1C | Considers the spatial location and scale of the stakeholders’ interest |
| 1D | Defines the stakeholders interest, including their field of activity, form of role and their sector |
| Part 2: snowball sample | |
| 2A | Collects information on the other stakeholders that are known to the responding stakeholder |
| 2B | Collects information on stakeholder engagement opportunities that the stakeholder knows of |
| 2C | Collects information on the relevant policies that the stakeholder is aware of |
Stakeholders identified by the questionnaire process
| Case study | A. Stakeholder numbers | B. Field of activity | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Initiala | Finalb | Education | Forestry | Env. protection/conservation | Agriculture | Recreation | Research and development | Product/commodity exploitation | Water management | Land use policy and planning | Community development | Other | |
| 1 | 33 | 44 | Y, X | Y, X | Y, X | Y, X | Y, X | Y, X | Y, X | Y, X | Y, X | Insurance | |
| 2 | d | 19 | X | X | X | X | X | X | Fire management | ||||
| 3 | c | 8 | Y, X | Y, X | X | Y, X | X | Y, X | Cultural Heritage | ||||
| 4 | 4 | 10 | X | Y, X | Y, X | X | Tourism water end users construction | ||||||
| 5 | 26 | 46 | Y, X | Y, X | Y, X | X | Y, X | Traffic management | |||||
| 6 | c | 9 | X | X | X | X | |||||||
| 7 | c | 6 | X | X | X | X | |||||||
| 8 | c | 48 | X | X | X | X | X | X | Soil | ||||
| 9 | d | 35 | X | X | X | X | X | Insurance companies | |||||
| 10 | 9 | 13 | Y, X | Y, X | X | X | Y, X | Land owners | |||||
| 11 | d | 31 | X | X | X | ||||||||
| 12 | 0 | 6 | X | X | X | X | |||||||
| 13 | d | 49 | X | X | X | X | X | X | X | X | |||
| 14 | 6 | 26 | X | X | Y, X | Y, X | Y, X | Y, X | |||||
| 15 | d | 6 | X | X | X | X | X | X | X | X | X | X | |
| 16 | 6 | 16 | X | Y, X | Y, X | Y, X | X | ||||||
| 17 | c | 19 | X | X | X | X | X | X | Military | ||||
Y field of activity included in initial list of stakeholders from the case study leader at the beginning of the process (information can only be provided where superscript letters d and c are not used in the ‘stakeholder numbers’ columns). X field of activity and level included by the end of the process
aNumber identified by case study partners on their initial completion of Part 2 of the questionnaire
bNumber of stakeholders identified at the end of the process
cInformation not provided by case study partner
dInformation was provided directly in Excel format, rather than in questionnaire form, meaning parts of the process were not visible to the core team