29.01.2013 Views

here - Circles for Connection

here - Circles for Connection

here - Circles for Connection

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Katholieke Universiteit Leuven<br />

Faculteit psychologie en pedagogische wetenschappen<br />

Centrum voor Organisatie- en Personeelspsychologie<br />

The systems psychodynamics of collaborative work: issues in<br />

direction setting of the process<br />

Proefschrift aangeboden tot het verkrijgen van de graad van Doctor in de<br />

Psychologische Wetenschappen, 2006<br />

door Silvia Prins<br />

Promotor: Prof. Dr. Tharsi Taillieu


Cover illustration: “Ik ben, omdat wij zijn” (“I am, because we are”), Klaus Elle.<br />

de Liefde, W.H.J. (2002). African tribal leadership voor managers. Van dialoog tot besluit.<br />

Deventer, Kluwer.


Silvia Prins<br />

Een systeem psychodynamisch perspectief op multipartij samenwerking: thema’s in het<br />

richting geven aan het proces.<br />

Proefschrift aangeboden tot het verkrijgen van de graad van Doctor in de Psychologische<br />

Wetenschappen, 2006.<br />

Promotor: Prof. Dr. T. Taillieu<br />

SAMENVATTING<br />

Multipartij samenwerking is een strategie waarbij vertegenwoordigers van verschillende<br />

organisaties en sociale groepen samenwerken om duurzame oplossingen te ontwikkelen<br />

voor een ‘metaprobleem’ dat allen aanbelangt. In gedeelde verantwoordelijkheid nemen ze<br />

beslissingen voor de toekomst van het domein. ‘Leiderschap’ in dergelijke horizontale,<br />

participatieve organiseerprocessen is een problematisch begrip. Over het algemeen is er geen<br />

<strong>for</strong>mele leider met hiërarchische autoriteit. Geen enkele groep of organisatie kan eenzijdige<br />

beslissingen nemen voor het domein. Dit onderzoek richt zich op leiderschap als een<br />

gedeelde groepsfunctie. Het doel was om te exploreren welke betekenis deelnemers gaven<br />

aan thema’s en dilemma’s waarmee ze geconfronteerd werden. De onderzoeker ging na hoe<br />

de dynamiek die rond deze thema’s ontstond de richting van het proces mee beïnvloedde.<br />

Om de specifieke aard van inter-organisationele samenwerkingsprocessen te begrijpen, nam<br />

de onderzoeker deel aan drie projecten waarin deelnemers poogden een meta-probleem op<br />

te lossen: erosie, geïntegreerd management van een riviervallei, en pleegzorg. Het doel was<br />

om de complexiteit en de uniciteit van deze processen in hun natuurlijke context te<br />

documenteren. De dataverzameling was ontworpen om de diverse perspectieven doorheen<br />

de tijd in kaart te brengen, waarbij de antecedenten en de context van het<br />

samenwerkingsinitiatief eveneens gedocumenteerd werden. De onderzoeker gebruikte data<br />

triangulatie: participerende observatie tijdens vergaderingen, interviews, documenten, en<br />

dagboeknotities. Één project (pleegzorg) werd, op een systematische wijze, in de diepte<br />

geanalyseerd. Een gedetailleerde reconstructie van het proces bood een voorlopig overzicht<br />

voor analyse en interpretatie. De onderzoeker analyseerde daarnaast ook de thema’s die naar<br />

voren kwamen op verschillende momenten in het proces: bij de start (stakeholder<br />

interviews), tijdens het proces (observaties) en na het project (kritische incidenten<br />

interviews).<br />

De onderzoeker gebruikte het systeem psychodynamisch perspectief om betekenis te geven<br />

aan de dynamieken die zich ontwikkelden tijdens de samenwerking. Dit kader benadrukt de<br />

wederzijdse beïnvloeding van systeemkenmerken en processen: de dynamieken beïnvloeden<br />

het systeem en het systeem beïnvloedt de interacties. Dit onderzoekskader maakte het<br />

mogelijk om te begrijpen hoe de betrokkenen omgingen met de dilemma’s die in<strong>here</strong>nt zijn<br />

aan samenwerking over organisatiegrenzen heen en hoe ze teveel spanningen afweerden.<br />

Het bood ook inzicht in welke voorwaarden en interventies taakgericht en productief werk<br />

mogelijk maakten.<br />

De gevalstudies zijn een narratieve weergave van zich ontwikkelende organiseerprocessen<br />

en ze bieden een ‘dikke beschrijving’ van samenwerkingsprocessen. Dit empirisch<br />

onderzoek draagt bij tot theorieontwikkeling in het domein van multipartij samenwerking.<br />

De onderzoeker ontwikkelde contextuele inzichten voor elke gevalstudie, die relevant<br />

kunnen zijn in gelijkaardige organisatiecontexten. De cases laten zien dat niet alleen<br />

personen of organisaties in een ‘leidinggevende’ rol de richting van de samenwerking<br />

i


epalen. Dit gebeurt ook door elementen in de context (b.v. evenementen, actoren in de<br />

omgeving); de betekenissen die aan de taak worden gegeven (b.v. verschil tussen <strong>for</strong>mele en<br />

fenomenologische taak); het structureren en <strong>for</strong>maliseren van het proces (b.v.<br />

stakeholderanalyse, <strong>for</strong>mele rollen, interventies); en de manier waarop de actoren omgaan<br />

met moeilijke relationele thema’s en dilemma’s. Enkele karakteristieke afweermechanismen<br />

worden besproken. De onderzoeker besluit met een aantal specifieke interventies en<br />

faciliterende voorwaarden die de negatieve gevoelens opgeroepen door de openheid,<br />

complexiteit en onzekerheid van samenwerking kunnen dragen en betekenis geven.<br />

ii


Silvia Prins<br />

The systems psychodynamics of collaborative work: issues in direction setting of the<br />

process.<br />

Thesis presented to obtain the degree of Ph.D. in psychology, 2006<br />

Promoter: Prof. Dr. T. Taillieu<br />

SUMMARY<br />

In multiparty collaboration stakeholder representatives of different organizations and social<br />

groups work together to develop sustainable solutions <strong>for</strong> a meta-problem that concerns<br />

them all. They jointly take decisions <strong>for</strong> the future of the domain. ‘Leadership’ in such<br />

horizontal, participative processes of organizing, is a problematic notion. Usually t<strong>here</strong> is no<br />

<strong>for</strong>mal leader with hierarchical authority. No single group or organization can take unilateral<br />

decisions <strong>for</strong> the domain. This research focused on leading as a shared group function. The<br />

aim of the research was to explore how participants made sense of the issues and dilemmas<br />

with which they were confronted. The researcher investigated how dynamics that emerged<br />

around those issues influenced the direction of the process.<br />

In order to understand the specific nature of inter-organizational collaborative processes the<br />

researcher participated in three projects dealing with a meta-problem: erosion, integrated<br />

management of a river valley, and foster care. The aim was to capture the complexity and<br />

uniqueness of the collaborative experiences in their natural setting. Data collection was set<br />

up to assess the multiple perspectives over time, taking the antecedents and context of the<br />

collaborative into account. The researcher used data triangulation: participative observation<br />

of meetings, interviewing, documents, and journalizing. One case (foster care) was analyzed<br />

in depth following a systematic approach. A detailed reconstruction of the process provided<br />

a provisional overview <strong>for</strong> analysis and interpretation. The researcher also analyzed the<br />

issues that emerged at different moments in the process: at the start (stakeholder interviews),<br />

during the process (observations) and after the project (critical incident interviews).<br />

The researcher used the system psychodynamic perspective to make sense of the dynamics<br />

that emerged in the collaborative. This frame allowed <strong>for</strong> an interpretation of the<br />

interconnection between system features and emergent dynamics in the system: the<br />

dynamics influence the system and the system influences the interactions. This research<br />

frame helped to understand how participants dealt with the dilemmas in<strong>here</strong>nt in<br />

collaboration across organizational boundaries and how they defended against uncontained<br />

tensions. It also provided insight in conditions and interventions that facilitated task oriented<br />

and productive collaborative work.<br />

The case studies are narrative accounts of emergent processes of organizing and provide a<br />

‘thick description’ of collaborative processes. This empirical research contributes to theory<br />

building in the domain of multiparty collaboration. The researcher developed contextual<br />

insights <strong>for</strong> each case that can be illustrative <strong>for</strong> similar organizational settings. The cases<br />

demonstrate that not only persons or organizations in ‘leading’ roles set the direction in<br />

collaborative work. Direction is also established through context elements (e.g. events,<br />

players in the environment); sense making of the task (e.g. difference between <strong>for</strong>mal and<br />

phenomenological task); structuring and <strong>for</strong>malizing of the process (e.g. stakeholder<br />

analysis, <strong>for</strong>mal roles, interventions); and the way in which the participants deal with<br />

difficult issues and dilemmas in their relationship. Some particular defensive dynamics are<br />

discussed. To conclude, the researcher stresses a number of specific interventions and<br />

iii


facilitating conditions to contain the negative feelings stirred up by the openness, complexity<br />

and uncertainty of collaboration.<br />

iv


TABLE OF CONTENTS<br />

DANKWOORD/ACKNOWLEDGMENTS........................................................................................................X<br />

INTRODUCTION............................................................................................................................................ XIV<br />

READING INSTRUCTIONS ......................................................................................................................... XVI<br />

PART 1: THEORETICAL FRAMEWORK ...................................................................................................... 1<br />

CHAPTER 1: MULTIPARTY COLLABORATION AS AN ORGANIZATIONAL STRATEGY............................................... 1<br />

1.1. Organizational context: societal and environmental 'meta-problems' ................................................... 1<br />

1.2. Definition and organizational features of multiparty collaboration....................................................... 2<br />

1.3. Challenges <strong>for</strong> direction setting: ’collaborative leadership’.................................................................. 4<br />

CHAPTER 2: THE SYSTEMS PSYCHODYNAMIC PERSPECTIVE .............................................................................. 15<br />

2.1. The field: origins and definition ........................................................................................................... 15<br />

2.2. Basic assumptions in this research....................................................................................................... 17<br />

2.3. A systems psychodynamic perspective on collaborative work: the challenges of direction setting...... 26<br />

2.4. Direction setting and the ambiguity of authority relations................................................................... 32<br />

CHAPTER 3: RESEARCH APPROACH ................................................................................................................... 35<br />

3.1. Interpretive inquiry: epistemological position ..................................................................................... 35<br />

3.2. An attitude of inquiry: the interpretive stance ...................................................................................... 38<br />

3.3. Subjectivity and inter-subjectivity as a source of data ......................................................................... 39<br />

3.4. Methodological approach..................................................................................................................... 41<br />

3.5. Relevance of this research.................................................................................................................... 49<br />

3.6. References............................................................................................................................................. 51<br />

PART 2: EMPIRICAL RESEARCH ................................................................................................................ 66<br />

CASE STUDY 1: EROSION CASE .......................................................................................................................... 66<br />

Context and antecedents of the erosion project........................................................................................... 66<br />

Main events in the erosion project............................................................................................................... 67<br />

Research approach...................................................................................................................................... 67<br />

Conclusion of the erosion case.................................................................................................................... 69<br />

For the reader ............................................................................................................................................. 70<br />

“WHO’S IN CHARGE HERE?!” EMOTIONAL CHALLENGES AND EMERGENT DYNAMICS IN INTERDEPENDENT WORK<br />

(ARTICLE 1)....................................................................................................................................................... 71<br />

Introduction................................................................................................................................................. 71<br />

Organizational frame: multiparty collaboration......................................................................................... 71<br />

Frame <strong>for</strong> analysis: the systems psychodynamic perspective...................................................................... 73<br />

Case: mud in the streets and water in the basement.................................................................................... 75<br />

Conclusion................................................................................................................................................... 99<br />

References ................................................................................................................................................. 101<br />

CASE 2: RIVER VALLEY CASE........................................................................................................................... 105<br />

v


Introduction............................................................................................................................................... 105<br />

Context and antecedents of the river valley project .................................................................................. 105<br />

Main events in the river valley project ...................................................................................................... 109<br />

Research approach.................................................................................................................................... 113<br />

For the reader ........................................................................................................................................... 122<br />

BOUNDARY DYNAMICS IN NATURAL RESOURCE MANAGEMENT: THE AMBIGUITY OF STAKEHOLDER INCLUSION<br />

(ARTICLE 2)..................................................................................................................................................... 124<br />

Introduction............................................................................................................................................... 124<br />

Theoretical framework .............................................................................................................................. 124<br />

The case: wet feet and dry marshes........................................................................................................... 130<br />

Conclusion................................................................................................................................................. 151<br />

References ................................................................................................................................................. 152<br />

PART 3: MAIN CASE STUDY ....................................................................................................................... 156<br />

INTRODUCTION CASE STUDY 3: FOSTER CARE.................................................................................................. 156<br />

CONTEXT AND ANTECEDENTS OF THE FOSTER CARE PROJECT ......................................................................... 157<br />

Socio-political context............................................................................................................................... 157<br />

Institutional context................................................................................................................................... 159<br />

Antecedents of the project.......................................................................................................................... 160<br />

Main events in the foster care project ....................................................................................................... 161<br />

Research approach.................................................................................................................................... 163<br />

REFERENCES ................................................................................................................................................... 178<br />

FOR THE READER............................................................................................................................................. 179<br />

THE PSYCHODYNAMIC PERSPECTIVE IN ORGANIZATIONAL RESEARCH: MAKING SENSE OF THE DYNAMICS OF<br />

DIRECTION SETTING IN EMERGENT COLLABORATIVE PROCESSES (ARTICLE 3)................................................. 180<br />

Introduction............................................................................................................................................... 180<br />

Collaborative work and the challenges of direction setting ...................................................................... 180<br />

The psychodynamic perspective in organizational research ..................................................................... 182<br />

‘Understanding’ dynamics ........................................................................................................................ 184<br />

The case: from competition to collaboration............................................................................................. 186<br />

Conclusion................................................................................................................................................. 204<br />

References ................................................................................................................................................. 206<br />

FROM COMPETITION TO COLLABORATION: DYNAMICS OF DIRECTION SETTING IN MULTIPARTY COLLABORATION<br />

(ARTICLE 4) .................................................................................................................................................... 212<br />

Introduction............................................................................................................................................... 212<br />

Conceptual background............................................................................................................................. 212<br />

The case: issues in direction setting .......................................................................................................... 215<br />

Some reflections......................................................................................................................................... 238<br />

Conclusions ............................................................................................................................................... 241<br />

References ................................................................................................................................................. 242<br />

vi


PART 4: A SYSTEM PSYCHODYNAMIC PERSPECTIVE ON DIRECTION SETTING IN<br />

COLLABORATIVE WORK ........................................................................................................................... 247<br />

1. CONTEXT AND STARTING CONDITIONS ........................................................................................................ 249<br />

1.1. Antecedents of the collaborative ef<strong>for</strong>t ............................................................................................... 250<br />

1.2. Characteristics of the domain............................................................................................................. 251<br />

1.3. Players in the context ......................................................................................................................... 252<br />

1.4. Events and changes in the environment.............................................................................................. 255<br />

1.5. Shared sense of urgency ..................................................................................................................... 257<br />

2. TASK AND COLLABORATIVE AIMS ............................................................................................................... 258<br />

2.1. The normative primary task................................................................................................................ 260<br />

2.2. The existential task ............................................................................................................................. 262<br />

2.3. The phenomenological task ................................................................................................................ 263<br />

3. STRUCTURING AND FORMALIZING OF THE PROCESS .................................................................................... 265<br />

3.1. Minimal structure ............................................................................................................................... 267<br />

3.2. Structuring of the domain: stakeholder analysis and stakeholder involvement.................................. 268<br />

3.3. Formal and in<strong>for</strong>mal roles ................................................................................................................. 270<br />

3.4. Formal and in<strong>for</strong>mal structures and interventions............................................................................. 277<br />

4. COLLABORATIVE RELATIONSHIPS, RELATEDNESS AND DYNAMICS.............................................................. 281<br />

4.1. Working with diversity........................................................................................................................ 282<br />

4.2. Mutual dependence and interdependence........................................................................................... 285<br />

4.3. The paradoxical nature of ‘collaboration’: collusive behavior.......................................................... 289<br />

NEW PERSPECTIVES ON DESIGNING AND FACILITATING EMERGENT ORGANIZATIONAL PROCESSES ................. 293<br />

Critical competencies <strong>for</strong> designing and leading emergent processes ...................................................... 295<br />

To conclude ............................................................................................................................................... 300<br />

REFERENCES ................................................................................................................................................... 301<br />

vii


ATTACHMENTS<br />

Attachment 1: COPP members involved in the different projects<br />

Attachment 2: Overview of the stakeholders interviewed in foster care<br />

Attachment 3: Presentation of analysis stakeholder interviews<br />

Attachment 4: Stakeholder analysis of the domain of foster care<br />

Attachment 5: Issues, questions and dilemmas based on the stakeholder interviews<br />

Attachment 6: Categories and subcategories of provisional data analysis<br />

Attachment 7: Process reconstruction foster care<br />

Attachment 8: Issues that emerged during the stakeholder conferences<br />

Attachment 9: Overview of ‘critical incidents’<br />

Attachment 10: Output of the research<br />

LIST OF TABLES<br />

Table 1: Overview of approach to data collection in the erosion case........................... 69<br />

Table 2: Overview of the phases, events and the main challenges in the erosion<br />

project...................................................................................................................................... 79<br />

Table 3: Overview of the organizations involved in the river valley cae.................... 107<br />

Table 4: Main events and issues in the river valley case. .............................................. 113<br />

Table 5: Organizational structure and participating organizations in the river valley<br />

case. ....................................................................................................................................... 115<br />

Table 6: Overview of the approach to data collection in the river valley case........... 118<br />

Table 7: Organizational structure of the river valley project. ....................................... 132<br />

Table 8: Differences between the two central groups in the coordination group (river<br />

valley case). .......................................................................................................................... 138<br />

Table 9: Overview of the phases and challenges in the foster care project................. 163<br />

Table 10: Overview of data collection in the foster care case........................................ 168<br />

Table 11: Membership of the project group and characteristics of the participating<br />

organizations........................................................................................................................ 188<br />

Table 12: Issues and sub-issues in direction setting. ...................................................... 249<br />

viii


LIST OF FIGURES<br />

Figure 1: Organizational structure of the erosion project................................................ 77<br />

Figure 2: A systems psychodynamic process model <strong>for</strong> direction setting in multiparty<br />

collaboration......................................................................................................................... 292<br />

ix


DANKWOORD/ACKNOWLEDGMENTS<br />

Dit onderzoek zou nooit gebeurd zijn zonder een ‘toevallige’ ontmoeting met<br />

professor Leo Lagrou in de wandelgangen van het psychologisch instituut. Hij<br />

herinnerde zich mijn licentiaatthesis en moedigde mij aan om eens contact op te<br />

nemen met het COPP. Niet lang daarna begon ik aan mijn assistentschap en aan de<br />

turbulente reis waarvan u het product nu in handen heeft.<br />

Er zijn heel wat mensen die hebben bijgedragen aan dit werk en die ik hiervoor<br />

oprecht wil danken. Uiteraard allereerst veel dank aan mijn promotor, professor<br />

Tharsi Taillieu, die vanaf het begin geloofde in mijn werk. Zijn encyclopedische<br />

kennis van het domein zorgde ervoor dat ik mijn weg vond in oude en nieuwe<br />

theorieën die relevant waren voor dit onderzoek. Bedankt voor de vrijheid en de<br />

ondersteuning op momenten dat ik die het meest nodig had.<br />

Graag wil ik de commissieleden danken voor het vertrouwen dat zij schonken aan<br />

dit project: Jos Corveleyn, Bert Overlaet, Norbert Van Beselaer, Danny Wildemeersch<br />

Johan Hovelynck en René Bouwen. Ook dank aan Sandra Schruijer voor haar<br />

constructieve feedback op mijn doctoraatsvoorstel. De juryleden wil ik danken voor<br />

hun bereidheid en tijd om dit werk te lezen en hun vragen en bedenkingen te<br />

<strong>for</strong>muleren: de professoren Sandra Schruijer, Jos Corveleyn, Danny Wildemeersch en<br />

René Bouwen.<br />

Dit onderzoek is gebaseerd op samenwerking in concrete projecten. Dank aan de<br />

talloze mensen die mij en mijn collega’s toegang gaven in hun projecten en tijd<br />

vrijmaakten voor interviews en besprekingen. Omdat de gevalsstudies anoniem zijn<br />

gemaakt in dit werk, zal ik ook hier de namen niet noemen. De betrokkenen weten<br />

wel over wie ik het heb! Allereerst bedank ik de mensen van het erosieproject, een<br />

moeizame maar leerzaam proces om expertkennis aan de kennis van mensen op het<br />

terrein te koppelen. Ook dank aan de initiatiefnemers en voortrekkers van het<br />

rivierbekken project voor hun bereidheid ons deelgenoot te laten zijn van hun<br />

x


zoektocht naar zinvolle manieren van participeren in een maatschappelijk belangrijk<br />

project. Dank aan de leden van het pleegzorgproject voor het enthousiasme waarmee<br />

ze samen met ons op zoek gingen naar een toekomstscenario voor structurele<br />

samenwerking. De tientallen ‘stakeholder’ vertegenwoordigers die ik mocht<br />

interviewen in de verschillende projecten ben ik ook dank verschuldigd.<br />

Ook mijn collega’s van het COPP ben ik erkentelijk voor de leerrijke en plezierige<br />

samenwerking in de projecten. Tharsi Taillieu voor het openen van deuren en de<br />

feedback op mijn artikels over de ‘cases’. René Bouwen voor de inspirerende<br />

reflecties op onze ervaringen in het ‘veld’. Marc Craps voor de fijne samenwerking,<br />

de collegiale vriendschap en de talloze gesprekken en uitwisselingen. Johan<br />

Hovelynck, mijn sympathieke bureaugenoot, voor de humor, de goede gesprekken<br />

en de kritische zin. Karel De Witte voor het delen van zijn ervaring. Edward Van<br />

Rossen voor de korte, maar aangename samenwerking. En dank aan Maarten<br />

Andriessen voor de onvergetelijke ‘interviewmarathon’ doorheen het Vlaamse land<br />

en de vele uren dat we samen worstelden met de analyses van de resultaten. Ook<br />

dank aan de andere collega’s van het COPP voor hun collegialiteit: Art, Jacqueline,<br />

Miriam, Karin, Eva, Greet, en Thomas.<br />

De discussies met Stephanie, Greet, Liesbeth, Ann, Julie, Sophie, en Elisabeth,<br />

thesisstudenten die worstelden met de theorie en praktijk van multipartij<br />

samenwerking, waren ook stimulerend voor mijn werk.<br />

Thanks to the members of the International Society <strong>for</strong> the Psychoanalytic Study of<br />

Organizations (ISPSO) who warmly welcomed me in their midst and made me feel<br />

‘at home’. Their writings, generous feedback and encouragement have been<br />

extremely inspiring and helpful <strong>for</strong> my work. Thanks to Stephanie Wilke, Rose<br />

Mersky, Burkhard Sievers, Erika Stern, Carolyn Cooper, Ellen Ramvi, Brigid Nosal,<br />

Janet Fitzell, Lilian Hupkens, Larry Gould, Jim Krantz, Larry Hirschhorn, Karen<br />

Poulenc, Michael Diamond, Lionel Stapley, Susan Long, Derek Raffaeli, Yiannis<br />

Gabriel, Laura Crawshaw, and many others. I’m also grateful to Susan Schneider, <strong>for</strong><br />

xi


teaching me how to write up a case study and <strong>for</strong> her interesting feedback on one of<br />

the papers.<br />

Samen met mijn intervisie-collega’s van het International Professional Development<br />

Programme (Prodev), Joëlle, Mark, Bart, Stef, Jan en Hans, zochten we naar manieren<br />

om te werken met het systeem psychodynamisch kader in groepen en organisaties.<br />

Bedankt voor de inspirerende sessies. Ook dank aan de staf van de IPDP opleiding:<br />

Marie-Jeanne Vansina-Cobbaert, Sandra Schruijer, en Helgi Rasmussen. Mijn speciale<br />

dank gaat uit naar Leopold Vansina. Zijn werk is steeds een grote bron van inspiratie<br />

geweest voor mij. Ik heb veel geleerd van zijn erudiete kennis, kritische zin en<br />

feedback op mijn teksten.<br />

Ook dank aan de collega’s van de seminariegroep ‘psychoanalyse en leiderschap’:<br />

Anita Wydoodt, Frieda Verbist, Johan De Groef, Johan Taghon, Johan Vereycken en<br />

Bernadette Bertin. Samen bestudeerden we de ideeën van Anzieu, Enriques,<br />

Hirschhorn en Menzies. Onze maandenlange worsteling met het werk van Bion zal<br />

ik niet snel vergeten.<br />

Thanks to Klaus Elle <strong>for</strong> graciously letting me use his artwork <strong>for</strong> the cover of this<br />

book: ‘I am, because we are’. For me, this image is a visual representation of the<br />

philosophy and hope expressed in this work.<br />

Dank aan mijn lieve vrienden en vriendinnen die jarenlang geïnteresseerd bleven<br />

in<strong>for</strong>meren: “En? Hoe staat het met je doctoraat?” Dat deed me altijd oprecht deugd,<br />

zeker in momenten, dat het moeilijk was. Ik noem er een paar en vergeet er zeker een<br />

heleboel: Karin, Jan, Anneke, Hans, Karen, Katrien, Laura, Cécile, Kaya, Marc,<br />

Benedicte, Frieda, Anouk, Jo, Welmoet, Wivina, Lieve, Sonja, Carla, Veerle, …<br />

I am very grateful to Bettina Hausschild who helped me keep a healthy balance<br />

between my work life and personal life. A special word of thanks to my friend Dan<br />

Frank, who helped me believe in my own voice.<br />

xii


Heel veel dank aan mijn ouders en zus Saskia voor de onvoorwaardelijke steun,<br />

praktische hulp en hun geloof in mij.<br />

Dank aan Luc om me steunen bij de start van dit onderzoek en om er te zijn voor de<br />

kinderen wanneer dat nodig was.<br />

Ik draag dit boek op aan mijn lieve kinderen Caspar, Clara en Felix. Zij hebben alle<br />

turbulenties van deze reis van dichtbij meegemaakt zonder goed te beseffen waar het<br />

allemaal om ging. Ik hoop van harte dat ze zullen leven en werken in een<br />

samenleving waar mensen beter gewapend zijn om over organisatiegrenzen heen<br />

samen te werken, zodat we van deze aarde een betere plek kunnen maken.<br />

Leuven, 13 februari 2006<br />

xiii


INTRODUCTION<br />

This work on multiparty collaboration is part of ongoing research at the Center <strong>for</strong><br />

Organizational and Personnel Psychology. My colleague Marc Craps has written a<br />

study on the inclusion of local communities. Art Dewulf studied issue framing in<br />

multi-actor contexts. My specific interest was in how representatives who make up a<br />

collaborative, make progress on their self-designed task when t<strong>here</strong> is no <strong>for</strong>mal,<br />

hierarchical leader to guide them. By using a different and complementary<br />

perspective, my aim is to contribute to a better understanding of the specific nature<br />

of multi-stakeholder processes.<br />

Multiparty collaboration is a strategy to develop sustainable solutions <strong>for</strong> pressing<br />

and important environmental problems and societal issues that one organization<br />

cannot solve alone. Over the years I came to the conclusion that multiparty<br />

collaboration is an ideal. Conveners, facilitators and participants need to establish the<br />

most appropriate way of organizing ‘their’ process, taking into account the<br />

opportunities and restrictions in the domain. Multiparty collaboration, as an<br />

organizational paradigm, can be used as a ‘model’. However, old paradigms and<br />

scripts still govern our assumptions and behavior, in the field as well as in<br />

academics.<br />

This research reflects my search <strong>for</strong> an integration of clinical and organizational<br />

psychology. I have often been puzzled by ‘irrational’ and unexpected behavior in<br />

people, groups and organizations. The traditional management literature and<br />

organizational theories, based on rational assumptions and an instrumental<br />

approach, could not account <strong>for</strong> the phenomena I encountered. In this literature little<br />

attention is given to the individual as a ‘human being’ in organizational life. The<br />

individual is regarded as a 'resource' in a global and economically determined<br />

context. According to Leopold Vansina (1998) one of the reasons <strong>for</strong> this evolution is<br />

the split between organizational and clinical psychology. When I discovered the<br />

‘systems psychodynamics perspective’ on working and organizing, I found an<br />

integrated frame to help me understand what happens in organizations. My research<br />

xiv


is inspired by the seminal work of action researchers associated with the Tavistock<br />

Institute of Human Relations, and by contemporary work of members of the<br />

International Society <strong>for</strong> the Psychoanalytic Study of Organizations (ISPSO), such as<br />

Larry Hirschhorn, Jim Krantz, Larry Gould, Susan Long, Gilles Amado and Leopold<br />

Vansina. Un<strong>for</strong>tunately, I did not have the opportunity, so far, to thoroughly study<br />

the French tradition of ‘psychosociologie’, which has its particular vision on<br />

organizational life.<br />

My motivation to undertake this research was to understand how people cope with<br />

the challenges, increasing uncertainties and emergent nature of today’s<br />

organizational life. The broader issue in this research is how organizational<br />

psychology in general, and organizational design in particular, can respond to the<br />

new challenges and realities in today’s organizational world. T<strong>here</strong> is a genuine<br />

demand in the field <strong>for</strong> new, adapted models and interventions to support<br />

interdependent work across organizational boundaries.<br />

xv


READING INSTRUCTIONS<br />

This book is built around four articles that make up its essence. T<strong>here</strong> are five parts<br />

in this work, which I will briefly introduce.<br />

In part one I present an overview of the theoretical foundations of my research. It<br />

<strong>for</strong>ms the basis <strong>for</strong> understanding the articles and the way in which I have carried<br />

out this research. In chapter one I outline the theoretical insights that are relevant to<br />

understand multiparty collaboration as an organizational strategy. I focus on<br />

different views on ‘collaborative leadership’ and argue how I define this<br />

phenomenon in my research. The second chapter introduces the system<br />

psychodynamic perspective on working and organizing, which is the organizing<br />

principle in this research. I discuss the origins, main theories, and assumptions that<br />

inspired my research. Then I present the specific challenges <strong>for</strong> designing, leading<br />

and facilitating collaborative work from this perspective. In the third chapter, I<br />

discuss my research approach, the epistemological position I take as researcher, the<br />

methodological choices I have made and how this established the way in which this<br />

research was carried out. Finally, I conclude with the theoretical relevance of this<br />

research.<br />

In part two, I discuss two case studies. The first is a pilot case in the domain of<br />

erosion management, which I worked out to fine-tune the subject of my research. The<br />

first article is preceded by an introduction w<strong>here</strong> I present the context and<br />

antecedents of the project, and the approach to data collection and analysis. The same<br />

structure was used <strong>for</strong> the introduction of the second article, which is based on a case<br />

study in the domain of river basin management. Both case studies were written up as<br />

an article and submitted <strong>for</strong> publication (see attachment 10).<br />

Part three is dedicated to the main case of this research, a project in foster care. The<br />

two articles, based on this case, are extensively introduced. Because of the restrictions<br />

xvi


of journal articles, I have discussed the issues that emerged in the case analysis in<br />

two articles. The issues were grouped in a co<strong>here</strong>nt whole. Inevitably, t<strong>here</strong> is<br />

overlap <strong>for</strong> the reader between the introduction to the case and the theoretical and<br />

methodological paragraphs of both articles. Extensive case material is available in the<br />

attachments.<br />

In part four, I compare the findings of the three cases in order to draw conclusions<br />

<strong>for</strong> this research. I present the issues that influenced direction setting in collaborative<br />

work in a structured way. Each issue is divided in sub-issues and illustrated with<br />

case material. I conclude with some implications <strong>for</strong> the theory and practice of<br />

organizational design in new, emergent organizing processes.<br />

In the attachments, I present case material to support the main case. These include:<br />

background in<strong>for</strong>mation, in<strong>for</strong>mation on the research approach, a process overview,<br />

and intermediate steps in the data analysis. This may help the reader to make his or<br />

her own sense of the issues and dynamics in the foster care case. In the attachments,<br />

the reader also finds further in<strong>for</strong>mation on the background of the four articles and<br />

other output of this research.<br />

A research account based on four separate articles inevitably results in overlap <strong>for</strong><br />

the reader of this ‘book’. The parts were written at different moments in the research<br />

process (1999-2006). I have maintained the articles as they have been submitted or<br />

published. The differents parts are linked by introductory texts. Hopefully this will<br />

help you to follow the evolution of the core arguments and approach of the subject<br />

throughout this work.<br />

xvii


PART 1: THEORETICAL FRAMEWORK<br />

CHAPTER 1: MULTIPARTY COLLABORATION AS AN ORGANIZATIONAL<br />

STRATEGY<br />

1.1. Organizational context: societal and environmental 'metaproblems'<br />

A central characteristic of the present world of working and organizing is an<br />

increasing interdependency, diversity and requirement <strong>for</strong> collaboration across<br />

organizational boundaries. In this so-called ‘connective era’ t<strong>here</strong> is a need <strong>for</strong> more<br />

sophisticated <strong>for</strong>ms of collaboration drawing on new competencies because of the<br />

nature of the problems our society is facing (Chisholm, 1998; Lipman-Blumen, 1996).<br />

Business opportunities and challenges <strong>for</strong> creative innovation can inspire inter-<br />

organizational collaboration. This research, however, focuses on collaboration as a<br />

strategy to deal with societal and environmental 'meta-problems'. “Since<br />

problématiques, meta-problems, or messes - rather than discrete problems - are what societies<br />

currently have to face up to, the cultivation of domain-based, inter-organizational competence<br />

has become a necessary societal project” (Trist, 1983, 270). Solving these large-scale<br />

problems or 'messes' requires multidisciplinary and multi-organizational<br />

involvement (Chisholm & Elden, 1993; Ackoff, 1997). In dealing with the important<br />

public issues and problems that threaten us all, no organization has the legitimacy,<br />

power, authority or intelligence to act alone. No one is ‘in charge’ (Bryson & Crosby,<br />

1992). We can only survive if we change our competitive attitude into an attitude of<br />

collaboration accepting mutual dependency (Trist, 1983). Inter-organizational<br />

collaboration can be considered as an adaptive response to the 'turbulent fields' with<br />

which organizations are confronted, because it recognizes and deals with member<br />

1


interdependencies and acknowledges the futility of competitive strategies (Emery &<br />

Trist, 1997; McCann & Selsky, 1997).<br />

Gilmore (1997) also argues that we can no longer rely on existing organizational<br />

solutions and ways of working to face the societal and business problems of today.<br />

We are in transition from hierarchical <strong>for</strong>ms to ‘loosely coupled organizations’ in<br />

which the relationship among the parties is negotiated rather than predetermined.<br />

We have to learn to develop ‘emerging’ structures and processes, coupling several<br />

organizations. These ‘loosely coupled systems’ are characterized by ambiguous<br />

membership boundaries, unclear values and norms, role ambiguity, unclear<br />

purposes or goals, and absence of <strong>for</strong>mal systems and procedures (Chisholm &<br />

Elden, 1993). A critical challenge is to create participative environments w<strong>here</strong> all<br />

parties feel responsible and jointly take up ownership <strong>for</strong> the collective output. This<br />

requires people to establish relationships, think together, be curious together and<br />

connect their ideas in defining a shared objective (Krantz, 1998). This is an ideological<br />

perspective, reflecting a 'normative re-educative' strategy of change which might not<br />

always be the most appropriate way of dealing with a task (Gray, 1989). In the<br />

following paragraph I define multiparty collaboration and introduce its main<br />

features.<br />

1.2. Definition and organizational features of multiparty<br />

collaboration<br />

A general definition of ‘collaboration’ is one <strong>for</strong>warded by Chrislip and Larson (1994,<br />

5): “It is a mutually beneficial relationship between two or more parties who work toward<br />

common goals by sharing responsibility, authority, and accountability <strong>for</strong> achieving results.<br />

Collaboration is more than simply sharing knowledge and in<strong>for</strong>mation (communication) and<br />

more than a relationship that helps each party achieve its own goals (cooperation and<br />

coordination). The purpose of collaboration is to create a shared vision and joint strategies to<br />

address concerns that go beyond the purview of any particular party”. In collaborative<br />

work people sit around the table to work across organizational boundaries towards<br />

some positive end (Huxham & Vangen, 2005). Multiparty collaboration is one step<br />

2


eyond inter-disciplinary work; it is a <strong>for</strong>m of trans-organizational collaboration<br />

(Cummings & Worley, 2001).<br />

My research is inspired by the work of Barbara Gray and Chris Huxham, because<br />

they focus on the ‘process’ of collaborating. Gray (1989: 5) defines multiparty<br />

collaboration as “(…) a process through which parties who see different aspects of a problem<br />

can constructively explore their differences and search <strong>for</strong> solutions that go beyond their own<br />

limited vision of what is possible”. It involves a process of collective decision making<br />

and negotiation among key stakeholders of a problem domain, focused on the future<br />

development of that particular domain. Collaborative processes demonstrate five<br />

characteristics: (1) the stakeholders are interdependent; (2) solutions emerge by<br />

dealing constructively with differences; (3) the stakeholders take decisions in joint<br />

ownership; (4) stakeholders assume collective responsibility <strong>for</strong> the future direction<br />

of the domain; and (5) collaboration is an ‘emergent’ process (Gray, 1989). The<br />

underlying assumption of this organizational strategy is that it is critical to include<br />

stakeholders who are affected by the issue, those who are needed to address the<br />

issue, and those who have the power to support or block collaborative action<br />

(Chrislip & Larson, 1994). In their definition, Vansina and his colleagues (Vansina,<br />

Taillieu & Schruijer, 1998, 4) emphasize the inter-group characteristics of the parties<br />

and the self-defining nature of such systems. “(…) an emerging or developing<br />

worksystem of people who, because of their membership in other groups, institutions or social<br />

categories, come to work together on a largely self-constructed task or problem domain”.<br />

A classical function of organizing is to reduce complexity and uncertainty to<br />

manageable proportions. Collaborative <strong>for</strong>ms, however, are likely to increase the<br />

degree of turbulence (Wood & Gray, 1991). Collaboration between more than two<br />

organizations or social groups confronts the participants with particular challenges.<br />

Participants have to deal with more turbulent dynamics, unstable group<br />

identification, large differences in social identity, the difficulty to establish trust, and<br />

a bigger complexity regarding in<strong>for</strong>mation, social processes, procedures and<br />

strategy, inter-group phenomena (Kramer, 1991; Vansina, Taillieu & Schruijer, 1998).<br />

3


A higher number of parties increases the amount of values, interests and perceptions<br />

to be integrated and accommodated, and it increases uncertainty concerning the<br />

motives and interests of others, and the perception of one’s own utility. On the other<br />

hand, more participants represent more resources to work on solutions (Midgaard &<br />

Underdal, 1977). Other potential features are an unclear and shifting purpose,<br />

ambiguous values or norms, absence of <strong>for</strong>mal systems or procedures, ambiguity of<br />

role, membership, status and representativeness, complexity in structure, shifting<br />

membership, coalition <strong>for</strong>mations and shifting alliances (Chisholm & Elden, 1993;<br />

Huxham & Vangen, 2000b). Exploring the nature of a collaborative process and<br />

understanding how participants respond to the challenges it poses is at the heart of<br />

this research.<br />

A particular challenge in multiparty collaboration is how leadership is ‘translated’ in<br />

such horizontal organizational contexts. A number of questions have triggered this<br />

research. How do ‘equal’ parties make sense of leadership when t<strong>here</strong> is no identified<br />

leader? How do they enact leadership when authority relations are ambiguous? How<br />

do they deal with the different leadership functions that have to be taken up? Is it<br />

possible to share leadership functions? How do the parties balance attempts at<br />

influencing the outcome and direction of the process? In the following section, I<br />

describe the specific nature of leadership in a collaborative setting, I briefly discuss<br />

some perspectives on collaborative leadership from the literature, and I conclude<br />

with the conception I hold of ‘collaborative leadership’ in this research.<br />

1.3. Challenges <strong>for</strong> direction setting: ’collaborative leadership’<br />

1.3.1. The nature of collaborative leadership<br />

Collaborative leadership has not been researched very often: “(…) it almost seems that<br />

the in<strong>here</strong>ntly consensual nature of collaborative partnership working inhibit the emergence<br />

of explicit or overt leadership, and research so far has largely ignored this topic” (Razzaque<br />

& Stewart, 1998, 2). However, a critical aspect of multiparty collaboration is how to<br />

facilitate productive work. A particular challenge is how leadership is defined and<br />

4


enacted in a <strong>for</strong>m of organizing w<strong>here</strong> hierarchy is no longer a valid organizing<br />

principle. The challenge is how to manage inter-organizational dynamics and the<br />

relations between internal and external stakeholder groups (Stokes, 1998). Those<br />

taking up leading functions have to learn how to design and facilitate collaborative<br />

processes w<strong>here</strong> different parties are brought together and collectively create fresh<br />

maps of a new, emerging terrain (Gilmore, 1997).<br />

‘Leadership’ in a collaborative context is a problematic notion. Traditional models of<br />

leadership are not suitable in collaborative settings. The specific nature of<br />

‘leadership’ in multiparty collaboration can be summarized as follows (Schuman,<br />

1996; Razzaque & Stewart, 1998; Huxham & Vangen, 2000a; 2005):<br />

- The existing leadership literature presumes t<strong>here</strong> is a <strong>for</strong>mal leader with<br />

managerial responsibility functioning in a hierarchical relationship with<br />

followers. However, in collaborative work no person, organization or social<br />

group has the authority to take decisions that influence the future of the<br />

problem domain.<br />

- Leadership models presume a clearly specified and accepted goal, w<strong>here</strong><br />

literature demonstrates that precisely agreeing upon collaborative goals is a<br />

critical and difficult task.<br />

- Leading a collaborative means influencing or trans<strong>for</strong>ming organizations and<br />

not individuals.<br />

- T<strong>here</strong> is not always an identified ‘leader’; authority relations are usually<br />

ambiguous. Moreover, membership of a collaborative is often unclear and<br />

shifting.<br />

- Often representatives with a stake in the domain take up leadership functions.<br />

They are wearing ‘multiple hats’ and have to be able to switch roles effectively<br />

in order to preserve the integrity of the process. This can make it hard <strong>for</strong><br />

them to be perceived as ‘neutral’ and impartial facilitators or conveners.<br />

- The consensual nature of collaborative work, stressing empowerment,<br />

ownership and joint decision making, is likely to inhibit the emergence of<br />

overt leadership. Explicit leadership may lead to exclusion of the process<br />

5


ecause it may be perceived as a one sided attempt of one party to push its<br />

agenda.<br />

Collaborative work takes place in groups such as project groups, steering groups,<br />

stakeholder meetings, and work groups. The dynamics in this study refer to three<br />

group processes: operational processes (how the group does its work),<br />

developmental processes (how the group as an entity changes over time), and<br />

adaptive processes (how the group reacts to events) (McGrath & Tschan, 2004). The<br />

leadership function supports these three processes that operate simultaneously.<br />

Bouwen and Taillieu (2004) distinguish two leadership functions. A first function is<br />

task and strategic leadership. It consists of convening, setting the agenda, organizing,<br />

and chairing meetings. It is about the day to day coordination of a collaborative<br />

process, focusing on content or task elements. They have identified the following<br />

problem-solving or task related activities: sharing perspectives on issues; defining<br />

common issues and identifying resources; generating and sharing in<strong>for</strong>mation;<br />

exploring optional alternatives; selecting an intervention strategy; planning concrete<br />

action steps; implementing in the field; and evaluating outcomes. Task leadership<br />

helps a group or system to work on the task. This refers to the operational processes<br />

in a group (McGrath & Tschan, 2004).<br />

A second leadership function is process leadership, which is often the focus of social<br />

scientists. Bouwen and Taillieu (2004) distinguish the following relational activities<br />

that shape the problem solving process. Getting attention and awareness of<br />

stakeholders; mobilizing actors to arrive at commitment to collaborate ; legitimating<br />

stakeholders and conveners; dialoguing to explore diversity; connecting stakes and<br />

interests; negotiating roles and identities; guaranteeing commitment of<br />

constituencies ; and aligning ef<strong>for</strong>ts and agreements. Leadership of the process is<br />

about creating conditions to get the most out of the diversity of perceptions,<br />

competencies and resources, while ensuring that each stakeholder can realize his<br />

objectives (Vansina, 1999). It is a stand-back role, attentive <strong>for</strong> the expression of<br />

needs, anxieties, and obstacles to collaboration. This role requires insight in agenda<br />

6


setting to initiate and stimulate the collaboration, and insight in group dynamics.<br />

Neutrality and impartiality are important aspects of the role. The leading role should<br />

provide the conditions under which the stakeholders can take up their responsibility<br />

in defining and solving the problem (Vansina, 1999; Taillieu, Schruijer & Vansina,<br />

2000). Key issues in taking a leading role are to invest energy: “(a) in raising the<br />

importance of the collaborative task-system to counterbalance the pull towards the respective<br />

parties; and (b) in trust-building by creating a minimal structure of ground rules” (Vansina,<br />

1999, 52). It is important to facilitate direct interaction, to deal with frustration, and to<br />

foster group development. According to Schruijer and her colleagues, the leadership<br />

function crystallizes around “(a) creating conditions to enable the collaborative task-system<br />

to go on with the work, rather than taking responsibility <strong>for</strong> finding an acceptable solution;<br />

and (b) the capacity to ‘contain’ the messiness, divergence and ambiguity in the task-system<br />

and to create ‘space’ to enable the stakeholders to discover areas w<strong>here</strong> they can find one<br />

another” (Schruijer, Taillieu & Vansina, 1998, 2). Process leadership supports the<br />

group in its developmental process (McGrath & Tschan, 2004).<br />

Chrislip and Larson (1994) found that strong 'process leadership' is a critical<br />

condition <strong>for</strong> the success of collaborations (e.g. keeping stakeholders at the table<br />

through periods of frustration and skepticism). The primary focus of process<br />

leadership is how people work together and not the content of the collaboration. The<br />

collaborative process is a self-reflective, emerging process that must be constantly<br />

nurtured. T<strong>here</strong><strong>for</strong>e “(…) it needs leaders who can safeguard the process, facilitate<br />

interaction, and patiently deal with high levels of frustration. Collaboration works when t<strong>here</strong><br />

are a few key leaders, either in <strong>for</strong>mal or in in<strong>for</strong>mal roles, who keep the process going”<br />

(Chrislip & Larson, 1994, 97). For instance, the leader has to be able to voice the<br />

feelings of ambiguity and discom<strong>for</strong>t that are often brought about by the situation<br />

(Roose, Taillieu & Sips, 2000). The main conclusion of Chrislip and Larson is the<br />

inability of people to work together constructively.<br />

According to Huxham and Vangen (2003), however, leading in a facilitative manner<br />

from the spirit of collaboration is necessary but not sufficient to generate<br />

7


collaborative advantage. Their research demonstrates that the right balance between<br />

facilitative leadership activities (embracing, empowering, involving, and mobilizing<br />

members) and pragmatic leadership activities towards collaborative ‘thuggery’<br />

(manipulating the collaborative agenda, playing politics) help to make progress. The<br />

literature hardly addresses leadership supporting ‘adaptive processes’ and focusing<br />

on the interchange between the collaborative group and the environment in which it<br />

is embedded.<br />

Since no single person or organization has the <strong>for</strong>mal authority to take decisions on<br />

behalf of the inter-organizational domain, these leadership functions need to be<br />

distributed, shared or outsourced. The participants in the process can share<br />

leadership functions, take turns, switch roles, split task leadership and process<br />

facilitation or delegate leadership or part of the leadership functions by bringing in<br />

an outside facilitator, such as a mediator or third party (Schuman, 1996). The next<br />

paragraph gives a brief overview of the literature on collaborative leadership.<br />

1.3.2. Collaborative leadership in the literature<br />

Some authors in the domain of multiparty collaboration focus on the collaborative<br />

‘leader’. Lipman-Blumen’s (1996) concept of ‘connective leadership’ stresses the<br />

psychological factors of effective leadership in an interdependent world. Bilimoria,<br />

Wilmot and Cooperrider (1996) focus on the tasks the leader needs to per<strong>for</strong>m:<br />

managing vision, trust, reciprocity, identity, and meaning. Midgaard and Underdal<br />

(1977) argue that the complexity of the process requires a chairman or leader to<br />

conduct orderly and efficient interactions. Often, however, t<strong>here</strong> is no single leader.<br />

The multiparty literature has mainly focused on the role of the ‘convener’ (Wood &<br />

Gray, 1991; Gray, 1985; Gray, 1996; Razzaque & Stewart, 1998). Wood and Gray<br />

(1991) stress the role of the convener, the organization(s) or person(s) that identify<br />

relevant stakeholders and bring them around the table to work on an issue that<br />

concerns them all. A convener can be a natural authority, a stakeholder or a third<br />

8


party (Gray, 1985). The literature does not provide much clarity on the specific<br />

meaning of and relationship between convening and leading. Gray (1989) also<br />

describes other leadership roles, such as mediator or facilitator. Razzaque and<br />

Stewart (1998) identified eight leadership roles: champion, salesperson, interpreter,<br />

broker, co-ordinator, visionary, representative, agent provocateur. Himmelman<br />

(1996) describes collaborative roles that can be taken up by the participating<br />

organizations to contribute to the collaboration (e.g. catalyst, community organizer,<br />

facilitator).<br />

Schuman (1996) stresses the importance of ‘process’ in collaboration, as process<br />

issues “(…) are the means by which problems get solved and decisions made”. He<br />

distinguishes social, cognitive and political processes. He does not, however, link<br />

these processes to the issue of leadership. Hardy and Phillips (1998) focus on power<br />

dynamics, or how stakeholders use their power and how this affects interactions<br />

between them and other organizations in the domain. This perspective provides<br />

insight in the underlying power relations in collaborative work.<br />

In the multiparty literature empowerment, participation, and collective decision<br />

making are highly valued. Many authors refer to some shared <strong>for</strong>m of leadership.<br />

These include: ‘shared leadership’ (Chrislip & Larson, 1994; Yukl, 1999), ‘shared<br />

power’ (Bass, 1990; Bryson & Crosby, 1992), ‘leadership from a shared power base’<br />

(Vansina, 2002), 'dispersed leadership' (Bryman, 1996), ‘joint ownership’ (Gray, 1989),<br />

‘leadership as a network of influence’ (Feyerherm, 1994), ‘overall system leadership’<br />

(Krantz, 1990) and 'distributed leadership' (Gibb, 1969; Brown & Hosking, 1986;<br />

Miller, 1998; Gronn, 2002; Huffington, James & Armstrong, 2004). This perspective on<br />

collaborative leadership stresses the importance of leadership in terms of actions and<br />

processes (Bryman, 1996). It does not focus on the person of the leader, but on the<br />

critical contribution of the participants. The participants need to share responsibility<br />

<strong>for</strong> the process as well as <strong>for</strong> the outcome (Carlisle & Leary, 1981). The more they are<br />

able to share leadership, the more successful and sustainable the collaborative ef<strong>for</strong>t<br />

is expected to be. Taillieu and his colleagues (Schruijer, Taillieu & Vansina, 1998;<br />

9


Taillieu, Schruijer & Vansina, 2000), <strong>for</strong> instance, stress that inducing shared<br />

responsibility in collaborative work is a critical function of leadership. This<br />

perspective accentuates mature and interdependent relationships as a condition <strong>for</strong><br />

sharing leadership functions.<br />

The concept of 'distributed leadership' is not new. Gibb (1954) introduced the notion<br />

of distributed leadership more than fifty years ago. He conceived distributed<br />

leadership as 'leadership acts' or as 'a set of functions' which the group must carry<br />

out (Gibb, 1969). Distributed leadership refers to the way in which influence is<br />

distributed over the parties in an emergent inter-organizational system. This<br />

perspective on leadership stresses the complexity of leadership processes. The level<br />

of conceptualization shifts from the dyadic relationship (leader and follower) to the<br />

group or system perspective. Leadership as a group phenomenon is not a new<br />

insight. In the traditional group dynamic literature leadership functions are defined<br />

as actions per<strong>for</strong>med by group members. These actions are aimed at setting group<br />

goals, moving the group towards its goals, improving the quality of interactions<br />

among the members, building cohesiveness, or making resources available to the<br />

group (e.g. Cartwright & Zander, 1960). Leadership as a shared group function refers<br />

to the level of maturity in the group. Mature groups have outgrown dependent and<br />

counter-dependent relationships with authority figures. In collaborative work,<br />

however, the ‘group’ cannot develop by working through its conflict with the leader,<br />

because t<strong>here</strong> is no clear person or organization that embodies authority. This is a<br />

new challenge. When members are able to share leadership functions they can work<br />

in an interdependent way (Bennis & Shepard, 1956).<br />

To conclude this brief overview: “The notion of collaborative leadership is, however, still<br />

ambiguous, not well defined and described from different perspectives.” (Schruijer, Taillieu<br />

& Vansina, 1998, 7). This research is an attempt to further develop the notion of<br />

collaborative leadership, based on empirical data.<br />

10


1.3.3. Collaborative leadership: sources of inspiration<br />

My interest in leadership is inspired by some researchers in the domain of multiparty<br />

collaboration. Huxham and Vangen (2000a, 1165) define leadership in multiparty<br />

collaboration as “(…) the mechanisms that make ‘things happen’ in a collaboration. (…) the<br />

mechanisms that lead a collaboration’s policy and activity agenda in one direction rather than<br />

another”. They developed a holistic view on leadership in collaboration by taking the<br />

notion of leadership beyond the individual and the organization. Two elements<br />

influence the way in which collaborative agendas are shaped and enacted. The first is<br />

‘leadership media' (structure, processes, and participants). As the members often do<br />

not control these media, one can consider them as providing ‘contextual leadership’.<br />

The second element is ‘leadership activities’, or those activities carried out by the<br />

stakeholders to establish the agenda and drive it <strong>for</strong>ward. This includes controlling<br />

the agenda and mobilizing member organizations (Huxham & Vangen, 2000a).<br />

Huxham and Vangen have broadened the concept of leadership to leadership<br />

emanating from different sources, both from the stakeholders or participants and<br />

from the context. Their central question was: what is it that participants do in order<br />

to cope with, or build on, the constraints and possibilities dictated by structures,<br />

processes, or other participants? A ‘leader’ in this perspective, is any individual who<br />

tries to influence the direction or output of the collaboration. They focus on<br />

leadership as a process of influence and as it is enacted by participants (Huxham &<br />

Vangen, 2005). “Once we begin to understand leadership media and activities <strong>here</strong> as a<br />

collective framework responsible <strong>for</strong> ‘leading’ the system then the balance of ownership and<br />

responsibility is brought closer to the ‘individual players’” (Mac Rae & Huxham, 2000, 21).<br />

Huxham, a senior lecturer in the field of management science, observed the effects of<br />

external elements on the collaborative process. In her perspective these context<br />

elements also provide 'leadership'. From a psychological perspective, however, the<br />

effects only occur because people give meaning to events and external elements (e.g.<br />

a deadline). I consider these external elements to be 'triggers' that generate meaning<br />

and provoke responses: it is the people who are capable of generating and expressing<br />

'leadership'. This view on leadership joins the classic definition by Katz and Kahn<br />

(1978) who argue that human beings provide leadership: "(…) we consider the essence<br />

11


of organizational leadership to be the influential increment over and above mechanical<br />

compliance with the routine directives of the organization. Such an influential increment<br />

derives from the fact that human beings rather than computers are in positions of authority<br />

and power" (Katz & Kahn, 1978, 528).<br />

Feyerherm constructs a dynamic leadership model based on the processes in<br />

multiparty collaboration. Her model links leadership behavior to the activities and<br />

meaning attribution of the stakeholders. She defines leaders as the persons “who<br />

influence the course of events, the ways issues get framed and resolved, and the people who<br />

influence the outcomes of the gathering” (Feyerherm, 1997, 1). Her definition of<br />

leadership comes close to a classic definition in the group dynamic literature: “(…)<br />

the leader is a person who engages in leadership behaviors” (Shaw, 1976). The leaders are<br />

those who advance the task towards the collective goal. Chrislip and Larson (1994)<br />

emphasize that in complex organizational settings different parties are part of the<br />

overall leadership process. Direction is established through the process of<br />

constructive, collaborative interactions between the stakeholders, including<br />

alignment, involvement, agreement, motivation and inspiration. Ring and Van de<br />

Ven conceive inter-organizational relationships (IOR) as ‘developmental processes’.<br />

“From a developmental process perspective, cooperative IORs are socially contrived<br />

mechanisms <strong>for</strong> collective action, which are continually shaped and restructured by actions<br />

and symbolic interpretations of the parties involved” (Ring & Van de Ven, 1994, 96). Smith<br />

and Peterson (1989) also define leadership as a process of influence, supported by<br />

explicit structures, implicit conventions and emerging behaviors. Their focus of<br />

research is on the meaning of events. Leadership can be considered as an emerging<br />

process of influence that develops through actions and interactions between the<br />

participating stakeholders. These actions and interactions are influenced by the way<br />

in which the stakeholders make sense of events that occur in the process. The focus is<br />

on how the organization is created 'in-action' and on the emerging quality of the<br />

organizing process (Hosking & Fineman, 1990). These perspectives on leadership are<br />

stimulating, because they try to understand and make sense of what is actually<br />

happening in a collaborative process as it unfolds.<br />

12


A final and important source of inspiration is the work of Taillieu, Vansina and<br />

Schruijer on multiparty collaboration in simulations and educational contexts. Their<br />

research includes studies of the phenomenon of leadership (Schruijer, Taillieu &<br />

Vansina, 1998; Vansina, 2002), management of multiparty issues (Vansina, Taillieu &<br />

Schruijer, 1998) and management of diversity (Vansina & Taillieu, 1997; Vansina,<br />

2002). Their insights have been extremely helpful in the study of collaborative<br />

processes in ‘natural’ settings.<br />

1.3.4. Direction setting: issues and dynamics<br />

For a long time I looked <strong>for</strong> an appropriate concept to label the phenomenon I was<br />

trying to study and understand. These concepts shifted from ‘emergent coordination<br />

processes’, ‘leadership processes’, ‘leadership dynamics’, to ‘distributed leadership’.<br />

The notion ‘leadership’, however, provoked associations of individual leaders. I<br />

looked <strong>for</strong> a broader concept which referred to the ‘mechanisms that make things<br />

happen’ (Huxham & Vangen, 2000) and to the concept of ‘group locomotion’<br />

developed in the classic literature on group dynamics (Cartwright & Zander, 1960).<br />

Research in group dynamics has demonstrated the problems of coordination in<br />

group work (Shaw, 1976). In collaborative groups, this is likely to be even more<br />

problematic, because of the difficulty to set collaborative goals.<br />

To capture the way in which the participants enact leadership, I explored how they<br />

dealt with important ‘issues’ with which they were confronted. An ‘issue’ is a theme<br />

or dilemma that arises in the process and that provokes questions, tensions and<br />

anxiety in the participant(s) or in the system (e.g. dealing with diversity, choices<br />

about membership). The issues reflect the essence of collaborative work and need to<br />

be dealt with by those involved. They either relate to the task or to the relationships.<br />

The themes and dilemmas are interrelated and often remain present during the entire<br />

process (Huxham & Vangen, 2005). The participants attribute meaning to the issues<br />

in a subjective and inter-subjective process. This research focuses on the dynamic<br />

13


nature and evolution of the issues in the course of the process and the responses of<br />

the participants when confronted with those issues. Issues can, <strong>for</strong> instance, be<br />

ignored, denied, explored, dealt with, or they can provoke conflict. The dynamics<br />

that unfold around those issues play at a <strong>for</strong>mal and in<strong>for</strong>mal level (Ring & Van de<br />

Ven, 1994). They are manifest or latent and may help or hinder progress on the task.<br />

To explore the dynamics at the manifest and latent level, I have used the system<br />

psychodynamic perspective on working and organizing. Unlike social psychology, it<br />

focuses on overt behavior and the underlying dynamics (Schruijer, 1990). This<br />

perspective on direction setting allows <strong>for</strong> a study of the dynamics in the group or<br />

system, and of the system features that emerge as the process is <strong>for</strong>malized. In the<br />

following chapter I present the theoretical foundation of this framework and the<br />

assumptions I hold in my research. Then I couple this perspective with the<br />

framework of multiparty collaboration and discuss a number of specific challenges<br />

<strong>for</strong> direction setting in collaborative work.<br />

14


CHAPTER 2: THE SYSTEMS PSYCHODYNAMIC PERSPECTIVE<br />

2.1. The field: origins and definition<br />

The frame of reference <strong>for</strong> studying direction setting in collaborative processes is<br />

based on the work of the Tavistock Institute of Human Relations in London. The<br />

foundations of the so-called ‘Tavistock model’ were developed through several<br />

government funded post-war projects in the <strong>for</strong>ties (Mosse, 1994). The aim of the<br />

Tavistock was to integrate the social sciences and psychoanalysis and to relate the<br />

internal world of object relations with the external world of society (Menzies, 1988;<br />

Miller, 1997). This paradigm integrates the subjective experience of people (fantasies,<br />

wishes, dreams) and the systemic features of an organization (Anderson & White,<br />

2000). This body of knowledge is founded in psychodynamics, training in group<br />

relations and open system thinking (see unpublished literature overview, Prins,<br />

2001).<br />

The notion ‘psychodynamic’ refers to a broad domain of insights, such as<br />

anthropology, social and clinical psychology (Vansina, 2004). Most authors draw<br />

upon the work of the Object Relations School represented by Klein, Bion and<br />

Winnicott. This school emphasizes how people's perceptions and fantasies about<br />

work, organizations and the people with whom they work, influence their feelings,<br />

thoughts and actions in the workplace. This phenomenological view focuses on the<br />

world of social interactions w<strong>here</strong> we relate to one another subjectively and inter-<br />

subjectively in order to give meaning to our life by sharing stories, feelings, ideas,<br />

and opinions (Anderson & White, 2000).<br />

Group relations conferences were organized by the Tavistock Institute of Human<br />

Relations in collaboration with Leicester University since 1957. The experience of the<br />

conferences has offered, and still offers, insight in leadership, authority and power<br />

(Rice, 1965; Obholzer, 1994). A group relations conference is a temporary educational<br />

institution, which provides various settings to learn about inter-personal, inter-group<br />

15


and institutional relations, and about authority and leadership (Rice, 1965; Miller,<br />

1990). The subject of today’s conferences is leadership in complex and uncertain<br />

organizational contexts.<br />

The third pillar of the Tavistock model is open systems thinking. During the Second<br />

World War Wilfred Bion worked in the Northfield military hospital <strong>for</strong> mentally ill<br />

soldiers. He discovered that the immediate surroundings of the military hospital and<br />

the wider context had a critical impact on group functioning and mental recovery.<br />

“Groups are not only passively influenced by their environments, but eager, active<br />

interaction with the external environment is psychologically healthy.” (Vansina-Cobbaert &<br />

Vansina, 1996, 13) When Harold Bridger took over Bion’s work, he introduced the<br />

notion ‘open-system thinking’ in his work with groups. Until that moment group<br />

analysis had been restricted to what happened within the boundaries of the group<br />

itself (Bridger, 1990). Lewin also applied ideas from the open system theory<br />

developed in biology (von Bertalanffy, 1950) to human systems. Miller and Rice<br />

(1967) further elaborated these ideas. The open system perspective is the dominant<br />

frame to conceive the structural aspects of an organizational system. An open system<br />

has characteristics in common with a biological organism. Central concepts of the<br />

'organizational anatomy' include: design, division of labor, levels of authority,<br />

reporting relationships; the nature of work tasks, processes and activities; mission<br />

and primary task; the nature and patterning of the organization’s task and<br />

boundaries and the transactions across them (Miller & Rice, 1967; Zagier Roberts,<br />

1994a; Gould, Stapley & Stein, 2001). The boundary separates what is inside the<br />

system from what is outside. It provides a structure <strong>for</strong> the system and it regulates<br />

transactions with the environment <strong>for</strong> the survival of the system.<br />

In trying to define the field I came across a dozen different names <strong>for</strong> the so-called<br />

‘Tavistock model’. A range of approaches stresses different elements and t<strong>here</strong> is no<br />

single 'psychoanalytic voice' because of the developments and variety in<br />

psychoanalysis itself (Neumann & Hirschhorn, 1999; Vansina, 2000; Anderson &<br />

White, 2000; Eisold, 1996). A number of recent publications try to clarify the present<br />

16


oundaries of this emerging field of social science (Obholzer & Roberts, 1994; Gould,<br />

Stapley & Stein, 2001; Huffington, Armstrong, Halton, Hoyle & Pooley, 2004). In this<br />

research I adopt the so-called ‘systems psychodynamics of organizations’ as a frame<br />

<strong>for</strong> exploring the dynamics of direction setting. My work is primarily inspired by the<br />

ideas of Larry Hirschhorn and James Krantz. In what follows I develop the main<br />

assumptions I hold in this research.<br />

2.2. Basic assumptions in this research<br />

2.2.1. The ambiguity of organizational and group life<br />

The initial idea of setting up a multiparty collaboration may be a rational decision or<br />

intention, but the emergent process of collaboration is not fully 'rational' or<br />

conscious. Working in a collaborative is influenced by conscious as well as by<br />

hidden, emotional and unconscious motives. The system psychodynamic perspective<br />

provides a 'holistic' perspective on collaborative processes, considering both manifest<br />

and unconscious dynamics, represented by the ‘iceberg metaphor’ (Anderson &<br />

White, 2000; Lau & Shani, 1992). It is complementary to conventional organizational<br />

approaches because it challenges the exclusively rational view on organizations. The<br />

‘myth of management’ (Bowles, 1997), the ‘dominant logics’ (Vansina, 2000) or the<br />

‘rational madness’ (Lawrence, 1998) stress the belief in competition, growth and<br />

‘functional rationality’ w<strong>here</strong> organizational activities are rationalized and<br />

controlled. The psychodynamic perspective is primarily interested in the unknown<br />

<strong>for</strong>ces of organizational life and the sources of energy and motivation that are<br />

inaccessible to the conscious mind (Neumann & Hirschhorn, 1999; Adams &<br />

Diamond, 1999; Morgan, 1986; Denhardt, 1981; Mitroff, 1984; Driver, 2003).<br />

The psychodynamic perspective stresses two aspects of group life. First,<br />

organizational processes and groups have a ‘shadow’ side, because human behavior<br />

is often the result of conscious and unconscious mental processes. The shadow side<br />

of groups is well described by Bion (1961). He argued that a group functions on two<br />

levels. On the one hand it is a ‘work group’ working on the task in a rational and<br />

17


effective way. At the same time the group is united in a shared basic assumption that<br />

may prevent the group from working on the task. Bion (1961) described three basic<br />

assumption groups. In the basic assumption group ‘dependency’ the group assumes<br />

that the leader will sustain the group. The group depends on the leader <strong>for</strong><br />

nourishment, material and spiritual protection. The leader is perceived as<br />

omnipotent and omniscient (Miller, 1997). The group members feel powerless and<br />

their dependency on the leader inhibits growth and development (Vansina-Cobbaert<br />

& Vansina, 1996; Stokes, 1994). The second basic assumption is ‘pairing’. The group<br />

believes that a future event will save them and expects the leader to <strong>for</strong>m a pair with<br />

something or someone. This group often functions on the basis of changing<br />

subgroups and is dominated by feelings of hope which are disconnected from reality<br />

(Vansina-Cobbaert & Vansina, 1996). The group is focused on the future as a defense<br />

against the difficulties in the present (Stokes, 1994). The third basic assumption is<br />

called ‘fight-flight’. The group members assume t<strong>here</strong> is an enemy from which they<br />

have to flee or that needs to be attacked. In this group the leader is important because<br />

action is perceived as critical to ensure the survival of the group (de Board, 1978).<br />

Other authors have described defensive motives <strong>for</strong> setting up teams in<br />

organizations (e.g. Guerin, 1997), the paradoxical nature of groups (Smith & Berg,<br />

1987), and the tension between personal identity and connection with the group<br />

(Diamond & Allcorn, 1987; Gabriel & McCollom Hampton, 1999). In collaborative<br />

work ambiguity is ever so great, because the group members are confronted with<br />

many uncertainties and dilemmas. For instance, the boundaries of the group are<br />

often fuzzy and membership is not always clear. Group members have to deal with<br />

multiple identities in their role as representative. These issues may be played out at<br />

the underlying level of the collaborative.<br />

A second aspect of groups is that they embody important values in western culture,<br />

such as teamwork, collaboration, in<strong>for</strong>mality and equality. The group can have a<br />

motivating effect on people: it gives us the feeling we belong somew<strong>here</strong>, it makes us<br />

feel valued and gives us the feeling we make a significant contribution. Collaborative<br />

work is associated with positive values such as empowerment, participation and<br />

18


joint ownership. Groups and teams can offer a space w<strong>here</strong> difficult issues can be<br />

dealt with in an environment that is safer than other organizational structures<br />

(Guerin, 1997).<br />

2.2.2. The subjective experience of organizational life<br />

People create their ‘psychic reality’ of organizational life. They attribute subjective,<br />

emotional and partly unconscious meanings to experiences and relationships in the<br />

work place (Adams & Diamond, 1999). This internal image is also called the<br />

‘organization-in-the-mind’ (Hutton, Balzagette & Reed, 1997; Armstrong, 2005).<br />

Attribution of meaning mediates between organizational reality and the human<br />

experience. This ‘psychic reality’ influences the behavior of individuals and shapes<br />

organizational processes and structures. The notion ‘organization-in-experience’<br />

accentuates how organizational members experience the organization and ‘enact’<br />

their <strong>for</strong>mal role (Long, Newton & Dalgleish, 2000). It is an inter-subjective<br />

perspective focusing on processes of sense making and on how participants-in-<br />

interaction shape the organization. My research studies processes of sense-making<br />

and the emotional responses to collaboration.<br />

2.2.3. The interconnection of system features and emergent dynamics<br />

Collaborative processes are not just organizational processes, but they are conceived<br />

as 'psycho-social' processes. The ‘social’ refers to external realities, including the<br />

organizational structures, culture, technologies, procedures, and products. These<br />

social factors are connected to the psychological factors or the beliefs, values, hopes,<br />

fears, defense mechanisms and sense making processes of the participants. The<br />

structures stimulate particular patterns of individual and inter-organizational<br />

dynamics and these, in turn, may determine how particular features of the<br />

collaborative are <strong>for</strong>malized and structured (Gould et al., 2001). The internal and<br />

external worlds are thus in continual interrelation (Wells, 1995; Amado & Ambrose,<br />

2001; Gould et al., 2001). In this research I emphasize the interrelation between<br />

system features and the dynamics that emerge in the process.<br />

19


2.2.4. Anxiety and social defenses<br />

Most people tend to avoid uncertainty, anxiety and threats to their self-esteem. They<br />

often want to control their environment and make it predictable. Anxiety and<br />

defenses against anxiety are part of organizational life. Developmental processes in<br />

our early childhood play a critical role in present behavior and the way we deal with<br />

uncertainty and stress (Neumann & Hirschhorn, 1999). The psychodynamic<br />

perspective assumes that an organization offers containing mechanisms to protect<br />

individuals from too much uncertainty and ambiguity. People can ‘use’ an<br />

organization <strong>for</strong> unconscious reasons, to defend against anxiety, to renew their lost<br />

sense of omnipotence, to enhance their self-esteem or as a psychological space <strong>for</strong><br />

play and imagination (Adams & Diamond, 1999).<br />

When anxiety is too strong or not sufficiently contained, individuals, groups and<br />

organizations will develop defense mechanisms. 'Social defenses' (Jaques, 1955;<br />

Menzies, 1960) may emerge when a group unconsciously colludes to ward off the<br />

anxiety and tensions of collaborative work, often at the cost of task per<strong>for</strong>mance. The<br />

pioneering work of Menzies (1960) on social defenses, has demonstrated that<br />

unconscious anxieties are often reflected in organizational structure and design,<br />

which function to defend against the uncontained anxieties in the workplace. Social<br />

defense mechanisms “relieve individuals of the burden of managing their escape into<br />

illusion, of turning away from reality, by creating social systems that support systematic role<br />

violations. The social defenses externalize individual defenses.” (Hirschhorn, 1988, 56) The<br />

notion of social defenses demonstrates how individual unconscious fantasies and<br />

defenses are expressed in social processes without reducing the latter to individual<br />

psychology (Hinshelwood, 1989).<br />

According to Krantz (1998) the social defense theory is more relevant than ever.<br />

Working in today’s organizational world requires a state of mind and behavior that<br />

stem from functioning in the ‘depressive position’: being able to see and integrate the<br />

20


‘good’ and ‘bad’ elements of a situation without splitting off the ‘bad’ ones as a<br />

defense (Hinshelwood, 1989; Segal, 1973). Novel ways of organizing elicit primitive<br />

anxieties. New social defenses need to be created to cope with the changes we are<br />

facing. These need to balance the need to avoid anxiety and the need to do<br />

productive work. “The shape of social defense systems that are adapted to new marketplace<br />

realities remains to be discovered” (Krantz, 1998, 100). A collaborative does not offer the<br />

traditional containing structures (e.g. structured roles, procedures) to deal with the<br />

task. T<strong>here</strong><strong>for</strong>e it is likely that defensive dynamics will occur.<br />

2.2.5. Containment of organizational anxiety: a transitional approach to change<br />

A number of concepts are important <strong>for</strong> understanding the facilitating function of<br />

organizational processes, structures and interventions. The concepts were developed<br />

in the domain of child development and later adapted to the world of adults and<br />

organizations. I will define and discuss the main concepts.<br />

Containment<br />

When the mother is capable to contain the projected fears of the child, Bion (1970)<br />

speaks of ‘maternal reverie’. Containment is a psychic function w<strong>here</strong> the mother<br />

takes on the anxiety, and unpleasant emotions of the child in order to protect it from<br />

destruction. In later life, every person who is able to take on the anxiety of another<br />

person can function as a ‘container’ (Hinshelwood, 1989). “(…) the container can<br />

absorb, filter or manage difficult or threatening emotions or ideas – the contained – so that<br />

they can be worked with, or it can become a rigid frame or shell that restricts or blocks.”<br />

(French & Vince, 1999, 9).<br />

In the organizational context, containment is a psychic task w<strong>here</strong> those in a leading<br />

role temporarily protect their collaborators from being overwhelmed by the demands<br />

and complexity of the situation. The ‘container’ – temporarily - carries the stress <strong>for</strong><br />

other persons, and gives it back in a manageable <strong>for</strong>m. In organizational change,<br />

managers and consultants can function as a ‘container’ by, <strong>for</strong> instance, reframing the<br />

21


situation (Halton, 1994; Miller, 1997; Neumann, 1999; Boalt Boëthius, 1999; Cardona,<br />

1999; Obholzer, 1999; Krantz, 1998; Hirschhorn & Gilmore, 1992). The ‘contained’ can<br />

be an emotion, an idea or a person. The ‘container’ can have different shapes in an<br />

organizational context. A ‘team’, <strong>for</strong> instance, can function as a container <strong>for</strong> the<br />

organizational experience (Czander, 1997; Krantz, 1998). Whether or not groups are<br />

capable of containment, determines their potential <strong>for</strong> development. “A group’s<br />

capacity to elaborate on certain opinions, and mainly to contain new ideas and the fears that<br />

come with them, to sort them out and possibly integrate them either fully or partially, is<br />

essential to the continuous development and vitality of the group in question.” (Vansina-<br />

Cobbaert & Vansina, 1996, 9)<br />

Holding environment<br />

A ‘holding environment’ (Winnicott, 1971) refers to the constant and consistent<br />

physical and emotional care provided by the mother that enables the infant to<br />

develop. Holding is protecting the child from too much stimulation coming from the<br />

outside and from the inside. This requires a high level of empathy and sensitivity<br />

from the mother. The ‘good enough’ mother helps the child to make a distinction<br />

between the self and the outer world and to gain basic confidence. As the child<br />

grows older, the holding environment is extended to the father, the family, and the<br />

school. It protects the child against too much stress, conflicting demands and threats<br />

in the outer world, also at a later age. “The psychological and physical holding an infant<br />

needs throughout his development continues to be important, and the holding environment<br />

never loses its importance <strong>for</strong> everyone.” (Abram, 1996, 183)<br />

In the organizational world holding environments are still important to protect<br />

people from the anxiety stirred up by the organizational experience. It refers to “(...)<br />

those practices and symbols characteristic of a local organizational culture which supports<br />

(either well or poorly) the specific identities of organizational members.” (van Buskirk & Mc<br />

Grath, 1999, 812). From that perspective, organizational experiences can contribute to<br />

the development of individuals. In change processes, leaders or consultants can<br />

22


provide a holding environment, or a setting that itself can be trusted to provide<br />

physical and psychological safety to those willing to experience and explore issues<br />

that might normally be anxiety provoking, politically subversive or counter-cultural<br />

within the organization. It allows <strong>for</strong> exploration of ideas and feelings that emerge<br />

during work, which otherwise would be suppressed or operate in an underground<br />

manner. It is important to contain such experiences and explorations so that they can<br />

be integrated <strong>for</strong> work, rather than <strong>for</strong> counter-work purposes (Long, et al., 2000). “A<br />

holding environment generates the feeling that things are all right the way they are, and that<br />

it is acceptable to be anxious and insecure, helping people to accept their own doubts and<br />

fears.” (Overlaet & Barrett, 2000, 16) Consultants or leaders can provide a holding<br />

environment by “(...) serving as a safe container who can accept and survive the anxieties<br />

and sometimes hostile projections (…).” (Miller, 1997, 191)<br />

Transitional phenomena<br />

Transitional phenomena refer to experiences in the mother-child relationship that are<br />

critical <strong>for</strong> the development of the infant. It refers to a space that separates and<br />

connects the internal and external reality. Winnicott (1971) used different terms to<br />

refer to this space: ‘the third area’, ‘the intermediate area’, ‘the potential space’, ‘a<br />

resting place’ and ‘the location of cultural experience’ (Abram, 1996). He did not use<br />

the notion ‘transitional space’, which is often used in the organizational literature.<br />

The ‘third space’ is located between the inner and outer world. “(...) the third part of<br />

the life of a human being, a part that we cannot ignore, is an intermediate area of<br />

experiencing, to which inner reality and external life both contribute. It is an area that is not<br />

challenged, because no claim is made on its behalf except that it shall exist as a resting-place<br />

<strong>for</strong> the individual engaged in the perpetual human task of keeping inner and outer reality<br />

separate yet interrelated.” (Winnicott, 1971, 2) Culture, creativity and play originate in<br />

this space (Abram, 1996).<br />

The child uses ‘transitional objects’ to start distinguishing the self from the not-self<br />

and to develop from total dependence on the mother to relative independence. This<br />

23


is a self chosen object which represents the aspects of ‘mothering’, but at the same<br />

time allows the child to create, by himself, what he needs. This object can be a thumb,<br />

a blanket, a teddy bear, but also a tune, or a word. Its function is to defend against<br />

the anxiety, which is particularly important when the child goes to sleep (Winnicott,<br />

1971). At a certain point in time the child no longer needs the transitional object<br />

because he is able to make the distinction ‘me’ ‘not-me’. He is capable to “(...) live in<br />

the third area, keeping inside and outside apart and yet inter-related.” (Abram, 1996, 317).<br />

According to Winnicott the notions of development, holding and transitional objects,<br />

based in childhood, are paradigmatic <strong>for</strong> later life (van Buskirk & Mc Grath, 1999).<br />

Harold Bridger and Gilles Amado trans<strong>for</strong>med the ideas of Winnicott to the world of<br />

adults and organizations. Because change ef<strong>for</strong>ts often fail, Bridger wanted to<br />

understand the nature of change processes or ‘transitions’. According to Bridger,<br />

transitional change is a psychological process made up of three phases: the ending<br />

phase, the neutral zone phase and the vision or new beginning. It is a process of re-<br />

birth, which requires the recognition of many losses <strong>for</strong> the people involved. In a<br />

state of transition t<strong>here</strong> is confusion and uncertainty, but also space <strong>for</strong><br />

experimentation and innovation (Amado & Amato, 2001). To facilitate such change,<br />

it is important to design conditions <strong>for</strong> a ‘transitional space’. A transitional space is<br />

“(…) an environment w<strong>here</strong> options can be explored in safety without later repercussions,<br />

w<strong>here</strong> people can experiment with roles and behaviours beyond their habitual ones, and w<strong>here</strong><br />

issues can be worked through that the normal working culture may not encourage to surface.”<br />

(Klein, 2001) Leaders or consultants can establish the conditions <strong>for</strong> such a space, but<br />

they cannot impose the experience. It is not a technique, but an opportunity <strong>for</strong><br />

development and change. The participants can use the space <strong>for</strong> reflection and<br />

working through the emerging relations with work, colleagues and the new<br />

organization. This allows them to make the transition from one state of existence to<br />

another (Vansina, 1998). During a transition, the past and present are simultaneously<br />

present in the <strong>here</strong>-and-now. It is not ‘real’ yet; it is a temporary, virtual world w<strong>here</strong><br />

thinking, fantasy and play are central to prepare <strong>for</strong> the future. Transitional<br />

experiences are “(...) the ‘in between’ when organizational members find that they cannot<br />

24


ely on familiar routines and yet do not have new frameworks that are up to the challenge.<br />

During such transitions old conceptions and practices are no longer valid, but new practices<br />

are not yet available, and have to be constructed.” (Overlaet & Barrett, 2000, 3) In<br />

transitional change processes, participants may choose a transitional object (e.g. a<br />

compelling vision, a slogan, a computer model of a future state) to contain the<br />

anxiety of the change. Transitional objects cannot be ‘designed’ by leaders or<br />

consultants. They represent neutral ‘objects’ that acquire an emotional meaning. A<br />

transitional object can serve different functions, such as prepare people <strong>for</strong> the future<br />

or provide com<strong>for</strong>t and reassurance (Hutton et al., 1997). They may help people in a<br />

change process to let go of the old and embrace something new.<br />

The paranoid-schizoid position and the depressive position<br />

In 1946 Melanie Klein (1993) described the ‘paranoid-schizoid position’. In the<br />

earliest development the child experiences persecutory anxiety, resulting in<br />

processes of fragmentation of the mind. “The splitting processes typically lead to<br />

projection of parts of the self or ego (projective identification) into objects, with a depleting<br />

effect on the self.” (Hinshelwood, 1989, 156) Splitting and projection are a defense<br />

against the intense anxieties. “The paranoid-schizoid position is characterized by the<br />

infant’s unawareness of ‘persons’, his relationships being to part objects, and by the<br />

prevalence of splitting processes and paranoid anxiety.” (Segal, 1973, ix) Adults can also<br />

function in the paranoid-schizoid position when they are confronted with extreme<br />

anxiety. “Operating from the more primitive paranoid-schizoid end of the spectrum brings<br />

out grandiosity, persecution, and inflexible thinking.” (Krantz, 1998, 81)<br />

When the child is able to accept the positive and negative qualities of ‘objects’ (e.g.<br />

mother), he is able to function in the ‘depressive position’. The child discovers that<br />

the ‘good’ and ‘bad’ are manifestations of the same person or object. “The infant, at<br />

some stage (normally at four to six months), is physically and emotionally mature enough to<br />

integrate his or her fragmented perceptions of mother, bringing together the separately good<br />

and bad versions (imagos) that he or she has previously experienced.” (Hinshelwood, 1989,<br />

25


138) The child recognizes the mother as a whole person and is able to relate to whole<br />

objects (Segal, 1973). He needs to give up his self-idealization and accept the<br />

complexity of inner and outer reality. The term ‘depressive’ refers to the experience<br />

of guilt and sadness associated with this position (Halton, 1994).<br />

Containment of the anxiety of the organizational experience facilitates functioning in<br />

the depressive position; the participants are able to work with the complexity of<br />

reality. “In the depressive position, omnipotent fantasy, obsessional ritual and paranoid<br />

blaming can give way to thinking: one can seek to know, to learn from experience and to solve<br />

problems.” (Zagier Roberts, 1994c, 118) Groups able to function in the depressive<br />

position can cope with the emotional complexity of work and do not split off<br />

negative elements. However, when the survival and self-esteem of a group is<br />

threatened, t<strong>here</strong> may be a tendency to return to more primitive ways of functioning<br />

(Halton, 1994). The essence is to stay in touch with reality. According to Krantz, a<br />

critical condition to function in new <strong>for</strong>ms of organizing is to enable people to<br />

function in the depressive position. This means that people need “(...) to be able to<br />

learn from experience, to be vulnerable without feeling persecuted so that one can learn from<br />

experience, to be curious about, rather than fearful of, the unknown, to be able to link with<br />

others across important differences, and to be realistically connected to the genuine<br />

opportunities and challenges they face.” (Krantz, 1998, 82)<br />

The theoretical frame presented <strong>here</strong>, provided the organizing principle <strong>for</strong> my<br />

research. In the following section I connect these theoretical insights with multiparty<br />

collaboration and emphasize a number of specific challenges.<br />

2.3. A systems psychodynamic perspective on collaborative work:<br />

the challenges of direction setting<br />

The ideas developed in this section are essentially inspired by the insights of Larry<br />

Hirschhorn (1988; 1990; 1997; 2002) and James Krantz (1985; 1990; 1998). Their work<br />

on new <strong>for</strong>ms of organizing, the responses of individuals and groups to these new<br />

organizational conditions, and new ways of conceiving and shaping leadership in so-<br />

26


called ‘post-modern’ or ‘new order’ organizations has been stimulating in this<br />

research on multiparty collaboration. In collaborative work, the participants need to<br />

deal with the challenges of this complex organizational reality. In what follows, I<br />

discuss a number of organizational features of multiparty collaboration that may<br />

provoke anxiety and trigger defensive responses.<br />

2.3.1. The socio-economic and organizational context<br />

To understand the dynamics in a collaborative, it is critical to pay attention to its<br />

environment. An exclusive focus on the group as a human system does not lead to a<br />

full understanding of a collaborative experience. The group is always a group in a<br />

particular historical, political, societal and institutional context (McCollom, 1995). It<br />

is important to study how a group reacts to external events and which adaptive<br />

processes emerge (McGrath & Tschan, 2004). The organizational context of a<br />

collaborative is often complex, uncertain and ambiguous. Political processes and<br />

dynamics in the environment, between the representatives and their constituency,<br />

affect the collaborative (Schuman, 1996). The boundary between the collaborative<br />

and its environment is extremely fluid.<br />

The complex nature of the context and the inter-organizational domain (Trist, 1983)<br />

may provoke tensions. In response, the participants may try to reduce the complexity<br />

and rely on primitive defenses, such as splitting and projection (Segal, 1973;<br />

Lawrence, 1998; Krantz, 1998). They can easily slip into dynamics, such as exclusion<br />

of threatening stakeholders or premature <strong>for</strong>malizing of the process.<br />

Collaborative work is also characterized by uncertainty. "For all actors at the beginning<br />

of the process, this results in a high degree of uncertainty about how the process will be<br />

handled and how the interaction with other actors will develop" (Koppenjan & Klijn, 2004:<br />

7). 'Substantive' uncertainty concerns the availability of in<strong>for</strong>mation. Relevant<br />

in<strong>for</strong>mation is not available, not available in time or interpreted in different ways by<br />

the participating actors. Secondly, 'strategic' uncertainty is provoked by the strategic<br />

27


choices the actors need to make with regard to the articulation of complex problems.<br />

Unexpected strategic turns to solve problems and to take decisions are an intrinsic<br />

characteristic of interaction processes dealing with complex problems. Finally,<br />

'institutional' uncertainty refers to the tasks, opinions, rules and language of the<br />

organizations involved. Representatives in a collaborative will most likely have to<br />

deal with all three types of uncertainty.<br />

Ambiguity is a quality resulting from the social process of negotiating different<br />

frames, interests and values. In a collaborative multiple frames and perspectives are<br />

used to make sense of the situation. The consequences are that different stakeholders<br />

will give a different meaning to the situation, have different priorities, include or<br />

exclude different issues, in<strong>for</strong>mation and members, and choose different solutions. A<br />

process of joint sense making and reframing can be an opportunity <strong>for</strong> change and<br />

creative and innovative solutions (Dewulf, Craps, Bouwen, Taillieu & Pahl-Wostl,<br />

2004). However, confrontation of different frames can also be threatening and result<br />

in conflict or defensive responses.<br />

Hirschhorn and Krantz stress the increase in organizational anxiety as a consequence<br />

of the deep-seated changes, the fundamental uncertainty and the greater turbulence<br />

with which we are confronted. “More specifically, the great vulnerability and insecurity<br />

characteristic of today’s environments are likely to resonate with the very primitive fear of<br />

annihilation and terrifying potential <strong>for</strong> psychological disintegration that many analysts have<br />

found in the primitive recesses of their patients.” (Krantz, 1998, 86) Representatives need<br />

to learn how to adapt to the changing opportunities and restrictions in the<br />

environment.<br />

2.3.2. The self-designing nature of the collaborative task<br />

In multiparty collaboration the task is often of a self-designing nature. The first<br />

challenge <strong>for</strong> the convener and the collaborative group is to develop a shared<br />

understanding of the task and to establish ‘common ground’ (Gray, 1989). This<br />

28


enables the development of interdependence, trust and productive work. Defining<br />

the task is a critical act and a highly sensitive process, because the different interests<br />

and ambitions of the parties are involved. T<strong>here</strong><strong>for</strong>e a critical issue is: who is<br />

included in the process of task construction? Stakeholders may fear to be excluded<br />

from the process, or dominated by more powerful parties.<br />

Traditionally the ‘primary task’ refers to the task the organization has to per<strong>for</strong>m in<br />

order to survive (Rice, 1958; Miller, 1993). This concept, however, is not relevant in<br />

an inter-organizational context because of the turbulence in the environment and the<br />

dynamic nature of a collaborative. A critical task of leadership is to ensure that the<br />

primary task is constantly reviewed and adapted in the light of a changing<br />

environment (Obholzer & Miller, 2004). In a context w<strong>here</strong> leadership is a shared<br />

phenomenon, all those involved need to pay attention to the relevance of the primary<br />

task in relation to, <strong>for</strong> instance, changes in membership, changing boundaries, or<br />

events in the environment.<br />

2.3.3. The emergent nature of the collaborative process<br />

For many, collaboration is a new and unfamiliar way of working. They often lack the<br />

skills and scripts to deal with the situation. Working in a multiparty logic means that<br />

participants engage in an open, under-organized process with an uncertain outcome.<br />

The process is ‘emergent’ (Gray, 1989). The general direction and desired outcome<br />

can be described, but the final outcome is not predetermined and will be shaped by<br />

the interplay of different issues in the process. This demands the capacity to deal<br />

with the uncertainty and ambiguity of the journey. T<strong>here</strong> are few containing<br />

structures and processes because these cannot always be established in advance.<br />

Krantz (1998) argues that the decline of stable structures as a key dimension of<br />

organizational life stirs up anxiety. “Many anxieties, <strong>for</strong>merly contained, become<br />

‘dislodged’, others are stimulated by the fact of change, and still more are elicited by the<br />

frightening and unknown conditions we often face” (Krantz, 1998, 87-88). T<strong>here</strong><strong>for</strong>e the<br />

29


isk is that participants will tend to reduce uncertainty and complexity and<br />

prematurely <strong>for</strong>malize the process as a defense against the tensions of the openness.<br />

Formalization or over-structuring of the process may result in a loss of the benefits of<br />

collaborating. Trist (1983) calls it a referent organization taking ‘the wrong path’ by<br />

establishing bureaucratic principles, central power, and hierarchical <strong>for</strong>ms of<br />

organizing. The result is a sub-optimization of diversity and interdependence.<br />

However, uncertainty and anxiety as such are not a source of ineffective functioning.<br />

According to Hirschhorn (1988) the critical factor is how anxiety is ‘contained’ by<br />

individuals, groups and organizations. “(…) authority and facilitating structures are<br />

necessary to channel anxiety into productive work. In their absence, the anxiety is bound up<br />

in socially defensive or ritualized patterns such as basic assumption dynamics in teams or<br />

ritualized organizational behavior, thus distorting the constructive use of available energy.”<br />

(Guerin, 1997, 21) The challenge is to establish new <strong>for</strong>ms of containment.<br />

2.3.4. Development of collaborative relationships<br />

Working in a collaborative confronts the representatives with relational challenges.<br />

They need to deal with mutual dependency, diversity, asymmetries between the<br />

parties, and with ambiguous authority relations.<br />

Many years ago, Lewin (1951) argued that the essential aspect of a collection of<br />

individuals which makes it a ‘group’ is the interdependency of individuals on one<br />

another. In multiparty collaboration the stakeholders in the problem domain are, by<br />

definition, mutually dependent upon each other to achieve results. In order to work<br />

out sustainable solutions that are widely supported in the domain, stakeholders need<br />

to develop interdependent relationships. ‘Dependence’ is a natural property of<br />

groups. Interdependence can be viewed as the outcome of successfully negotiating<br />

the inevitable anxieties generated by mutual dependence (Miller, 1993; Gould, et al.,<br />

1999; Carr, 2001). In collaborative work it is critical to understand the broader social<br />

field in which work takes place and to have a system perspective (Hirschhorn, 1988).<br />

30


Most organizations and social groups are used to work independently and they often<br />

cultivate their autonomy and competitive ways of working. Interdependence makes<br />

actors vulnerable as their success depends on others. It seems paradoxical, but<br />

collaborative relationships can provoke more anxiety than more familiar competitive<br />

relationships (Krantz & Gilmore, 1990).<br />

To arrive at optimal and sustainable solutions, the participants in a collaborative<br />

need to integrate the diversity present in the system (Vansina, 2002). T<strong>here</strong><strong>for</strong>e they<br />

need to acknowledge the different perspectives, values, interests, and contributions<br />

of the stakeholders. An appropriate degree of contesting with the other, without<br />

conflict or evasion, seems required (Huffington, James & Armstrong, 2004). A<br />

confrontation with diversity may jeopardize one's identity, position and feelings of<br />

self-esteem. This may lead, <strong>for</strong> instance, to rivalry, independent action, ignoring the<br />

interests of certain parties, or to the dominance of one perspective. The challenge of<br />

collaborative work is to keep the diversity around the table and to work with<br />

diversity.<br />

Participants can experience the tension between the ideology and rhetoric of<br />

'equality' and 'legitimacy' of all participating groups and organizations, and the<br />

obvious asymmetries that exist. Asymmetries can relate to power, resources, know-<br />

how, social network, competencies, status, available time, and degree of<br />

involvement. It is important to explicitly acknowledge the legitimate presence of all<br />

parties involved and to make sure the existence of the asymmetries is recognized.<br />

Participants need to learn to relate to each other in new ways and develop a<br />

‘collaborative attitude’. This attitude is characterized by trust, the capacity to work<br />

with different power relations, the possibility to work in a situation of ‘not knowing’<br />

and the readiness to learn from the experience of collaboration. Mature inter-group<br />

relations, as opposed to defensive relations, can lead to a group culture aimed at<br />

collaboration. It can also result in the development of genuine interdependence<br />

between stakeholders as the result of working through the anxieties provoked by not<br />

31


eing in control and by being dependent upon others (Long et al., 2000; Gould, Ebers<br />

& Mc Vicker Clinchy, 1999; Carr, 2001).<br />

These different sources of anxiety are important to consider in the study of processes<br />

of direction setting. They relate to difficult issues that need containment, in order to<br />

avoid the emergence of defensive dynamics that endanger collaborative work. In the<br />

next paragraph, I briefly discuss the issue of ambiguous authority relationships, as<br />

this is a critical aspect <strong>for</strong> direction setting.<br />

2.4. Direction setting and the ambiguity of authority relations<br />

According to Krantz (1998, 96) t<strong>here</strong> are two important consequences related to<br />

organizational anxieties and how we cope with them in the post-industrial world of<br />

working and organizing. “With the decline of the bureaucratic order, the two key<br />

dimensions of organizational life that were used in socially defensive fashion are diminishing:<br />

stable structures and authority that is embedded in structure”. The psychodynamic frame<br />

enhances insight in how individuals and groups deal with ambiguous authority<br />

relations. As t<strong>here</strong> is no identified ‘leader’, it is harder to blame, admire, despise, or<br />

depend on someone. Upward identification and delegation of authority are not so<br />

obvious. Moreover, dependency needs that are not responded to, may lead to<br />

ambivalent feelings such as disappointment, anger, or fear (Hirschhorn, 1990).<br />

In a collaborative people can no longer rely on stereotypes of leadership and<br />

followership. “The new post-industrial economic order is leading to dramatic changes in<br />

individual’s relationships with their organizations and in the character of authority relations,<br />

creating pressure to re-examine the attribution of leadership exclusively to <strong>for</strong>mal leaders”<br />

(Krantz, 1990, 51-52). Authority relations are ambiguous and often authority is<br />

implicit, difficult to identify and structures or <strong>for</strong>mal roles to contain authority are<br />

unclear or lacking. In a collaborative it is not always clear who is influencing the<br />

direction and outcome of the process. According to Diamond and Allcorn (1987)<br />

ambiguity in authority relations is one of the most important reasons <strong>for</strong><br />

32


organizational conflict and failure. It increases anxiety, regression, withdrawal,<br />

projections and results in a defensive group culture. Czander (1993) argues that<br />

under conditions of ambiguity, when roles and responsibilities are not clear, the<br />

political and in<strong>for</strong>mal social systems will prevail. T<strong>here</strong><strong>for</strong>e a collaborative needs a<br />

'good enough' authority structure (Gilmore, 1997), such as clearly negotiated roles, in<br />

order to experience some stability and emotional reassurance.<br />

Literature on leadership in the post-modern world of organizing stresses ownership,<br />

the need to take up personal authority and to be ‘psychologically present’<br />

(Hirschhorn, 1997; Miller, 1999). People are increasingly expected to manage<br />

themselves in their role and to take up authority (Zagier Roberts, 1999). This shift in<br />

expectations challenges our common ideas on authority. According to Krantz (1990)<br />

our assumptions on authority are partly maintained as defenses against anxiety. In a<br />

collaborative setting, these assumptions may lead to tension between dependency<br />

needs and the requirement to take up authority. The parties who are not in a <strong>for</strong>mal<br />

leading role may fall back on stereotypes or fantasies about leadership and project<br />

their expectations on the parties that take up a leading role (e.g. facilitator, convener).<br />

Not being able to rely on familiar and shared notions of authority eliminates the<br />

reassuring, dependent fantasy that at least someone 'knows' or is in control (Shapiro,<br />

2000). Having to let go of these assumptions is likely to stir up anxieties and may<br />

provoke regressive behavior.<br />

The concept of 'post-industrial authority relations’, developed by Hirschhorn (1990),<br />

is relevant <strong>for</strong> collaborative work. Representatives need to negotiate their roles,<br />

establish authority relations, and demonstrate the capability to take up ownership<br />

(self-management). In new ways of organizing authority does not come from a<br />

position or defined role, but from taking up authority. People engage in processes of<br />

'authorizing' and 'de-authorizing' (Kahn & Kram, 1994). Symmetrical and horizontal<br />

relationships, based on partnership, mobilize mature interdependence. They are<br />

opposed to defensive relationships (e.g. dependency, counter-dependency) with the<br />

unconscious purpose of containing anxieties (Miller, 1998; 1999). It is an issue of<br />

33


individual development and group development. As negotiation becomes a critical<br />

aspect of organizing, it is important to focus on the process of collaboration. This may<br />

increase understanding of how leadership is enacted and how the direction of a<br />

collaborative ef<strong>for</strong>t is established.<br />

Collaboration confronts us with a paradox (Krantz, 1998). In order to arrive at<br />

innovative, sustainable and accepted solutions, the actors need to develop mature<br />

collaborative relationships. However, it is precisely the openness, complexity and<br />

uncertainties of a collaborative journey that make it hard to develop open and<br />

trustful relationships. This paradox is at the core of this research.<br />

34


CHAPTER 3: RESEARCH APPROACH<br />

3.1. Interpretive inquiry: epistemological position<br />

In this chapter, I position this research in the broad tradition of qualitative research. I<br />

discuss the epistemological position I take and the specific nature of doing research<br />

from the systems psychodynamic perspective.<br />

Several authors define the nature of psychodynamic or ‘clinical’ research in<br />

organizational contexts. Berg and Smith (1988) identify the following characteristics:<br />

- Direct involvement with and/or observation of people or social systems ;<br />

- The commitment of the researcher to engage in a process of self reflection<br />

while carrying out the research;<br />

- The readiness to change the chosen theory or method in response to the<br />

experience of carrying out the research;<br />

- A description of social systems that is ‘thick’ and deep rather than broad;<br />

- Involvement of the social system under study, based on the assumption that<br />

most of the relevant in<strong>for</strong>mation can only be reported by the organizational<br />

members.<br />

Lowman draws a parallel between research in clinical and organizational settings.<br />

“(…) the interventionist translates client-presented data to theories or understandings that<br />

would explain the behavior and about which the client may be unaware. The veracity of the<br />

theory is confirmed, if at all, by the reception it receives from the client in an interactive<br />

process (…). The clinical inferential process is t<strong>here</strong><strong>for</strong>e personalistic and highly related to the<br />

skill, intuition, and competence of the therapist or researcher.” (Lowman, 1988, 181). The<br />

clinical researcher gives feedback to the client system with a double intention:<br />

improve the functioning of the system and stimulate learning.<br />

According to Schein (1987a) the clinical perspective is based on an ‘action research’<br />

model. The assumption is that one cannot understand a human system without<br />

35


trying to change it. The essential dynamics of the system remain invisible <strong>for</strong> the<br />

passive observer. The aim of the interventionist is to change the system, because the<br />

starting point is a ‘problem’ presented by the client. By intervening in the system the<br />

consultant will provoke a response from the client (Schein, 1987b). “The nature of that<br />

response then becomes primary diagnostic data <strong>for</strong> determining what may really be going on.<br />

(…) In my own experience, it is the observed anomalies, blank looks in response to simple<br />

questions, defensive denials and counterarguments, and various other kinds of emotional<br />

responses that occur in reaction to my own behavior that are the most valuable sources of<br />

insight into what is going on.” (Schein, 1987a, 29-30) The ‘clinician’ brings the system in<br />

movement. In the action research model the focus is not on data ‘out t<strong>here</strong>’ that can<br />

be observed, but on a careful analysis of the relationship between the organizational<br />

members and the ‘outsider’.<br />

Psychodynamic research focuses on the manifest and latent meaning of experiences.<br />

It is a phenomenological approach, w<strong>here</strong> the researcher tries to bring the subjective<br />

experience of the individuals to the surface and discover the meaning of that<br />

experience. The aim is not to determine causal relations or to predict phenomena, but<br />

to understand the phenomena in their complexity, wholeness and uniqueness<br />

(Lapierre, 1993; Edelson, 1988). I have chosen <strong>for</strong> a study of specific cases in the<br />

interest of understanding the complexity of a social process in a particular<br />

organizational context (Druckman, 1977). The aim of my research is to construct a<br />

‘thick description’ (Geertz, 1973) of meaning. Geertz’s interpretive anthropology<br />

focuses on sense making. He opposed the structuralist tradition that was looking <strong>for</strong><br />

the ‘true’ meaning of, <strong>for</strong> instance, a myth or ceremony, in order to translate it into<br />

scientific terms. The way meaning is shaped in a particular culture has to be ‘read’ or<br />

interpreted by the ethnographer, just like one would read or interpret a difficult text.<br />

It is not about a world of social facts waiting to be observed, described and analyzed.<br />

“Rather, the inquirer constructs a reading of the meaning-making process of the people he or<br />

she studies.(…) The task of ethnography is not observation and description, but the<br />

inscription or thick description of these meanings of human action.” (Schwandt, 1994, 123)<br />

36


In order to make sense of organizational experiences an interpretive method is<br />

required. “The constructivist or interpretivist believes that to understand this world of<br />

meaning one must interpret it.” (Schwandt, 1994, 118). In this research the<br />

psychodynamic frame is a method of inquiry or a lens to collect and make sense of<br />

the data, and not so much a theory to explain behavior. Some authors use misleading<br />

images: the 'organizational detective' (Kets de Vries, 1999) or the '<strong>for</strong>ensic researcher'<br />

(Gabriel, 1999). These images suggest that the researcher needs to discover 'a truth<br />

out t<strong>here</strong>’, under the surface.<br />

Interpretation of the data is not the ‘truth’ or a certainty, but it is a co-creation of<br />

meaning by the participants, the researcher, and colleagues involved in the process<br />

(Hollway & Jefferson, 2000). My understanding is, necessarily, a 'partial<br />

understanding'. Interpretation means proceeding from one hypothesis to another<br />

hypothesis, rather than from uncertainty to certainty (Shapiro & Carr, 1991). A<br />

psychodynamic reading of phenomena is one interpretation that cannot be a<br />

complete description. It can be complementary, reposition existing views, or enrich<br />

those views (Halton, 1994; Schonberg, 1998). Moreover, I assume t<strong>here</strong> are multiple<br />

‘truths’. The stakeholders differ in the way they make sense of their experiences, and<br />

my interpretation may be different from their sense making ('multiple realities').<br />

The case studies in this research are ‘confessional tales’ (Van Maanen, 1988). They are<br />

stories with personalized authorship: I describe the role I played in the system and<br />

share my point of view when relevant <strong>for</strong> the focus of research. According to Flick<br />

(2002) this way of presenting a case gains in importance.<br />

For each case study three levels can be distinguished:<br />

1. The data in chronological order (observations, quotes from interviews and<br />

meetings): what happened?<br />

2. Processes of sense making: what meaning do participants attribute to the<br />

events and issues?<br />

3. Interpretation of the data: which dynamics and patterns emerge?<br />

37


Interpretation of the experiences is based on the ‘wholeness’ of the data, linked with<br />

the particular context in which the experiences occur. The meaning of the events and<br />

experiences, ascribed by the researcher, is constructed following a systematic<br />

approach <strong>for</strong> data analysis and interpretation.<br />

3.2. An attitude of inquiry: the interpretive stance<br />

Adopting the psychodynamic lens in research refers to a particular sensitivity to the<br />

data during data collection and data analysis. I will briefly discuss some features of<br />

the 'interpretive stance' (Shapiro & Carr, 1991).<br />

A first feature is that the researcher should demonstrate an evenly divided attention<br />

<strong>for</strong> the manifest and underlying dynamics. The researcher listens with the 'third ear'<br />

to the participants and pays attention to the ‘hidden music’ in the stories (Reik, 1948;<br />

Gilmore & Krantz, 1985). The manifest, latent and unconscious dynamics are closely<br />

intertwined. This distinction is made <strong>for</strong> the sake of clarity.<br />

Listening to the hidden music means the researcher needs to be sensitive to ‘clues’ in<br />

order gain access to (latent) meaning. “The odd, the out of place, the significant exception<br />

provide far more insight than large volumes of uni<strong>for</strong>m and unidirectional data.” (Gabriel,<br />

1999, 251) The researcher needs to be attentive <strong>for</strong> the incidental or unexpected event.<br />

Special attention is directed at the energy level, non-verbal cues, what is not being<br />

talked about, colorful language, images, silence, and unexpected or strong emotions<br />

in the other or in the self (transference or counter transference). Levinson (1993), <strong>for</strong><br />

instance, stresses the importance of paying attention to first impressions when<br />

entering an organization. A clue can hint to an underlying meaning of experience<br />

that should be explored further.<br />

The researcher needs to ‘listen’ both to the other and to the self and engage in<br />

inquiry and self-inquiry (Gardner, 1989). The 'self' is used as an instrument in<br />

38


sensing and exploring. This attitude requires a commitment to introspection, self-<br />

reflection and personal scrutiny (Hunt, 1989). In listening to the self the researcher<br />

pays attention to her emotions (e.g. bored, enthusiastic) and physical sensations (e.g.<br />

tired, nervous). She should also be aware of her assumptions about the issue under<br />

study. Whenever the researcher has an uneasy feeling, she should explore both what<br />

derives from 'within' and what arises from 'without' and sort out what is 'me' and<br />

'not me' in the experience (Shapiro & Carr, 1991). What the researcher is experiencing<br />

might be what the other person is experiencing too. It requires careful exploration of<br />

what it might mean.<br />

To conclude, the researcher has to be able to tolerate and contain the anxiety of ‘not-<br />

knowing’. Bion (1970) called this attitude ‘negative capability’: without memory,<br />

desire, nor understanding (Vansina-Cobbaert & Vansina, 1996). In the research<br />

context this means that the researcher should try to suspend judgment and to look at<br />

phenomena with a fresh and open mind. It is important to be open <strong>for</strong> what happens<br />

in the <strong>here</strong>-and-now, to be curious and receptive <strong>for</strong> surprises, and not to just hear,<br />

see and feel what you expect to find. The purpose is not to look <strong>for</strong> illustrations of<br />

theoretical concepts in the data. In the following section I further explore the<br />

subjective nature of doing research.<br />

3.3. Subjectivity and inter-subjectivity as a source of data<br />

Fieldwork is an inter-subjective process, a dialogue and an interpretive endeavor,<br />

mediated by the minds of the participant(s) and the researcher and by unconscious<br />

processes (Hunt, 1989). The participant is not just a source of in<strong>for</strong>mation and the<br />

researcher is not just an objective observer, diagnosing a person or system in order to<br />

classify it in a typology or link it to a theoretical concept (Edelson, 1988; Vansina,<br />

1998). The researcher and participants are engaged in a relationship w<strong>here</strong><br />

unconscious dynamics are at play that can be meaningful. The assumption is that the<br />

subjectivity of the researcher generates data about what is going on in the system.<br />

“The researchers must face their own often unconscious emotional biases to situations of<br />

39


anxiety. (…) one must be maximally open to one’s own feelings and prejudicial ways of<br />

coping with anxiety so that, when stimulated to feel in a particular way, one can use the<br />

feeling as data about relationships in the client system.” (Hirschhorn, 1988, 249)<br />

Researchers have to stay in touch with their feelings and be alert to situations w<strong>here</strong><br />

they experience anxiety because this may be a sign that further exploration is<br />

required.<br />

It is critical to document the subjective dimension of the research process.<br />

Journalizing allows <strong>for</strong> a continuous process of self-monitoring or 'disciplined<br />

subjectivity' (Hutjes & van Buuren, 1992). It helps to make the assumptions and<br />

biases of the researcher explicit, how the researcher is being used in her role and it<br />

clarifies the distinction between personal dynamics and dynamics in the<br />

collaborative (Berg, 1988; Huffington & James, 1999; Bradbury & Bergmann<br />

Lichtenstein, 2000). Journalizing notes document the relevant issues <strong>for</strong> the research<br />

process itself, such as implicit assumptions, reasons <strong>for</strong> choosing a method of data<br />

collection, or the choice of a role (Hunt, 1989). It documents how data were<br />

produced, to what extent the researcher has projected assumptions or fantasies onto<br />

the case material, and it may reflect the connection between our intellectual and<br />

personal life. Journalizing helps the researcher to assess how the anxiety provoked<br />

by the research may lead to a defensive use of methodology, a defensive negotiation<br />

of role, and a distortion in the perception and interpretation of the data (Devereux,<br />

1967; Hunt, 1989; Clarke, 2002; Meek, 2003). Every researcher has hidden<br />

assumptions about the research subject. “In journalizing the goal is not to remove biases -<br />

that would be impossible - but instead to render them conscious” (Bradbury & Bergmann<br />

Lichtenstein, 2000, 559). Journalizing stimulates an attitude of curiosity, inquiry and<br />

exploration. The researcher can document premature hunches, questions, worries,<br />

and fears. This enables <strong>for</strong>mulation of working hypotheses as the process unfolds.<br />

To conclude, journalizing is useful to document the dynamics in the research<br />

relationship. In the psychodynamic research tradition the relatedness in the research<br />

relationship is considered as an important source of data (Gilmore & Krantz, 1985).<br />

40


'Relatedness' refers to the quality of our relationship with others based on what is in<br />

our mind. “In contrast to ‘relationship’, relatedness refers to the quality of connectedness<br />

between individuals or groups that are internally represented, and which, being partially or<br />

fully unconscious, are unavailable as clear, articulated thoughts and feelings. As distinct from<br />

the manifest experiences of contact, which gives rise to one dimension of the qualities of a<br />

relationship, relatedness contains mutual projections, which stimulate other, deeper feelings,<br />

which in turn, may affect the relationship in powerful ways as well.” (Gould et al., 1999,<br />

700) A 'relationship' is based on actual personal contact (Shapiro & Carr, 1991).<br />

Unconscious images mediate the relationship between researcher and participant.<br />

"Any fieldwork encounter involves a shifting interplay of social interaction, unconscious<br />

fantasy, anxiety, and defense" (Hunt, 1989, 69). Transference and counter transference,<br />

projective identification and parallel processes are important dynamics in the<br />

research relationship (Gilmore & Krantz, 1985; Hunt, 1989; Clarke, 2002; Diamond &<br />

Alcorn, 2003). The first encounter between researcher and the participants can<br />

provide clues. It is important <strong>for</strong> the researcher to pay attention to her feelings,<br />

impressions, the attitude of the organizational members towards her, and events that<br />

give her a good or a bad feeling (Levinson, 1993). Important clues <strong>for</strong> transference<br />

reactions include strong emotions (e.g. anger, anxiety, shame, boredom, idealization)<br />

how the researcher is perceived, and which role is <strong>for</strong>ced upon her. Documentation<br />

of what happens in the research relationship and scrutinizing its dynamics may<br />

increase the meaning of the data obtained with other methods and provide access to<br />

more subtle aspects of experience. However, these dynamics can also disrupt the<br />

research (Devereux, 1967; Berg & Smith, 1988; Hunt, 1989; Gabriel, 1999).<br />

3.4. Methodological approach<br />

In this section I discuss the overall methodological choices and approach to the<br />

research. In the introductions of the cases and in the articles (parts 2 and 3) I discuss<br />

more in detail how I collected data and how I developed interpretations <strong>for</strong> each<br />

41


specific case study. The main methodological concerns in my research were the<br />

following:<br />

- Can I retrace the methodological choices I have made and why I made them?<br />

(transparency of the research process)<br />

- Can I retrace w<strong>here</strong> data come from? (transparency of data collection and data<br />

management)<br />

- Can I demonstrate that my interpretations are grounded in empirical data?<br />

(transparency of data analysis)<br />

3.4.1. Overall method: case study research<br />

For several reasons case study research was the most suitable approach <strong>for</strong> dealing<br />

with my research subject. Collaboration deals with interactions in the <strong>here</strong>-and-now,<br />

in a natural setting, in a complex and dynamic organizational context. To arrive at a<br />

deep understanding of the issues and dynamics in a collaborative process I included<br />

multiple data sources. As Yin (1994) suggests, I was part of the process and my<br />

presence and interventions influenced the system, but I had limited control over<br />

what actually happened. I entered the field with a theoretical pre-understanding,<br />

some insights from other experiences, and a number of explorative questions. During<br />

the research process I strived <strong>for</strong> a balance between structure and flexibility. I started<br />

the research with some general questions in order to explore the subject. The insights<br />

I developed in the pilot case allowed me to specify the research questions and<br />

influenced the way in which I approached data collection and data analysis in the<br />

subsequent cases (= flexibility). The research was an explorative and iterative process<br />

and the different cases influenced each other (Yin, 1994; Hutjes & van Buuren, 1992).<br />

"Indeed, a key feature of theory-building in case research is the freedom to make adjustments<br />

during the data collection process" (Eisenhardt, 1989, 539). The intention of my research<br />

was to identify important issues and dynamics in collaborative processes embedded<br />

in a particular context and to develop theoretical insights. For a long time I struggled<br />

to find a relevant concept to describe the phenomenon I was studying (see chapter 1).<br />

In the course of my research I redefined and changed the concept. This is not unusual<br />

42


in grounded research, because "(…) the construct, its definition, and measurement often<br />

emerge from the analysis process itself, rather than being specified a priori" (Eisenhardt,<br />

1989, 542).<br />

In this research I have treated each case as a single case. In two cases I collected data<br />

by documenting an action research (erosion case and foster care case). In these cases<br />

the research was ‘problem driven’ and the researcher(s) played a role in solving the<br />

problem (Gabriel, 1999). Long gives the following definition: “Action research is a type<br />

of problem-driven research which diminishes the distance between researcher and researched;<br />

it emphasizes the active involvement of both researcher and researched in the process of<br />

knowledge generation through active interventions.” (Long, 1999, 262). In the third case<br />

(river valley) my role was more like an ethnographer, because I had to negotiate<br />

access to the field, t<strong>here</strong> was no ‘problem’ to solve <strong>for</strong> the research team, and my<br />

position was mainly one of observer (Schein, 1987a). The cases were too different to<br />

make a structured cross-case analysis (Yin, 1994). In part four, I will draw learnings<br />

from the three cases and look <strong>for</strong> differences and similarities in the findings.<br />

3.4.2. Systematic and structured approach to data collection<br />

The approach in my research was not purely inductive. I started the analysis from a<br />

theoretical pre-understanding, based on a thorough review of the literature. This<br />

theoretical framework and the assumptions I held, presented in chapters 1 and 2,<br />

provided the organizing principle in my research. In the case studies I have coupled<br />

my theoretical pre-understanding with empirical material. This kind of research is an<br />

iterative process moving back and <strong>for</strong>th between theoretical concepts and empirical<br />

data. Gabriel (1999, 259) describes this position as follows: “Research and theory are<br />

closely inter-related processes: it is not possible to research or even observe the world, unless<br />

we have some frame of reference obtained from a tacit or explicit theory. Nor is it possible to<br />

theorize without having some conceptual and methodological ideas of how theories may be<br />

corroborated through research. Thus, neither research nor theory are purely cerebral<br />

processes; they are social practices, subject to specific disciplines and controls, and involving<br />

communities of practitioners and traditions of testing and presenting.”<br />

43


In each case I used data triangulation, as suggested in case study research (Yin, 1994).<br />

This enabled me to arrive at a ‘thick description’ of the process starting from the<br />

'wholeness' of the data (Yin, 1994; Hutjes & Van Buuren, 1992; Flick, 2002). It allowed<br />

me to capture the complexity and dynamic nature of the process and to interpret the<br />

data in their context. Direct participation and observation provided the main data<br />

<strong>for</strong> my research. I observed relevant meetings in each project. This allowed me to<br />

observe the 'system-in-interaction' while participating in it. This approach was<br />

relevant to deal with the research questions, because I wanted to understand the<br />

process from within. Thus I could experience all the phenomena (e.g. emotions,<br />

metaphors, stories) without explicitly having to elicit them (Gabriel, 1999). These<br />

observations resulted in field notes, which also included ‘journalizing notes’.<br />

In the three cases I interviewed the main actors in the collaborative. In the river<br />

valley case and the foster care case I also interviewed a wider range of stakeholder<br />

representatives in the domain. The aim of interviewing was to document the<br />

subjective experiences of the participants (accounts). It provided additional insight in<br />

the critical issues and their meaning <strong>for</strong> those involved (Clarke, 2002; Rubin & Rubin,<br />

1995; Seidman, 1991; Kvale, 1996). It is difficult to gain access to the latent or<br />

unconscious aspects of organizational life, because they are the result of defensive<br />

responses. T<strong>here</strong> are specific methods to stimulate 'free association' and fantasy in<br />

participants (Hunt, 1989; Gould, 1987; Barry, 1994; Gabriel, 1999). I did not, however,<br />

rely on psychodynamic methods <strong>for</strong> data collection (e.g. metaphors, social<br />

dreaming), because they were too unfamiliar and may have provoked resistance in<br />

the interviewees. In the foster care case I used a critical incident interview which is<br />

used by a wide range of researchers (Gabriel, 1999; Chell, 2004).<br />

In each case documents helped to reconstruct the antecedents of the collaborative<br />

initiative, the features of the problem domain, the historical, socio-political and<br />

institutional context, and the <strong>for</strong>mal aspects of the collaborative (e.g. objectives). I<br />

44


assumed it is not possible to understand the dynamics in a system without situating<br />

them in the wider context.<br />

A first step in solid theory building is the transparency of data collection. I used the<br />

following principles as systematically as possible:<br />

- Structured field note taking, marking a distinction between literal quotes,<br />

descriptions, and personal reflections.<br />

- Systematic documentation of personal reflections (‘journalizing’).<br />

- Clear and complete descriptions of the context of data collection (e.g. date,<br />

setting, relevant in<strong>for</strong>mation about the participants) in order to arrive at a<br />

vivid description of the important aspects of the study ('the whole picture')<br />

(descriptive clarity).<br />

- Systematic typing out of field notes using the same structure.<br />

- Clear description of procedures used, indication of sources of in<strong>for</strong>mation,<br />

in<strong>for</strong>mation about the data gathering process (e.g. gaining access, length of<br />

time spent on data collection, amount of data collected) (procedural rigor).<br />

I systematically typed out my field notes, made data summaries and overviews<br />

based on interviews and observations. The data files were organized in a structured<br />

way. I paid close attention to data management (Miles & Huberman, 1994) using the<br />

following guidelines:<br />

- Systematic filing and organizing of different kinds of data (e.g. interviews,<br />

interaction moments, documents);<br />

- Careful management of the case study databases (Hutjes & van Buuren, 1994;<br />

Yin, 1994);<br />

- Systematic reconstruction of the chronology of the collaborative process<br />

indicating date, type of event, participants, content of the interaction, issues at<br />

stake and available documentation;<br />

- Reduction of the available data into categories based on clear criteria, <strong>for</strong> a<br />

different kind of handling and analysis.<br />

45


In part 2 and 3 I describe the methodological choices I have made <strong>for</strong> each case in<br />

order to make the research process transparent <strong>for</strong> an outsider.<br />

3.4.3. The internal quality and transparency of the research: a chain of evidence<br />

Data analysis begins at the moment of data collection: sharing, comparing, finding<br />

out and being curious about what is going on in the <strong>here</strong>-and-now of the situation.<br />

To substantiate my interpretations of the dynamics in the process, I constructed a<br />

transparent 'chain of evidence' (Hollway & Jefferson, 2000) from empirical data to the<br />

interpretation <strong>for</strong> each case. My aim was to develop robust interpretations grounded<br />

in empirical data and to make the research process as a whole transparent,<br />

consistent, and rigorous in an ongoing ‘process of validating’ (Mishler, 1990). My<br />

intention was not to reproduce reality, but to represent it and to present a credible<br />

interpretation of the phenomena.<br />

The process of data analysis consists of three activities: data reduction, data display<br />

and conclusion drawing and verification. These three types of analysis <strong>for</strong>m an<br />

"interactive, iterative cycle" (Huberman & Miles, 1988, 362). In order to describe<br />

dynamics of direction setting, I categorized the issues and looked <strong>for</strong> emerging<br />

patterns and dynamics in each case separately. The aim of my research was to<br />

develop contextualized insights that can be relevant <strong>for</strong> similar organizational<br />

settings. The insights provide a 'dynamic understanding', that can inspire further<br />

research.<br />

In order to arrive at solid interpretations I followed five principles <strong>for</strong>warded by<br />

Clarke (2002). In this section I only mention them briefly; they are further discussed<br />

in detail in the empirical part of my research.<br />

1. data triangulation (see previous paragraph)<br />

2. a systematic method <strong>for</strong> data analysis<br />

3. peer debriefing<br />

4. member check<br />

46


5. use of rules <strong>for</strong> interpretation<br />

I followed a systematic method <strong>for</strong> data analysis. For each case I made a process<br />

reconstruction. To start the analysis it was important to become intimately familiar<br />

with the case and to keep the ‘wholeness’ of the data in mind (Eisenhardt, 1989;<br />

Clarke, 2002; Hollway & Jefferson, 2000). During this process I took notes on themes<br />

and issues that emerged from the whole text. As I was interested in the manifest and<br />

latent issues and dynamics in the collaborative process, I asked myself: what is the<br />

‘message between the lines’ (Yin, 1994). Spradley (1980) considers such an overview<br />

as a particular kind of field notes. It is a provisional overview <strong>for</strong> analysis and<br />

interpretation.<br />

A next step was to start making links and look <strong>for</strong> similarities and differences in the<br />

material. In a first order analysis I remained close to the data and systematically<br />

compared and contrasted field notes of interviews and observations within each case<br />

in order to identify the critical issues (coding). Then I started to look <strong>for</strong> deeper<br />

patterns and dimensions of understanding. I tried to build an interpretation of the<br />

dynamics, by putting the data in a more theoretical perspective (second order<br />

analysis). The final step was an interpretation of the dynamics that unfolded around<br />

the issues.<br />

‘Peer debriefing’ was an important method to support reflection on the research<br />

process and to check emergent hypotheses with my colleagues (Clarke, 2002). In the<br />

three cases I worked with colleagues who acted as sparring partners ('investigator<br />

triangulation', Patton, 1987). In a continuous process of joint reflection (<strong>for</strong>mal and<br />

in<strong>for</strong>mal) I checked to what extent my experiences and insights were idiosyncratic or<br />

biased, or whether they were congruent with the experiences of my peers.<br />

Another method I have used is ‘member check’ or checking the findings and<br />

interpretations with the participants of the research. In doing so it is possible to<br />

buffer each progressive inductive cycle and to pay attention to the possible biases of<br />

47


the researcher(s). I integrated the responses of the participants as additional data<br />

(Hutjes & van Buuren, 1994; Huberman & Miles, 1988). In the three cases I presented<br />

the findings of interviews and observations to the relevant groups of stakeholder<br />

representatives. I also shared some writing (e.g. conference paper) with the key<br />

actors of some projects. In the river valley case, <strong>for</strong> instance, we had an agreement<br />

with the conveners that we would send them every text we produced about the case.<br />

We invited them to send us their feedback, which they sometimes did.<br />

A final principle is the use of criteria to arrive at robust interpretations. The literature<br />

presents several criteria <strong>for</strong> interpretation (Kets de Vries, 1993; Hirschhorn, 1988;<br />

Gould, 1993; Klein, 1996; Menzies Lyth, 1988; Levinson, 1993; Gabriel, 1999). The<br />

main rules include the following:<br />

- Interpretations need to be related to evidence and empirical data in order to<br />

avoid 'wild interpretations'.<br />

- The context (tasks and circumstances) of the collaborative needs to be taken<br />

into account to understand the dynamics in the collaborative.<br />

- Reliability and validity depend on a many times repeated process of<br />

establishing hypotheses and returning to concrete situations in the process to<br />

'test' , retest, refine and elaborate them.<br />

- The goal of interpretative work is to find a common thread that unifies many<br />

apparently disparate encounters, uncovering the purpose and meaning of a<br />

person's or a group's particular action and experience. Different observations<br />

are trans<strong>for</strong>med to a co<strong>here</strong>nt unity (thematic unity).<br />

- The interpretations do not produce irrefutable explanations. The<br />

interpretation has to be assessed on the basis of its economy and its ability to<br />

account <strong>for</strong> many phenomena.<br />

- The interpretation of parts is consistent with the interpretation of the whole;<br />

different signs or clues point in the same direction (internal consistency).<br />

Levinson (1993) argues that different researchers can arrive at different<br />

interpretations. The value of the interpretation, however, is determined by the<br />

48


‘evidence’ presented <strong>for</strong> the conclusions. My intention with this research was also to<br />

contribute to organizational research in<strong>for</strong>med by the system psychodynamic<br />

perspective, because it can provide complementary insights in processes of<br />

organizing. This point is elaborated in article 3.<br />

3.5. Relevance of this research<br />

3.5.1. Understanding the nature of collaborative processes<br />

After reviewing the multiparty literature, I identified some aspects that were missing<br />

and that seemed critical to a better understanding of collaborative work. A first<br />

aspect that is lacking is an in-depth understanding of the nature of collaborative<br />

processes. Gray (1989, 244) has pointed at the need <strong>for</strong> a "dynamic, process-oriented<br />

theory of interorganizational relations". It is critical to study the social dynamics<br />

(Bouwen & Taillieu, 2004). As I was particularly interested in how the participants in<br />

a collaborative process make progress come about, I studied ‘practices of<br />

collaboration’ (Huxham & Vangen, 2005). This is complementary to the approach in<br />

social psychology, which does not study overt behavior in natural settings (Schruijer,<br />

1990). This research is an attempt to understand the phenomenon of ‘group<br />

locomotion’ (Cartwright & Czander, 1960) in a collaborative context and to develop a<br />

psychological perspective on the ‘mechanisms that make things happen’ (Huxham &<br />

Vangen, 2000a). The system psychodynamic perspective allows <strong>for</strong> an understanding<br />

of the complexity of such processes. It relates different levels of organizational life<br />

(Krantz, 1985). It focuses on the individual, the group and the organizations and the<br />

way they are interconnected. Thus a rich, vivid and complex picture of collaborative<br />

dynamics can be established (Eisold, 1996).<br />

3.5.2. New perspectives on collaborative leadership<br />

Secondly, I was interested in how the concept of ‘leadership’ is translated in<br />

horizontal, participative, collaborative processes. I missed a process perspective on<br />

leadership in multiparty collaboration. As suggested by several authors, little<br />

research explores the enactment of ‘leadership’ in collaborative settings; leadership<br />

49


as a ‘process’ has received little scholarly attention (Huxham & Vangen, 2000a;<br />

Razzaque & Stewart, 1998; Ring & Van de Ven, 1994). According to Bryman (1996)<br />

qualitative research can be especially instructive when it comes to exploring<br />

processes of leadership. It enables an approach w<strong>here</strong> leadership is seen through the<br />

eyes of ‘leaders’ and ‘followers’, it is sensitive to the context w<strong>here</strong> leadership<br />

emerges, and it allows different questions and issues to be addressed. Kahn and<br />

Kram (1994) argue t<strong>here</strong> is little research on authority relations in collaborative ways<br />

of working, dealing with processes of authorizing, de-authorizing and internal<br />

models of authority. According to Schruijer and Vansina (1999) exploration and<br />

research is required in two domains. (1) Understanding the nature of collaborative<br />

processes that need to be 'led' to generate coordinate actions. (2) How persons in<br />

attributed positions handle the projected leader-expectations to enable the<br />

collaborative processes to be shared within that system of diversity. They argue that<br />

in order to understand the conditions <strong>for</strong> and outcome of ‘distributed leadership’ as a<br />

function, it is important to understand the group and organizational processes<br />

embedded in a sociopolitical and economic environment. By using a qualitative<br />

research approach focusing on the ‘process’, I contribute to insights in dynamics of<br />

leadership and direction setting when t<strong>here</strong> is no <strong>for</strong>mal leader.<br />

3.5.3. Understanding the latent and unconscious dynamics<br />

A third issue that requires further elaboration is a better understanding of the latent<br />

and unconscious dynamics in collaborative processes. Many authors (e.g. Kanter,<br />

1994; Mintzberg, Jorgensen, Dougherty & Westly, 1996) acknowledge the importance<br />

of relational aspects and communication in collaborative work. They do not,<br />

however, address underlying dynamics that can severely hinder collaborative work.<br />

The multiparty literature has mainly offered ‘rational’ responses to the difficulties of<br />

participating in a collaborative ef<strong>for</strong>t. The quality of collaborative processes and the<br />

relational and emotional challenges of collaborative work have not been explored<br />

thoroughly (Gould, Ebers, McVicker & Clinchy, 1999; Czander, 1993; Page, 2003).<br />

Little research has been conducted on relationship-based coalitions, including issues<br />

50


like in<strong>for</strong>mal relationships, underlying organizational normative systems, or<br />

in<strong>for</strong>mal roles (Crump & Glendon, 1998).<br />

The psychodynamic perspective on inter-organizational relations looks at the nature<br />

of transactions between parties, the inevitable conflicts that arise, the motivation <strong>for</strong><br />

inter-organizational collaboration, boundary and authority issues, internal images of<br />

authority and inter-group phenomena like 'scapegoating' (Czander, 1993; Higgin &<br />

Bridger, 1965; Gemmill & Elmes, 1993; Rice, 1990; Rice, 1965; Hinshelwood, 1987;<br />

Zagier Roberts, 1994b; Kahn & Kram, 1994). This perspective can deepen our insights<br />

in powerful irrational group and inter-organizational dynamics that may interfere<br />

with or even derail the most manifestly sensible relationships. These insights may<br />

provide an additional understanding of the frequently observed phenomena of<br />

anomie, deadlock, process loss, and 'collaborative inertia', or the observation that the<br />

output of collaborations is often slowed down or below the expectations (Carlisle &<br />

Leary, 1981; Huxham, 1996). Finally, it helps to understand the dynamics of<br />

facilitating interventions, processes and structures that foster creative and innovative<br />

work and help participants to reach agreement.<br />

3.6. References<br />

Abram, J. (1996). The Language of Winnicott. A Dictionary of Winnicott’s Use of Words.<br />

Karnac Books, London.<br />

Ackoff, R. (1997). Systems, Messes and Interactive Planning. In Trist, E., Emery, F. &<br />

Murray, H. (Eds.) The Social Engagement of Social Science. A Tavistock Anthology.<br />

Volume III: The Socio-Ecological Perspective. Philadelphia: PENN, pp. 417-438.<br />

Adams, G. & Diamond, M.A. (1999). Psychodynamic Perspectives on Organizations:<br />

Identity, Politics, and Change. American Behavioral Scientist, 43 (2), 221-224.<br />

Amado, G. & Amato, R. (2001). Organizational change theories and practices: a critical<br />

review. In Amado, G. & Ambrose, A. (Eds.) The Transitional Approach to Change.<br />

London: Karnac, pp.87-118.<br />

Amado, G. & Ambrose, A. (Eds.) (2001). The Transitional Approach to Change. London:<br />

Karnac.<br />

51


Amado, G. & Vansina, L. (Eds.) (2005). The Transitional Approach in Action. London:<br />

Karnac.<br />

Ambrose, A. (2001). An introduction to transitional thinking. In Amado, G. &<br />

Ambrose, A. (Eds.) The transitional approach to change. London: Karnac, 1-28.<br />

Anderson, D. & White, J.D. (2000). Psychoanalytic Organizational Theory: Comparative and<br />

Philosophical Perspectives. Paper presented at the 13th Conference of the Public<br />

Administration Theory Network, Fort Lauderdale, Fl, January.<br />

Armstrong, D. (2005). The organization in the mind. London: Karnac.<br />

Barry, D. (1994). Making the invisible visible: symbolic means <strong>for</strong> surfacing<br />

unconscious processes in organizations. Organizational Development Journal, 12 (4),<br />

37-48.<br />

Bass, B.M., (1990). Bass & Stogdill's Handbook of Leadership. Theory, Research, and<br />

Managerial Applications. Third Edition. New York: The Free Press.<br />

Bennis, W.G. & Shepard, H.A. (1956). A theory of group development. Human Relation,<br />

9 (4), 415-457.<br />

Berg, D.N. (1988). Anxiety in the Research Relationships. In Berg, D.N. & Smith, K.K.<br />

(Eds.) The Self in Social Inquiry. Researching Methods. Newbury Park, Cali<strong>for</strong>nia: Sage<br />

Publications, pp. 213-228.<br />

Berg, D.N. & Smith, K.K. (1988). The clinical demands of research methods. In Berg,<br />

D.N. & Smith, K.K. (Eds.) The Self in Social Inquiry. Researching Methods. Newbury<br />

Park, Cali<strong>for</strong>nia: Sage Publications, pp. 21-34.<br />

Bilimoria, D., Wilmot, T.B. & Cooperrider, D.L., (1996). Multi-organizational<br />

Collaboration <strong>for</strong> Global Change. New Opportunities <strong>for</strong> Organizational Change<br />

and Development. In Woodman, R. & Pasmore, W. (Eds.) Research in Organizational<br />

Change and Development, Volume 9, pp. 201-236.<br />

Bion, W.R. (1961). Experiences in Groups. London: Routledge.<br />

Bion, W.R. (1970). Attention and Interpretation. London: Karnac Books.<br />

Boalt Boëthius, S. (1999). In the Nick of Time: Reactivating an Organization through<br />

Leader-initiated Interactions with Members of Staff. In French, R. & Vince, R. (Eds.)<br />

Group Relations, Management and Organization. Ox<strong>for</strong>d University Press, 173-189.<br />

Bouwen, R. & Taillieu, T. (2004). Multiparty collaboration as social learning <strong>for</strong><br />

interdependence: Developing relational knowing <strong>for</strong> sustainable natural resource<br />

management. Journal of Community and Applied Social Psychology, 14, 137-153.<br />

Bowles, M. (1997). The Myth of Management: Direction and Failure in Contemporary<br />

Organizations. Human Relations, 50 (7), 779-803.<br />

52


Bradbury, H. & Bergmann Lichtenstein, B.M. (2000). Relationality in Organizational<br />

Research: Exploring The Space Between, Organization Science, 11 (5), September-<br />

October, 551-564.<br />

Bridger, H. (1990). The discovery of the therapeutic community: The Northfield<br />

experiments. In Trist, E. & Murray, H. (Eds.), The Social engagement of Social Science,<br />

Volume I, The socio-psychological perspective, London: Free Association Books, pp. 68-<br />

87.<br />

Brown, M.H. & Hosking, D. (1986). Distributed leadership and skilled per<strong>for</strong>mance as<br />

successful organization in social movements. Human Relations, 39 (1), 65-79.<br />

Bryman, A. (1996). Leadership in Organizations. In Clegg, S.R., Hardy, C. & Nord,<br />

W.R. (Eds.), Handbook of Organization Studies. London: Sage.<br />

Bryson, J. & Crosby, B.C. (1992). Leadership <strong>for</strong> the Common Good: tackling Public Problems<br />

in a Shared-Power World. San Francisco: Jossey-Bass.<br />

Cardona, F. (1999). The Team as a Sponge: How the Nature of the Task affects the<br />

Behaviour and Mental Life of a Team. In French, R. & Vince, R. (Eds.) Group<br />

Relations, Management and Organization. Ox<strong>for</strong>d University Press, 239-250.<br />

Carlisle, J. & Leary, M. (1981). Negotiating groups. In Hackman, J. (Ed.) Groups at work<br />

(and those that don’t): creating conditions <strong>for</strong> effective teamwork. San Francisco: Jossey-<br />

Bass, pp. 165-188.<br />

Carr, W. (2001). The Exercise of Authority in a Dependent Context. In Gould, L.G.,<br />

Stapley, L.F. & Stein, M. (Eds.) The Systems Psychodynamics of Organizations.<br />

Integrating the Group Relations Approach, Psychoanalytic, and Open Systems<br />

Perspectives. London: Karnac, 45-66.<br />

Cartwright, D. & Zander, A. (Eds.) (1960). Group Dynamics. Research and Theory. Second<br />

Edition. New York: Harper & Row.<br />

Chell, E. (2004). Critical Incident Technique. In Cassell, C. & Symon, G. (Eds.), Essential<br />

Guide to Qualitative Methods in Organizational Research. London: Sage, pp. 45-60.<br />

Chisholm, R.F. (1998). Developing Network Organizations. Learning from Practice and<br />

Theory. Reading: Addison-Wesley.<br />

Chisholm, R.F. & Elden, M. (1993). Features of Emerging Action Research, Human<br />

Relations, 46 (2), 275-297.<br />

Chrislip, D. & Larson, C. (1994). Collaborative leadership: How citizens and civic leaders can<br />

make a difference. San Francisco: Jossey-Bass.<br />

Clarke, S. (2002). Learning from experience: psycho-social research methods in the<br />

social sciences. Qualitative Research, 2 (2), 173-194.<br />

53


Crump, L. & Glendon, I. (1998). A Multiparty Negotiation Framework: Building Bridges<br />

Across Multiparty Domains. Paper presented at the 5th National Mediation<br />

Conference, Brisbane, Australia.<br />

Cummings, T.G. & Worley, C.G. (2001). Essentials of Organization Development and<br />

Change. South-Western College Publishing, Cincinnati, Ohio.<br />

Czander, W.M. (1993). The Psychodynamics of Work and Organizations. Theory and<br />

Application. New York: Guil<strong>for</strong>d Press.<br />

Czander, W. (1997). Work Related Fantasies. Corporate Downsizing and Teambuilding,<br />

paper presented at the International Society <strong>for</strong> the Psychoanalytic Study of<br />

Organizations Symposium, June.<br />

de Board, R. (1978). The Psychoanalysis of Organizations. A psychoanalytic approach to<br />

behaviour in groups and organizations. London: Tavistock Publications.<br />

Denhardt, R. (1981). The Shadow of Organization. Regents Press of Kansas.<br />

Devereux, G. (1967). From Anxiety to Method in the Behavioral Sciences. The Hague:<br />

Mouton & Co.<br />

Dewulf, A., Craps, M., Bouwen, R., Taillieu, T. & Pahl-Wostl, C. (2004). Integrated<br />

management of natural resources: uncertainty, ambiguity and the role of framing and<br />

reframing. Paper presented at the International Symposium on Uncertainty and<br />

Precaution in Environmental Management, Copenhagen, June.<br />

Diamond, M.A. & Allcorn, S. (1987). The Psychodynamics of Regression in Work<br />

Groups, Human Relations, 40 (8), 525-543.<br />

Diamond, M. & Alcorn, S. (2003). The cornerstone of psychoanalytic organizational<br />

analysis: psychological reality, transference and countertransference in the<br />

workplace. Human Relations, 56 (4), 491-514.<br />

Driver, M. (2003). Nothing clinical, just business? Reflections on psychoanalytically<br />

grounded organizational diagnosis and intervention. Human Relations, 56 (1), 39-59.<br />

Druckman, D. (Ed.) (1977). Negotiations. Social-psychological perspectives. London: Sage<br />

Publications.<br />

Edelson, M. (1988). The Hermeutic Turn and the Single Case Study in Psychoanalysis.<br />

In Berg, D.N. & Smith, K.K. (Eds.) The Self in Social Inquiry. Researching Methods.<br />

Newbury Park, Cali<strong>for</strong>nia: Sage Publications, pp. 71-106.<br />

Eisenhardt, K.M. (1989). Building Theories from Case Study Research. Academy of<br />

Management Review, 14 (4), 532-550.<br />

Eisold, K. (1996). Psychoanalysis today: implications <strong>for</strong> organizational applications.<br />

Free Associations, vol.6, part two, no.38, 174-191.<br />

54


Emery, F. & Trist, E. (1997). The Causal Texture of Organizational Environments. In<br />

Trist, E., Emery, F. & Murray, H. (Eds.) The Social Engagement of Social Science. A<br />

Tavistock Anthology. Volume III: The Socio-Ecological Perspective. Philadelphia: PENN,<br />

pp. 53-65.<br />

Feyerherm, A.E. (1994). Leadership in Collaboration: A Longitudinal Study of Two<br />

Inter-organizational Rule-Making Groups. Leadership Quarterly, 5 (3-4), 253-270.<br />

Feyerherm, A., (1997) Leading M.E.N.: Perspectives on leadership in multistakeholder<br />

environmental negotiations. Paper presented at the Academy of Management, Boston.<br />

Flick, U. (2002). An Introduction to Qualitative Research. Second Edition. London: Sage.<br />

French, R. & Vince, R. (1999). Learning, managing, and organizing: the continuing<br />

contribution of group relations to management and organization. In French R. &<br />

Vince, R. (Eds.) Group Relations, Management, and Organization. Ox<strong>for</strong>d University<br />

Press, Ox<strong>for</strong>d, pp. 3-19.<br />

Gabriel, Y. (Ed.) (1999). Organizations in Depth. The Psychoanalysis of Organizations.<br />

London: Sage.<br />

Gabriel, Y. & McCollom Hampton, M. (1999). Work groups. In Gabriel, Y. (Ed.)<br />

Organizations in Depth. The Psychoanalysis of Organizations, London: Sage, pp. 112-<br />

138.<br />

Gardner, M.R. (1989). Self Inquiry. Hillsdale: The Analytic Press.<br />

Geertz, C. (1973). The Interpretation of Cultures. New York: Basic Books.<br />

Gemmill, G. & Elmes, M. (1993). Mirror, Mask, and Shadow. Psychodynamic Aspects<br />

of Inter-group Relations. Journal of Management Inquiry, 2 (1), 43-51.<br />

Gibb, C.A., (1954) Leadership, in G. Lindzey (Ed.), Handbook of social psychology,<br />

Volume Two, Reading: Addison-Wesley, pp. 877-917.<br />

Gibb, C.A., (1969) Leadership, in G. Lindzey & E. Aronson (Eds.) The Handbook of Social<br />

Psychology, Volume Four, Second Edition, Reading: Addison-Wesley, pp. 205-282.<br />

Gilmore, T.N. (1997). The social architecture of group interventions. In Neumann, J.E.,<br />

Kellner, K. & Dawson-Sheperd, A. (Eds.) Developing Organisational Consultancy.<br />

London: Routledge, pp. 32-48.<br />

Gilmore, T.N. & Krantz, J. (1985). Projective identification in the consulting<br />

relationship: exploring the unconscious dimensions of a client system, Human<br />

Relations, 38 (12), 1159-1177.<br />

Gould, L.J. (1987). A Methodology <strong>for</strong> Assessing Internal Working Models of the<br />

Organization: Applications to Management and Organizational Development Programs.<br />

Paper presented at the 1987 Annual Meeting of the International Society <strong>for</strong> the<br />

Psychoanalytic Study of Organizations, October 24-25, New York.<br />

55


Gould, L. J. (1993). Gebruik van psychoanalytische kaders voor de analyse van<br />

organisaties. In Kets de Vries (Ed.), Organisaties op de divan; gedrag en verandering<br />

van organisaties in klinisch perpectief, Schiedam: Scriptum Books, pp. 39-54.<br />

Gould, L.J., Ebers, R. & McVicker Clinchy, R. (1999). The Systems Psychodynamics of a<br />

Joint Venture: Anxiety, Social Defenses and the Management of Mutual<br />

Dependence. Human Relations, 52 (6), 697-722.<br />

Gould, L.J., Stapley, L.F. & Stein, M. (Eds.) (2001). The Systems Psychodynamics of<br />

Organizations. Integrating the Group Relations Approach, Psychoanalytic, and Open<br />

Systems Perspectives. London: Karnac.<br />

Gray, B. (1985). Conditions Facilitating Inter-organizational Collaboration. Human<br />

Relations, 38 (10), 911-936.<br />

Gray, B. (1989). Collaborating: Finding Common Ground <strong>for</strong> Multiparty Problems. San<br />

Francisco: Jossey Bass.<br />

Gronn, P., (2002). Distributed Leadership as a unit of analysis. Leadership Quarterly, 13<br />

(4), pp. 423-452.<br />

Guerin, M.L. (1997). Teamwork at Barton Company: A Psychodynamic Perspective, paper<br />

presented at the International Society <strong>for</strong> the Psychoanalytic Study of<br />

Organizations Symposium.<br />

Halton, W. (1994). Some unconscious aspects of organizational life: contributions from<br />

psychoanalysis. In Obholzer, A. & Zagier Roberts, V. (Eds.) The unconscious at work.<br />

Routledge, London, pp. 11-18.<br />

Hardy, C. & Phillips, N. (1998). Strategies of Engagement: Lessons from the Critical<br />

Examination of Collaboration and Conflict in an Inter-organizational Domain,<br />

Organization Science, 9 (2), 217-230.<br />

Higgin, G. & Bridger, H. (1965). The Psychodynamics of an Inter-group Experience,<br />

Tavistock Pamphlet No. 10, London: Tavistock Publications.<br />

Himmelman, A.T. (1996). On the Theory and Practice of Trans<strong>for</strong>mational<br />

Collaboration: From Social Service to Social Justice. In Huxham, C. (Ed.) Creating<br />

collaborative advantage. London: Sage Publications, pp. 19-43.<br />

Hinshelwood, R.D. (1987). What Happens in Groups. Psychoanalysis, the individual and the<br />

community. London: Free Association Books.<br />

Hinshelwood, R.D. (1989). A Dictionary of Kleinian Thought. London: Free Association<br />

Books.<br />

Hirschhorn, L. (1988). The Workplace Within. Psychodynamics of Organizational Life.<br />

Cambridge: MIT Press.<br />

56


Hirschhorn, L. (1990). Leaders and Followers in a Post-industrial Age: A<br />

Psychodynamic View. Journal of Applied Behavioral Science, 26 (4), 529-542.<br />

Hirschhorn, L. (1997). Reworking Authority; Leading and Following in the Post-Modern<br />

Organization. Cambridge Massachusetts: The MIT Press.<br />

Hirschhorn, L. (2002). The modern project and the feminisation of men. In<br />

Hinshelwood, R.D. & Chiesa, M. (Eds.) Organisations, anxieties & defences. Towards a<br />

psychoanalytic social psychology. London: Whurr Publishers, pp. 35-64.<br />

Hirschhorn, L. & T. Gilmore (1992). The New Boundaries of the “Boundaryless”<br />

Company. Harvard Business Review, May/June, v70, n3, 104-115<br />

Hollway, W. & Jefferson, T. (2000). Doing Qualitative Research Differently: Free<br />

Association, Narrative and the Interview Method. London: Sage.<br />

Hosking, D. & Fineman, S. (1990). Organizing Processes. Journal of Management Studies,<br />

27 (6), 583-604.<br />

Huberman, A.M. & Miles, M.B. (1988). Assessing Local Causality in Qualitative<br />

Research. In Berg, D.N. & Smith, K.K. (Eds.) The Self in Social Inquiry. Researching<br />

Methods. Newbury Park, Cali<strong>for</strong>nia: Sage Publications, pp. 351-381.<br />

Huffington, C. & James, K. (1999). Issues in Management Research, and the Value of a<br />

Psychoanalytic Perspective: A Case Study in Organisational Stress in a Japanese Multi-<br />

National Company. Paper presented at the International Society <strong>for</strong> the<br />

Psychoanalytic Study of Organizations Symposium, June.<br />

Huffington, C., Armstrong, D., Halton, W., Hoyle, L. & Pooley, J. (Eds.) (2004). Working<br />

below the surface. The emotional life of contemporary organizations. London: Karnac.<br />

Huffington, C., James, K. & Armstsrong, D. (2004). What is the emotional cost of<br />

distributed leadership? In Huffington, C., Armstrong, D., Halton, W., Hoyle, L. &<br />

Pooley, J. (Eds.) Working below the surface. The emotional life of contemporary<br />

organizations. London: Karnac, pp. 67-82.<br />

Hunt, J. (1989). Psychoanalytic Aspects of Fieldwork. Qualitative Research Methods.<br />

Volume 18. London: Sage.<br />

Hutjes, J.M. & van Buuren, J.A. (1992). De gevalsstudie: strategie van kwalitatief onderzoek.<br />

Meppel: Boom.<br />

Hutton, J., Bazalgette, J. & Reed, B. (1997). Organisation-in-the-mind. In Neumann, J.E.,<br />

Kellner, K. & Dawson-Shepard, A.(Eds.) Developing Organisational Consultancy,<br />

London: Routledge, pp. 113-126.<br />

Huxham, C. (Ed.) (1996). Creating collaborative advantage. London: Sage Publications.<br />

57


Huxham, C. & Vangen, S. (2000a). Leadership in the Shaping and Implementation of<br />

Collaboration Agendas: how Things happen in a (not quite) Joined-up World.<br />

Academy of Management Journal, 43 (6), 1159-1175.<br />

Huxham, C. & Vangen, S. (2000b). Ambiguity, complexity and dynamics in the<br />

membership of collaboration. Human Relations, 53 (6), 771-806.<br />

Huxham, C. & Vangen, S. (2003). Enacting leadership <strong>for</strong> collaborative advantage:<br />

dilemmas of ideology and pragmatism in the activities of partnership managers.<br />

British Journal of Management, 14, 61-76.<br />

Huxham, C. & Vangen, S. (2005). Managing to collaborate. The theory and practice of<br />

collaborative advantage. London: Routledge.<br />

Jaques, E. (1955). Social Systems as a Defense Against Persecutory and Depressive<br />

Anxiety. In M. Klein, P. Heimann & R. Money-Kyrle (Eds.) New Directions in<br />

Psychoanalysis, London: Tavistock Publication.<br />

Kahn, W.A. & Kram, K.E. (1994). Authority at Work: Internal Models and their<br />

Organizational Consequences. Academy of Management Review, 19 (1), 17-50.<br />

Kanter, R.M. (1994). Collaborative Advantage: the Art of Alliances, Harvard Business<br />

Review, 72 (4), 96-108.<br />

Katz, D. & Kahn, R.L. (1978). The Social Psychology of Organizations. Second Edition.<br />

New York: John Wiley & Sons.<br />

Kets de Vries, M.F.R. (1993). De rationaliteit van organisaties en managers: het einde<br />

van een mythe. In Kets de Vries, M.F.R. (Ed.) Organisaties op de divan; gedrag en<br />

verandering van organisaties in klinisch perspectief. Schiedam: Scriptum Books, pp. 19-<br />

35.<br />

Kets de Vries, M.F.R. (1999). What’s playing in the Organizational Theater? Collusive<br />

Relationships in Management, Human Relations, 52 (6), 745-773.<br />

Klein, L. (1996). On the Use of Psychoanalytic Concepts in Organisational Social Science,<br />

paper presented at the International Society <strong>for</strong> the Psychoanalytic Study of<br />

Organizations.<br />

Klein, L. (2001). Transitional interventions. In Amado, G. & Ambrose, A. (Eds.) The<br />

Transitional Approach to Change. London: Karnac, pp. 173-195.<br />

Klein, M. (1993). Notes on some schizoid mechanisms. In Envy and gratitude and other<br />

works 1946-1963. London: Karnac, pp. 1-24.<br />

Koppenjan, J. & Klijn, E.H. (Eds.) (2004). Managing uncertainties in networks. London:<br />

Routledge.<br />

58


Kram, K.E. (1988). On the Researcher’s Group Membership. In Berg, D.N. & Smith,<br />

K.K. (Eds.) The Self in Social Inquiry. Researching Methods. Newbury Park, Cali<strong>for</strong>nia:<br />

Sage Publications, pp. 247-265.<br />

Kramer, R. (1991). The more the merrier? Social psychological aspects of multiparty<br />

negotiations in organizations. Research on negotiation in organizations. Vol. 3,<br />

Greenwich, Connecticut: JAI Press.<br />

Krantz, J. (1985). Group Process Under Conditions of Organizational Decline, The<br />

Journal of Behavioral Science, 21 (1), 1-17.<br />

Krantz, J. (1990). Lessons from the Field: An Essay on the Crisis of Leadership in<br />

Contemporary Organizations, The Journal of Applied Behavioral Science, 26 (1), 49-64.<br />

Krantz, J. (1998). Anxiety & the New Order. In Klein, E.B. & Gabelnick, F. & Herr, P.<br />

(Eds.) The Psychodynamics of Leadership, Madison: Psychosocial Press, pp. 77-107.<br />

Krantz, J. & Gilmore, T.N. (1990). The Splitting of Leadership and Management as a<br />

Social Defense, Human Relations, 43 (2), 183-204.<br />

Kvale, S. (1996). InterViews. An Introduction to Qualitative Research Interviewing.<br />

Thousand Oaks: Sage Publications.<br />

Lapierre, L. (1993). Onderzoek van leiderschapsprocessen. In Kets de Vries, M.F.R.<br />

(Ed.) Organisaties op de divan; gedrag en verandering van organisaties in klinisch<br />

perspectief. Schiedam: Scriptum Books, pp. 75-93.<br />

Lau, J.B. & Shani, A.B. (Eds.) (1992). Behavior in Organizations. An Experiential Approach.<br />

Fifth Edition. Chicago: Irwin.<br />

Lawrence, G. (1998). Unconscious Social Pressure on Leaders. In Klein, E.B., Gabelnick,<br />

F. & Herr, P. (Eds.) The Psychodynamics of Leadership, Madison: Psychosocial Press,<br />

pp. 53-75.<br />

Levinson, H. (1993). Systematisch diagnosticeren van organisaties. In Kets de Vries,<br />

M.F.R. (Ed.) Organisaties op de divan; gedrag en verandering van organisaties in klinisch<br />

perspectief. Schiedam: Scriptum Books, pp. 55 -74.<br />

Lewin, K. (1951). Field theory in social science. New York: Harper.<br />

Lipman-Blumen, J. (1996). The Connective Edge. Leading in an Interdependent World. San<br />

Francisco: Jossey-Bass Publishers.<br />

Long, S. (1999). Action research, participative action research and action learning in<br />

organizations. In Gabriel, Y. (Ed.) Organizations in depth. London: Sage, pp. 262-266.<br />

Long, S., Newton, J. & Dalgleish, J. (2000). In the presence of the other: developing<br />

working relations <strong>for</strong> organizational learning. In Klein, E.B., Gabelnick, F. & Herr,<br />

P. (Eds.) Dynamic consultation in a changing workplace. Madison: Psychosocial Press,<br />

pp.161-192.<br />

59


Lowman, R.L. (1988). What is clinical method? In Berg, D.N. & Smith, K.K. (Eds.) The<br />

Self in Social Inquiry. Researching Methods. Newbury Park, Cali<strong>for</strong>nia: Sage<br />

Publications, pp. 173-187.<br />

MacRae, M. & Huxham, C. (2000). Collaborative Leadership: an Analysis of the Dynamics<br />

involved in Progressing a Collaboration, Paper presented at the Seventh International<br />

Conference on Multi-Organizational Partnerships and Co-operative Strategy,<br />

Leuven, July.<br />

McCann, J. & Selsky, J. (1997). Hyperturbulence and the Emergence of Type V<br />

Environments. In Trist, E., Emery, F. & Murray, H. (Eds.) The Social Engagement of<br />

Social Science. A Tavistock Anthology. Volume III: The Socio-Ecological Perspective.<br />

Philadelphia: PENN, pp. 185-202.<br />

McCollom, M (1995). Reevaluating group development: a critique of the familiar<br />

models. In Gillette, J. & McCollom, M. (Eds.): Groups in context. A new perspective on<br />

group dynamics. Lanham: University Press of America, pp. 133-154.<br />

McGrath, J.E. & Tschan, F. (2004). Dynamics in groups and teams. Groups as complex<br />

action systems. In Poole, M.S. & Van de Ven, A.H. (Eds.) Handbook of organizational<br />

change and innovation. Ox<strong>for</strong>d: University Press, pp. 50-72.<br />

Meek, H.W. (2003). The place of the unconscious in qualitative research. Forum<br />

Qualitative Social Research, 4 (2), May.<br />

Menzies, I. E. P. (1960). A case study in the functioning of social systems as a defense<br />

against anxiety, Human Relations, 13, 95-121.<br />

Menzies Lyth, I. (1988). Containing Anxiety in Institutions. Selected essays. Volume 1.<br />

London: Free Association Books.<br />

Midgaard, K. & Underdal, A. (1977). Multiparty conferences. In Druckman, D. (Ed.),<br />

Negotiations. Social-psychological perspectives. London: Sage Publications, pp. 329-<br />

345).<br />

Miles, M.B. & Huberman, A.M. (1994). An Expanded Sourcebook. Qualitative Data<br />

Analysis. Second Edition. Thousand Oaks: Sage Publications.<br />

Miller, E. (1990). Experiential learning in groups I: the development of the Leicester<br />

model. In Trist, E. & Murray, H. (Eds.) The Social Engagment of Social Science. Volume<br />

I. The Socio-Psychological Perspective. London: Free Associations Books, pp. 165-185.<br />

Miller, E.J. (1993). From Dependency to Autonomy: Studies in Organization and Change.<br />

London: Free Associations Books.<br />

Miller, E. (1997). Effecting organisational change in large complex systems: a<br />

collaborative consultancy approach. In Neumann, J.E., Kellner, K. & Dawson-<br />

Sheperd, A. (Eds.) Developing Organisational Consultancy, London: Routledge, pp.<br />

187-212.<br />

60


Miller, E.J. (1998). The Leader with the Vision; Is Time Running Out? In Klein, E.B.,<br />

Gabelnick, F. & Herr, P. (Eds.) The Psychodynamics of Leadership, Madison:<br />

Psychosocial Press, pp. 3-25.<br />

Miller, E. (1999). Dependency, Alienation, or Partnership? The changing relatedness of<br />

the individual to the enterprise. In French, R. & Vince, R. (Eds.) Group Relations,<br />

Management and Organization, Ox<strong>for</strong>d University Press, pp. 98-111.<br />

Miller, E.J. & Rice, A.K. (1967). Systems of Organization: The Control of Task and Sentient<br />

Boundaries. London: Tavistock Publications.<br />

Mintzberg, H., Jorgensen, J., Dougherty, D. & Westley, F. (1996). Some Surprising<br />

Things About Collaboration - Knowing How People Connect Makes It Work Better,<br />

Organizational Dynamics, Spring, 60-71.<br />

Mishler, E.G. (1990). Validation in inquiry-guided research: the role of exemplars in<br />

narrative studies, Harvard Educational Review, 60, 415-442.<br />

Mitroff, I. (1984). Stakeholders of the Mind. San Francisco: Jossey Bass.<br />

Morgan, G. (1986). Images of Organization, Cali<strong>for</strong>nia: Sage Publications.<br />

Mosse, J. (1994). The institutional roots of consulting to institutions. In Obholzer, A. &<br />

Zagier Roberts, V. (Eds.) The unconscious at work, London : Routledge, pp. 1-8.<br />

Neumann, J.E. (1999). Systems Psychodynamics in the Service of Political<br />

Organizational Change. In French, R. & Vince, R. (Eds.) Group Relations,<br />

Management and Organization. Ox<strong>for</strong>d University Press, 54-69.<br />

Neumann, J. & Hirschhorn, L. (1999). The Challenge of Integrating Psychodynamic and<br />

Organizational Theory, Human Relations, 52 (6), 683-695.<br />

Obholzer, A. (1994). Authority, power and leadership. Contributions from group<br />

relations training. In Obholzer, A. & Zagier Roberts, V. (Eds.) The unconscious at<br />

work, London: Routledge, pp. 39-47.<br />

Obholzer, A. (1999). Managing the Unconscious at Work. In French, R. & Vince, R.<br />

(Eds.) Group Relations, Management and Organization. Ox<strong>for</strong>d University Press, 87-97.<br />

Obholzer, A. & Miller, S. (2004). Leadership, followership, and facilitating the creative<br />

workplace. In Huffington, C., Armstrong, D., Halton, W., Hoyle, L. & Pooley, J.<br />

(Eds.) Working below the surface. The emotional life of contemporary organizations.<br />

London: Karnac, pp. 33-48.<br />

Obholzer, A. & Zagier Roberts, V. (Eds.) The unconscious at work, London: Routledge.<br />

Overlaet, B. & F. Barrett (2000). The Dynamics of Transitional Space, Paper submitted to<br />

the ODC Division of the Academy of Management Meeting, Toronto.<br />

61


Page, M. (2003). Leadership and collaboration challenges in not <strong>for</strong> profit partnerships.<br />

Organisational and Social Dynamics, 3 (2), 207-225.<br />

Patton, M.Q. (1987). How to use qualitative methods in evaluation. Newbury Park, CA:<br />

Sage.<br />

Razzaque, K. & Stewart, M. (1998). Networks and Nodes: Community Leadership in Area<br />

Regeneration. Paper presented at the Fifth International Conference on Multi-<br />

Organisational Partnerships and Co-operative Strategies, Ox<strong>for</strong>d, July.<br />

Reik, T. (1948). Listening with the Third Ear. The Inner Experience of a Psychoanalyst. New<br />

York: Grove Press.<br />

Rice, A.K. (1958). Productivity and social organization. New York and London: Garland<br />

Publishing.<br />

Rice, A.K. (1965). Learning <strong>for</strong> Leadership. Interpersonal and Inter-group Relations. London:<br />

Karnac Books.<br />

Rice, A.K. (1990). Individual, Group and Inter-Group Processes. In Trist, E. & Murray,<br />

H. (Eds.) The Social Engagement of Social Science. Volume I. The Socio-Psychological<br />

Perspective. London: Free Association Books, pp. 272-283.<br />

Ring, P.S. & Van de Ven, A.H. (1994). Developmental processes of cooperative<br />

interorganizational relationships. Academy of Management Review, 19 (1), 90-118.<br />

Roose, H., T. Taillieu & K. Sips (2000). The Reverse Effects of Governmental Policy and<br />

Regulations in the Social Service Sector in Flanders. In Taillieu, T. (Ed.) Collaborative<br />

Strategies and Multi-Organizational Partnerships, Leuven: Garant, pp. 147-154.<br />

Rubin, M. & Rubin, I. (1995). Qualitative Interviewing. The Art of Hearing Data. Thousand<br />

Oaks: Sage.<br />

Schein, E.H. (1987a). The Clinical Perspective in Fieldwork, Newbury Park, Cali<strong>for</strong>nia:<br />

Sage.<br />

Schein, E.H. (1987b). Process Consultation volume II. Lessons <strong>for</strong> Managers and Consultants.<br />

Addisson Wesley OD Series.<br />

Schonberg, A. (1998). Two Basic Assumptions in the Psychoanalytic Study of Organizations,<br />

Paper presented at the International Society <strong>for</strong> the Psychoanalytic Study of<br />

Organizations Symposium, June.<br />

Schruijer, S. (1990). Norm violation, attribution theory and attitudes in intergroup relations.<br />

Tilburg: Tilburg University Press.<br />

Schruijer, S., Taillieu, T. & Vansina, L. (1998). ‘Leadership’ in Collaborative Task-systems.<br />

Paper presented at the Fifth International Conference on Multi-Organisational<br />

Partnerships and Co-operative Strategies, Ox<strong>for</strong>d, July.<br />

62


Schruijer, S. & Vansina, L. (1999). Leadership and organizational change: an<br />

introduction. European Journal of Work and Organizational Psychology, 8 (1), 1-8.<br />

Schuman, S.P. (1996). The role of facilitation in collaborative groups. In Huxham, C.<br />

(Ed.) Creating collaborative advantage, London: Sage Publications, pp. 126-140.<br />

Schwandt, T.A. (1994). Constructivist, Interpretivist Approaches to Human Inquiry. In<br />

Denzin, N. & Lincoln, Y., Handbook of Qualitative Research.Thousand Oaks: Sage.<br />

Seidman, I.E. (1991). Interviewing as Qualitative Research. A Guide <strong>for</strong> Researchers in<br />

Education and the Social Sciences. New York: Teachers College Press.<br />

Segal, H. (1973). Introduction to the work of Melanie Klein. London: Karnac.<br />

Shapiro, E.R. (2000). The Changing Role of the CEO. Organisational and Social Dynamics,<br />

1 (1), 130-142.<br />

Shapiro, E.R. & Carr, A.W. (1991). Lost in Familiar Places. Creating New <strong>Connection</strong>s<br />

between the Individual and Society. New Haven: Yale University Press.<br />

Shaw, M.E. (1976). Dynamics of small group behavior. Second Edition. New York:<br />

McGraw-Hill Book Company.<br />

Smith, K.K. (1988). Epistemological problems in researching human relationships. In<br />

Berg, D.N. & Smith, K.K. (Eds.) The self in social inquiry. Researching Methods.<br />

Newbury Park: Sage, pp. 123-142.<br />

Smith, K.K. & Berg, D.N. (1987). Paradoxes of Group Life. Understanding Conflict,<br />

Paralysis, and Movement in Group Dynamics. San Francisco: The New Lexington<br />

Press.<br />

Smith, P.B. & Peterson, M.F. (1989). Leadership, Organizations and Culture. An Event<br />

Management Model. London: Sage.<br />

Spradley, J.P. (1980). Participant Observation. New York: Holt.<br />

Stokes, J. (1994). The unconscious at work in groups and teams. Contributions from the<br />

work of Wilfred Bion. In Obholzer, A. & Zagier Roberts, V. (Eds.) The unconscious at<br />

work. London: Routledge, pp. 19-27.<br />

Stokes, J. (1998). W<strong>here</strong> are the boundaries? Paper presented at the annual symposium of<br />

the International Society <strong>for</strong> the Psychoanalytic Study of Organizations, Jerusalem.<br />

Taillieu, T., Schruijer, S. & Vansina, L. (2000). Dynamiek van samenwerking tussen<br />

organisaties. In Bouwen, R., De Witte, K., De Witte, H. & Taillieu, T. (Eds.) Van<br />

groep naar gemeenschap. Liber Amoricum Prof. Dr. Leo Lagrou, Leuven: Garant, pp.<br />

147-164.<br />

Trist, E. (1983). Referent Organizations and the Development of Inter-Organizational<br />

Domains, Human Relations, 36 (3), 269-284.<br />

63


Van Buskirk, W. & Mc Grath, D. (1999). Organizational Cultures as Holding<br />

Environments : A Psychodynamic Look at Organizational Symbolism. Human<br />

Relations, 52 (6), 805-832.<br />

Van Maanen, J. (1988). Tales of the field: on writing ethnography. Chicago: University of<br />

Chicago Press.<br />

Vansina, L. (1998). The Individual in Organizations: Rediscovered or Lost Forever?<br />

European Journal of Work and Organizational Psychology, 7 (3), 265-282.<br />

Vansina, L. (1999). Towards a dynamic perspective on trust-building, In Schruijer, S.<br />

(Ed.) Multi-organizational partnerships and cooperative strategy, Dutch University<br />

Press, pp. 47-52.<br />

Vansina, L. (2000). The Relevance and Perversity of Psychodynamic Interventions in<br />

Consulting and Action Research. Concepts and Trans<strong>for</strong>mations, 5 (3), 321-348.<br />

Vansina, L. (2002). Making the best out of diversity: working towards collaboration between<br />

different interest groups. Paper presented at the annual symposium of the Society <strong>for</strong><br />

the Psychoanalytic Study of Organizations, Melbourne, June.<br />

Vansina, L. (2004). Over zin en onzin van psychodynamiek voor organisatieadviseurs.<br />

In Varwijk, W.G.J.M. & van Zijl, R.M.H.J. (Eds.) Strategie moet je samen doen. Visies<br />

op strategisch management uit theorie en praktijk. Liber amicorum Prof.Dr. Michel<br />

Vandenput. Ubbergen: Tandem Felix Uitgevers, pp. 159-177.<br />

Vansina, L. & Taillieu, T. (1997). Diversity in collaborative task-systems. European<br />

Journal of Work and Organizational Psychology, 6 (2), 183-199.<br />

Vansina, L., Taillieu, T. & Schruijer, S. (1998). “Managing” Multiparty Issues: Learning<br />

from Experience. In W. Pasmore & R. Woodman (Eds.) Research in Organizational<br />

Change and Development (vol. 11), JAI Press Inc., pp. 159-181.<br />

Vansina-Cobbaert, M.J. & Vansina, L. (1996). W. Bion : Insights into and contributions to<br />

group dynamics. (The original version was written and published in Dutch, Fall<br />

1996)<br />

Von Bertalanffy, L. (1950). An outline of General System Theory. British Journal <strong>for</strong> the<br />

Philosophy of Science, 1, 134-165.<br />

Wells, L. (1995). The group as a whole: a systemic socioanalytic perspective on<br />

interpersonal and group relations. In Gillette, J. and McCollom, M. (Eds.). Groups in<br />

context. A new perspective on group dynamics. Lanham: University Press of America,<br />

pp. 49-85.<br />

Winnicott, D.W. (1971). Playing and Reality. London: Routledge.<br />

Wood, D.J. & Gray, B. (1991). Toward a Comprehensive Theory of Collaboration,<br />

Journal of Applied Behavioral Science, 27 (2), 139-162.<br />

64


Yin, R.K. (1994). Case Study Research. Design and Methods. Second Edition. Applied Social<br />

Research Methods Series, Volume 5, Thousand Oaks, Cali<strong>for</strong>nia: Sage Publications.<br />

Yukl, G., (1999) An evaluative essay on current conceptions of effective leadership.<br />

European Journal of Work and Organizational Psychology, 8 (1), pp. 33-48.<br />

Zagier Roberts, V. (1994a). The organization of work. Contributions from open system<br />

theory. In Obholzer, A. & Zagier Roberts, V. (Eds.) The unconscious at work, London:<br />

Routledge, pp. 28-38.<br />

Zagier Roberts, V. (1994b). Conflict and collaboration. Managing inter-group relations.<br />

In Obholzer, A. & Zagier Roberts, V. (Eds.) The unconscious at work, London:<br />

Routledge, pp. 187-196.<br />

Zagier Roberts, V. (1994c). The self-assigned impossible task. In Obholzer, A. & Zagier<br />

Roberts, V. (Eds.) The unconscious at work, London: Routledge, pp. 110-118.<br />

Zagier Roberts, V. (1999). Isolation, autonomy, and interdependence in organizational<br />

life. In French, R. & Vince, R. (Eds.) Group Relations, Management, and Organization,<br />

Ox<strong>for</strong>d: University Press, pp. 224-238.<br />

65


PART 2: EMPIRICAL RESEARCH<br />

CASE STUDY 1: EROSION CASE<br />

Two senior researchers at the Center <strong>for</strong> Organizational and Personnel Psychology<br />

(COPP), CO1 and CO2 (see attachment 1), were invited to the erosion project because<br />

of their expertise in the domain of multiparty collaboration. The direct reason was<br />

that one of the university partners (soil expert) had collaborated with CO2 in a<br />

similar project in Ecuador. They decided to engage in this project because it seemed<br />

to fit well with ongoing research in the field of multiparty collaboration at the COPP.<br />

At the moment the project started, in September 1999, I had just joined the Center. I<br />

participated in the project from the beginning. The project provided me with an<br />

opportunity to be closely engaged in a multiparty project while simultaneously<br />

reviewing the literature. The project was the pilot study <strong>for</strong> my research. It helped<br />

me to understand the reality and challenges of collaborative work and to develop a<br />

focus <strong>for</strong> further research.<br />

Context and antecedents of the erosion project<br />

The case study was a European project sponsored by the Life Fund (1999-2003). An<br />

engineering firm took the initiative <strong>for</strong> the project. They developed a project proposal<br />

with three municipalities and submitted it to the funding organization. The aim of<br />

the project was to manage erosion and flooding problems in a restricted area in the<br />

province of Flemish Brabant (Belgium). The objective was to experiment with<br />

innovative solutions <strong>for</strong> erosion management, to be used as a demonstration <strong>for</strong><br />

other regions in Europe.<br />

66


The project included different types of organizations and social groups: profit<br />

organizations (2 consulting firms), not-<strong>for</strong> profit organizations (e.g. farmer’s union),<br />

universities (erosion specialists, organizational psychologists), government<br />

institutions (local, provincial and Flemish), and unorganized parties (e.g. residents<br />

living in the area). Approximately 15 stakeholders were represented in the steering<br />

group. The project group was responsible <strong>for</strong> coordinating the project. It was made<br />

up of representatives of the consulting firms, the university partners and the local<br />

authorities.<br />

Main events in the erosion project<br />

In article 1 the main events and issues are summarized (table 2), based on a process<br />

reconstruction.<br />

Research approach<br />

At the start of the project I did not have a clear research question yet. I focused on<br />

the collaborative process and the dynamics in the project group. Over time, I<br />

developed an interest in leadership issues in the project group. The research setting<br />

was made up of different <strong>for</strong>mal and in<strong>for</strong>mal meetings. My two colleagues and I<br />

were members of the project group, the central group in this collaborative. I<br />

participated in meetings of the project group, Steering group, and in in<strong>for</strong>mation<br />

sessions organized in the three municipalities (table 1). Moreover, I participated in<br />

occasional events, such as visits to potential sites <strong>for</strong> experimentation or a visit of a<br />

similar project in Holland. I also visited some farmers with one of the consultants<br />

and had in<strong>for</strong>mal talks with several people.<br />

In the project proposal the role <strong>for</strong> COPP members was described as: (1) facilitation<br />

of a ‘participative’ and ‘bottom-up’ process, involving multiple stakeholders, and (2)<br />

documentation of the collaborative process. In the course of the project we decided to<br />

split up the two roles: the senior researchers acted as facilitators and I took up the<br />

role of researcher. At several moments we involved other colleagues <strong>for</strong> specific<br />

67


tasks (e.g. join a consultant on his interview round among the farmers). My aim was<br />

to foster reflection and learning in the project by giving feedback to the participants.<br />

Secondly, I wanted to have a collaborative ‘experience’, collect data <strong>for</strong> my research,<br />

and clarify my research questions.<br />

I used data triangulation to document the process (table 1). During the <strong>for</strong>mal<br />

meetings I took extensive field notes. I interviewed the members of the project group.<br />

The focus of these interviews was on how the participant experienced the project:<br />

what according to them was happening, and what helped or hindered the process? I<br />

also consulted documents (e.g. project proposal, <strong>for</strong>mal reports). During the process<br />

I took journalizing notes.<br />

Date/Period Method of data<br />

September 1999 –<br />

June 2003<br />

July 2001 – July<br />

2002<br />

collection<br />

Participative<br />

observation<br />

– Semi-structured<br />

interviews<br />

– No taping<br />

– One<br />

interviewer<br />

68<br />

Participants/Setting Type of data<br />

– Field visits<br />

– Project group<br />

– Steering group<br />

– In<strong>for</strong>mation<br />

sessions at local<br />

municipalities<br />

Members of the<br />

project group (10):<br />

representatives of 3<br />

municipalities, 1<br />

soil expert, 6 junior<br />

and senior<br />

consultants of two<br />

consulting firms<br />

Field notes<br />

Interview notes


January 2002 Feedback sessions<br />

(‘member check’)<br />

Ongoing Documents<br />

69<br />

1 st with project<br />

leader<br />

2 nd with project<br />

group<br />

Documents<br />

produced by<br />

members of the<br />

project<br />

Ongoing Journalizing Comments,<br />

questions, etc in<br />

field notes<br />

Table 1: Overview of approach to data collection in the erosion case.<br />

Field notes<br />

E.g. project<br />

proposal, journal<br />

articles, <strong>for</strong>mal<br />

reports of meetings<br />

Journalizing notes<br />

Data analysis in this case study was based on a process reconstruction (chapter 3).<br />

This allowed me to capture the process as a whole and to document the issues that<br />

emerged over time. I did not analyze the data more in detail, as I was mainly<br />

interested in relevant issues <strong>for</strong> further research that emerged from the data. In<br />

article 1, I make sense of the issues and dynamics in this process. After the project I<br />

shared a conference paper with one of the key actors. On a continuous basis, my<br />

colleagues and I tried to make sense of what was happening in the project<br />

(‘researcher triangulation’). The three consultants-researchers jointly wrote an article<br />

based on this case study. I also organized a number of seminars w<strong>here</strong> I discussed<br />

the case with other researchers of the faculty (‘peer debriefing’). I had the<br />

opportunity to work on the paper in a focused way in a seminar on writing and<br />

publishing with the Academy of Management (see attachment 10).<br />

Conclusion of the erosion case<br />

The pilot case was an opportunity to learn about data collection and data<br />

management, data analysis, and writing up a case study. It helped me to make sense


of my role as researcher. This case also provided more focus in my research. Initially<br />

my interest was in ‘distributed leadership’. I discovered, however, that the concept of<br />

leadership was not of primary concern <strong>for</strong> the participants in this particular case.<br />

Instead I chose the concept of ‘dynamics of direction setting’ (see chapter 1). I<br />

re<strong>for</strong>mulated my research questions <strong>for</strong> the following cases:<br />

- What are the issues and dilemmas with which representatives in a collaborative<br />

are confronted?<br />

- How do the dynamics that unfold around those issues set the direction of the<br />

process?<br />

For the reader<br />

The article presented in the next section is, in broad lines, the paper I have submitted<br />

to Human Relations (see attachment 10). The reviewers asked me to submit a revised<br />

version of the paper (due: March 2006). I have made some minor adjustment to the<br />

paper presented <strong>here</strong>, based on their feedback. The references follow the criteria <strong>for</strong><br />

publication applied by Human Relations. T<strong>here</strong> is some overlap with the theoretical<br />

framework presented in part 1 and with the introduction of the case, which will<br />

hopefully not disturb the reader. The subtitles are not numbered.<br />

As this project was not a success story, the case description and quotes are<br />

anonymous <strong>for</strong> reasons of confidentiality (cover names). I have translated the quotes<br />

from Dutch. The participants often used colloquial speech or dialect. It was<br />

particularly challenging to express the essence of dialect, humor, word games,<br />

metaphoric language or indirect references to people or situations. The quotes in the<br />

case description are from interviews, unless mentioned otherwise.<br />

‘I’ in the article refers to me as researcher and principle author of the article. The<br />

reference ‘we’ includes the two senior organizational psychologists, involved as<br />

facilitators and co-researchers.<br />

70


“WHO’S IN CHARGE HERE?!” EMOTIONAL CHALLENGES AND EMERGENT<br />

DYNAMICS IN INTERDEPENDENT WORK (ARTICLE 1)<br />

Silvia Prins, Tharsi Taillieu & René Bouwen<br />

Introduction<br />

The purpose of this paper is to explore the emotional challenges of working together<br />

in a collaborative project and to make sense of the dynamics. We present an in-depth<br />

case study of a 4-year project in the domain of erosion prevention. Our research<br />

focuses on the emergent dynamics in the 'project group', responsible <strong>for</strong> leading the<br />

project. We try to make sense of why this collaborative ef<strong>for</strong>t ended up in<br />

'collaborative inertia', or the observation that the output of collaborations is often<br />

slowed down or below the expectations (Huxham, 1996). We explore why in this<br />

particular context, as in many collaborative groups, trust and openness were hard to<br />

develop, politics were rife, conflict was accommodated, feelings and processes were<br />

worked on covertly (Jarrett & Kellner, 1996). First we present the frames we used to<br />

make sense of the dynamics. Then we introduce the case and discuss the main<br />

themes that emerged. In the following section we present an interpretation of some<br />

of the dynamics and conclude with relevant issues <strong>for</strong> further research.<br />

Organizational frame: multiparty collaboration<br />

In order to find sustainable solutions <strong>for</strong> societal and ecological problems,<br />

multidisciplinary and multi-organizational involvement is required (Chisholm,<br />

1998). 'Multiparty collaboration' (Gray, 1989; Huxham, 1996; Huxham & Vangen,<br />

2005) is an organizational strategy designed to tackle such ‘meta-problems’ (e.g.<br />

nature conservation, unemployment). Gray (1989: 5) defines multiparty collaboration<br />

as “(…) a process through which parties who see different aspects of a problem can<br />

constructively explore their differences and search <strong>for</strong> solutions that go beyond their own<br />

limited vision of what is possible”. It involves a process of collective decision making<br />

and negotiation among key stakeholders of a problem domain, focused on the future<br />

71


development of that domain. Five characteristics are critical: (1) the stakeholders are<br />

interdependent; (2) solutions emerge by dealing constructively with differences; (3)<br />

joint ownership of decisions is involved; (4) stakeholders assume collective<br />

responsibility <strong>for</strong> the future direction of the domain; (5) collaboration is an emergent<br />

process (Gray, 1989).<br />

The multiparty context generates particular challenges that require an emotional and<br />

relational maturity from the representatives involved. These challenges include<br />

turbulent dynamics, unstable group identification, large differences in social identity,<br />

the difficulty to establish trust, and a higher complexity regarding in<strong>for</strong>mation, social<br />

processes, procedures and strategy (Kramer, 1991; Vansina, Taillieu & Schruijer,<br />

1998). The task is often of a self-designing nature, boundaries, norms and values are<br />

ambiguous. Formal systems and procedures to structure the process are absent.<br />

Ambiguity of roles, membership, status, representation, and authority relations<br />

characterize collaborative work (Chisholm & Elden, 1993; Huxham, 1996; Krantz,<br />

1998; Huxham and Vangen, 2000; 2005). The dynamics that emerge operate at<br />

different levels: within the parties, between the parties in the collaborative system<br />

and in the larger sociopolitical and economic environment (Schruijer & Vansina,<br />

1999). Representatives t<strong>here</strong><strong>for</strong>e have to be able to deal with complex relationships,<br />

unstable structures and a diversity of partners (Trist, 1983; Lipman-Blumen, 1996;<br />

Ackoff, 1997).<br />

Although many authors recognize the importance of communication and relational<br />

aspects (Kanter, 1994; Mintzberg, Jorgensen, Dougherty & Westly, 1996) t<strong>here</strong> is little<br />

research in this domain. Many authors point at the need to investigate the nature of<br />

collaborative processes and dynamics, the emotional challenges of developing and<br />

leading a collaborative ef<strong>for</strong>t, and how to foster shared collaborative processes (Gray,<br />

1989; Page, 2003; Schruijer & Vansina, 1999). The literature has mainly offered<br />

‘rational’ responses to the difficulties of participating in a collaborative ef<strong>for</strong>t (Gould,<br />

Ebers & McVicker Clinchy, 1999). In order to make sense of the specific nature of<br />

72


collaborative processes, we adopt the systems psychodynamic perspective on<br />

processes of organizing.<br />

Frame <strong>for</strong> analysis: the systems psychodynamic perspective<br />

This body of knowledge, originally developed by the Tavistock Institute of Human<br />

Relations, is founded in psychoanalysis, group dynamics and open system thinking<br />

(Miller & Rice, 1967; Bion, 1961; Menzies, 1960; Jaques, 1955). Some contemporary<br />

representatives of this paradigm focused on the nature and challenges of working in<br />

‘new’ <strong>for</strong>ms of organizing (Hirschhorn, 1988; 1990; 1997; Krantz, 1990; 1998;<br />

Huffington, Armstrong, Halton, Hoyle & Pooley, 2004). We will briefly present the<br />

main assumptions we hold in this research.<br />

The initial idea of starting a collaborative ef<strong>for</strong>t may be a rational decision, but the<br />

emergent process of collaboration is not fully 'rational' or conscious. We assume that<br />

working in a collaborative is influenced by rational, conscious as well as by hidden,<br />

emotional and unconscious motives. Most people tend to avoid uncertainty and<br />

anxiety and they often want to control their environment and make it predictable.<br />

T<strong>here</strong> are different sources of anxiety. First, we assume that working in a<br />

collaborative provokes anxiety because the organizational context is complex,<br />

ambiguous, and turbulent. The participants are confronted with interdependence,<br />

diversity, uncertainty about the outcome of the process, and they have to deal with<br />

fluid boundaries. The risk is that uncontained tensions result, <strong>for</strong> instance, in a<br />

tendency to reduce complexity (e.g. exclude stakeholders) or to close down the<br />

boundaries around the small group of those leading the collaborative ef<strong>for</strong>t. A<br />

second source of tension is the self-designing nature of the task. The participants<br />

involved in the process, need to define the task they are working on and establish<br />

sufficient common ground (Gray, 1989). Moreover, the primary task of a<br />

collaborative needs to be adapted continuously in response to changes within the<br />

collaborative and changes in the environment (Miller, 1993). Thirdly, the process is<br />

under-organized and ‘emergent’; t<strong>here</strong> are few processes and structures to contain<br />

73


the tensions of collaborative work (Krantz, 1998). The lack of containing structures,<br />

models of behavior, and clear leadership confronts the participants with uncertainty.<br />

The challenge is to develop new facilitating structures and processes Trist, 1983).<br />

Finally, the participants involved in a collaborative have to deal with a number of<br />

relational challenges. They have to be able to work with diversity, to develop an<br />

interdependent relationship and to work from a shared power base while t<strong>here</strong> are<br />

obvious asymmetries between the participants. This increases the potential <strong>for</strong><br />

conflict and may, <strong>for</strong> instance, result in covert rivalry, independent action, bilateral<br />

deal-making or exclusion of conflicting voices. These different sources of anxiety<br />

may trigger defensive responses and result in social defenses to ward off the tensions<br />

of collaborative work (Menzies, 1980; Krantz, 1998).<br />

In this research we assume t<strong>here</strong> is mutual influencing between the features of the<br />

collaborative (system) and the dynamics that emerge between the participating<br />

actors. System features generate particular patterns of individual, group and inter-<br />

organizational dynamics (Amado & Ambrose, 2001; Gould, Stapley & Stein, 2001).<br />

An obstacle to effective collaboration is the paradox that just as the necessity <strong>for</strong><br />

creative collaboration is growing, the rising level of diversity, uncertainty and<br />

anxiety pose major barriers to achieving it (Krantz, 1990; 1998). In the case analysis<br />

we try to make sense of the dynamics and to what extent they helped or hindered<br />

work on the task.<br />

Approach to the case study<br />

Two senior researchers in the field of organizational psychology were invited to the<br />

project because of their expertise in the domain of multiparty collaboration. The<br />

project seemed to fit well with ongoing research in the field of multiparty<br />

collaboration at the Center. At the moment the project started, I was involved. In the<br />

project proposal our role was described as: (1) facilitation of a ‘participative’ and<br />

‘bottom-up’ process, involving multiple stakeholders and (2) documentation of the<br />

collaborative process. In the course of the project we decided to split up the roles: the<br />

74


senior researchers acted as facilitators and I took up the task of documentation. My<br />

aim was double: foster reflection and learning in the project, and generate relevant<br />

questions <strong>for</strong> further research in multiparty collaboration.<br />

The outcome of this research is in-depth case study. In order to make sense of the<br />

nature of the process I used data triangulation: direct participation and observation,<br />

interviewing, journalizing (introspection) and written documents (Yin, 1994). I<br />

participated in all meetings of the project group, and other relevant gatherings (e.g.<br />

field visits, public in<strong>for</strong>mation sessions). I al kept journalizing notes to keep track of<br />

my personal feelings, ideas, questions and hunches. This allowed <strong>for</strong> a continuous<br />

process of self-monitoring or 'disciplined subjectivity' (Hutjes & van Buuren, 1994).<br />

Halfway the project (2001) I conducted 10 semi-structured interviews with the<br />

members of the project group. The focus was on how they perceived the process:<br />

what helped and hindered the work in the project? To validate the interview findings<br />

I gave feedback to the project leader and to the project group ('member check'). Their<br />

responses were included as additional data (Huberman & Miles, 1988). Written<br />

documents provided context in<strong>for</strong>mation (e.g. project proposal, journal articles).<br />

Based on these data I made a chronological process reconstruction. I focused on the<br />

‘meetings’ and the issues that emerged in the interactions. This enabled me to keep<br />

the whole process in mind without deconstructing or decontextualizing the data<br />

(Hollway & Jefferson, 2000). Along the process my colleagues and I tried to make<br />

sense of what was happening (peer debriefing, Clarke, 2002; Patton, 1987). We also<br />

had in<strong>for</strong>mal conversations with the project leaders and we gave <strong>for</strong>mal feedback to<br />

the project group (member check, Huberman & Miles, 1988; Hutjes & van Buuren,<br />

1994).<br />

Case: mud in the streets and water in the basement<br />

The regional manager of a large technical engineering firm initiated a project in the<br />

field of erosion management on farming land in three municipalities in Flanders<br />

(Belgium). He was a personal friend of a politician in the area who had complained<br />

75


that other regions in Flanders obtained European money and their municipality<br />

never did. The convener knew his way around in the labyrinth of European funding.<br />

He acted as 'convener' and invited relevant parties around the table. His personal<br />

and business relationships in the area facilitated this convening process. He<br />

convinced three municipalities to participate in the project. A public officer of one of<br />

the municipalities remembered "The convener came to sell the project. (…) They<br />

presented a nice picture to the local authorities. (…) We ended up in the project without<br />

really knowing how or what". The politicians of the municipalities were under pressure,<br />

because the problem of flooding and mud in the streets had been bothering the<br />

community <strong>for</strong> many years. With the local elections coming up (October 2000), this<br />

project provided an opportunity to do something about this problem. The convener<br />

worked out a project proposal <strong>for</strong> the European Community. His firm was hired to<br />

carry out the construction works <strong>for</strong> the project. This convening process took about<br />

one year.<br />

The objective of the erosion project was to develop innovative measures to manage<br />

erosion and to experiment with state of the art techniques. Relevant stakeholders<br />

were to be consulted during the phases of problem analysis, the search <strong>for</strong> solutions<br />

and implementation of the selected measures. The subsidizing organization<br />

(European Commission) strongly promoted a bottom-up, participative, multi-<br />

stakeholder approach in order to increase public support and to test the feasibility of<br />

solutions in consultation with multiple stakeholders. To meet the requirements of the<br />

funding organization, the erosion project included government institutions, profit<br />

organizations, and not-<strong>for</strong>-profit organizations. The project proposal specified a<br />

number of sub-systems to organize the participative process: a project group<br />

(coordination), a steering group (advisory body) and several work groups (work out<br />

solutions). In the case analysis we focus on the project group. It was composed of<br />

representatives from the three participating local municipalities, a technical<br />

engineering firm (the convening party) specialized in construction works, a<br />

participative engineering firm specialized in facilitation of public participation<br />

processes, erosion specialists from university, and organizational psychologists. The<br />

76


ole of each member of this group was specified in the project proposal. Figure 1 is a<br />

functional organizational chart which shows the relationships between the different<br />

subsystems (report project group meeting, December 1999).<br />

Scientific<br />

advice: erosion<br />

specialists,<br />

organizational<br />

psychologists<br />

Figure 1: Organizational structure of the erosion project.<br />

The 4-year project was approved and started in September 1999. Table 2 gives an<br />

overview of the phases and main events in the collaborative project, based on the<br />

process reconstruction.<br />

Commissioners: 3<br />

local authorities<br />

Project group<br />

Project team: 3<br />

consulting firms<br />

77<br />

Steering group:<br />

Flemish, Provincial,<br />

local authorities,<br />

farmers,<br />

environmental<br />

council<br />

Workgroups:<br />

farmers,<br />

environmental<br />

council,<br />

consultants, local


Phase Events Main challenges<br />

Convening<br />

phase<br />

(November<br />

1998-September<br />

1999)<br />

Problem<br />

definition<br />

(September<br />

1999 - March<br />

2000)<br />

Work out<br />

solutions<br />

(March 2000 -<br />

June 2001)<br />

– Convener solicits participation<br />

in project<br />

– Submission of project to<br />

European Commission<br />

– Start in September 1999<br />

– Identification of additional<br />

stakeholders<br />

– Field visits and selection of<br />

experimental sites<br />

– First meeting of steering group<br />

– 4 meetings of project group<br />

– Public in<strong>for</strong>mation sessions in<br />

3 municipalities<br />

– December 1999: first change in<br />

leadership<br />

– 2nd and 3rd meeting steering<br />

group<br />

– 5 meetings of project group<br />

– Field visit<br />

– Public in<strong>for</strong>mation sessions in<br />

3 municipalities<br />

– Start up of local work groups<br />

– October: local elections<br />

– June 2001: second change in<br />

leadership<br />

78<br />

– Identification of problem<br />

domain<br />

– Bring the parties with an<br />

interest in the problem<br />

domain around the table<br />

and generate commitment<br />

– Develop a definition of the<br />

problem domain which<br />

includes the interests and<br />

perspectives of a wide<br />

group of stakeholders<br />

– Arrive at a sense of<br />

common ground<br />

Include expert and<br />

experiential knowledge in the<br />

elaboration of solutions


Negotiations<br />

with farmers<br />

(July 2001 -<br />

March 2003)<br />

Implementation<br />

of solutions<br />

(March 2003 -<br />

September<br />

2003)<br />

– Municipalities complain about<br />

lack of results: convener<br />

intervenes<br />

– Farmers complain about the<br />

lack of in<strong>for</strong>mation regarding<br />

financial compensation<br />

– Two rounds of visits to<br />

individual farmers: no<br />

contracts<br />

– In<strong>for</strong>mation session <strong>for</strong><br />

individual farmers in each<br />

district: low attendance and<br />

handful of contracts signed<br />

– Flemish government approves<br />

new 'erosion policy' (December<br />

2001)<br />

– No meetings of project group<br />

– Part of the farmers sign<br />

individual contract with<br />

municipalities<br />

– 3 farmers implement<br />

experimental measures<br />

– No scientific or visual<br />

monitoring and evaluation of<br />

results<br />

– Publication of inventory<br />

report, 2 newsletters, small<br />

newspaper articles<br />

– Participation in in<strong>for</strong>mation<br />

sessions <strong>for</strong> local, regional and<br />

Flemish government,<br />

presentations at some<br />

conferences<br />

79<br />

Commitment of farmers to<br />

implement experimental<br />

solutions on their farmland<br />

– Demonstration of<br />

ownership by<br />

municipalities<br />

– Implementation and<br />

follow-up<br />

– Demonstration of the<br />

technical results and<br />

learnings<br />

Table 2: Overview of the phases, events and the main challenges in the erosion<br />

project.


T<strong>here</strong> were two changes in project leadership in the period of four years. With each<br />

change, the collaborative process took a different turn. The first project leader was a<br />

technical engineer, colleague of the convener. After a few weeks he was taken off the<br />

job by the board of his organization, because of an internal restructuring of<br />

responsibilities. The holding to which the technical consulting firm belonged had<br />

acquired a small Dutch engineering firm specialized in facilitation of public<br />

participation processes. Because of their expertise these 'participative' engineers took<br />

over project leadership. Due to this change in leadership, the convening party shifted<br />

from the role of convener and project leader to subcontractor, responsible <strong>for</strong> part of<br />

the technical solutions. This shift was not easy <strong>for</strong> them. "They had a hard time<br />

accepting it. They have invested a lot of work in it, but the project went to the other<br />

organization. (…) They had to give away their baby." (a technical engineer).<br />

The participative engineers led the process in a different way (e.g. interactive<br />

construction of solutions with the stakeholders) and they favored cheap, small-scale<br />

and ecological anti-erosion measures (e.g. small grass dams). This approach, which<br />

was more in line with the intention of the project proposal, was a threat to the<br />

business of the technical engineers. It endangered their contract with the pilot<br />

municipality to carry out civil engineering interventions (e.g. construction of water<br />

basins).<br />

Inertia emerged early in 2001, in the period be<strong>for</strong>e the second project leader left.<br />

Nothing seemed to happen, t<strong>here</strong> was little direct interaction among the parties<br />

involved, the negotiation process with individual farmers did not result in contracts<br />

and participation in the project, t<strong>here</strong> was little follow up of agreements, and<br />

everybody seemed to be waiting <strong>for</strong> others to make things happen. The third project<br />

leader described this phenomenon as, “In the beginning t<strong>here</strong> was a lot of enthusiasm,<br />

but then it collapsed like a pudding.” In June 2001 the second project leader left and his<br />

manager took over. He limited his role to budget management and handed over<br />

daily management of the project to a junior colleague who had been involved as<br />

80


assistant of the second project leader. From this point on t<strong>here</strong> were no more<br />

meetings of the project group, because "the budget <strong>for</strong> meetings is finished" (third<br />

project leader). Despite the focus on 'results' and 'action' t<strong>here</strong> was little outcome.<br />

In the final phase of the project 'ownership' of the problem became the central issue.<br />

The project group expected the municipalities to take over ownership, but this did<br />

not happen. This expectation, however, was never openly negotiated with the<br />

municipalities. A public officer blamed the consultants <strong>for</strong> having "too much respect"<br />

<strong>for</strong> the politicians and <strong>for</strong> not negotiating roles and responsibilities explicitly. In the<br />

summer of 2003, shortly be<strong>for</strong>e the <strong>for</strong>mal deadline, the project died a silent death.<br />

When I asked the in<strong>for</strong>mal project leader (telephone conversation, January 2004)<br />

whether t<strong>here</strong> were any visible results, he said "No, hardly. T<strong>here</strong> are only one or two<br />

small interventions."<br />

In the following section we discuss our observations. The main observation was an<br />

increasing discrepancy between the intentions and objectives of the project, and what<br />

the members of the project group were actually doing. Essential characteristics of the<br />

project proposal were: (1) develop 'source oriented' erosion control measures; (2)<br />

experimentation, innovation, demonstration and learning; (3) involvement of all<br />

relevant stakeholders in the different phases of the project. We try to make sense of<br />

what happened and why the project ended up in inertia and failure, based on themes<br />

that emerged during the interviews and during the reconstruction of the<br />

collaborative process. Sense making and interpretation were part of an iterative<br />

process, moving between empirical data and theoretical insights (Gabriel, 1999).<br />

Emergent themes<br />

From experimentation at the source to solving real problems in the streets<br />

In the course of the process the objective of the project shifted. The original intention<br />

to experiment with state of the art erosion techniques on farmland (source oriented)<br />

was replaced by a different objective. The politicians seemed more interested in<br />

81


solving problems of flooding and mud sedimentation in the streets and sewer system<br />

of their communities. For electoral reasons, it was more attractive <strong>for</strong> them to solve<br />

real and visible problems. The choice of some sites <strong>for</strong> experimentation, <strong>for</strong> instance,<br />

was inspired by the fact that a particular site was close to a residential area or near<br />

the residence of a politician. In these cases the choice of the sites was not determined<br />

by the <strong>for</strong>mal criteria <strong>for</strong> selection, such as ‘demonstration effect, opportunities <strong>for</strong><br />

measuring, and the on and off site effects of erosion’ (Technical Final Report, 2003).<br />

The technical engineers went along with the politicians. Their interest, as <strong>for</strong>malized<br />

in the project proposal, was to carry out civil engineering constructions.<br />

The participative engineers focused on experimentation with small scale<br />

interventions on farmland, such as the use of green fertilizers. They did notice the<br />

shift in objective. During a meeting of the project group (August 2000) the second<br />

project leader observed "Now I see measures that are influencing the environment<br />

downstream, while last time we agreed to concentrate on upstream interventions on farming<br />

land in collaboration with the farmers!" The objective had shifted from prevention of soil<br />

erosion on farmland (upstream) to flood prevention in the streets (downstream).<br />

Lack of common ground and interdependence<br />

In the course of the collaboration it became obvious t<strong>here</strong> was little common ground<br />

and hardly an integration of interests and objectives. Individual goals and positions<br />

of the members of the project group (e.g. business, scientific, public interests)<br />

prevailed and were not openly discussed around the table. One of the members of<br />

the project group made a comparison with projects in developing countries w<strong>here</strong><br />

the method of ‘participative problem analysis’ is used. People go along with the<br />

approach, but everybody knows <strong>for</strong> which specific solution the money is intended.<br />

This uneasy feeling was expressed by several members of the project group. A<br />

participative engineer observed: "Everybody has set his goal <strong>for</strong> this project.” One of the<br />

erosion specialists cynically stated "To put it crudely (…) now the money is in the pocket,<br />

all sorts of things are being done with it, and nobody cares how it is spent." It was as if the<br />

82


members of the project group tacitly agreed to each pursue their objectives, spend<br />

the money from the sponsor, and not take a too critical look at how it was spent.<br />

A critical factor was that most stakeholders expressed little interest in soil erosion. A<br />

member of the project group observed: "Nobody has sleepless nights because of erosion.<br />

That is probably the main problem." (Public officer). The farmers didn't perceive it as a<br />

major problem in terms of decreasing production or permanent loss of fertile soil. "O,<br />

this problem of erosion! We have had it <strong>for</strong> centuries and it never changes!" (a farmer). The<br />

convener stated, "It bothers them but they don't experience it as a problem". He also<br />

pointed at the lack of interests in soil erosion with the local authorities "They were not<br />

interested in erosion, but they were in the flooding problems in the streets, out of political<br />

interests." (Convener) This means that erosion was not a priority. T<strong>here</strong> was no sense<br />

of urgency, and no shared task to connect the stakeholders and drive interdependent<br />

work.<br />

From a multi-stakeholder approach to a ‘project’ approach<br />

The <strong>for</strong>mal objective of the project was to develop "an effective action program <strong>for</strong><br />

erosion management, integrating agricultural, community and ecological interests" (project<br />

proposal). The intention was to include representatives from the agricultural sector<br />

(e.g. farmers, landowners, and farmers union) the community (e.g. residents,<br />

municipalities, fire brigade) and from environmental groups (e.g. environmental<br />

council). At the start of the project the second project leader organized in<strong>for</strong>mation<br />

sessions at the three municipalities. He facilitated the construction of a joint<br />

definition of the problem domain. This approach demonstrated the interdependence<br />

of the stakeholders present in the room. The flow of events written up on cards on<br />

the wall of the meeting room showed that not only the farmers were to ‘blame’ <strong>for</strong><br />

erosion and flooding in the streets. The responsibility of the municipalities also<br />

became apparent. They were responsible <strong>for</strong> bad maintenance of the sewer and<br />

drainage system and <strong>for</strong> granting building permits in lower parts of the community<br />

that were known to flood on a regular basis. Residents were also identified as part of<br />

83


the chain. Many had moved in from cities and were not used to living with water,<br />

mud and dust. They complained more because they had a lower tolerance <strong>for</strong> the<br />

kind of problems that the local residents had known <strong>for</strong> many decades.<br />

The wider group of stakeholders was <strong>for</strong>mally represented in the steering group.<br />

This group was only convened three times in the course of the four year project. It<br />

was reduced to a <strong>for</strong>mal body and only had a marginal contribution to the project. In<br />

the period after the second project leader left it became obvious that the influence of<br />

the politicians and the technical engineers moved the project away from its original<br />

intention of involving multiple stakeholders. The project group was no longer<br />

convened and eventually most members of the project group worked separately (e.g.<br />

measure the experimental sites, prepare contracts <strong>for</strong> construction work, negotiate<br />

contracts with farmers, write articles) or stopped contributing.<br />

Dealing with diversity: differences in dominant logic<br />

Related to the previous issues was the observation that each member of the project<br />

group and of the wider group of stakeholders held a different ‘dominant logic’<br />

(Vansina, 2000) generating different assumptions, expectations and behaviors. This<br />

logic can be determined by many aspects, such as social identity (e.g. farmer,<br />

engineer, and scientist) or professional category (e.g. consultant, public officer). We<br />

present some observations focusing on how different representatives made sense of<br />

the stated ‘participative approach’ of the project and how two subgroups emerged in<br />

the system.<br />

According to the participative engineers participation meant "being prepared to<br />

work in the evening hours and to have an open debate with the parties concerned<br />

and jointly define the problem and possible solutions." They conceived their role as<br />

process facilitator focusing on sharing responsibility, negotiation, and integration of<br />

interests. For them the technical side of the project was not the main focus.<br />

"Technique plays a minor role in this project. T<strong>here</strong>’s a source of tension between on<br />

84


the one hand technical measures and behavioral change and on the other hand<br />

technology. (…) It is not about demonstrating that it works, that has happened<br />

be<strong>for</strong>e. But it's about sustainability and how you can mobilize people to make it<br />

happen. (…) It's a long term developmental process." (In<strong>for</strong>mal conversation, April<br />

2001) We supported this inclusive approach and tried to contribute to the design and<br />

facilitation of stakeholder participation.<br />

The technical engineers defined participation as "making a plan and asking <strong>for</strong> feedback"<br />

(first project leader). They in<strong>for</strong>med and consulted the stakeholders in view of<br />

constructing a better technical solution. The erosion specialists also held an expert<br />

logic and did not understand the need to invest so much time and ef<strong>for</strong>t in<br />

participation. "In the old days we only needed a good idea and publish a scientific article<br />

afterwards. Now someone has to have a real problem en the solution must be constructed with<br />

the end users. That is not self evident <strong>for</strong> us scientists. (…) We scientists think it is not really<br />

necessary. We already know it. But we have to give people the feeling that they are involved,<br />

that's what I have learned." The municipalities had little experience with participation<br />

and were surprised when they were asked to invite over 100 people to an<br />

in<strong>for</strong>mation session. "When the participative engineers came with their debate culture we<br />

had a good laugh” (public officer). Other stakeholders such as the farmers (“What do<br />

they want from us, they are so nice to us?!") and environmental group ("It is a fake<br />

democracy”) also had little confidence in the good intentions of the consultants.<br />

The convener admitted that the use of the notion ‘participation’ in the project<br />

proposal had been strategic: "Your project has a better chance if you mention it." When<br />

the project group was discussing the choice of the experimental sites, <strong>for</strong> instance, he<br />

said, "Lets keep it deliberately vague. (…) Let's give them the impression they can decide<br />

with us". The technical engineers conceived their role as technical experts and project<br />

managers. For them and <strong>for</strong> the local authorities this project was a temporary<br />

collaboration to solve specific problems driven by expert knowledge and political<br />

decision making. One of the engineers said, "They have the last word. It is politics. (…)<br />

85


We are in contact with the local municipalities using the classic method, through technical<br />

designs."<br />

This resulted in a polarization between two dominant logics: a solution-oriented,<br />

expert and politically driven approach versus an interactive and inclusive process<br />

stressing sustainability. The participative engineers observed the "<strong>for</strong>mation of blocks"<br />

and "two tracks sometimes crossed, but most of the time they were running in parallel". At<br />

several moments the second project leader tried to address the differences in logic in<br />

the project group. "T<strong>here</strong> are different visions in the project group: steering or not steering.<br />

(…) We do have the same objective, but our perspective on solutions differs. (…) Differences<br />

of opinion must be possible in our group." (August 2000). His interventions, however,<br />

did not result in an exchange about the meaning of participation, the underlying<br />

logic was left implicit, and the subgroups drifted apart.<br />

Role ambiguity: who's in charge <strong>here</strong>?<br />

The roles of the members of the project group were <strong>for</strong>malized in the proposal, but as<br />

the process unfolded members struggled with their roles or stepped out of role. The<br />

interviews revealed that most members found it hard to contribute. We will discuss<br />

the emergence of role ambiguity in the different members of the project group.<br />

The two changes in <strong>for</strong>mal project leadership were not intentional, but inspired by<br />

external circumstances. Each project leader attributed a different meaning to his role<br />

and worked with a different (implicit) logic. The first and third project leader used<br />

technical and procedural aspects to manage the project. The second project leader<br />

focused his energy on facilitation of the process and creating moments of direct<br />

interaction (e.g. field trip, in<strong>for</strong>mation sessions at municipality). Most members of the<br />

project group expressed the need <strong>for</strong> explicit and directive leadership from the<br />

<strong>for</strong>mal project leaders and they criticized them all. On reflecting back on his<br />

experience the second project leader had the overall impression that everybody felt<br />

committed but nobody felt responsible. He observed, “When the drive, the momentum<br />

86


disappeared in me, the whole project lost its momentum, it fell to pieces. Nobody was really<br />

committed to this project.” Most members of the project group admitted that his loss of<br />

motivation had a strong impact on the energy level in the project and on their<br />

personal drive. The members of the project group were disappointed in the project<br />

leaders and they, in turn, were disappointed in the group.<br />

T<strong>here</strong> were also ‘in<strong>for</strong>mal’ leaders. The first was the convener of the project who<br />

played a critical role behind the scene. He made visible, explicit interventions at two<br />

points in time when the project was in danger. He <strong>for</strong>cefully negotiated with the local<br />

authorities to restore their confidence in the project. The members of the project<br />

group had mixed feelings about his interventions. They admired him <strong>for</strong> the way he<br />

‘saved’ the project, and were relieved someone finally took charge. At the same time,<br />

however, they were suspicious about his intentions and wondered whether his<br />

business interests prevailed over the interests of the project. A participative engineer<br />

stated “This project is publicity in the area <strong>for</strong> his business. Even if it costs him money, I<br />

think he is willing to pay it." The convener used political activity in a way that was<br />

detrimental <strong>for</strong> the collaborative nature of the project. During one of his<br />

interventions, the third project leader exclaimed: “who’s in charge <strong>here</strong>?!”<br />

The second in<strong>for</strong>mal leader was a young engineer who had been involved in the<br />

project since the start. When the third project leader took over, he handed over<br />

project leadership to this young man, without publicly authorizing him to take the<br />

lead. This made it very hard <strong>for</strong> him to exercise his authority. He had great difficulty<br />

to determine his position: go along with the vision of the powerful technical<br />

engineers and 'betray' the project, or follow up on his own ideas and ‘fight’ <strong>for</strong> a<br />

participative approach?<br />

The municipalities were critical actors who did not fully play their role <strong>for</strong> several<br />

reasons. The project leaders never made an appeal on them and they did not contract<br />

roles and responsibilities. Initially the representatives of the local authorities were<br />

not even invited to project group meetings. Moreover each project leader had<br />

87


different expectations from the municipalities. The technical engineers did not<br />

perceive them as competent, interested or committed and they took over important<br />

tasks from them (e.g. writing financial reports). One of them commented "In Belgium<br />

the engineering firms drive those projects. (…) How the project is managed is not their<br />

business." The second project leader expected the municipalities to take decisions,<br />

determine the policy and drive the project. He said, “Here the advise and the decision<br />

were with the consultant, although not <strong>for</strong>mally. (…) The consultant is supposed to sit next<br />

to them, but was given a central role. (…) The hired people have to do all the work. They<br />

should be the motor. All they do is open the meeting." For him the role of the consultant<br />

was to give advice and to facilitate the process. The representative of the<br />

municipalities claimed they had 'no time' <strong>for</strong> the project. Towards the end of the<br />

project the members of the project started to blame the municipalities <strong>for</strong> not taking<br />

up ownership, although not openly. Open negotiation with the municipalities was<br />

perceived as risky and 'not done'. This lack of openness about role expectations and<br />

contracting led to ambiguous authority relations, suspicion, misunderstanding,<br />

inefficiency and an authority vacuum.<br />

The facilitators also suffered from role ambiguity. In the course of the collaboration<br />

our role was reduced from active facilitation to designing scenarios <strong>for</strong> meetings,<br />

writing articles, being shadow consultants, being observers, to being <strong>for</strong>gotten.<br />

Because the second project leader took up an explicit role as facilitator, we were in<br />

the background as his sparring partner. He stressed that in order to facilitate a<br />

complex, technical process it is critical that you have to be 'bilingual': speak the<br />

language of the technical experts and be a process expert. After he left the third<br />

project leader did not believe the project would benefit from our facilitation. He<br />

asked us <strong>for</strong> ‘hard evidence’ to demonstrate the added value of our contribution. At<br />

one point he explicitly requested us to limit our role to documentation.<br />

As it turned out most members of the project group had a hard time taking up their<br />

<strong>for</strong>mal role. We tried at two occasions to engage in role negotiation in the project<br />

group. It was remarkable how little interaction emerged. These interventions did not<br />

88


lead to clarification of roles or to a more focused participation in the project. The<br />

participative engineers came up with several potential reasons. One was that not<br />

everybody had been honest when expressing intentions and expectations. Another<br />

reason they <strong>for</strong>warded was “We were too nice to each other." The second project leader<br />

found it hard to be clear and firm towards the other members of the project group.<br />

He had not selected them in the first place, and avoided open confrontation about the<br />

relevance of certain representatives. He observed “The roles were not explicit enough.<br />

When a role is explicit, the composition of the groups becomes clear straight away.” He<br />

judged that the presence of the erosion specialists, <strong>for</strong> instance, was not necessary at<br />

certain meetings. "The situation had just grown this way. I found it hard to say ‘I do not<br />

expect you to be present’. (…) I did not have the courage to do that, because otherwise I would<br />

have lost them.” Not clarifying roles seems to have been a way of avoiding difficult<br />

issues and interpersonal confrontation.<br />

The importance of the context<br />

It is hard to understand dynamics in a collaborative without considering issues and<br />

events in the wider context. The permeability of the boundaries around a<br />

collaborative system is essential <strong>for</strong> its survival. The project was embedded in a<br />

socio-political context that influenced its direction and outcome. For instance local<br />

elections (October 2000) contributed to the inertia in the project. They resulted in a<br />

change in political representation in two of the three municipalities. Because of this<br />

change some of the work had to be repeated (e.g. ‘sell’ the project), and t<strong>here</strong> was a<br />

halt in decision making <strong>for</strong> a period of about 9 months. An important institutional<br />

change was the introduction of an erosion policy by the Flemish authorities. As they<br />

would now sponsor 75% of the costs <strong>for</strong> farmers adopting anti- erosion measures and<br />

the European project only 50%, the project lost some of its attraction and relevance.<br />

For the same financial reasons one of the municipalities decided to collaborate with a<br />

different European project <strong>for</strong> erosion management that had started in the area.<br />

89


Another context factor is what Vansina (2002) calls the 'ghosts around the table':<br />

parties who are not physically present during interaction moments, but who do<br />

influence the agenda. The most important ‘ghost’ was the European Commission.<br />

Their requirements (e.g. the nature of the parties to be involved, specification of<br />

outcome, timing and approach) had a big impact on the process.<br />

In this collaborative experience it seemed hard to engage in interdependent and<br />

productive work. We will try to make sense of why it was so difficult to take up a<br />

critical role and what the main emotional challenges and obstacles were in this<br />

collaborative experience.<br />

Sense making of the dynamics<br />

Mirroring and parallel processes<br />

In a psychodynamic perspective documenting what happens in the research<br />

relationship and scrutinizing ‘parallel processes’ provides additional in<strong>for</strong>mation<br />

that may increase the meaning of data obtained with other methods. These data may<br />

provide access to subtle aspects of participants and their experience (Gilmore &<br />

Krantz, 1985; Schein, 1987; Berg & Smith, 1988; Hunt, 1989). We explored how we<br />

were perceived by the members of the project group, what they did to us in our role<br />

as researchers and facilitators, and which parallel dynamics emerged in our team.<br />

To make sense of the dynamics in the project group I reflected on my experiences. I<br />

found myself confronted with feeling enthusiastic, hopeful, confused, inexperienced,<br />

powerless, and useless. For instance, towards the end of the project the in<strong>for</strong>mal<br />

project leader <strong>for</strong>got to let me know a meeting was canceled and he <strong>for</strong>got to put<br />

‘my’ issue on the agenda of a project group meeting. The notes in my research<br />

journal enabled me to trace back that I was increasingly anxious about my role and<br />

grateful I could ‘hide’ in my role of ‘documentation’ (Devereux, 1967; Hunt, 1989).<br />

This role justified my presence at meetings and it gave me the feeling of contributing<br />

to the project. I did notice I lost interest and started delaying things (e.g. writing up<br />

90


eport, interviewing). I often had the feeling of going 'through the ceremony' of<br />

meetings. The project and our contribution to it felt like a failure to me. This feeling<br />

of failure resonates with what most members of the project group expressed in the<br />

interviews.<br />

The internal dynamics in our team seemed to mirror some of the dynamics in the<br />

project group. They included procrastination, not treating the project as a priority,<br />

involving different colleagues in the project which made it harder to feel responsible.<br />

An important dynamic in our team was the repetition of the same discussion related<br />

to our present and potential role. We discussed issues such as: can we promote or<br />

push <strong>for</strong> sustainability or shouldn't we interfere on the substance? To what extent are<br />

we allowed, expected, requested to actively take up our role as facilitator? Are we<br />

responsible <strong>for</strong> the lack in progress? It was as if we talked as a defense against the<br />

feeling of being inadequate, and because taking action seemed unwanted, hazardous<br />

and risky.<br />

The most prominent feelings in our team were hope and disillusion, and the anger<br />

<strong>for</strong> not being ‘authorized’ to act as facilitators. At the start, however, the members of<br />

the project group seemed to project expectations of competence and responsibility on<br />

us. When I gave feedback of the interviews, however, I was struck by the reluctance<br />

of the project group to discuss the findings. We seemed to give them the message<br />

that what was happening was not 'right'. This may have provoked resistance and<br />

irritation in the third project manager. He made us feel inadequate and vulnerable in<br />

our professional role. We ended up in the position of 'evaluator' or 'punitive figure'<br />

(Cooper & Dartington, 2004) and were put aside. We were sucked into the system. It<br />

was as if the members of the project group were doing to us what they were doing to<br />

each other: have high expectations and subsequently de-authorize the other by<br />

inducing feelings of inadequacy.<br />

91


Dealing with poorly defined leadership: defensive responses<br />

Working in a collaborative requires a mental shift and a developmental process from<br />

dependency on a 'leader', who is thought to be omnipotent and omniscient, to<br />

sharing leadership functions. It is an evolution towards working from a shared<br />

power base (Vansina, 2002). The participating actors did not seem to have a mental<br />

model that could help them to take up a critical role (Hirschhorn, 1990; Kahn &<br />

Kram, 1994). They seemed to rely on fantasies of a strong leader which were not<br />

appropriate in this organizational context. They seemed powerless and dependent<br />

upon those demonstrating leadership. These dynamics point at basic assumption<br />

dependency (Bion, 1961) w<strong>here</strong> the group hopes someone will guide them. Some<br />

members of the project group projected expectations of strong leadership on the<br />

convener when he came <strong>for</strong>ward. After conducting the interviews I was 'the only one<br />

who knew what everybody was thinking'. Some expressed the hope I would get the<br />

project back on track by telling the project leader what was ‘really going on’.<br />

In this collaborative t<strong>here</strong> was no hierarchical leader with a mandate to take<br />

decisions <strong>for</strong> the collaborative system. The project leaders were wearing 'multiple<br />

hats': they were managing and facilitating the process, and at the same time<br />

defending the interests of their organization. T<strong>here</strong><strong>for</strong>e it was hard to perceive them<br />

as 'neutral' facilitators. Authority relations had not been negotiated and were<br />

ambiguous. The participants had contrasting expectations on who should be taking<br />

decisions. The discrepancy between the <strong>for</strong>mal and emergent authority relations<br />

generated uncertainty in the system. This context created feelings of vulnerability<br />

due to the absence of protective hierarchical structures and clear leadership roles.<br />

The members of the project group did not succeed to contain the perceived risks and<br />

to engage in productive work.<br />

In new organizational <strong>for</strong>ms such as multi-stakeholder processes, people have to<br />

exercise personal authority without being able to rely on bureaucracy, position or<br />

92


<strong>for</strong>mal power (Hirschhorn, 1997; Huffington, James & Armstrong, 2004). The<br />

convener did take up authority because his objectives were clear. In doing so he<br />

disregarded those of the other parties involved and reduced the complexity of<br />

reality. His heroic or tactical leadership was not ‘impartial’ and it ran counter to the<br />

assumed 'equality' of the parties involved and the consensual nature of bottom-op,<br />

multi-stakeholder processes. He mobilized power to impose his views, values and<br />

interests and to determine who was included and who was excluded (Vansina, 2002).<br />

In this project the function of leadership (inspiring, connecting, facilitating)<br />

embodied by the second project leader, was split off from the management function<br />

(budget control, project follow-up) taken up by the first and third project leader. A<br />

lack of integration of the two functions made it hard <strong>for</strong> ideas to be implemented.<br />

Krantz and Gilmore (1990) refer to both leadership functions and their idealization as<br />

'heroism' and 'managerialism': two defensive ideologies that are used to avoid the<br />

uncertainty and ambiguity of the organizational context. Each project leader seemed<br />

so preoccupied with his perspective on the nature and requirements of the project<br />

that a partnership did not get off the ground (Huffington, James & Armstrong, 2004).<br />

De-authorization and blaming: killing off the leaders!<br />

In this web of unclear authority relations we observed a striking dynamic: those who<br />

tried to move the process <strong>for</strong>ward were disempowered, de-authorized (Kahn &<br />

Kram, 1994) and blamed. The first project leader was hardly given a chance to take<br />

up his role. The second project leader took up a prominent role as facilitator, and in<br />

doing so he disempowered us. He was heavily criticized when he left, even by his<br />

close colleague and manager. The third project leader abdicated right from the start.<br />

He passed over project leadership to his inexperienced colleague who was hardly up<br />

to the task. This young engineer was not openly or <strong>for</strong>mally authorized to take<br />

charge. He was de-authorized by the local authorities because they did not accept his<br />

instructions. The third project leader also explicitly de-authorized us to facilitate the<br />

process and at the same time he criticized us <strong>for</strong> not contributing in a meaningful<br />

93


way to the project. The group members criticized the third project leader <strong>for</strong> not<br />

being visible, <strong>for</strong> not speaking up and <strong>for</strong> not being interested. Most group members<br />

downplayed the competence and minimized the importance of the municipalities.<br />

They were disempowered because they were not invited to most project meetings.<br />

When it became obvious the project was going to fail, the municipalities got the<br />

blame <strong>for</strong> not taking up ownership. Meanwhile, the 'invisible' leader (convener) was<br />

pulling the ropes behind the scene. Explicit role definitions and role negotiation<br />

hardly had an effect. The project group turned out to be an unsafe place to<br />

demonstrate initiative. This was perceived as a threat to the self, leading to<br />

regression in the group (Diamond & Allcorn, 1987).<br />

Most members of the project group also de-authorized themselves to take up a<br />

critical role. They came up with reasons such as lacking experience and seniority, not<br />

wanting to exclude others, not having a <strong>for</strong>mal position, not being asked to<br />

contribute, or feeling small and insignificant. This process of disempowering oneself<br />

and each other resulted in an authority vacuum w<strong>here</strong> all group members were<br />

waiting <strong>for</strong> others to take action. This vacuum allowed the differences in dominant<br />

logic, interests, values and identity to paralyze the group, as t<strong>here</strong> could be no<br />

containment of the potential conflicts (Hirschhorn & Gilmore, 1992). Responsibility<br />

became diffused and the lack of concentration of authority might have prevented the<br />

project group from making and implementing decisions (Menzies, 1988).<br />

Basic assumption me-ness: we are not a group!<br />

The main characteristics of a ‘group’ are the interdependent relationship between<br />

members and their commitment to a shared task. The lack of common ground made<br />

it hard <strong>for</strong> members to take up a critical role, to focus energy and to sustain<br />

motivation. The boundary of task was unclear; t<strong>here</strong> was hardly an integration of<br />

separate ef<strong>for</strong>ts. The members of the project group seemed to behave as if they were<br />

not a 'group' with a task, mandate and responsibilities. In this basic assumption 'me-<br />

ness' culture (Lawrence, Bain & Gould, 1996) it was not possible to join with others to<br />

94


create something new. The boundary of identity (Hirschhorn & Gilmore, 1992) was<br />

fuzzy. The name 'project group', <strong>for</strong> instance, was used <strong>for</strong> different constellations<br />

and mixed up with other names. Juniors took over from seniors. Some<br />

representatives joined and some left. T<strong>here</strong> was no open contracting and t<strong>here</strong> were<br />

no clear ground rules. The members did not clarify the mandate of the group. Was<br />

the group a space w<strong>here</strong> decisions were taken, w<strong>here</strong> in<strong>for</strong>mation was shared, did it<br />

have an advisory role or was it supposed to have, as one member suggested, a<br />

‘modeling role’ <strong>for</strong> the municipalities?<br />

The lack of face to face interaction hindered identification with the group and the<br />

development of a sense of belonging. The group only seems to have had an<br />

instrumental value <strong>for</strong> its members. It was as if the members could not decide to<br />

bring an important contribution to the group. As soon as the inspiring leadership of<br />

the second project leader stopped, the rest of the group lost their drive and sense of<br />

direction. T<strong>here</strong> was little containment offered by protective processes, such as clear<br />

boundaries of roles, procedures, lines of accountability, or structures (Huffington,<br />

James & Armstrong, 2004). The group itself did not develop a 'minimal structure'<br />

(e.g. ground rules) or ‘normative system’ (Mills, 1967) to cope with the openness and<br />

uncertainty of the situation and to establish trust. T<strong>here</strong> were few containing<br />

experiences, like <strong>for</strong> instance, reviewing the way we were working or working<br />

through the uncertainty around our roles.<br />

In the project group it was not safe to talk about issues related to the difficulties of<br />

collaborating. These unwanted issues were partly split off, disowned and projected<br />

outside the project group. For instance, the farmers were perceived as ‘difficult’,<br />

‘only interested in money’, and ‘unwilling to collaborate’. The municipalities were<br />

blamed <strong>for</strong> ‘not taking up ownership’, <strong>for</strong> being ‘incompetent’, and <strong>for</strong> ‘playing<br />

political games’. The group discussed issues 'out t<strong>here</strong>' (e.g. how can we involve the<br />

farmers?), but failed to look at its own functioning. In doing so, the members of the<br />

project group seemed to diminish their capacity to address important and difficult<br />

issues. The project group disowned these relational aspects, and split them off as if<br />

95


the relational challenges were not part of the overall functioning of the collaborative<br />

system (Obholzer & Miller, 2004). The members of the project group seemed to avoid<br />

personal responsibility <strong>for</strong> the success of the project. The result was a 'boarding<br />

house' mentality w<strong>here</strong> t<strong>here</strong> was no sense of common venture.<br />

Denial of interdependence and diversity<br />

Developing an interdependent relationship with different kinds of stakeholder<br />

representatives and the capacity to deal with diversity are critical emotional<br />

challenges of collaborative work. An appropriate degree of contesting with the other,<br />

without conflict or evasion, seems required (Huffington, James & Armstrong, 2004).<br />

However, the confrontation with being dependent on others who are very different<br />

may jeopardize one's identity, position and feelings of self-esteem. Depending on<br />

others <strong>for</strong> success makes actors vulnerable. We observed rivalry (e.g. technical and<br />

participative engineers), independent action (e.g. intervention of convener),<br />

exclusion of perspectives (e.g. ecological voice), and dominance of the technical and<br />

political logic. Actors seemed to struggle to find a balance between, on the one hand,<br />

autonomy and holding onto one's identity, and on the other hand, engaging in<br />

interdependent work and facing the differences.<br />

In this collaborative process the successful implementation of the technical solutions<br />

proposed by the engineers, ultimately depended on the readiness of the farmers to<br />

participate. This issue only emerged when the technical designs were ready and<br />

when it turned out the farmers were not so keen to participate. For experts and<br />

engineers, it was not self-evident to put their solution mindedness and technical<br />

expertise aside, to include the experiential knowledge of farmers and to open up the<br />

debate. As soon as the second project left, the project fell back on 'old ways' of<br />

working, based on dominance and centrality of technical expertise and autonomous<br />

work.<br />

96


Collusive and ‘as-if’ behavior<br />

Another striking phenomenon was the emergence of ‘as-if’ behavior regarding a<br />

number of issues. The first issue was the identified problem domain and the<br />

motivation to start a project. T<strong>here</strong> was no 'emotional context' (Vansina, 2002) <strong>for</strong> this<br />

collaboration: no sense of urgency to do something about the identified problem and<br />

a poor awareness of the need to find solutions through collaboration. Most actors<br />

were not preoccupied with soil erosion and the consequences <strong>for</strong> the community (e.g.<br />

pollution by chemical fertilizers, costs <strong>for</strong> cleaning the streets and sewers, permanent<br />

loss of fertile soil). Our findings suggest that all actors had their personal reasons to<br />

take part in the project. It was not so much a pressing problem in the community, but<br />

the availability of European funds that triggered off the project.<br />

The requirements of the financial sponsor resulted in the <strong>for</strong>mal involvement of<br />

different groups of stakeholders. Some actors, however, did not play their role. For<br />

instance, the convener invited academic experts in soil erosion to the project. Their<br />

task was to give scientific advice, to ‘measure’ and to present their results at an<br />

international conference, organized by the project. They were hardly asked <strong>for</strong> advice<br />

and the equipment to measure sedimentation be<strong>for</strong>e and after the interventions<br />

failed. The project did not organize a scientific meeting. Inviting experts may have<br />

been a way to increase chances <strong>for</strong> funding.<br />

As the project moved on and uncertainty increased, collusive behavior started to<br />

emerge. The project group acted as if t<strong>here</strong> was ‘common ground’, and as if roles<br />

were clear. Interventions to invite a discussion around these issues in the group were<br />

systematically neglected or put aside. T<strong>here</strong> was no transparency around budget<br />

issues. Keeping these issues unclear might have served the function of sustaining the<br />

ambiguity and leaving space <strong>for</strong> the stakeholders to pursue their personal objectives<br />

and agenda.<br />

97


Towards the end of the four years, when issues of failure, reputation and<br />

responsibility were emerging, the group colluded around how to elegantly deal with<br />

‘failure’, by calling it a ‘low-end version’. At that point it was still not clear what the<br />

criteria <strong>for</strong> success or evaluation were. This contributed to the uncertainty and<br />

anxiety in the project group. The members of the group were aware of the fact that<br />

the project would not be a success and that their names were linked to it. T<strong>here</strong> was<br />

hardly discussion around the issue of not meeting the standards. As the parties lost<br />

trust in the successful outcome of the collaboration, they abdicated and became more<br />

passive.<br />

The project group also engaged in collusive behavior around issues of integrity.<br />

T<strong>here</strong> were some practices at the limit of ethical behavior. For instance, the members<br />

of the project group received their allowance <strong>for</strong> participation in the project at the<br />

start of the project and did not openly justify their expenses in the project group.<br />

Another ethical issue was the ambiguous and double role of the convening party.<br />

They were both initiator of the project and hired as subcontractor <strong>for</strong> the<br />

municipality. T<strong>here</strong> was suspicion of political maneuvering, but nobody talked about<br />

these issues in public. These practices were justified as 'this is the way things go <strong>here</strong>'<br />

or they were labeled as 'typical Belgian practices'.<br />

Collaboration as a cover<br />

The question is whether the identified problem was suitable <strong>for</strong> a multiparty<br />

approach. Why would a powerful party, like the technical engineering firm, promote<br />

a participative way of working in the first place (Hardy & Phillips, 1998)? Why<br />

would they share their power with other groups when their organization could cover<br />

all aspects? The definition of the problem, know-how <strong>for</strong> solving the problem and<br />

the means to carry out the solutions were concentrated with the experts, in particular<br />

the technical engineers. The farmers, who were in the position to provide a<br />

meaningful contribution to all three aspects, were hardly involved in the process.<br />

They were asked <strong>for</strong> their reaction to the technical solutions proposed by the<br />

98


engineers, thus providing the engineers with useful in<strong>for</strong>mation as input <strong>for</strong> their<br />

technical problem solving process.<br />

In this project the subsidizing policy of the sponsoring organization generated a<br />

paradoxical situation. The sponsor stressed the importance of multi-organizational<br />

collaboration, transfer of knowledge between government institutes, non-<br />

government institutes and/or socio-economical actors, using a ‘bottom up’ approach.<br />

The project proposal used the collaborative rhetoric of the sponsor. However, be<strong>for</strong>e<br />

the start of the project the solutions, organizational systems, procedures and<br />

approach were already specified in advance (e.g. steering group meeting every 6<br />

months). T<strong>here</strong> was little space <strong>for</strong> the in<strong>here</strong>ntly emergent and open nature of<br />

bottom-up processes. Moreover the budget <strong>for</strong> interaction moments turned out to be<br />

very limited. This made a collaborative approach unrealistic. Thus the organization<br />

holding the power to provide funding generated behavior w<strong>here</strong> collaboration<br />

turned into a ‘cover’. Even though some people tried very hard to do things<br />

differently, participation and multi-stakeholder involvement were quite limited in<br />

the end. ‘Cover’ collaborations often initiate with the hope of approaching a problem<br />

in a different and more inclusive way. The societal cost of such endeavors is<br />

disillusion in all stakeholders involved.<br />

Conclusion<br />

This in-depth case study demonstrates a number of striking phenomena. The project<br />

group engaged in collusive behavior. They tacitly agreed not to question a number of<br />

issues. These included: the lack of common ground and the shift in the task; the<br />

absence of a pressing environmental problem and the underlying motivation <strong>for</strong><br />

setting up a project; the rhetoric of engaging in a multi-stakeholder, bottom-up<br />

process w<strong>here</strong> ‘collaboration’ was used as a cover <strong>for</strong> ongoing ‘business as usual’. A<br />

final observation was the defensive way of dealing with poorly defined leadership,<br />

w<strong>here</strong> the participants avoided open contracting, de-authorized each other to move<br />

things ahead, and w<strong>here</strong> all participants just let it happen. This resulted in an<br />

99


authority vacuum that moved the process towards inertia. The overarching dynamic<br />

was a polarization between two different dominant logics. For the technical<br />

engineers projects were driven on a solution-orientation, technical expertise, political<br />

lobbying, the use of power when necessary, and a procedural organization of the<br />

process. For the participative engineers these processes were about facilitation of the<br />

process, inclusion of stakeholders, a focus on problem exploration and definition.<br />

They valued shared responsibility, negotiation as opposed to management, and an<br />

integration of interests. The gap between the two logics proved to be too wide. The<br />

tensions stirred up by the differences in perspective resulted in defensive dynamics<br />

that severely hindered innovative and productive work.<br />

Individuals, groups and organizations will increasingly be invited or <strong>for</strong>ced to<br />

collaborate across organizational boundaries. It is critical to find new ways of<br />

designing, developing, and facilitating collaborative processes. "The shift towards a<br />

culture of fluidity, flexibility, and negotiated interdependences in social life contains new<br />

possibilities <strong>for</strong> new <strong>for</strong>ms of depth engagements, but in the absence of a function to do the<br />

work of containment these are as likely to be risky, volatile, enervating, destructive, and<br />

unpredictable as they are to promote solidarity, creativity, purpose, and growth rooted in a<br />

sense of security" (Cooper & Dartington, 2004, 149). Collaboration confronts us with a<br />

paradox. In order to arrive at innovative, sustainable and accepted solutions, the<br />

actors need to develop mature collaborative relationships. However, it is precisely<br />

the openness, complexity and uncertainties of a collaborative journey that make it<br />

hard to develop open and trustful relationships (Krantz, 1998). This raises several<br />

questions that require further research. How can insight in the underlying tension<br />

and the (covert) dynamics inspire generative interventions? How can those taking up<br />

leadership functions design and facilitate containing experiences if containing<br />

structures are not available? Who will take up this containing function when t<strong>here</strong> is<br />

no identified or accepted leader or facilitator? How can a group responsible <strong>for</strong><br />

‘leading’ a collaborative ef<strong>for</strong>t arrive at some <strong>for</strong>m of shared leadership and joint<br />

ownership of decisions?<br />

100


References<br />

Ackoff, R. Systems, messes and interactive planning. In Trist, E., Emery F. & Murray H.<br />

(Eds.), The social engagement of social science. A Tavistock anthology. Volume III: The<br />

Socio-ecological perspective. Philadelphia: Penn, 1997, pp. 417-438.<br />

Amado, G. & Ambrose A. (Eds.). The transitional approach to change. London: Karnac,<br />

2001.<br />

Berg, D.N. & Smith K.K. The clinical demands of research methods. In Berg, D.N. &<br />

Smith K.K. (Eds.), The self in social inquiry. Researching methods. Newbury Park,<br />

Cali<strong>for</strong>nia: Sage Publications, 1988, pp. 21-34.<br />

Bion, W.R. Experiences in groups. London: Routledge, 1961.<br />

Chisholm, R.F. Developing network organizations. Learning from practice and theory.<br />

Addison-Wesley, 1998.<br />

Chisholm, R.F. & Elden M. Features of emerging action research. Human Relations, 1993<br />

46 (2), 275-297.<br />

Clarke, S. Learning from experience: psycho-social research methods in the social<br />

sciences. Qualitative Research, 2002, 2 (2), 173-194.<br />

Cooper, A. & Dartington T. The vanishing organization: organizational containment in<br />

a networked world. In Huffington, C., Armstrong, D., Halton, W., Hoyle L. &<br />

Pooley J. (Eds.), Working below the surface. The emotional life of contemporary<br />

organizations. Tavistock Clinic Series, London: Karnac, 2004, pp.127-150.<br />

Devereux, G. From anxiety to method in the behavioral sciences. The Hague: Mouton & Co,<br />

1967.<br />

Diamond, M.A. & Allcorn, S. The psychodynamics of regression in work groups.<br />

Human Relations, 1987, 40 (8), 525-543.<br />

Gilmore, T.N. & Krantz J. Projective identification in the consulting relationship:<br />

exploring the unconscious dimensions of a client system. Human Relations, 1985, 38<br />

(12), 1159-1177.<br />

Gould, L.J., Ebers, R. & Mc Vicker Clinchy, R. The systems psychodynamics of a joint<br />

venture: anxiety, social defenses and the management of mutual dependence.<br />

Human Relations, 1999, 52 (6), 697-722.<br />

Gould, L.G., Stapley, L.F. & Stein, M. (Eds.). The systems psychodynamics of organizations.<br />

Integrating the group relations approach, psychoanalytic, and open systems perspectives.<br />

London: Karnac, 2001.<br />

101


Gray, B. Collaborating: finding common ground <strong>for</strong> multiparty problems. San Francisco:<br />

Jossey Bass, 1989.<br />

Hardy, C. & Phillips, N. Strategies of engagement: lessons from the critical examination<br />

of collaboration and conflict in an interorganizational domain. Organization Science,<br />

1998, 9 (2), March-April, 217-230.<br />

Hirschhorn, L. Leaders and followers in a post-industrial age: a psychodynamic view.<br />

Journal of Applied Behavioral Science, 1990, 26 (4), 529-542.<br />

Hirschhorn, L. Reworking authority; Leading and following in the post-modern organization.<br />

Cambridge Massachusetts: The MIT Press, 1997.<br />

Hirschhorn, L. & Gilmore, T. The new boundaries of the “boundaryless” company.<br />

Harvard Business Review, 1992, May/June, 70 (3), 104-115.<br />

Hollway, W. & Jefferson, T. Doing qualitative research differently: free association, narrative<br />

and the interview method. London: Sage, 2000.<br />

Huberman, A.M. & Miles, M.B. Assessing local causality in qualitative research. In<br />

Berg, D.N. & Smith, K.K. (Eds.), The self in social inquiry. Researching methods.<br />

Newbury Park, Cali<strong>for</strong>nia: Sage, 1988, pp. 351-381.<br />

Huffington, C., Armstrong, D., Halton, W., Hoyle, L. & Pooley, J. (Eds.). Working below<br />

the surface. The emotional life of contemporary organizations. Tavistock Clinic Series,<br />

London: Karnac, 2004.<br />

Huffington, C., James, K. & Armstrong, D. What is the emotional cost of distributed<br />

leadership? In Huffington, C., Armstrong, D., Halton, W., Hoyle, L. & Pooley, J.<br />

(Eds.), Working below the surface. The emotional life of contemporary organizations.<br />

Tavistock Clinic Series, London: Karnac, 2004, pp. 67-82.<br />

Hunt, J. Psychoanalytic aspects of fieldwork. Qualitative Research Methods. Volume 18.<br />

London: Sage, 1989.<br />

Hutjes, J.M. & van Buuren, J.A. De gevalsstudie: strategie van kwalitatief onderzoek.<br />

Meppel: Boom, 1994.<br />

Huxham, C. (Ed.). Creating collaborative advantage. London: Sage, 1996.<br />

Huxham, C. & Vangen, S. Ambiguity, complexity and dynamics in the membership of<br />

collaboration. Human Relations, 2000, 53 (6), 771-806.<br />

Huxham, C. & Vangen, S. (Eds.) Managing to collaborate. The theory and practice of<br />

collaborative advantage. London: Routledge, 2005.<br />

Jaques, E. Social systems as a defense against persecutory and depressive anxiety. In<br />

Klein, M., Heimann, P. & Money-Kyrle, R. (Eds.), New directions in psychoanalysis.<br />

London: Tavistock Publication, 1955.<br />

102


Jarrett, M. & Kellner, K. Coping with uncertainty: a psychodynamic perspective on the<br />

work of top teams. Journal of Management Development, 1996, 15, (2), 54-68.<br />

Kahn, W.A. & Kram, K.E. Authority at work: internal models and their organizational<br />

consequences. Academy of Management Review, 1994, 19 (1), 17-50.<br />

Kanter, R.M. Collaborative advantage: the art of alliances. Harvard Business Review,<br />

1994, 72 (4), 96-108.<br />

Kramer, R. The more the merrier? Social psychological aspects of multiparty<br />

negotiations in organizations. Research on negotiation in organizations. Vol. 3,<br />

Greenwich, Connecticut: JAI Press, 1991.<br />

Krantz, J. Lessons from the Field: An Essay on the Crisis of Leadership in<br />

Contemporary Organizations, The Journal of Applied Behavioral Science, 1990, 26 (1),<br />

49-64.<br />

Krantz, J. Anxiety & the new order. In Klein, B. & Gabelnick, F. & Herr, P. (Eds.), The<br />

psychodynamics of leadership. Madison: Psychosocial Press, 1998, pp. 77-107.<br />

Krantz, J. & Gilmore, T.N. The splitting of leadership and management as a social<br />

defense. Human Relations, 1990, 43 (2), 183-204.<br />

Lawrence, G., Bain, A. & Gould, L. The fifth basic assumption. Free Association, 1996, 6,<br />

(37), 28-55.<br />

Lipman-Blumen, J. The connective edge. Leading in an interdependent world. San Francisco:<br />

Jossey-Bass Publishers, 1996.<br />

McCollom, M. Group <strong>for</strong>mation: boundaries, leadership, and culture. In Gillette, J. &<br />

McCollom, M. (Eds.), Groups in context. A new perspective on group dynamics.<br />

Lanham: University Press of America, 1995, pp. 34-48.<br />

Menzies, I. E. P. A case study in the functioning of social systems as a defense against<br />

anxiety. Human Relations, 1960, 13, 95-121.<br />

Menzies Lyth, I. Containing anxiety in institutions. Selected essays. Volume 1. London: Free<br />

Association Books, 1988.<br />

Miller, E.J. From Dependency to Autonomy: Studies in Organization and Change. London:<br />

Free Associations Books, 1993.<br />

Miller, E.J. & Rice, A.K. Systems of organization: The control of task and sentient boundaries.<br />

London: Tavistock Publications, 1967.<br />

Mills, T.M. The Sociology of Small Groups. New Jersey: Prentice-Hall, 1967.<br />

103


Mintzberg, H., Jorgensen, J., Dougherty, D. & Westley, F. Some surprising things about<br />

collaboration. Knowing how people connect makes it work better. Organizational<br />

Dynamics, 1996, Spring, 60-71.<br />

Obholzer, A. & Miller, S. Leadership, followership, and facilitating the creative<br />

workplace. In Huffington, C., Armstrong, D., Halton, W., Hoyle, L. & Pooley, J.<br />

(Eds.), Working below the surface. The emotional life of contemporary organizations.<br />

Tavistock Clinic Series, London: Karnac, 2004, pp.33-48.<br />

Page, M. Leadership and collaboration challenges in not <strong>for</strong> profit partnerships.<br />

Organisational and Social Dynamics, 2003, 3 (2), 207-225.<br />

Patton, M.Q. How to use qualitative methods in evaluation. Newbury Park, CA: Sage, 1987.<br />

Schein, E.H. The clinical perspective in fieldwork. Newbury Park, Cali<strong>for</strong>nia: Sage, 1987.<br />

Schneider, S.C. Managing boundaries in organizations. In Kets de Vries (Ed.),<br />

Organizations on the couch: clinical perspectives on organizational behavior and change.<br />

San Francisco: Jossey-Bass, 1991, pp. 169-190.<br />

Schruijer, S. & Vansina, L. Epilogue to special issue on ‘Leadership and organizational<br />

change’. European Journal of Work and Organizational Psychology, 1999, 8 (1), 135-138.<br />

Trist, E. Referent organizations and the development of inter-organizational domains.<br />

Human Relations, 1983, 36 (3), 269-284.<br />

Vansina, L. Making the best of diversity: working towards collaboration between different<br />

interest groups, paper presented at the ISPSO symposium, Melbourne, Australia,<br />

June 2002.<br />

Vansina, L., Taillieu, T. & Schruijer, S. “Managing” multiparty issues: learning from<br />

experience. In Pasmore, W. & Woodman, R. (Eds.), Research in Organizational<br />

Change and Development. (vol. 11). Greenwich, Connecticut: JAI Press Inc., 1998, pp.<br />

159-181.<br />

Yin, R.K. Case study research. Design and methods. Second Edition. Applied Social<br />

Research Methods Series, Volume 5, Thousand Oaks, Cali<strong>for</strong>nia: Sage Publications,<br />

1994.<br />

Zagier Roberts, V. Conflict and collaboration. Managing inter-group relations. In<br />

Obholzer, A. & Zagier Roberts, V. (Eds.), The unconscious at work. London:<br />

Routledge, 1994, pp. 187-196.<br />

104


CASE 2: RIVER VALLEY CASE<br />

Introduction<br />

In 2003 the Center <strong>for</strong> Organizational and Personnel Psychology (COPP) was<br />

involved in a European project on ‘social learning in river basin management’<br />

(HarmoniCOP project). The aim of one of the work packages (5: national case<br />

studies) was to document local case studies to illustrate the practices of river basin<br />

management in different European countries. In that context we were looking <strong>for</strong> a<br />

specific project. We were in contact with a public officer from the Department Nature<br />

of the Ministry of Environment whom we knew from a different project. He<br />

suggested that the river valley project could be interesting <strong>for</strong> the European project. I<br />

joined the project even though I was not closely involved in the European project,<br />

because the project seemed interesting <strong>for</strong> my research purpose and the timing was<br />

perfect. During one year I was engaged in the project with my colleagues (see<br />

attachment 1). We developed a case study <strong>for</strong> the HarmoniCOP project from the<br />

perspective of ‘social learning’. In a later phase I also analyzed the case from a more<br />

specific research focus. Because I had chosen the foster care case as main case study<br />

(see introduction part 3), I did not analyze the case in great depth.<br />

Context and antecedents of the river valley project<br />

This case study is based on a study project that was initiated by the subdivisions<br />

Nature and Water of the Environment Administration. In 1998 the valley had<br />

suffered the consequences of a severe flooding. This was the drive <strong>for</strong> the<br />

administration to invest additional resources in an extensive study of the area. The<br />

river in this case study is one of the tributaries of the Scheldt basin. The study<br />

focused on a restricted part of the river catchment. The study was coordinated with<br />

other planning initiatives which were being developed at the time, aligned with the<br />

European Water Frame Directive. The study project was not intended as a pilot<br />

experience experimenting with public participation, as promoted in the European<br />

Directive. However, the initiators were genuinely interested in a participatory<br />

105


approach in order to guarantee a societal support <strong>for</strong> an integrated valley plan. The<br />

aim of the study project was to study the river valley as an ecosystem. The objectives<br />

were:<br />

- Work out an integrated vision <strong>for</strong> the river valley, with an emphasis on nature<br />

and safety.<br />

- Contribute to the development of a Strategic Nature Management Plan, <strong>for</strong> one<br />

part of the valley.<br />

- Work out a Nature Development Project Plan, a <strong>for</strong>mal plan <strong>for</strong> a geographically<br />

restricted part of the valley.<br />

The conveners of the project were aware of the need to integrate their study in the<br />

broader integrated management plan at catchment level (Flemish administration)<br />

and in the more local sustainable water management plans (provincial<br />

administrations) which were being developed simultaneously.<br />

Environmental context<br />

According to the Flemish Water Frame Directive, a river basin is a territorial area in<br />

which all the affluent water flows through a system of rivers and streams to the sea.<br />

T<strong>here</strong> are four ‘river basins’ in Flanders: Scheldt, Meuse, Ijzer and Bruges Polders.<br />

The three last mentioned basins cross international boundaries. A sub-basin, or<br />

'catchment', is a territorial area in which the affluent water flows into another river or<br />

stream. In Flanders this is generally the Scheldt or the Meuse. The river of this case<br />

study is part of one of the 11 catchments identified in this logic. On the third level,<br />

‘sub-catchments’ are identified (local water management plans).<br />

The area of the river valley under study is defined by a city upstream and by a point<br />

in the river downstream w<strong>here</strong> two rivers come together. The distance of the river<br />

section is approximately 27 kilometers. The total catchment of the river, with a<br />

surface area of 191.000ha, is the largest of the 11 catchments identified by the Flemish<br />

106


Water Administration <strong>for</strong> the integrated planning process (Water Framework<br />

Directive). The area of the study (3.600 has.) is a small but critical part of the<br />

catchment.<br />

Institutional context<br />

The subdivisions of Water and Nature coordinated the study project in a joint ef<strong>for</strong>t.<br />

Table 3 gives an overview of the main actors involved in the study.<br />

Governmental Environment<br />

Semi-official<br />

Non-<br />

governmental<br />

Regional (Flemish) level Provincial<br />

Administration,<br />

subdivisions Water and<br />

Water<br />

Navigable Waterways<br />

Administration<br />

“Related” subdivisions<br />

(Woods, Landscape,<br />

Spatial planning, …)<br />

Flemish Environment<br />

Institute<br />

Flemish Institute <strong>for</strong><br />

Drinking Water<br />

Nature Conservation,<br />

Farmers, Landscape, etc.<br />

107<br />

level<br />

Provincial<br />

government<br />

Sustainable<br />

Local Water<br />

Plans<br />

Local level<br />

Municipal<br />

government<br />

Polders and<br />

Watering<br />

Local sections<br />

and<br />

committees<br />

Table 3: Overview of the organizations involved in the river valley cae.


Socio-economic and political context<br />

Historically the river had an important economic value <strong>for</strong> shipping, transportation,<br />

and water mills. As early as the 17 th century, interventions were implemented to<br />

improve the use of the river. These human interventions contributed to the<br />

occurrence of flooding in the valley. Although the river has not been used <strong>for</strong><br />

shipping purposes <strong>for</strong> the last 100 years, the river still had the status of ‘navigable’<br />

river. T<strong>here</strong><strong>for</strong>e the Navigable Waterways Administration, a subdivision of the<br />

Infrastructure department of the Flemish Administration, still had the <strong>for</strong>mal<br />

authority over the river at the time of the project.<br />

Due to demographical pressure and the evolution of agriculture in the 20 th century,<br />

t<strong>here</strong> was a high demand <strong>for</strong> arable land. By the end of the fifties a ‘note concerning<br />

infrastructural works to improve the water affluence of the river’ was issued by the<br />

Navigable Waterways Administration. Its aim was to control the river course by<br />

damming it up, in the interest of agriculture and safety against flooding. Between<br />

the sixties and the nineties the Navigable Waterways Administration carried out<br />

drastic infrastructure works. As a consequence of these interventions the relationship<br />

between the river and the surrounding alluvial plain was profoundly disturbed. For<br />

instance, groundwater levels lowered dramatically, affecting the natural flora and<br />

fauna in the valley. From the eighties on, agricultural interests diminished due to<br />

worldwide competition. In the same period ecological awareness in society<br />

increased. In the nineties the new ‘Environmental Department of the Flemish<br />

Administration’ was created. ‘Water' and 'Nature' were subdivisions of this<br />

administration. The Department developed an alternative vision on river<br />

management. In this new vision safety against flooding was achieved by giving<br />

space to the river. Water management and restoration and conservation of the<br />

surrounding natural valley go hand in hand. A consequence of the severe floods in<br />

the cities and villages in the valley in 1998 was that the conflicting visions between<br />

the two departments of the Flemish administrations (Environment and<br />

Infrastructure) came to the <strong>for</strong>e.<br />

108


The Flemish Administration, various consultants and (academic) research centers<br />

carried out studies to explore and document environmental aspects of the river and<br />

the valley. In 1996 the Environment Administration set up an ‘Integrated Water<br />

Management Project’ emphasizing measurement and modeling. The objective of the<br />

initiative, the “Integrated Development Planning of the river valley”, was to<br />

integrate previous and recent study results in a plan that is socially balanced and<br />

negotiated with all stakeholders to create a societal plat<strong>for</strong>m guaranteeing its<br />

implementation. The study was a joint initiative of the Nature and Water<br />

subdivisions of the Flemish Environment Administration. However, the <strong>for</strong>mal<br />

authority over the river was still in the hands of the Navigable Waterways<br />

Administration. At the start of the initiative the administrators of the Environment<br />

Administration hoped and presumed that the authority over the river would soon be<br />

handed over to their Administration. In the course of the project it became clear that<br />

this would not happen in the near future. This produced a new governmental context<br />

<strong>for</strong> the study.<br />

Main events in the river valley project<br />

Table 4 summarizes the main events and the issues that emerged in the process,<br />

based on the process reconstruction I developed (October 2003 to November 2004).<br />

Date Event Issues<br />

June 2003 Start of the study project<br />

August 2003 1 st meeting coordination<br />

September<br />

2003<br />

committee<br />

In<strong>for</strong>mation sessions in<br />

five cities and villages<br />

109<br />

How to in<strong>for</strong>m the local authorities?<br />

Little interest and poor attendance


September –<br />

November<br />

2003<br />

October<br />

2003<br />

October<br />

2003<br />

November<br />

2003<br />

Sector analysis by external<br />

consultants, the provincial<br />

and regional catchment<br />

coordinators<br />

Start of the research<br />

1 st meeting of the<br />

planning group<br />

2 nd meeting of<br />

coordination committee<br />

110<br />

– Make inventory of the interests and<br />

claims on the water system by the<br />

organized stakeholder groups<br />

– Result: overview of bottlenecks and<br />

opportunities<br />

Formal start up of the project<br />

Presentation of the project<br />

– Tension between long term vision<br />

and immediate needs<br />

– Is t<strong>here</strong> a need <strong>for</strong> a more active<br />

participation of stakeholders in the<br />

process?<br />

– Politics take the final decisions<br />

– Dominance of the interests of the<br />

Nature and Water subdivisions<br />

– Strategy: ‘not give in yet, because we<br />

will have to give in later anyways’<br />

– Ambition: determine the use of the<br />

space of the planning area <strong>for</strong> the<br />

future to make sure it will be<br />

definitive<br />

– What if transfer of the river will not<br />

happen?<br />

– Belief that a waterproof plan will be<br />

sufficient to create consensus<br />

between all actors in the valley


March 2004 3 rd meeting of the<br />

coordination committee<br />

March 2004 Joint meeting of steering<br />

April-May<br />

2004<br />

and planning group<br />

Start up of two work<br />

groups: recreation and<br />

hydrology<br />

May 2004 4 th meeting of the<br />

coordination committee<br />

111<br />

– ‘Ideal solution’: from the perspective<br />

of the conveners<br />

– Need to be defensive about the plan<br />

is not justified because most<br />

stakeholders are in favor of the<br />

ecological agenda<br />

– Organizational design of project is<br />

unclear: authority relations, degree<br />

of autonomy?<br />

– How to organize the meeting of the<br />

steering group and planning group?<br />

– Presentation of the results of the<br />

sector analysis<br />

– Announcement and call <strong>for</strong><br />

participation in work groups<br />

– What is specific mandate of work<br />

groups?<br />

– Can laymen participate in the<br />

decision making?<br />

– Presentation of hydraulic modeling<br />

– Presentation of the overview of<br />

bottlenecks and opportunities<br />

– New planning of activities and<br />

deadlines<br />

– How to communicate about the<br />

project?


June 2004 5 th meeting of the<br />

8 September<br />

2004<br />

15<br />

September<br />

2004<br />

coordination committee<br />

6 th meeting of the<br />

coordination committee<br />

112<br />

– Announcement of HarmoniCOP<br />

workshop<br />

– Reporting of work group hydrology<br />

and recreation: mandate?<br />

– Suggestion to consult relevant<br />

stakeholders be<strong>for</strong>e organizing a<br />

second meeting of the steering<br />

group<br />

– Steering group postponed<br />

– Consultants hardly manage to meet<br />

the deadlines (modeling)<br />

– ‘minimum’ or ‘maximum’ scenario?<br />

– Communication strategy (website,<br />

press release)<br />

– Start of the survey among farmers in<br />

the valley<br />

– Presentation of modeling results:<br />

discussion ‘minimum’ or<br />

‘maximum’ scenario?<br />

– Presentation ground water modeling<br />

– Organization of consultation<br />

meetings with local authorities<br />

Workshop HarmoniCOP Observations of the researchers<br />

Discussion of learnings<br />

Action steps


16<br />

September<br />

2004<br />

October<br />

2003<br />

7 th meeting of the<br />

coordination committee<br />

8 th meeting of the<br />

coordination committee<br />

March 2005 2 nd meeting of the steering<br />

group<br />

113<br />

– Navigable Waterways<br />

Administration is present with five<br />

representatives and tries to stop the<br />

process: suggestion to duplicate the<br />

measuring and modeling ef<strong>for</strong>ts of<br />

the consultants<br />

– Conveners insist on seeing the local<br />

authorities and farmers, even with<br />

an ‘unfinished’ plan<br />

– Announcement by researchers:<br />

survey, final interviews<br />

– Reporting of in<strong>for</strong>mation tour that is<br />

ongoing (local authorities, farmers)<br />

– Technical discussion about different<br />

types of interventions and possible<br />

scenarios<br />

– Underlying conflict between the<br />

Navigable Waterways<br />

Administration (one representative)<br />

and the other members of the<br />

coordination committee<br />

Technical presentation of a provisional<br />

plan <strong>for</strong> the valley<br />

Table 4: Main events and issues in the river valley case.<br />

Research approach<br />

Research question<br />

My focus in this case study was on the dynamics of direction setting, since the<br />

explicit issue of ‘leadership’ was – also in this case - not a central one. The<br />

coordination group and, in particular, the small group of conveners set the direction<br />

of this collaborative. In the analysis I emphasized boundary dynamics as this was a


central issue in the project. The conveners were struggling with the ambiguity of<br />

including the voice of stakeholders in the process. Their decisions about inclusion<br />

and exclusion had a strong influence on direction setting.<br />

The research setting<br />

The study project was an initiative of two subdivisions. The public officers of those<br />

departments who conceived the study (‘conveners’) were our contact persons. We<br />

were closely related to this small group of four public officers, because they were the<br />

key actors driving the process. We participated in the ‘system in interaction’ and<br />

attended and documented meetings of several subgroups in the project: the<br />

coordination group, the steering group, the planning group and some meetings of<br />

work groups (table 5).<br />

Coordination<br />

committee<br />

Members Role and mandate<br />

Approximately 10 members,<br />

all public officers:<br />

Flemish Water and Nature<br />

administration<br />

Institute <strong>for</strong> Nature<br />

Conservation<br />

Public officers responsible<br />

<strong>for</strong> the Integrated river<br />

Catchment Plan<br />

Public officers responsible<br />

<strong>for</strong> the Local Sustainable<br />

Water management plans<br />

A representative of the<br />

Navigable Waterways<br />

Administration<br />

114<br />

Coordinate and steer the<br />

process<br />

Supervise the consultants<br />

Maintain contact with all<br />

actors involved


Planning<br />

Committee<br />

Steering<br />

Committee<br />

Representatives of related<br />

administrations, including:<br />

– <strong>for</strong>est management<br />

– nature and landscape<br />

– spatial planning<br />

+ the members of the<br />

coordination committee<br />

Stakeholder representatives:<br />

local governments (province,<br />

7 municipalities, and 2<br />

polder governments)<br />

civil actors (representatives<br />

of officially recognized<br />

organizations in the domain<br />

of environment, agriculture,<br />

woods, hunting, angling,<br />

regional landscape)<br />

Work groups Members of the Steering<br />

Committee, Planning Group<br />

and some interested<br />

participants<br />

115<br />

Work out a vision <strong>for</strong> the<br />

river valley<br />

Consultative function:<br />

Give proposals to planning<br />

process<br />

Give feedback on the results<br />

(feedback is not binding <strong>for</strong><br />

policy makers)<br />

Propose specific and local<br />

solutions<br />

Table 5: Organizational structure and participating organizations in the river<br />

valley case.


Role of the researchers<br />

We joined the project in October 2003; it had <strong>for</strong>mally started in June 2003. We were<br />

given access to documents, we could participate in the meetings of the project, and<br />

we were allowed to interview a wide group of stakeholders. Moreover, the initiators<br />

were interested in multiparty collaboration and in the HarmoniCOP project and they<br />

voluntarily collaborated. The only restriction was that our presence or interventions<br />

could not lead to delays in the timing of the project or to extra expenses. We<br />

negotiated our potential role in the project, but the conveners had no interest or<br />

resources to give us a more ‘active’ role (e.g. process facilitation, design). We<br />

presented different models <strong>for</strong> participation to the in<strong>for</strong>mal group of conveners and<br />

consultants. The conveners were uncertain on how to involve stakeholders without<br />

endangering the objectives and values of their project. They also asked our advice,<br />

<strong>for</strong> instance, on how to organize the meeting of the first steering group. We gave<br />

them feedback of our observations and of the interviews from a learning perspective.<br />

Our primary aim, however, was to document the collaborative process.<br />

The members of the research team participated in the project with a somewhat<br />

different focus. CO1 was directly linked to the HarmoniCOP project as senior<br />

researcher. CO2 participated in the research as junior researcher <strong>for</strong> HarmoniCOP <strong>for</strong><br />

a period of about six months. I participated with my research agenda in the back of<br />

my mind (see attachment 1).<br />

Data collection<br />

My focus was on documentation of the process. I used observations and accounts to<br />

document the dynamics of direction setting in the process. I have summarized my<br />

approach to data collection in table 6.<br />

Date/Period Method of data<br />

collection<br />

116<br />

Participants/Setting Type of data


October 2003<br />

– November<br />

2004<br />

November<br />

2003 -<br />

February<br />

2004<br />

3 December<br />

2003<br />

13 February<br />

2004<br />

Participant observation<br />

of interaction moments<br />

(meetings)<br />

Stakeholder interviews<br />

semi-structured<br />

2 interviewers<br />

no taping<br />

note taking<br />

approx. 1,5 hour<br />

Feedback of key issues<br />

that emerged from the<br />

stakeholder interviews<br />

Reactions of the<br />

participants included as<br />

additional data<br />

117<br />

Coordination<br />

committee (8)<br />

In<strong>for</strong>mal ‘restricted<br />

committee’ (2)<br />

Planning group (1)<br />

Joint meeting<br />

planning and<br />

steering group (1)<br />

Steering group (1)<br />

First round: 5<br />

members of<br />

coordination<br />

committee<br />

Second round:<br />

selection of 12<br />

stakeholder<br />

representatives<br />

Two feedback<br />

sessions with<br />

conveners and<br />

consultants<br />

Field notes: 63p<br />

Field notes: 106p<br />

Field notes: 18p


15 September<br />

2004<br />

October 2004<br />

- November<br />

2004<br />

Feedback of main<br />

findings during overall<br />

project and discussion:<br />

‘Stakeholder workshop’<br />

(1 day)<br />

Reactions of the<br />

participants included as<br />

additional data<br />

Final round of<br />

interviews<br />

Ongoing Documents: reports,<br />

letters, mails, etc<br />

118<br />

Some<br />

representatives of<br />

the convening<br />

organizations and a<br />

selection of<br />

interested<br />

stakeholders<br />

Members of<br />

coordination group<br />

(4) and some<br />

stakeholder<br />

representatives (4)<br />

Issued by the<br />

conveners,<br />

consultants<br />

Field notes: 16p<br />

Field notes: 29p<br />

Written documents<br />

Table 6: Overview of the approach to data collection in the river valley case.<br />

Interviewing<br />

At the start of our research we interviewed the key actors (coordination committee)<br />

and a sample of stakeholder representatives with our team of three researchers. The<br />

interviews took place in the organization of the interviewee. We decided not to tape<br />

the interviews <strong>for</strong> reasons of confidentiality. Some interviewees confirmed that this<br />

made it easier <strong>for</strong> them to talk. One person took notes while the other asked<br />

questions. After the interview we immediately typed up our written notes and<br />

checked them with our colleague <strong>for</strong> accuracy. I participated in nine of the sixteen<br />

interviews.


We used a number of guiding questions in order to make the results of the<br />

interviews comparable. Questions included:<br />

- Who do you represent?<br />

- How are you involved in the project and how did you experience it so far?<br />

- How would you like to be involved in the future and how can you contribute?<br />

- What is your view on the objectives of the study and what would be the best<br />

approach to reach them?<br />

- Who are critical partners to be included in the process?<br />

- Who is mainly influencing the direction and results of the project?<br />

- What are the main enablers and obstacles in this project?<br />

- When, according to you, will this project be successful?<br />

First, we interviewed five members of the coordination committee. Then we fed back<br />

our findings to the in<strong>for</strong>mal group of conveners and external consultants. This<br />

enabled us to validate our findings and to help the key actors to become aware of the<br />

challenges, opportunities and obstacles in the process. The conveners suggested<br />

some names of relevant stakeholder representatives <strong>for</strong> further interviewing. With<br />

the same set of questions we interviewed 12 stakeholders. Again we discussed our<br />

findings with the in<strong>for</strong>mal group. I included the reactions to our feedback as<br />

additional data.<br />

At the end of our research, almost one year later, we organized a second round of<br />

interviews. We talked to eight participants: four members of the coordination group,<br />

and four members of the steering group. We split up the interviews: I interviewed six<br />

persons and my colleague the other two. We did not interview the conveners <strong>for</strong> a<br />

second time, because we just had an extensive discussion with them during a<br />

119


workshop which we organized (September). The questions of these semi-structured<br />

interviews included:<br />

- What, according to you, are the main issues in the project now?<br />

- How did you experience the way in which you and your organization were<br />

involved in the process? And what about the other actors? And the public?<br />

- What do you think about the way in which this project is coordinated?<br />

- Do you feel part of this project?<br />

- What event has, in the last year, most influenced the course of the project?<br />

- What lessons do you draw from this experience?<br />

We used the data from these interviews as additional in<strong>for</strong>mation <strong>for</strong> the case study<br />

report (HarmoniCOP). We did not feed back our findings with the coordination<br />

group or with the conveners, because our participation had stopped and the<br />

interviews did not reveal any new insights or in<strong>for</strong>mation.<br />

Participant observation<br />

Usually two researchers of our team were present at the meetings. In most meetings I<br />

took extensive field notes which I typed up straight after the meeting. I checked them<br />

with one or two of my colleagues <strong>for</strong> accuracy.<br />

Data analysis<br />

Analysis of stakeholder interviews and feedback<br />

We analyzed the interview data from first round of interviews in two batches (5 +<br />

11). The three researchers scrutinized the data and categorized the issues that<br />

emerged as critical. We presented them as ‘fields of tension’. The issues we found in<br />

the first five interviews included:<br />

- Mutual stereotyping between local and federal administrations;<br />

120


- No direct contact with the wide group of stakeholder representatives: to what<br />

extent is participation desirable or necessary and how should it be organized?<br />

- The mandate of the study is unclear and ambiguous: what is at stake?<br />

- Contradiction between the flexibility and openness in the approach of the<br />

communication process and the rigidity of the project: how much space is<br />

t<strong>here</strong> to do things differently than <strong>for</strong>eseen in the project proposal?<br />

- Mandate of the conveners: shouldn’t the <strong>for</strong>mal authority be involved in the<br />

process? Who will finance the interventions proposed in the plan?<br />

The fields of tension from the 11 stakeholder interviews were:<br />

- The conveners (one voice) vs. stakeholders (diversity and different voices)<br />

- Radical vision (long term ecological interests) vs. pragmatic approach<br />

(integration of interests)<br />

- Lack of clarity in in<strong>for</strong>mation (mandates, budget) vs. open and transparent<br />

communication (status of study, consequences of the interventions)<br />

- Technique (is data collection value free?) vs. politics (will the study be used to<br />

put pressure on the transfer of authority over the river?)<br />

- Interest of the stakeholders (desire and readiness to be more involved) vs.<br />

know-how (lack of ideas on how to involve or be involved; problem of time<br />

investment)<br />

- Goodwill (stakeholders are willing to collaborate and participate) vs.<br />

defensiveness (many stakeholders feel they are pushed in a defensive<br />

position)<br />

- Authority vs. actual role of the Navigable Waterways Administration (wish to<br />

be included in the coordination committee)<br />

121


Reconstruction of the collaborative process and inventory of emergent issues<br />

Based on all available data I made a process reconstruction (see chapter 3).<br />

Analysis of issues related to social learning<br />

We first analyzed the issues and dynamics based on the framework used in the<br />

HarmoniCOP project on social learning. The key concepts were: framing and<br />

reframing; basic role assumptions; boundary management; evolution of interests,<br />

functions, and strategies; critical moments; mechanisms that foster social learning;<br />

barriers to social learning. We used a checklist based on these issues which we had<br />

developed <strong>for</strong> work package 2 of the HarmoniCOP project (‘pool of questions’).<br />

These questions helped to scrutinize the data and to focus our analysis. The results of<br />

this analysis were discussed during the workshop and written down in the case<br />

study report (see attachment 10).<br />

Analysis of boundary dynamics<br />

Based on the process reconstruction and the previous analysis I made a more<br />

thorough and focused analysis of the boundary dynamics (inclusion and exclusion)<br />

in the project. This issue, one aspect of social learning, was directly relevant <strong>for</strong> my<br />

focus on the dynamics of direction setting.<br />

For the reader<br />

The paper presented on the next pages was published in January 2006 in Revue<br />

Gouvernance (see attachment 10). The paper may overlap to some extent with the<br />

text in this introduction. The subtitles are not numbered. As the project is still<br />

ongoing and politically sensitive, I have tried as much as possible to guarantee the<br />

anonymity of the participants. However, it was hardly possible to hide the identity of<br />

the participating organizations. The quotes in the articles have been translated from<br />

Dutch. I have tried to express the essence of what people say.<br />

122


‘We’ in the article, refers to the two or three researchers involved in this project.<br />

The findings are based on a case study on ‘Social learning in the development<br />

planning of a Flemish river valley. This study is part of the HarmoniCOP project on<br />

public participation in river basin management, funded by the EC 5 th Framework<br />

Programme.<br />

123


BOUNDARY DYNAMICS IN NATURAL RESOURCE MANAGEMENT: THE<br />

AMBIGUITY OF STAKEHOLDER INCLUSION (ARTICLE 2)<br />

Silvia Prins, Marc Craps & Tharsi Taillieu<br />

“We often experienced the river valley as a contemporary ‘battle field’ w<strong>here</strong> interests,<br />

opinions, and visions about the future are diametrically opposed to one another.”<br />

(Publication dedicated to the river of the case study, 2004)<br />

Introduction<br />

This paper discusses a case study in the domain of water management and nature<br />

conservation from the perspective of boundary dynamics. Multiparty collaboration is<br />

proposed as an organizational strategy to manage natural resources. This approach<br />

acknowledges the multiple perspectives of stakeholders, the differences in interest<br />

and power, and it provides a strategy <strong>for</strong> change in a domain with a high potential<br />

<strong>for</strong> conflict (Buckles, 1999). The first part of the paper outlines the theoretical insights<br />

and frames that underpin the case analysis. Then it discusses boundary issues in a<br />

project set up to design a plan <strong>for</strong> a river valley to solve problems of flooding and<br />

deterioration of nature. With this in-depth case study in a complex organizational<br />

setting we aim to contribute to empirical research on the perceptions of boundaries<br />

in processes of organizing (Paulsen & Hernes, 2003).<br />

Theoretical framework<br />

Multiparty collaboration: working across the boundaries<br />

The domain of nature and water management is traditionally governed by public<br />

administrations. Conventional ways of managing based on hierarchy and control as<br />

an organizational principle are, however, losing their meaning (Koppenjan & Klijn,<br />

2004). Public authorities realize that solving environmental ‘meta problems’ (e.g.<br />

flooding, pollution) calls <strong>for</strong> expert knowledge, while at the same time a wide range<br />

of stakeholders wishes to participate in the process. In order to arrive at an<br />

encompassing definition of the problem domain and to develop optimal, sustainable<br />

124


and widely supported solutions with a fair chance of implementation, it is essential<br />

to include a wide range of stakeholders with a diversity of perspectives. This<br />

organizational strategy is called ‘multiparty collaboration’ (Gray, 1989; Huxham,<br />

1996; Huxham & Vangen, 2005). Gray (1989, 5) defines multiparty collaboration as<br />

“(…) a process through which parties who see different aspects of a problem can<br />

constructively explore their differences and search <strong>for</strong> solutions that go beyond their own<br />

limited vision of what is possible”. It involves a process of collective decision making<br />

and negotiation among representatives of stakeholders of a problem domain, focused<br />

on the future development of the domain.<br />

The issue of boundaries is critical in collaborative work, because a collaborative is<br />

under-organized. It is an ‘emergent process’ (Gray, 1989). T<strong>here</strong> are few traditional<br />

structures and processes (e.g. hierarchy, structure, role, membership) to contain the<br />

uncertainty and openness of the process. A critical issue in this context is how the<br />

participants establish the boundary around the collaborative: who is included and<br />

who is left out? Does the collaborative represent the diversity, complexity and<br />

interdependence of the domain? The boundary of identity is an essential aspect in<br />

direction setting. Those who are included establish the problem definition based on<br />

their perceptions, interests and objectives, and consequently design the solutions.<br />

This confronts participants with the fear to lose their identity, to be ignored, to be<br />

overpowered by strong actors, or to be excluded from the process.<br />

The system psychodynamic perspective on boundaries<br />

An organization is a living system and boundaries make up its 'organizational<br />

anatomy' (Miller & Rice, 1967; Schneider, 1991; Zagier Roberts, 1994; Gould, Stapley<br />

& Stein, 2001). A boundary separates what is inside the system from what is outside<br />

and it regulates transactions with the environment (McCollom, 1995a). The survival<br />

of a system depends upon continuous interchange of ‘commodities’ (materials,<br />

people, ideas, values, fantasies) with the environment. A boundary is a ‘construct’. It<br />

can be conceived in different ways and serve different functions (Huffington &<br />

125


James, 1999; Diamond, Allcorn & Stein, 2004). The conception of boundaries ranges<br />

from concrete to abstract, from real to symbolic, and from physical to conceptual<br />

(Ehrlich, 2001).<br />

Boundary setting is an essential aspect of the process of organizing (Hernes, 2004).<br />

We study boundary setting from a psychological perspective. We consider a so-<br />

called ‘observable boundary’ as a reification. This refers, <strong>for</strong> instance, to physical,<br />

spatial and time indications that can be drawn on an organizational chart. A<br />

psychological boundary emerges when an individual or group marks a<br />

differentiation. Subjective boundaries are experienced and perceived by those inside<br />

and outside the system. They are enacted in the interactions among representatives<br />

and can be experienced at different levels: the intrapersonal, interpersonal, group<br />

level, the organizational, the inter-group or systemic level, and finally the inter-<br />

organizational level (Schneider, 1991; Wells, 1995; Ehrlich 2001). We assume t<strong>here</strong> is a<br />

relationship between the system features and the boundaries as they are experienced:<br />

the characteristics of the organizational context provoke particular dynamics and<br />

these dynamics in turn shape the organizational context.<br />

Because subjective boundaries are of an experiential nature, we use an interpretive<br />

approach (Schneider, 1991). This perspective on identity is rooted in constructionism<br />

rather than in social identity theory (Tajfel, 1978), which assumes that social identity<br />

is not easily changed. We focus on the dynamics of identity developed through<br />

interactions (Huxham & Vangen, 2005). The focus of the case analysis is on the<br />

dynamic and paradoxical nature of the boundaries. A boundary is not a clear cut<br />

line, but a ‘region’ or a ‘point of encounter’. It is subject to constant negotiation and<br />

definition in an inter-subjective process (Ehrlich, 2001). Boundaries separate and<br />

connect, constrain and release, restrict and enable, contain and create anxiety. “Once<br />

boundaries have been drawn, the possibility of relationship emerges” (Berg & Smith, 1995,<br />

115).<br />

126


Hirschhorn and Gilmore (1992) define the boundary of identity as: “who is, and who is<br />

not, ‘us’?” It is the group's understanding of who belongs to the group and who does<br />

not (Redlich & Astrachan, 1975). The boundary of identity is based on values and<br />

identification and defines the identity of a group. 'Sameness' or ‘difference’ refer to<br />

professional identity or culture (e.g. engineers, civil servants), membership of a<br />

particular local group (e.g. a project group, a hunting club) or it may have a more<br />

personal origin (e.g. gender, religion). Social identity is expressed through rituals,<br />

symbols or stories and the development of social norms. The identity of the system is<br />

the abstract characterization of a unity that persists over time (Merali, 2002). The<br />

group members can enact membership in their interactions with each other and with<br />

non-members. The boundary of identity <strong>for</strong>ms the psychosocial basis of group<br />

structure and is part of group development (Hartman & Gibbard, 1974). Becoming a<br />

<strong>for</strong>mal member of a ‘task group’ is relatively easy. It means being part of a group of<br />

individuals employed in an activity system (Miller & Rice, 1967). Psychological<br />

membership takes more time to develop (McCollom, 1995a).<br />

We analyze the case from the systems psychodynamic perspective on processes of<br />

organizing (e.g. Huffington, Armstrong, Halton, Hoyle & Pooley, 2004). From this<br />

perspective working in a collaborative is influenced by rational, conscious as well as<br />

by hidden, emotional and unconscious motives. In collaborative work groups share<br />

collective, unconscious assumptions about other relevant groups. “These assumptions<br />

are manifested in both conscious and unconscious processes, including projections,<br />

attributions, and stereotyping which shape the ensuing quality and character of their<br />

intergroup relationships.” (Gould, Ebers & Clinchy, 1999, 700) The pioneering work of<br />

Menzies (1960) has demonstrated that unconscious anxieties are often reflected in<br />

organizational structure and design, which function to defend against the anxieties in<br />

the workplace (‘social defenses’). We use this perspective to understand the<br />

emergence of the boundary of identity in response to the tensions provoked by the<br />

organizational experience. We analyze how the process was <strong>for</strong>malized and the way<br />

in which this triggered particular dynamics in the collaborative group.<br />

127


The boundary of identity and challenges <strong>for</strong> multiparty collaboration<br />

A first challenge is to set boundaries around the collaborative that are sufficiently<br />

firm. Collaboratives are often confronted with a fuzzy boundary of identity and an<br />

unstable group identity (Kramer, 1991; Vansina, Taillieu & Schruijer, 1998). In such<br />

case the collaborative remains an instrumental task group with fighting factions<br />

(Zagier Roberts, 1994). Direct interaction, joint work, and a relatively stable<br />

membership facilitate the process of group development and identification with the<br />

collaborative. It allows the group to develop into a so-called ‘sentient group’ or<br />

‘identity group’ to which individuals are prepared to commit themselves (Miller &<br />

Rice, 1967; Alderfer, 1987; McCollom, 1995b). Firm boundaries protect the<br />

participants from too much stress and uncertainty; they reduce the openness and<br />

complexity of the process, and provide some predictability and reassurance.<br />

Boundaries can contain the tensions of collaborative work and enable the group to<br />

work productively. When the participants manage to create a safe ‘transitional space’<br />

(Winnicott, 1971) they can engage in creative experimentation, innovation, and<br />

imagine scenarios without immediate binding consequences. It provides them with a<br />

temporary space w<strong>here</strong> they can express their questions, concerns and hopes, work<br />

them through, and jointly design the future.<br />

Groups often develop their identity through comparing and differentiating<br />

themselves from other groups, often a common enemy. In doing so the group<br />

defends against its shadow aspects by splitting them off and projecting them on an<br />

outside group (Gemmill, 1986, 1993). Strong identification with the group of<br />

‘insiders’ and disregard of other groups may lead to in-group/out-group dynamics.<br />

If the boundary of a collaborative is too firm it turns into a barrier and shuts out a<br />

vital part of the domain. A group can, <strong>for</strong> instance, deny the importance of particular<br />

stakeholders because they are experienced as a threat. In doing so, the system<br />

retreats from reality. A rigid boundary may block off the capacity of group members<br />

to relate, empathize, or deal appropriately with others. ‘Organizational silos’ emerge<br />

as the result of fragmentation caused by rigid boundaries and confront outsiders<br />

with a high threshold (Stein, 2004; Hernes, 2004). The boundary can be experienced<br />

128


as a ‘grey zone’ w<strong>here</strong> differences, separation and otherness are stressed (Diamond,<br />

Allcorn & Stein, 2004). When this tension is not contained, it may trigger defensive<br />

behavior (e.g. exclusion, scapegoating, or group think).<br />

A second challenge is to establish adequately fluid and flexible boundaries.<br />

Boundaries need to be adapted to changing conditions in the environment (e.g.<br />

change in policy) and to changes in the collaborative itself (e.g. new member, shifting<br />

objectives). In a multiparty logic a ‘convener’ invites stakeholder representatives to<br />

sit around the table. It is critical to include those stakeholders who are affected by the<br />

issue, who are needed to address the issue, and those who have the power to support<br />

or block collaborative action (Chrislip & Larson, 1994). The boundary around a<br />

collaborative is by its nature permeable because the members in their role as<br />

representatives bring in the interests of their constituency. A fluid boundary enables<br />

an inclusive process w<strong>here</strong> all stakeholders who represent the diversity,<br />

interdependence and complexity of the domain can participate in the dialogue. In<br />

this organizational logic boundaries are negotiated and not so much managed or<br />

controlled. However, a boundary that is too fluid can lead to confusion, over<br />

identification with others, and a loss of focus. The challenge is to support a sense of<br />

group spirit without disrespect <strong>for</strong> the potential contribution of other stakeholders<br />

(Hirschhorn & Gilmore, 1992).<br />

A final challenge is to create a multifaceted collective identity. A collaborative is<br />

composed of representatives with different social identities (e.g. engineers, public<br />

officers, farmers, residents). The representatives come together precisely because<br />

they are different and because they hold different perspectives (Zagier Roberts,<br />

1994). Diversity makes up the essence of collaborative work. Multiparty collaboration<br />

is about trans-disciplinary work, or working with diversity, and not so much about<br />

inter-disciplinarity. The challenge is to maintain the diversity around the table, and<br />

to arrive at sufficient common ground and shared values to enable change and<br />

productive work.<br />

129


The case: wet feet and dry marshes<br />

Antecedents and context of the case<br />

The river under study used to have an important economic value <strong>for</strong> the region (e.g.<br />

shipping activities, water mills). As early as the 17th century interventions to reduce<br />

meandering were implemented to improve the use of the river. Although t<strong>here</strong> has<br />

not been any shipping activity <strong>for</strong> the last 100 years, the river was still, at the time of<br />

the project, under the authority of the Navigable Waterways Administration. The<br />

policy of this administration was damming up and deepening the river, and<br />

straightening its course. Controlling the river was in the interest of farming activities<br />

in the valley. A consequence of this policy was a low ground water level in the valley<br />

leading to a deterioration of nature. On a regular basis villages were flooded, while<br />

at the same time the valley was dry.<br />

In the '80s the idea of ‘integrated’ water management gained in importance. In this<br />

vision water is managed as a total system guided by the principle of sustainability.<br />

The focus is on safety against flooding by giving space to the river, and preservation<br />

and development of nature. In December 2000 the European Water Frame Directive<br />

was issued. Flanders translated the European policy in the ‘Decree <strong>for</strong> integrated<br />

water management’ (July 2003). The European Directive promotes integrated and<br />

participative management of river catchments. At the time of the case study different<br />

administrations managed surface and ground water, the natural environment, and<br />

land use affecting the river: the Flemish government, Provinces, municipalities, and<br />

local groups of volunteers. Moreover organizations of different kinds were involved:<br />

governmental, semi-official and non-governmental. Responsibilities in water<br />

management were unclear and dispersed.<br />

Water management is by its nature a problem domain w<strong>here</strong> the involvement of<br />

multiple stakeholders with different perspectives, claims and interests is required.<br />

Water is a powerful symbol of interdependence because it connects all actors. It<br />

demonstrates the conflicts in use, claims and interests. Some stakeholders, <strong>for</strong><br />

instance, use ground water to purify it <strong>for</strong> drinking, while others use the river to<br />

130


drain effluent from their industry. A water system includes not only surface and<br />

ground water (quantity as well as quality), but also the plants and animals living in<br />

and around the river, the chemical and biological processes, the river banks, the<br />

bottom of the river and the technical infrastructure. It includes the ecological and<br />

economical functions of the river and the valley. The new policy states that the<br />

boundaries of a catchment establish the system responsible <strong>for</strong> managing the river<br />

basin (e.g. across national borders), and not administrative structures.<br />

The case study concerns a section of one of the 11 river basins in Flanders. As early as<br />

the 90’s, be<strong>for</strong>e the European Directive, the Flemish subdivisions of Water and<br />

Nature Management (established in 1990) carried out studies in this valley. They<br />

developed a digital model of the area, installed monitoring devices, and adopted<br />

software programs <strong>for</strong> modeling. The unique ecological value of the valley came to<br />

the <strong>for</strong>eground since farming activities were in decline due to world wide<br />

competition. Today a large part of the territory is protected area (e.g. European Bird<br />

and Habitat Directives) and in the hands of the Flemish administration of Nature and<br />

of environmental groups.<br />

The case story<br />

The departments of Nature and Water (Flemish Administration of Environment)<br />

initiated the study project (June 2003 – March 2005) in a joint ef<strong>for</strong>t. For the<br />

conveners (a core group of four public officers) it was the result of a long process.<br />

The study represented the ‘the jewel on the crown’ and in their letter to the local<br />

authorities they introduced it as ‘the ultimate study’. The aim of the project was to<br />

develop an ‘integrated vision’ <strong>for</strong> the river valley, with a focus on flood prevention<br />

and protection of nature. The study had to align with several other plans related to<br />

river management, area planning and nature development which were being<br />

developed at the same time. The negotiated outcome of the study was a plan <strong>for</strong> the<br />

valley, supported by the stakeholders, that could eventually be integrated in nature<br />

and river plans on a wider scale.<br />

131


Subsystems Representatives of… Responsibilities/role<br />

Coordination group Flemish and<br />

administrations <strong>for</strong> Water<br />

and Nature<br />

Provincial administrations<br />

<strong>for</strong> Water and Nature<br />

External consultants<br />

Planning group Public actors:<br />

Flemish administrations in<br />

water and nature<br />

management<br />

Steering group Civil actors:<br />

Provincial administration<br />

Local authorities (5 cities<br />

and villages)<br />

Organized stakeholder<br />

groups (e.g. farmers,<br />

industry, environmental<br />

groups, <strong>for</strong>est owners, and<br />

angling group)<br />

Work groups Members of planning or<br />

steering group and other<br />

interested participants<br />

132<br />

Control the process<br />

Disseminate in<strong>for</strong>mation<br />

Establish and facilitate<br />

sub-systems<br />

Communicate with<br />

external consultants<br />

Develop vision <strong>for</strong> the<br />

valley<br />

Table 7: Organizational structure of the river valley project.<br />

Take decisions<br />

Consultation<br />

Participation<br />

Work out proposals <strong>for</strong><br />

concrete solutions<br />

The initiators structured the project to organize participation (table 7). Federal,<br />

Flemish and provincial administrations, local authorities, three consulting firms and


a wide range of stakeholder groups in society were represented in the substructures<br />

of the project.<br />

The project was organized in three phases: (1) what do we have? (environmental<br />

study and sector analysis); (2) what do we want? (visioning process); (3) what are we<br />

going to do? (planning of specific interventions). In the first phase the consultants, in<br />

collaboration with public officers from the catchment and sub-catchment planning,<br />

interviewed the 'sectors' or groups of organized stakeholders (e.g. hunting group,<br />

industry, housing, tourism). The purpose was to make an inventory of the pressures<br />

and claims on the water system by different sectors. The result was an overview of<br />

bottlenecks and opportunities. The conveners and consultants communicated the<br />

results of the first phase to the steering group and the planning group in a first joint<br />

meeting in March 2004.<br />

In the second phase the conveners set up three workgroups to develop proposals <strong>for</strong><br />

solutions: recreation (e.g. align the claims of hikers, bike riders and horse riders on<br />

the territory), hydrology (e.g. reconnect meanders) and land use (e.g. solve problems<br />

of illegal weekend cottages). In the meantime the coordination group tried to<br />

develop a scenario <strong>for</strong> the river valley based on simulation studies. In March 2005, at<br />

the end of the 22 months, the coordination group organized a second meeting of the<br />

steering group w<strong>here</strong> they presented their provisional plan <strong>for</strong> the river valley.<br />

Research approach<br />

The project had started six months be<strong>for</strong>e we negotiated our participation. We<br />

collected data over a period of one year (November 2003-2004). In March 2005 we<br />

also attended the second meeting of the steering group. The initiators of the project<br />

gave us access to documents, meetings and we were allowed to interview<br />

stakeholders. They were interested in our experiences and ideas on multiparty<br />

collaboration and open to discuss and learn from our feedback. Our role was a<br />

133


combination of observation and interventions (Schein, 1987). In an action research<br />

perspective we made the following interventions:<br />

- Interviews (5) with the members of the coordination group<br />

- Feedback of our findings to the initiators and consultants<br />

- Interviews (12) with a selection of stakeholder representatives (e.g. hunters,<br />

local authorities, environmental group, and farmer group)<br />

- Feedback of our findings to the initiators and consultants and discussion of<br />

potential bottlenecks and opportunities.<br />

- Workshop at the end of the year with some members of the coordination<br />

group and a small number of interested external actors (e.g. administration, a<br />

municipality) to discuss our observations.<br />

- Final round of interviews (8) with members of the coordination group and<br />

some relevant stakeholder representatives to reflect on their experiences.<br />

Over a period of one year we observed meetings of the coordination group (8), the<br />

planning group (2) and the steering group (2). Our aim was to construct a rich, local<br />

and contextualized understanding of this particular collaborative experience (Geertz,<br />

1973; Yin, 1994). In the case analysis we discuss the following questions: (1) what was<br />

the nature of the boundary of identity that emerged? (2) Which dynamics emerged at<br />

the boundary? (3) What attempts were made to include stakeholders and to develop<br />

a multifaceted identity?<br />

Case discussion<br />

Identification with the project: the boundary of identity<br />

The institutional context influenced the <strong>for</strong>mal structures that were established early<br />

in the project. The conveners were concerned about the legitimacy of decisions taken<br />

in the project. They relied on legal procedures in the field of nature conservation to<br />

establish membership of the project, to define the role and mandate of the subgroups,<br />

134


and to organize the process (table 7). The ‘coordination group’ was at the heart of the<br />

project and of our research. The river valley as an ecosystem was characterized by a<br />

number of physical features, such as water and land, water quality and water<br />

quantity, and surface or ground water. These areas defined the responsibilities of the<br />

administrations. The intricate nature of responsibilities and authority in the domain<br />

was reflected in the project. The administration responsible <strong>for</strong> water quantity, <strong>for</strong><br />

instance, was at the heart of the project, but the administration <strong>for</strong> water quality was<br />

only marginally involved (steering group).<br />

An important aspect at the start of the project was the issue of ambiguous authority<br />

relations. The largest part of the river section under study was not under the<br />

authority of the department Water. Although t<strong>here</strong> had not been any shipping<br />

activity, it was still managed by the Navigable Waterways Administration. The<br />

transfer of authority over the river to the department Water had been on the political<br />

agenda <strong>for</strong> many years. The initiators had started the project assuming that a transfer<br />

was imminent. They acted as if they had the authority to take decisions and did not<br />

include the Navigable Waterways Administration in the conception phase of the<br />

study. Originally they were not even a member of the coordination group. Exclusion<br />

of this critical partner raised questions about the legitimacy of the project and the<br />

likelihood of implementation. The representative of the Navigable Waterways<br />

Administration pointed out they still had the power to refuse implementation if they<br />

did not agree. "But we don't intend to do that. As long as we are sufficiently involved."<br />

(Interview). They felt it should have been ‘their’ project.<br />

The boundary of identity was strongly influenced by identification with ecological<br />

values and by the way the conveners identified with their professional role. The<br />

study was the result of a joint initiative of the departments Land and Water. Both<br />

departments had been working together in the valley since 1995 in a project on<br />

‘Integrated water management’. Submitting a joint project had been an<br />

‘unprecedented’ and ‘very fruitful’ experience.<br />

135


“Writing together, paying together, that is not self evident and it does not happen very<br />

frequently!” (A convener, interview)<br />

“Trust among us is 100%” (A convener, interview)<br />

The project was inspired by common values and resulted in a shared strategy based<br />

on the ‘natural space <strong>for</strong> water’ vision. This strategy, addressing the complex<br />

interactions between water and the surrounding land, was promoted as an<br />

alternative <strong>for</strong> the old “infrastructure and control” approach. The conveners strongly<br />

identified with ecological values which they promoted as central in this study. Most<br />

of them had been, or still were, active in environmental groups and they knew the<br />

valley very well. When they started working at the departments <strong>for</strong> Nature and<br />

Water, established in 1990, they hoped they were in a position to make a difference.<br />

The initiators invested far more time than originally budgeted in the project. The firm<br />

boundaries around the group of conveners, based on strong identification with the<br />

values promoted in the project generated the energy and drive to commit to the<br />

project.<br />

One of the initiators talked about ‘our’ river and ‘our’ valley. We often wondered<br />

who he was referring to. During the final workshop we organized, he made a<br />

passionate statement. It clearly illustrates the values of the conveners, their<br />

assumptions about stakeholder inclusion and how this influenced the way they<br />

managed the boundaries in the project.<br />

“The objective of the study is not open to discussion. Nature conservation must be realized. The<br />

circumstances are favorable right now. This draws important boundaries <strong>for</strong> us and <strong>for</strong><br />

everybody. I want to protect those boundaries. The participative approach must also take those<br />

boundaries into account. The project proposal has <strong>for</strong>eseen to work a little bit in a participative<br />

way. We must take the actors into account. The agricultural study, <strong>for</strong> instance, is carried out by<br />

an independent organization. So we know the concerns of the farmers. We wanted to do a<br />

similar study <strong>for</strong> recreation last year but t<strong>here</strong> were no resources. We have carried out a <strong>for</strong>est<br />

analysis. The boundaries of the study are: the danger of flooding and nature conservation. The<br />

other actors are in the valley. We have to do some sort of interactive process and take a<br />

decision. Participative management is a flexible notion. Depending on the circumstances you<br />

have to define and organize the degree of participation. I’m not in favor of extreme<br />

participation. The problem definition had been defined a long time be<strong>for</strong>e the start of this<br />

study!! (…) If we reach consensus with all the actors: how much would be left of nature? I don’t<br />

believe in it. Nature interests always conflict with many other interests of individuals and<br />

groups. Who defends nature against all those individual interests? (…) Nature conservation is a<br />

very weak sector. In public participation nature always has to give in.” (A convener, workshop)<br />

136


A second source of identification was the way in which the conveners made sense of<br />

their professional role. They were convinced that the administration ‘knows what is<br />

best <strong>for</strong> the public’ and that it has to ‘defend the public interest'. For the conveners<br />

the study was about ‘policy preparation’. In their role of defenders of environmental<br />

values in the interest of the public, they took a central position in the project, both in<br />

the coordination group and in other subgroups. This central position was enacted<br />

and expressed in different ways. For instance, all meetings of the coordination group<br />

were held in the building of the administration <strong>for</strong> Nature. The documents of the<br />

project were presented in a folder with a dandelion on the cover, which <strong>for</strong> some,<br />

became a standing joke. At one point an in<strong>for</strong>mal ‘restricted committee’ was<br />

established, made up of the conveners, the consultants, and the researchers. This<br />

group of ‘insiders’ met several times to discuss the feedback from our interviews and<br />

observations. The group was safe enough to openly talk about the worries and hopes<br />

of the participants and about the opportunities and pitfalls of the project.<br />

Not all the members of the coordination group identified with the ecological values<br />

advocated in the project (table 8). T<strong>here</strong> was a split between on the one hand the<br />

conveners and some sympathizing administrations, and on the other hand the<br />

Navigable Waterways Administration.<br />

Conveners: Water and Nature<br />

Administration<br />

Vision The river as an ‘eco-system’:<br />

river and land<br />

Historical perspective: ‘natural<br />

river’<br />

Priorities Nature development<br />

Safety against flooding<br />

137<br />

Formal authority: Navigable<br />

Waterways Administration<br />

A ‘controlled river’ as a<br />

separate unit<br />

Civil engineering<br />

interventions<br />

Safety against flooding<br />

Control of the river


Professional<br />

identity<br />

Political and<br />

financial power<br />

Method of<br />

influencing<br />

Bio-engineers and system<br />

engineers<br />

Representatives of the public<br />

interest<br />

Low budget<br />

No political support<br />

No political influencing<br />

Technical evidence to support<br />

discussion<br />

Consultation of stakeholders<br />

No authority over the river<br />

138<br />

Civil engineers and hydraulic<br />

engineers<br />

Experts<br />

High budget<br />

Political support<br />

Political lobbying<br />

Technical evidence as solution<br />

Unilateral interaction based on<br />

expert knowledge<br />

Formal authority over river<br />

Table 8: Differences between the two central groups in the coordination group<br />

(river valley case).<br />

The administrations had had several conflicts in the valley. Following a severe<br />

flooding in the valley in 1998, <strong>for</strong> instance, the Navigable Waterways Administration<br />

had carried out civil engineering works at the river banks without construction<br />

permit. After a <strong>for</strong>mal complaint they had to take away the illegal dams because they<br />

did not fit with the new policy of water and nature management. The result was a<br />

hostile relationship in the valley between those in favor of the environment and those<br />

in favor of engineering interventions.<br />

“Lately a hostile image emerged around the environmental movement, due to what the<br />

administration has done. The authorities act in a pretentious way. They ignore the people.<br />

Communication has fallen still. They used to need us to become big and strong. But society<br />

changes, underneath it is boiling. (…) The water company, <strong>for</strong> instance, wanted to build a<br />

collector. They wanted to install the pipes in the streets. They bullied the people. They tell them<br />

‘the environmentalists don’t allow us in nature, so t<strong>here</strong><strong>for</strong>e we are <strong>for</strong>ced to go through your<br />

streets. T<strong>here</strong> is no point in objecting, because those of nature are in control.’ (…) They have<br />

unnecessarily stirred up emotions. The engineers were rude. If t<strong>here</strong> is resistance, they blame<br />

the environmental groups!” (A representative of an environmental group, interview)<br />

The antagonistic relationship between the administrations resulted in distrust,<br />

mutual stereotyping, blaming and exclusion. The conveners blamed their rival <strong>for</strong>


eing incompetent, not knowing what happened in the field, a radical approach,<br />

making mistakes, operating like a barony, and <strong>for</strong> not having any ecological<br />

awareness. The Navigable Waterways Administration accused the conveners of<br />

being ‘fundamentalist’, unrealistic and unfair. A representatives of the Navigable<br />

Waterways Administration remembered feeling left out during the meetings of the<br />

coordination group. He criticized the way in which the conveners positioned<br />

themselves and how they dealt with the process. His colleague objected to the<br />

stereotyping by the conveners.<br />

“We are in a strange situation now. They are studying a river over which they have nothing to<br />

say. (…) They are quite fundamentalist. They talk with everybody and then they don’t take that<br />

into account. (…) Everything starts from their vision. And we have to adapt the river. That is<br />

the world upside down! (…) I feel ignored in the coordination meeting. They take note of what I<br />

say, but they simply continue what they are doing. (…) Is t<strong>here</strong> sufficient support <strong>for</strong> what they<br />

are doing? (…) I felt alone in a room full with green ghosts. (…) I have the impression they want<br />

to prove they are right. And on that basis take over the authority over the river. I just want to<br />

avoid they make a plan that cannot be implemented. I want to protect them against themselves.<br />

(…) They have no money.” (A representative Navigable Waterways Administration, interview)<br />

"We have done some interventions t<strong>here</strong> in the nineties that were not appreciated by some. We<br />

have lost part of our credibility with some administrations at that moment. (…) At the time the<br />

river came to us on instruction of the Ministry of Agriculture, in the sixties. It was our task to<br />

straighten the course of the river in order to create more potential <strong>for</strong> farming. We have fulfilled<br />

that mission. The result was that the water is evacuated more quickly. Now t<strong>here</strong> are different<br />

and good ideas. The administration Water says: 'Those people from the Navigable Waterways<br />

Administration have ruined everything.' But at that time the vision was totally different! That is<br />

not our fault. Our vision changed a little later than theirs, but it did change in the meantime.<br />

(…) The image they have of us is totally wrong and has nothing to do with who we are today."<br />

(A representative Navigable Waterways Administration, interview)<br />

The conveners had a hidden agenda that provided them with an extra drive. They<br />

wanted to prove themselves, hoping this would speed up the transfer of authority<br />

over the river.<br />

“The study is an instrument to <strong>for</strong>ce a number of things. We say that the Navigable Waterways<br />

Administration is slow and incompetent. For our own credibility we must be able to do it and<br />

do it quickly.” (A convener, interview)<br />

The initial exclusion of a critical partner, strong identification of the conveners with<br />

ecological values and with their professional role established a firm boundary<br />

around a small group of ‘insiders’. T<strong>here</strong> was stereotyping and distrust on both<br />

sides. This led to tense relationships and splitting in the coordination group: the two<br />

subgroups had difficulty to perceive the other organization as both good and bad.<br />

139


The conveners wanted to keep control over the process and defend their values,<br />

interests and objectives. The small inner circle tried to provide the identity of the<br />

project and to push their agenda, even though they had no <strong>for</strong>mal authority. The<br />

‘identity group’ seemed to be narrowed down to the small group of conveners,<br />

supported by the external consultants and to some extent by the researchers. This<br />

in<strong>for</strong>mal grouping provided the conveners with a ‘potential space’ (Winnicott, 1971)<br />

w<strong>here</strong> they could openly discuss their hopes, doubts, worries and w<strong>here</strong> they could<br />

safely engage in learning and experimentation with ideas and future scenarios. As<br />

we will demonstrate, this made them more confident in the way they organized and<br />

facilitated the process.<br />

Fluidity of the boundary: the ambiguity of stakeholder inclusion<br />

The conveners struggled with questions and dilemmas related to stakeholder<br />

inclusion. How should we organize a participative process? Are representatives of<br />

groups and organizations able to make conscious and well in<strong>for</strong>med choices? At<br />

what moment should we include the stakeholders? They asked us to present<br />

different models <strong>for</strong> participation and were very interested in ways to involve<br />

stakeholders. The conveners had designed participative procedures and structures in<br />

the project. They encouraged the participants of the steering and planning group to<br />

participate.<br />

“We are going to involve everybody as much as possible. How are we going to do that? The<br />

Federal government takes the final decision. We are going to organize consultation and<br />

participation according to the guidelines. (…) This is an important decision process. It is the<br />

first time in 45 years that we think about this river. Now is the moment. In<strong>for</strong>mation will be<br />

available. If you want your voice to be heard: now is the moment to come <strong>for</strong>ward. (…) Take<br />

active part, give us your name and participate in the work group discussions!” (A convener,<br />

first joint steering and planning group)<br />

However, they were uncertain about how to organize participation without<br />

endangering ‘their’ project. A number of assumptions about their role, the role and<br />

potential contribution of stakeholders, and about participation in general prevented<br />

them from actively including stakeholders in the dialogue. We discuss the<br />

140


assumptions of the main representatives and the way they organized the process. We<br />

conclude this section with some boundary dynamics which we observed.<br />

At the start of the project the conveners assumed that the administration needed to<br />

come up with a waterproof plan, elaborated by the coordination group and the<br />

external consultants. They only felt safe enough to engage in a discussion with other<br />

administrations and stakeholder representatives with a solid plan. For them<br />

participation meant ‘selling’ the plan to the main stakeholders, establish sufficient<br />

support, and then organize a meeting <strong>for</strong> the planning and steering group. T<strong>here</strong><strong>for</strong>e<br />

they organized several bilateral consultation meetings with the farmers and local<br />

municipalities to make sure they agreed on the scenario. The conveners wanted to<br />

avoid a public attack of their plan during a steering group meeting.<br />

“You cannot just throw your plan <strong>for</strong> the lions. You have to prepare the terrain. The only<br />

question is: how? (…) The steering group must get a finished product that we can defend. We<br />

do not intend to discuss it with them.” (A convener, interview)<br />

It was obvious <strong>for</strong> the conveners that the objectives of the study could not be<br />

questioned. The conveners consulted the stakeholders (sector analysis) and after<br />

almost two years in<strong>for</strong>med them of the plans developed by the experts (steering<br />

group). ‘Participation’ was used as an instrument to prevent resistance. The<br />

conveners were defensive about their project because they feared that most<br />

stakeholders in the valley were against their plans. This was partly due to a history<br />

of conflicts between the administration and other stakeholders in the valley. It had<br />

resulted in mutual stereotyping and a focus on what divided the parties. One<br />

representative of a municipality, <strong>for</strong> instance, talked about the ‘unrealistic green<br />

boys’ of the administration, while someone from the administration blamed the<br />

municipalities <strong>for</strong> being ‘incompetent’ and ‘only interested in short term plans’<br />

because of their political agenda. However, the sector analysis and our interviews<br />

demonstrated that most stakeholders were in favor of an ecological agenda. For<br />

instance, some hunters collaborated with the environmental group (e.g. shooting<br />

wild ducks in the valley). A small number of farmers was involved in a project to<br />

141


promote ecological tourism. Most interviewees did emphasize that other interests<br />

had to be taken into account as well.<br />

“The green movement has missed a tremendous opportunity by positioning themselves in a<br />

diametrically opposed relationship to the farmers… By first going to the people you can avoid a<br />

lot of problems.” (A representative of a local authority, interview)<br />

Ambiguous assumptions about the legitimacy and competence of stakeholders<br />

emerged. During the workshop most participants agreed on the importance and<br />

relevance of gathering everyone around the table. They argued it was not always self<br />

evident to identify which parties were legitimate stakeholders. A representative of a<br />

municipality stated, <strong>for</strong> instance, that collaboration between government<br />

organizations is relatively easy because those parties are ‘organized and competent’.<br />

The conveners only wished to negotiate with representatives of ‘organized’<br />

stakeholder groups and administrations. However, the conveners did not believe the<br />

representatives were willing or competent to represent the interests of their<br />

constituency. According to them, the representative of the hunting group only<br />

participated in the work group ‘recreation’ out of personal interests and not to<br />

defend the interests of his group.<br />

"We want to get away from taking into account local and individual interests that oppose<br />

general interests. It is not democracy, otherwise you cannot achieve anything. (…) The local<br />

governments play an important role. I am a man of administrations. The governmental<br />

structures are the result of democracy. You have to negotiate with the representatives. I don't<br />

want to worry about all sorts of interest groups. The local governments are important.<br />

Everybody has to do his job. But in practice the local governments do not represent the interests<br />

of all societal groups. (…) The problem is: politicians want to score. T<strong>here</strong> is a conflict between<br />

short term interests and the interests of the community and interests that transcend<br />

boundaries." (A convener, interview)<br />

“Everybody in the area must be kept in<strong>for</strong>med and from time to time must have the<br />

opportunity to say something. (…) Maybe it sounds pejorative, but the local authorities are only<br />

interested when they can score over a period of six years: industry zones, bike lanes, flooded<br />

houses,… and when they have their face in the press. A federal plan and a study of two year do<br />

not fit with their priorities.” (A convener, interview)<br />

In the organizational design they had deliberately separated representatives of public<br />

authorities (planning group) and stakeholder representatives (steering group) to<br />

avoid confrontation. They were uneasy about direct interaction and uncertain about<br />

changing their way of managing a project.<br />

142


“We made sure the federal and provincial administrations were separated from the interest<br />

groups. (…) Public institutions speak differently in the presence of societal groups. (…) It is a<br />

steering group that does not steer. Something is not right… At this moment it is the only way.<br />

T<strong>here</strong> is no tradition.” (A convener, interview)<br />

One of the insights in the workshop was that t<strong>here</strong> had been no role negotiation or<br />

clarification of the expected contribution of the stakeholders at the start of the<br />

process. The participants realized that the stakeholder groups had not been aware of<br />

their potential impact on the process. All stakeholders had assumed the<br />

administrations would, as usual, take the decisions.<br />

“It is important to draw the boundaries of participation and to clearly discuss expectations with<br />

the participants. Telling them what their role and input can be and what will happen with their<br />

contribution” (A participant in workshop).<br />

The participants of the workshop considered consultation or involvement of the<br />

general public as irrelevant and not constructive. One public officer gave an example<br />

of an urban planning project w<strong>here</strong> she had tried to directly involve the public. She<br />

had been disappointed because the only response she got was: ‘not in my backyard’.<br />

As is the custom in Flanders, public participation is reduced to an existing <strong>for</strong>mal<br />

procedure. It is a way of avoiding direct interaction with the public.<br />

“Participation of the public is <strong>for</strong>mally organized. That is the procedure of ‘public inquiry’. The<br />

public has 60 days to look at the plans and introduce a <strong>for</strong>mal complaint. (…) In such a process<br />

you often get the most stupid remarks.” (A convener, interview)<br />

Most stakeholders we interviewed argued that a unilateral plan from the<br />

administration would not solve the problems in the valley. They were in favor of<br />

participation and wished to contribute to the development of solutions.<br />

“We became aware of the fact that we have to deal with the totality of the problem in a different<br />

way. If we only intervene to solve separate aspects of the problem, the problem simply shifts.<br />

(…) It is also important that it is more differentiated now. It is not about water, and that’s it. No,<br />

it is about rainwater, waste water, etc. We did not make that difference be<strong>for</strong>e and t<strong>here</strong><strong>for</strong>e we<br />

did not see clearly what the essence of the problem was. (…) We all used to sit on our little<br />

island. Now we work more easily across boundaries. For instance, around mobility and water.”<br />

(A representative of a local authority, interview)<br />

“On the Flemish level the idea of participation and alternatives is getting accepted. Public<br />

officers were used to being left in peace. 'We know better!' Now they are under fire.” (A<br />

representative of an environmental group, interview)<br />

143


Particularly at the start of the project the conveners perceived participation of<br />

stakeholders as a threat. A dilemma that came up on a regular basis was the ‘timing’<br />

of participation.<br />

“In the beginning the direction is not yet established. Is it worthwhile to undermine the process<br />

be<strong>for</strong>e it even started? (…) I see a tension between on the one hand wanting to have a finalized<br />

product that is clear, so we know what to communicate. On the other hand, however, once it is<br />

clear, t<strong>here</strong> is no time left <strong>for</strong> discussion and consultation. That is a bottleneck." (A convener,<br />

interview)<br />

The conveners hoped the results of the simulations and modeling process would<br />

reduce uncertainty and would provide them with solid, scientific in<strong>for</strong>mation to<br />

choose the ‘best’ scenario. They assumed that a perfect technical solution would be<br />

acceptable to all stakeholders, and would solve potential conflicts in the valley.<br />

Because of a strong belief in a technical solution, the conveners did not consider<br />

stakeholder or public participation as a necessity and heavily relied on the expertise<br />

of the consultants. For them the study was an “engineering contract” and not a project<br />

focusing on “facilitation of a process” (a convener). This implicit assumption was<br />

reflected in the project proposal. T<strong>here</strong> was no budget or plan <strong>for</strong> ‘communication’.<br />

The consultants expected the public officers to deal with that part of the process. The<br />

conveners, however, could not specify how they wanted to organize the<br />

‘communication process’. It seemed as if they had assumed that the technical<br />

scenario and the legal procedures and structures would be sufficient to manage the<br />

process.<br />

A number of role assumptions also influenced how the conveners dealt with the<br />

process. During the workshop they talked about the tension of being engaged in a<br />

double role. The initiators primarily identified with the role of stakeholder,<br />

defending the interests of their administrations. They also found themselves in the<br />

role of ‘convener’ of the process. This role refers to one or more stakeholders who<br />

create a <strong>for</strong>um <strong>for</strong> dialogue among the stakeholders and persuade others to<br />

participate (Gray, 1996). They felt uncertain in the role of convener because it was<br />

unfamiliar to them and they lacked the skills and experience to facilitate a multi-<br />

stakeholder process. Some realized this double role could lead to a confusion of<br />

144


interests. Indeed, many stakeholder representatives we interviewed did not perceive<br />

the initiators as neutral and credible facilitators of a ‘participative process’. For many<br />

the study was a vehicle <strong>for</strong> the administration to push the environmental agenda.<br />

Many stakeholders felt left out, not heard, they did not know how to take up a<br />

meaningful role, and they did not identify with the project.<br />

"I have the impression that it is private business between the engineers and the administration.<br />

That is how I feel it. T<strong>here</strong> is a lot of decadence, inertia and it is an arrogant administration." (A<br />

stakeholder, interview)<br />

"It cannot be one-sided. The valley is in the first place a natural reserve, but it also has other<br />

sides." (A stakeholder, interview)<br />

"The danger is that someone says: we know best" (a stakeholder, interview)<br />

In the course of the project, the initiators decided to split the two roles. Two senior<br />

administrators took up the role of convener and president of the meetings. This<br />

created space <strong>for</strong> their collaborators to defend the interests of the administrations.<br />

They also handed over presidency of the ‘workgroup recreation’ to an acceptable<br />

partner in the project. This enabled them to participate as stakeholder in the group.<br />

According to the conveners the external conditions were not favorable <strong>for</strong> a<br />

participative process. The conveners realized that decisions were taken in places they<br />

had no access to. This undermined the credibility of the participative process. For<br />

instance, in the course of the project, a new Minister <strong>for</strong> Environmental Affairs, who<br />

was known to support farmers, was appointed after the elections. They feared that<br />

this shift would endanger the priority of the project and the chances of<br />

implementation. With the new Minister the transfer of the authority over the river<br />

became unlikely. To add to the turbulence, the administrations were in the midst of<br />

a reorganization process. The status of the project was uncertain: nobody knew what<br />

would happen with the outcome of the study.<br />

“The most important question of the stakeholders was related to the legal character of the<br />

study: how binding are the results? (…) The fact that it is called a ‘study’ is confusing. It sounds<br />

as if it is without engagement. The vision that will be developed… is it legally valid?” (A<br />

representative of a provincial administration, interview)<br />

145


In the course of the process we observed some boundary dynamics expressing the<br />

ambiguity of the conveners to open up the boundaries of their identity group. A first<br />

observation was the dominance of the technical discourse. This created a gap<br />

between experts and laymen. For instance, when the consultants and specialists of<br />

the administration presented the models and scenarios <strong>for</strong> the valley the participants<br />

of the planning and steering group complained it was too ‘technical’. The members<br />

of the ‘workgroup hydrology’ also needed a fair amount of technical expertise to be<br />

able to follow the discussions (e.g. read maps, interpret results of simulation, and<br />

understand the consequences of an intervention). This created a threshold <strong>for</strong> laymen<br />

to participate.<br />

“To what extent can you disconnect the technical solutions from the participative process? To<br />

what extent are laymen interested in the technical part of the process?” (A public officer,<br />

workshop).<br />

The technical tools were not designed as communication tools, but merely as<br />

technical instruments to discuss technical problems among experts. T<strong>here</strong> was little<br />

attention <strong>for</strong> a ‘translation’ of technical language to the wider group of stakeholders.<br />

The result was that the consultants had a central role and a strong impact on the<br />

agenda of the project. As they carried out the sector analysis (interviews with<br />

organized stakeholder groups), they had the contacts, they possessed the knowledge<br />

and they were the ones crossing the boundaries. The simulations seemed to function<br />

as a transitional object (Winnicott, 1971) that helped them to contain the anxiety<br />

stirred up by the openness and complexity of the process. It provided the<br />

participants with a ‘plan’ to talk about’ and it facilitated the change process. The<br />

technical tools and solutions gave the participants some security in an extremely<br />

complex, highly visible and open process with an unknown outcome.<br />

We were also struck by the uncertainty and fear of the conveners to engage in direct<br />

interaction with the stakeholder representatives. It seemed more com<strong>for</strong>table <strong>for</strong> the<br />

initiators to work out solutions among experts and to avoid direct interaction with<br />

the actors in the valley. Although the planning and steering group <strong>for</strong>mally<br />

represented a wide group of stakeholders, they were not used to keep responsibility<br />

146


around the table and to provide a <strong>for</strong>um <strong>for</strong> open dialogue. The conveners did not<br />

consider the stakeholders as legitimate and competent partners in the problem<br />

solving process. At one point, the coordination group did decide to organize a joint<br />

meeting of the steering and planning group. In the design of the meeting, however,<br />

they tried to avoid direct interaction. It was a long, technical slide presentation and<br />

t<strong>here</strong> was hardly time <strong>for</strong> questions or discussion. The president of the meeting<br />

evacuated the few questions that came up to the work groups later in the process.<br />

The conveners stated it had been a strategic choice to only use the steering group <strong>for</strong><br />

in<strong>for</strong>mation sharing.<br />

On reflecting back on their experiences the participants of the workshop admitted it<br />

took courage to assemble potentially adversarial groups around the table. They<br />

feared they would not be able to deal with conflict and resistance. Due to the<br />

institutional context (‘the way we do things <strong>here</strong>’), the initiators argued they favored<br />

a ‘minimal’ <strong>for</strong>m of participation. The firm boundary of identity around the small<br />

group of insiders reflected a top-down vision on participation. The ‘internal’<br />

stakeholders decided to cross the boundary to in<strong>for</strong>m or consult ‘external’<br />

stakeholders (Finn, 1996). The conveners felt more com<strong>for</strong>table with bilateral contacts<br />

and negotiation. The downside of this approach was that it rein<strong>for</strong>ced the belief that<br />

the project was an adding up of individual interests. It did not allow stakeholders to<br />

realize that their claims on the river valley needed to be restricted and aligned with<br />

those of others. By limiting the role of the stakeholders, they did not have a chance to<br />

become aware of their interdependent relationships and to experience the diversity<br />

of interests in the valley and the many different claims on the ecosystem. This<br />

reduced the complexity in the process and shut out a large part of reality. The<br />

consequence was also that a number of issues were not thoroughly discussed or<br />

avoided (e.g. water quality and compensation <strong>for</strong> the farmers to clean up polluted<br />

soil, financing of the technical interventions of the plan).<br />

This ambiguity of inclusion and exclusion was also mirrored in the coordination<br />

group. For the conveners the ‘ideal scenario’, or so-called ‘maximum’ scenario, was a<br />

147


plan that fully integrated their ecological interests, without too many compromises.<br />

Paradoxically, in order to arrive at a ‘natural’ environment many technical<br />

interventions were required (e.g. deepening the river, restore meanders, dismantling<br />

dams). The conveners wished to restore the valley to the situation of 50 years ago,<br />

even though t<strong>here</strong> were many changes in the environment (e.g. more concrete<br />

surfaces, more rainfall, and more residents in the valley). The ‘minimum’ scenario,<br />

defended by the Navigable Waterways Administration, mainly focused on flood<br />

prevention and consisted of few additional interventions. This led to a paradoxical<br />

situation. The ‘maximum’ scenario turned out to be a unilateral scenario in the<br />

interest of one group of stakeholders (ecological interests). The 'minimal' scenario<br />

was a more inclusive scenario because it tried to take the interests of a maximum of<br />

stakeholders in the valley into account.<br />

The conveners had been looking <strong>for</strong> ways to foster broad support <strong>for</strong> an ecological<br />

perspective on the development of the river valley, without questioning their<br />

objectives. Allowing other voices in seemed like a threat to their identity and to their<br />

objectives and solutions. Because of this anxiety some defensive dynamics emerged:<br />

a split in the organizational structures (planning/steering group), tightly controlled<br />

interactions, avoidance of an open dialogue, exclusion of stakeholders, stereotyping<br />

of ‘outsiders’ who were experienced as threatening, and projection of their<br />

inadequacy on others. Strong identification of the conveners with the values<br />

promoted in the project initially resulted in a rigid boundary to avoid the threat of<br />

stakeholders watering down their ideal scenario.<br />

Attempts to bridge diversity: steps towards a multi-faceted identity<br />

The initiators were aware of the fact that policy makers had given them the<br />

opportunity to work out a qualitative and balanced plan. The project provided them<br />

with time and resources to foster support and deal with resistance. We will discuss<br />

how the coordination group, and the initiators in particular, used this opportunity<br />

and how they tried to loosen the boundary.<br />

148


The project benefited from existing relationships and previous experiences in other<br />

projects (e.g. joint management of natural reserves by the administration Nature and<br />

the environmental group). The conveners welcomed social scientists in their project.<br />

They were open to scrutinize their way of working and interested in alternative<br />

approaches. Our presence enabled the conveners and some core actors to use the<br />

in<strong>for</strong>mal ‘restricted committee’ and the workshop as a space to reflect on their<br />

assumptions and practices and to learn from each other.<br />

The ‘sector analysis’ contributed to the process of loosening the boundaries. The<br />

findings (bottlenecks and opportunities) were integrated in later discussions and<br />

plans. It was carried out by the external consultants jointly with a representative of<br />

the Province, and the manager of the river under study. This approach helped to<br />

work across the boundaries and was welcomed by the municipalities and other<br />

sectors. After a year the initiators organized an extensive individual survey of all<br />

farmers in the valley. Although this consultation happened a year too late because of<br />

funding problems, it did help to establish a relationship with the farmers and to take<br />

their interests into account.<br />

At the start of the project the relationship between the initiators and the authority<br />

over the river was antagonistic. Soon after our feedback from the interviews the<br />

conveners asked the Navigable Waterways Administration to participate in the<br />

coordination group. The representatives became regular members of the<br />

coordination group. At a one moment in the project, the Navigable Waterways<br />

Administration tried to take control of the process. They came to the meeting of the<br />

coordination group with five (instead of the usual one) representatives, including a<br />

senior manager. He criticized the accuracy of the scientific measures carried out by<br />

the consultants and suggested to duplicate the calculations in their laboratory. To<br />

emphasize his message he had brought two representatives of the laboratory along to<br />

the meeting. His interventions were direct and quite intimidating.<br />

“Everybody around the table wants more space <strong>for</strong> the river. But if you go public with water<br />

levels that are higher than be<strong>for</strong>e, we lose face. You need more certainty be<strong>for</strong>e you start talking<br />

149


to the local authorities! (…) Politically it is impossible at this point to implement this plan,<br />

because the Minister supports the farmers association. In addition to that, the consultants admit<br />

their program is full of bugs. My proposal is to make sure we are 100% certain be<strong>for</strong>e we start<br />

talking about this plan, in order to avoid panic.” (General Manager of Navigable River<br />

Administration, coordination group)<br />

At that point t<strong>here</strong> was a shift. The initiators refused to cancel their appointments<br />

with the local authorities and farmers and they insisted on continuing the process<br />

even with imperfect data. One of the conveners explicitly referred to the discussions<br />

we had held the day be<strong>for</strong>e during the workshop.<br />

“I am sure extra checking will not change anything fundamentally, even if you find a little<br />

mistake <strong>here</strong> and t<strong>here</strong>. The challenge remains the same: how are you going to communicate<br />

this to the local authorities? If we postpone it <strong>for</strong> two more months to check the figures, the<br />

issue is still the same and we will only have lost time. (…) We have learned the opposite in a<br />

workshop yesterday: the more unilateral we develop our plan, the more resistance we can<br />

expect from external actors. And the less opportunity will be left to take their concerns into<br />

account. T<strong>here</strong><strong>for</strong>e I strongly plead <strong>for</strong> communication with the local authorities as soon as<br />

possible.” (A convener, coordination group)<br />

The conclusion of the meeting was that consultation of the key stakeholders would<br />

continue as planned and that a representative of the Navigable River Administration<br />

would join the conveners on their visits. Gradually the relationship seemed to<br />

improve. The initiators eventually acknowledged that their plans had been too<br />

idealistic and not well grounded in scientific evidence. A more realistic and<br />

constructive relationship with the <strong>for</strong>mal authority of the river and an integration of<br />

competencies and insights increased the likelihood of an acceptable, technically<br />

sound and realistic plan and it enhanced chances <strong>for</strong> implementation.<br />

The work groups, established in the course of the project, also contributed to increase<br />

the permeability of the boundary around the collaborative. Although not <strong>for</strong>eseen in<br />

the initial design, they proved to be the most suitable context to work across the<br />

boundaries of different interest groups (e.g. recreation: industry, tourism, nature<br />

conservation, local authorities). The work groups consisted of members of the<br />

planning and steering group and other interested or relevant actors and were a cross-<br />

section of types of stakeholders. These smaller groups allowed <strong>for</strong> direct interaction<br />

and <strong>for</strong> ‘relational practices’. Relational practices enable different parties to engage in<br />

150


actions and interactions: through ‘content’ they engage in a ‘relation’ (Bouwen, 2001;<br />

Wenger, 1998). The work group recreation, <strong>for</strong> instance, organized a trip to a project<br />

in a natural reserve to learn from that experience. The work group hydrology visited<br />

particular parts of the river to see what the effects of different scenarios would be in<br />

the field. For the conveners it was a new experience to involve ‘outsiders’ in the<br />

process while the scenario was not finalized yet.<br />

“We don’t even know w<strong>here</strong> we’re going. We try to stay on top of the process and we attempt<br />

to involve others from that position.” (A convener, interview)<br />

As the process moved along the conveners cautiously tried to integrate the voice of<br />

other stakeholders. At the end of our research, the conveners were seeking to find a<br />

balance between on the one hand defending the objectives of their constituency and<br />

the values of their study, and on the other hand, the legitimate claims of other<br />

stakeholders in the domain and the restrictions and realities in the environment (e.g.<br />

financial aspects). They gradually became aware of the necessity to enlarge the<br />

boundary of identity in order to arrive at an encompassing assessment of the<br />

problem domain and to work out optimal, realistic and sustainable solutions <strong>for</strong> the<br />

river valley.<br />

Conclusion<br />

This paper analyzes the ef<strong>for</strong>ts of a group of public officers to develop an integrated<br />

plan <strong>for</strong> a river valley. We have documented the assumptions of the key<br />

representatives and the dilemmas they were facing when confronted with the wish<br />

and need of stakeholders to participate in the process. The boundary of identity<br />

proved to be a useful concept to demonstrate how strong identification with the<br />

values and interests of a central party, hindered the inclusion of the stakeholder<br />

voices. Loosening the boundaries was experienced as a threat to the passionately<br />

defended ecological interests of the study and the identity of the initiators. The<br />

process was characterized by ‘management’ and control of the boundaries and not so<br />

much by ‘negotiation’ of boundaries. Within the 22 months of the project the<br />

conveners did not succeed in developing a multifaceted identity of the study with<br />

151


which a wide group of stakeholders could identify. Although strongly opposed by<br />

some, the values of the initiators remained dominant in the process. As the process<br />

moved along the conveners did try to loosen the close boundaries they had drawn<br />

around the collaborative. They gradually succeeded to let go of control and to adapt<br />

their ‘idealized’ vision of the future.<br />

This case study demonstrates that the conveners of the change process were faced<br />

with several challenges in managing public policy issues (Anderson & White, 2003).<br />

Because technology was so complex, they needed to collaborate with external<br />

experts. They experienced the effects of globalization, in the sense that they needed<br />

to adapt their way of managing environmental issues as a result of European policy.<br />

T<strong>here</strong> was pressure, from policy as well as from the stakeholders, to manage the<br />

process in a ‘participative’ way. The conveners seemed caught between policy<br />

makers, the technical experts and the stakeholders in the valley. While they were<br />

defending their interests and values they were also looking <strong>for</strong> an appropriate role<br />

and a new identity. The project was a search process in how to design and facilitate a<br />

complex process with an uncertain outcome, involving the relevant stakeholders<br />

concerned by the problem domain.<br />

References<br />

Alderfer, C. P. (1987). An intergroup perspective on group dynamics. In Lorsch, J.<br />

(Ed.), Handbook of organizational behavior. NJ: Englewood Cliffs, pp. 199-222 .<br />

Anderson, D.K. & White, J.D. (2003). Organizational psychoanalysis in public<br />

administration. American Review of Public Administration, 33 (2), June, 189-208.<br />

Berg, D. N. & Smith, K. K. (1995). Paradox and Groups. In Gillette, J. & McCollom, M.<br />

(Eds.), Groups in context. A new perspective on group dynamics. Lanham: University<br />

Press of America.<br />

Bouwen, R. (2001). Developing Relational Practices <strong>for</strong> Knowledge Intensive<br />

Organizational Contexts. Career Development, 6/7, 361-369<br />

Buckles, D. (Ed.) (1999). Cultivating peace. Conflict and collaboration in natural resource<br />

management. IDCR/World Bank.<br />

152


Chrislip, D. & C. Larson (1994). Collaborative leadership: How citizens and civic leaders can<br />

make a difference. San Francisco: Jossey-Bass<br />

Diamond, M., Allcorn, S. & Stein, H. (2004). The surface of organizational boundaries:<br />

a view from psychoanalytic object relations theory. Human Relations, 57 (1), 31-53.<br />

Ehrlich, H.S. (2001). Enemies within and without: paranoia and regression in groups<br />

and organizations. In Gould, L.G., Stapley, L.F. & Stein, M. (Eds.). The systems<br />

psychodynamics of organizations. Integrating the group relations approach, psychoanalytic,<br />

and open systems perspectives. London: Karnac, pp. 115-131.<br />

Finn, C.B. (1996). Utilizing stakeholders strategies <strong>for</strong> positive collaborative outcomes.<br />

In Huxham, C. (Ed.). Creating collaborative advantage. London: Sage, 152-164.<br />

Geertz, C. (1973). The interpretation of cultures. New York: Basic Books<br />

Gemmill, G. (1986). The dynamics of the group shadow in intergroup relations. Small<br />

Group Behavior, 17 (2), 229-240.<br />

Gemmill, G. (1993). Mirror, mask, and shadow. Psychodynamic aspects of intergroup<br />

relations. Journal of Management Inquiry, 2 (1), March, 43-51.<br />

Gould, L.J., Ebers, R. & Mc Vicker Clinchy, R. (1999). The systems psychodynamics of a<br />

joint venture: anxiety, social defenses and the management of mutual dependence.<br />

Human Relations, 52 (6), 697-722.<br />

Gould, L.G., Stapley, L.F. & Stein, M. (Eds.) (2001). The systems psychodynamics of<br />

organizations. Integrating the group relations approach, psychoanalytic, and open systems<br />

perspectives. London: Karnac.<br />

Gray, B (1989). Collaborating: finding common ground <strong>for</strong> multiparty problems. San<br />

Francisco: Jossey Bass.<br />

Gray, B. (1996). Cross-sectoral partners: collaborative alliances among business,<br />

government and communities. In Huxham, C. (Ed.). Creating collaborative advantage.<br />

London: Sage, pp. 57-79.<br />

Hartman, J. J. & Gibbard, G. S. (1974). A note on fantasy themes in the evolution of<br />

group culture. In Gibbard, Hartman & Mann (Eds.) Analysis of groups. San<br />

Francisco: Jossey-Bass.<br />

Hernes, T. (2004). Studying composite boundaries: a framework <strong>for</strong> analysis. Human<br />

Relations, 57 (1), 9-29.<br />

Hirschhorn, L and Gilmore, T (1992): The new boundaries of the “boundaryless”<br />

company. Harvard Business Review, May/June, 70 (3), 104-115.<br />

Huffington, C., Armstrong, D., Halton, W., Hoyle, L. & Pooley, J.( Eds.) (2004). Working<br />

below the surface. The emotional life of contemporary organizations. London: Karnac.<br />

153


Huffington, C. & James K. (1999). Issues in management research, and the value of a<br />

psychoanalytic perspective. A case study in organisational stress in a Japanese multinational<br />

company. Paper presented at the annual Symposium of the Psychoanalytic<br />

Society <strong>for</strong> the Study of Organizations, Toronto.<br />

Huxham, C. (Ed.). (1996). Creating collaborative advantage. London: Sage.<br />

Koppenjan, J. & Klijn, E.H. (Eds.) (2004). Managing uncertainties in networks. London:<br />

Routledge.<br />

Kramer, R. (1991). The more the merrier? Social psychological aspects of multiparty<br />

negotiations in organizations. Research on negotiation in organizations. Vol. 3,<br />

Greenwich, Connecticut: JAI Press.<br />

McCollom, M (1995a): Group <strong>for</strong>mation: boundaries, leadership, and culture. In<br />

Gillette, J. and McCollom, M. (Eds.): Groups in context. A new perspective on group<br />

dynamics. Lanham: University Press of America, pp. 34-48.<br />

McCollom, M (1995b): Reevaluating group development: a critique of the familiar<br />

models. In Gillette, J. & McCollom, M. (Eds.): Groups in context. A new perspective on<br />

group dynamics. Lanham: University Press of America, pp. 133-154.<br />

Menzies, I. E. P. (1960). A case study in the functioning of social systems as a defense<br />

against anxiety. Human Relations, 13, 95-121.<br />

Merali, Y (2002): The role of boundaries in knowledge processes. European Journal of<br />

In<strong>for</strong>mation Systems, 11 (1), 47-60.<br />

Miller, E.J. & Rice, A.K. (1967). Systems of organization. The control of task and sentient<br />

boundaries. London: Tavistock Publications.<br />

Paulsen, N. & Hernes, T. (Eds.) (2003). Managing boundaries in organizations: Multiple<br />

perspectives. Basingstoke: Palgrave McMillan.<br />

Redlich, F.C. & Astrachan, B. (1975). Group dynamics training. In Colman, A.D. &<br />

Bexton, W.H. (Eds.), Group Relations reader. Sausalito: Grex.<br />

Schein, E.H. (1987). The clinical perspective in fieldwork, Newbury Park: Sage.<br />

Schneider, S.C. (1991). Managing boundaries in organizations. In Kets de Vries (Ed.),<br />

Organizations on the couch: clinical perspectives on organizational behavior and change.<br />

San Francisco: Jossey-Bass, pp. 169-190.<br />

Stein, M. (2004). Theories of experiential learning and the unconscious. In Gould, L.J.,<br />

Stapley, L.F. & Stein, M. (Eds.) Experiential learning in organizations. Applications of<br />

the Tavistock group relations approach. London: Karnac, pp. 19-36.<br />

Tajfel, H. (1978). (Ed.) Differentiation between social groups: Studies in the social psychology<br />

of intergroup relations. London: Academic Press.<br />

154


Vansina, L., Taillieu, T. & Schruijer, S. (1998). “Managing” multiparty issues: learning<br />

from experience. In Pasmore, W. & Woodman, R. (Eds.), Research in Organizational<br />

Change and Development. (vol. 11). Greenwich, Connecticut: JAI Press Inc., pp. 159-<br />

181.<br />

Yin, R.K. Case study research. Design and methods. Second Edition. Applied Social<br />

Research Methods Series, Volume 5, Thousand Oaks, Cali<strong>for</strong>nia: Sage Publications,<br />

1994.<br />

Wells, L. (1995). The group as a whole: a systemic socioanalytic perspective on<br />

interpersonal and group relations. In Gillette, J. and McCollom, M. (Eds.). Groups in<br />

context. A new perspective on group dynamics. Lanham: University Press of America,<br />

pp. 49-85.<br />

Wenger, E. (1998). Communities of practice. Learning, meaning, and identity. Cambridge<br />

University Press.<br />

Winnicott, D.W. (1971). Playing and reality. London: Routledge<br />

Zagier Roberts, V. (1994). Conflict and collaboration. Managing intergroup relations. In<br />

Obholzer, A. & Zagier Roberts, V. (Eds.), The unconscious at work. Individual and<br />

organizational stress in the human services. London: Routledge, pp. 187-196.<br />

155


PART 3: MAIN CASE STUDY<br />

INTRODUCTION CASE STUDY 3: FOSTER CARE<br />

In December 2002, CO1 (see attachment 1) in<strong>for</strong>med me about a proposal he had<br />

written <strong>for</strong> a project in the domain of foster care. The Minister of welfare rejected this<br />

initial proposal which had been submitted by two foster care services. In October<br />

2003, after the appointment of a new Minister, t<strong>here</strong> was interest in the project. I<br />

interviewed the main initiator (director of a foster care service) to assess whether the<br />

project was potentially interesting <strong>for</strong> my research. Some weeks later, the Ministry<br />

approved the project and I decided to participate. For one year (October 2003 –<br />

November 2004), I was simultaneously doing research in two projects: the river<br />

valley project and the foster care project. T<strong>here</strong> were several reasons why I chose to<br />

do this project in addition to the river valley project.<br />

- Timing: this project was a one-year project, starting at a convenient moment in<br />

the process of my research.<br />

- Early involvement: I was involved from the start and was able to participate until<br />

the end of the project.<br />

- Access to the field: I had easy access to the field because research was negotiated<br />

as part of the project.<br />

- Clear role: the project was an action research w<strong>here</strong> I had an active and defined<br />

role.<br />

- Multi-stakeholder process: the project was designed in a multiparty philosophy<br />

and it concerned a societal problem affecting many different stakeholder groups.<br />

156


- Interest of the in<strong>for</strong>mants: the participants (members of the project group) were<br />

interested in reflection on their experiences, curious to learn, and willing to invest<br />

time and energy in research activities.<br />

- Emergent nature and unpredictability of collaborative processes: I was not sure<br />

any of the two projects would continue or be sufficiently interesting <strong>for</strong> my<br />

research. T<strong>here</strong><strong>for</strong>e, I bet on two horses.<br />

In a later phase of my research, when my participation in both projects had ended, I<br />

decided to choose the foster care project as the main case <strong>for</strong> my research. The<br />

reasons <strong>for</strong> this choice were:<br />

- I had more interesting data;<br />

- The collaborative and its organizational features fitted better with the definition<br />

of multiparty processes in the literature;<br />

- The foster care project was an action research with a clear intention to facilitate a<br />

multi-stakeholder process, w<strong>here</strong>as in the river valley case the researchers were<br />

mainly involved as observers of an ongoing process, looking at the project<br />

through the lens of multiparty collaboration;<br />

- The foster care case was more transparent in terms of historical, political and<br />

institutional context. In the river valley case it was much harder to fully<br />

understand or have access to the issues that played in the context (politics).<br />

- In the foster care project, I had been able to focus on my research agenda, w<strong>here</strong>as<br />

the agenda of the HarmoniCOP project dominated the river valley case.<br />

CONTEXT AND ANTECEDENTS OF THE FOSTER CARE PROJECT<br />

Socio-political context<br />

Foster care is defined as full-time care, twenty four-hours a day, outside the child's<br />

home. A foster family (temporarily) provides a safe family environment <strong>for</strong> children<br />

157


who cannot live at home because of parental problems. T<strong>here</strong> are different types of<br />

foster families, based on characteristics of the child and on the length of placement<br />

(e.g. emergency placement, pre-adoptive placement, long-term placement). The<br />

foster family can be part of the child’s kinship network or it can be an unknown<br />

family. The foster families are considered as ‘voluntary collaborators’ and receive an<br />

allowance. Different types of foster care are available. Most placements are the result<br />

of a decision by the juvenile court (mandatory) or the Committee <strong>for</strong> special youth<br />

assistance (voluntary). A small proportion of the placements (10%) is organized by<br />

private arrangement. In a few cases, parents consider themselves temporarily unable<br />

to take care of their children. Referrals <strong>for</strong> cases in this type of preventive foster care<br />

usually come from community services, hospitals, or community-based family<br />

support agencies. These placements are mediated by a government agency (Child<br />

and Family). In addition to these general types of foster care, t<strong>here</strong> are at least seven<br />

specific types of foster care (e.g. weekend families, rooms with special attention).<br />

Several challenges and evolutions in the domain inspired people working in the<br />

field to take the initiative <strong>for</strong> a project. T<strong>here</strong> was pressure on foster care: demands<br />

were rising, while the number of candidate foster families was decreasing. The foster<br />

care services were confronted with a lack of candidate families <strong>for</strong> the increasing<br />

number of children eligible <strong>for</strong> foster care. Recently, the number of foster care<br />

situations increased with 20% (1998-2002). Moreover, the problem situations around<br />

the child had become more severe and complicated. The services were aware of their<br />

image: an unclear profile, a small player in welfare, an offer that was not well know,<br />

and lack of transparency and an ineffective coordination between the services.<br />

The subsidizing mechanism in foster case was perceived as the critical obstacle to<br />

collaboration between the services. Subsidies were based on the number of<br />

placements a service could organize and were only granted after placement of a child<br />

in a foster family. The more placements, the more personnel a service was able to<br />

contract. The managers felt caught in a competitive relationship due to this funding<br />

logic. The services were very aware that they were ‘fishing in the same pond’.<br />

158


Foster care is a politically interesting <strong>for</strong>m of assistance, because it is often voluntary,<br />

demand driven, it fosters networks and it is cheap compared to other <strong>for</strong>ms of<br />

assistance. For a long time policy makers had tolerated free initiative in the sector.<br />

This freedom, however, had resulted in competition among the services. T<strong>here</strong> was<br />

an increasing pressure from policy makers to change. Government policy tended to<br />

move towards a more integrated approach of assistance and a regional organization<br />

of services. Foster care, as a small and separate sector, was seriously questioned. This<br />

implied that foster care needed to align with other institutions and open up to other<br />

<strong>for</strong>ms of assistance (e.g. complementary or mixed <strong>for</strong>ms of assistance). The services<br />

also needed to develop a wider range of services and more specialized care. The<br />

environment was turbulent because of many changes. The sector providing<br />

assistance to handicapped people, <strong>for</strong> instance, was developing a new vision on<br />

welfare assistance: demand driven, a stronger position of the user, and personal<br />

budgets. The foster care services in the region under study were involved in a<br />

welfare project that aimed at coordination of different <strong>for</strong>ms of assistance <strong>for</strong><br />

children and adolescents in the region. Several years ago, t<strong>here</strong> had been a <strong>for</strong>ced<br />

merger of a number of welfare centers. These changes in the environment made the<br />

managers aware of the possibility of an imposed merger. This was an important<br />

trigger to submit a project.<br />

Institutional context<br />

The institutional landscape of foster care is complex and intricate. The foster care<br />

services are private agencies under authorization of and subsidized by the Flemish<br />

Community. Their tasks are: recruitment, screening and training of foster families;<br />

matching the child to the foster family; monitoring of the placement situation;<br />

assisting the child and the foster parents; providing assistance to the parents. T<strong>here</strong><br />

are several foster care services in each region. The services mediate between the<br />

child, the foster parents, and the natural parents (the ‘systemic triangle’). The<br />

Federation <strong>for</strong> foster care represents all the services in Flanders. They are member on<br />

159


a voluntary basis. Its function is to promote foster care, to ensure quality service, to<br />

be a think tank, and to represent foster care on the government level. T<strong>here</strong> are four<br />

subsidizing sectors: Special Youth Care (<strong>for</strong>ced or voluntary placement of children in<br />

a problematic situation), Care <strong>for</strong> the Handicapped, Mental Health (community<br />

psychiatry), and Child and Family (prevention). Each sector follows its own rules<br />

and regulations. The domain of foster care is characterized by differences in ideology<br />

(catholic, pluralistic, liberal) which are reflected, <strong>for</strong> instance, in the organizations<br />

representing the employers’ interests. T<strong>here</strong> are also differences in policy on the<br />

Flemish or Federal level (e.g. family allowances). The domain of welfare is<br />

institutionalized and foster care is only a small player.<br />

The organizations in de domain of foster care are interdependent and they<br />

collaborate in different ways. In order to provide solutions <strong>for</strong> the child the services<br />

collaborate with other institutions and centers on a regular basis. For instance,<br />

residential institutions call upon foster care to take care of a child during the summer<br />

holiday. Small foster care services exist in parallel with bigger services. This is an<br />

expensive way of organizing foster care (e.g. costs of administration, salaries of<br />

management).<br />

Antecedents of the project<br />

Two managers of different foster care organizations (two regions), took the initiative<br />

to write a project in order to develop structural collaboration in the domain of foster<br />

care (October 2002). They presented the idea to the members of the Federation <strong>for</strong><br />

Foster care and asked <strong>for</strong> their approval. In that period the initiator contacted CO1<br />

on the basis of his expertise in multiparty collaboration. She asked <strong>for</strong> coaching and<br />

research to support her ambition to develop a ‘network organization’. T<strong>here</strong> was a<br />

first meeting between the initiator, CO1 and an external expert in multiparty<br />

collaboration. As the fee of the external consultant was too high, this person could<br />

not be hired <strong>for</strong> the project. CO1 developed a design <strong>for</strong> the project. It was conceived<br />

as an action research with a multiparty focus (November 2002). The scope of the<br />

160


change was a three-year project <strong>for</strong> the area of Flanders. This project was rejected in<br />

January 2003. When a new Minister from a different political party came to power,<br />

the project was approved in a modified <strong>for</strong>m (October 2003). Policy makers set some<br />

limitations: funding was only <strong>for</strong> one year, the budget was cut in half, and the project<br />

had to be located in one region only. Subsequently, the COPP was contracted to<br />

coordinate and facilitate the pilot project.<br />

In the project proposal, the convener had specified the desired output <strong>for</strong> each<br />

stakeholder group. (1) Provide an offer adapted to the situation of the clients, by<br />

coordinating and assembling existing <strong>for</strong>ms of assistance and by developing new<br />

<strong>for</strong>ms of assistance if necessary. (2) Mobilize society and increase the number of<br />

potential candidate foster families, by establishing a clear profile of foster care and<br />

foster families (joint marketing ef<strong>for</strong>ts). (3) Ensure qualitative assistance, by making<br />

optimal use of the resources and know how of professional staff members. (4) Find<br />

quicker solutions <strong>for</strong> the child and facilitate collaboration between foster care<br />

services and relegating parties, by establishing a clear profile of foster care and by<br />

reducing the number of services. (5) Ensure more effective communication with<br />

policy makers, by increasing transparency and coordination in the domain of foster<br />

care.<br />

Main events in the foster care project<br />

Based on the process reconstruction I have summarized the main events and issues<br />

in the process (table 9). The detailed process reconstruction can be consulted in<br />

attachment 7.<br />

161


Phase Main activities Issues<br />

Convening<br />

phase<br />

(November-<br />

December<br />

2003)<br />

Start-up phase<br />

(December<br />

2003-February<br />

2004)<br />

Inventory<br />

phase<br />

(February-<br />

April 2004)<br />

- Contracting with funding<br />

agency, initiator, and<br />

facilitators/researchers<br />

- Selection of participating<br />

organizations<br />

- Convening and<br />

commitment of the 5<br />

services<br />

- Planning project<br />

- Stakeholder analysis<br />

- Clarification of roles<br />

- Planning interviews<br />

- Stakeholder interviews<br />

(34)<br />

- Feedback to project<br />

group: confrontation with<br />

different perspective of<br />

‘external’ stakeholders<br />

162<br />

- How to approach the project?<br />

- Who is ‘in’ and who is ‘out’ in<br />

this project?<br />

- Who is at the core of this<br />

project: the services <strong>for</strong> foster<br />

care or the target group (parents<br />

and children)?<br />

- How much common ground is<br />

t<strong>here</strong>?<br />

- How much of our identity can<br />

we keep?<br />

- How to involve personnel of the<br />

services?<br />

- How to engage the wider group<br />

of stakeholders?<br />

- Tension: holding on to identity<br />

↔ efficiency and effectiveness,<br />

best solution <strong>for</strong> the child<br />

- Tension: focus on ‘internal’<br />

stakeholders ↔ multistakeholder<br />

approach<br />

- How safe is it in the group of<br />

‘internal’ stakeholders?<br />

- Ambiguity around ‘being<br />

different’<br />

- What is the motive <strong>for</strong><br />

collaboration?<br />

- Tension: solution mindedness<br />

↔ openness of the process


Exploration<br />

phase<br />

(April-October<br />

2004)<br />

Final phase<br />

(October-<br />

November<br />

2004)<br />

- Stakeholder conference 1<br />

(May) and 2 (June)<br />

- Inactivity during summer<br />

- 3 thematic work groups:<br />

exploration differences<br />

and similarities<br />

- 1 service withdraws from<br />

the collaboration<br />

- First attempts to design<br />

scenarios <strong>for</strong><br />

collaboration<br />

- Stakeholder conference 3<br />

- Formal end of project<br />

163<br />

- Tension: include external<br />

stakeholders ↔ keep things<br />

under control and hold up<br />

positive image towards external<br />

stakeholders<br />

- Balancing between safety,<br />

openness, caution ↔<br />

confrontation<br />

- Tension: expected role<br />

facilitator (set direction) ↔<br />

contracted role facilitator<br />

(process facilitation)<br />

- Tension: take time to include all<br />

organizations ↔ move on and<br />

exclude reluctant organization<br />

- Sense of urgency? Who is the<br />

driving <strong>for</strong>ce?<br />

- How far do we want to go in<br />

working interdependently?<br />

- How can we include external<br />

stakeholders?<br />

- Tension: obtain results (policy<br />

makers) ↔ take time <strong>for</strong> process<br />

- How can we turn this project<br />

into a sustainable collaborative<br />

system with committed<br />

members?<br />

Table 9: Overview of the phases and challenges in the foster care project.<br />

Research approach<br />

In what follows I reconstruct the research process as a chain of evidence (Yin, 1994). I<br />

describe how I designed the research, what choices and decisions I made regarding<br />

data sampling, changes in the design, and methods <strong>for</strong> data collection. I document<br />

how I proceeded from the real life experience of a collaborative, to field notes, to text<br />

as data, and to the construction of a ‘new’ reality. I will describe the process in a


chronological order to make it transparent <strong>for</strong> an ‘outsider’. The steps in data<br />

collection and data analysis are documented in the attachments (2-9).<br />

Research questions<br />

My research focus was influenced by a theoretical pre-understanding and<br />

experiences in the other cases in this research. What emerged in the three cases as an<br />

interesting phenomenon was how participants made sense of the organizational<br />

reality in which they found themselves, the important themes and dilemmas with<br />

which they were confronted, and how their way of dealing with those issues<br />

influenced the direction and outcome of the process. I started to study the foster care<br />

case with the following questions in mind:<br />

- What are the issues and dilemmas with which representatives in a collaborative<br />

are struggling?<br />

- Which dynamics emerge around those issues and how do these dynamics<br />

influence the direction and outcome of the collaborative process?<br />

These questions stimulate exploration and discovery and are not aimed at testing<br />

hypotheses or theories. In the process of exploration I suspended my a priori<br />

knowledge in order to be as unbiased as I could.<br />

The research setting<br />

My research subject, a collaborative process, is an emergent, dynamic process, in a<br />

complex and uncertain organizational context, and involving multiple participants.<br />

The collaborative is <strong>for</strong>med by the relationships that develop between the<br />

representatives of stakeholders who make up the collaborative. The research setting<br />

can t<strong>here</strong><strong>for</strong>e be described as ‘a system-in-interaction’. Initially I selected the project<br />

group, which consisted of the managers of five services, the head of the Federation,<br />

and the four consultants, as the main setting <strong>for</strong> data collection (table 11, article 3). I<br />

focused on the managers and the head of the Federation, as they turned out to be the<br />

ones taking decisions <strong>for</strong> the future of the domain. However, after the project group<br />

164


decided to organize meetings with external stakeholders, I realized that these<br />

meetings provided a potential plat<strong>for</strong>m w<strong>here</strong> the future of the domain of foster care<br />

was designed in joint responsibility (Gray, 1989). T<strong>here</strong><strong>for</strong>e I decided to include the<br />

field notes of the stakeholder conferences as data. Towards the end of the project I<br />

became aware of the role and influence of the consultants on the process and<br />

included my field notes of our internal meetings as additional data.<br />

Role of the researcher<br />

The consultant team that was hired to design and facilitate the project was composed<br />

of four members, all working at the COPP. Each member took up a specific, but<br />

flexible role (attachment 1). CO1 had handed over the project to his colleague (CO2)<br />

who was well acquainted with the domain of welfare. CO3 was asked to support him<br />

with his facilitation tasks. CO4 was the coordinator of the project, doing most of the<br />

daily management. My role was to take up specific research tasks. T<strong>here</strong><strong>for</strong>e we<br />

ended up with a fairly large consulting team. None of the four team members had<br />

been involved in the initial negotiations with the convener.<br />

The project was set up as an action research. The aim was to support the participants<br />

in their search <strong>for</strong> a model <strong>for</strong> future collaboration and to facilitate the change<br />

process. This included interventions such as interviewing, design and structuring of<br />

the process, and facilitation of a search conference. The objective of action research is<br />

always double: facilitate organizational change and generate insights and theory,<br />

grounded in empirical data and in action (Eden & Huxham, 1996). My role was to<br />

document the action research project, to introduce data in the system in order to<br />

stimulate reflection, and to develop insights. I engaged with the participants in the<br />

clear position of researcher and could directly experience the dynamics in the system.<br />

I made some explicit interventions with the intention to improve the functioning of<br />

the system (e.g. share feedback of interviews). I consider my mere presence as<br />

researcher in the system as an ‘implicit’ intervention. Intervention and observation<br />

cannot be neatly distinguished and usually run in parallel (Schein, 1987; 2000).<br />

165


As research was a negotiated part of the project, I had easy access to documents (e.g.<br />

project proposal, mission statements of the services), I could interview members of<br />

the foster care services and the wide group of stakeholder representatives. I was<br />

allowed to participate in all meetings of the project group, internal meetings with the<br />

consultant team, and the three stakeholder days that were organized. My thesis<br />

students also had access to the stakeholder representatives. They interviewed the<br />

head of the Federation <strong>for</strong> foster care, participated in two stakeholder conferences<br />

and did a survey to assess collaborative relationships.<br />

Data collection<br />

In order to capture the complexity of the process, the various perspectives and the<br />

dynamics over time, I used a multiple approach to data collection with the following<br />

features:<br />

- Longitudinal: I collected data over a period of one year.<br />

- Triangulation of perspectives: in order to capture the multiple perspectives of the<br />

stakeholder representatives (Flick, 2002).<br />

- Data triangulation: to enable a robust interpretation of phenomena I used<br />

different sources (Yin, 1994; Clarke, 2002): different persons, at different moments<br />

in the process, and in different settings.<br />

- Triangulation of methods: I used an outside and inside perspective, accounts and<br />

observations, real time and retrospective data, implicit and explicit recording of<br />

data. The aim was to generate a rich set of data.<br />

- Investigator triangulation was used in the following way:<br />

o During all moments of data collection, at least one colleague was present<br />

(interviews, meetings);<br />

o I systematically checked my field notes with one or more colleagues;<br />

166


o During the process of data collection and afterwards, I checked emergent<br />

working hypotheses with colleagues (internal consulting meetings,<br />

in<strong>for</strong>mal conversations, conference paper, research seminar with<br />

colleagues);<br />

o I interviewed my colleagues to ask what, <strong>for</strong> them, had been critical events<br />

and how they made sense of them;<br />

o I jointly wrote one of the papers with a colleague.<br />

I made some choices to keep the amount of data at a manageable level.<br />

- I selected 12 months using the dates of the project as boundaries of time;<br />

- I mainly focused on the members of the ‘project group’ as they were the key<br />

actors;<br />

- I only documented ‘<strong>for</strong>mal’ moments of interaction;<br />

- I did not tape the meetings.<br />

Table 10 represents an overview of the approach to data collection.<br />

Date/Period Method of data<br />

October<br />

2003–<br />

November<br />

2004<br />

collection<br />

Participative<br />

observation of<br />

meetings<br />

Participants/<br />

167<br />

Setting<br />

– Meetings of project<br />

group (13)<br />

– Stakeholder<br />

conferences (3 days)<br />

– Internal meetings of<br />

consultants (13)<br />

Data<br />

Typed field notes:<br />

– Project group (66p)<br />

– Stakeholder<br />

conferences (44p)<br />

– Internal meetings<br />

(24p)<br />

– Including<br />

journalizing notes


February-<br />

April 2004<br />

March–May<br />

2004<br />

May-July<br />

2005<br />

Stakeholder<br />

interviews:<br />

– Semistructured<br />

– 1,5 hour<br />

– Two<br />

interviewers<br />

– No taping<br />

Feedback sessions<br />

to check findings<br />

Critical incident<br />

interviews:<br />

– Semistructured<br />

– 1,5 hour<br />

– One<br />

interviewer<br />

– Taping + field<br />

notes<br />

34 stakeholder<br />

interviews with wide<br />

group of stakeholder<br />

representatives<br />

Project group (2<br />

sessions)<br />

Stakeholder conference<br />

9 Members of the<br />

project group<br />

Table 10: Overview of data collection in the foster care case.<br />

Participative observation<br />

168<br />

Field notes of<br />

interviews (158p)<br />

(Field notes, included<br />

in the notes of<br />

meetings)<br />

– Approx. 14 hours of<br />

tape<br />

– Significant quotes<br />

typed up<br />

– Inventory of critical<br />

incidents typed up<br />

To obtain an ‘outside’ perspective I made field notes of observations of the ‘system-<br />

in-interaction’ in real time. These consisted of meetings of the project group,<br />

stakeholder conferences, and internal meetings of the consultant team. I considered<br />

meetings as ‘communication events’ embedded within a socio-cultural setting which<br />

the actors used to generate interaction and interpret events (Schwartzman, 1993).<br />

This was a non-intrusive way to collect data. In my field notes I made a clear<br />

distinction between literal quotes, descriptions of what was happening and personal<br />

reflections (Spradley, 1980). After each meeting I typed up the written notes and<br />

systematically checked the accuracy of the typed field notes with one or more<br />

colleagues. All interaction moments were numbered (e.g. meeting project group 3). I


have consistently used the numbering of the interactions in the papers and in the<br />

process reconstruction (attachment 7).<br />

Interviewing<br />

To document the subjective accounts of the participants I used interviews (‘inside’<br />

perspective). Together with my colleague researcher I carried out so-called<br />

‘stakeholder interviews’. The project group had made a stakeholder analysis. They<br />

had identified the main players in the domain and tried to reconstruct their<br />

relationships. On the basis of this analysis the group selected 34 stakeholder<br />

representatives <strong>for</strong> interviewing. During the interviews we did ‘additional sampling’:<br />

we asked all interviewees who the critical partners in this process were and checked<br />

if we had <strong>for</strong>gotten any. We did not add any additional stakeholder representative to<br />

our initial list. Attachment 3 presents an overview of the stakeholder clusters and the<br />

organizations and social groups selected <strong>for</strong> interviewing.<br />

We interviewed representatives of the wide group of stakeholders (including the<br />

managers of the project group) in the first few months of the project. We documented<br />

their perspective, needs, questions, future vision, hopes, and fears. All<br />

representatives agreed to be interviewed. As most representatives were concerned<br />

about optimizing foster care, they actively participated in the interviews which<br />

increased the relevance of the data obtained. The interviews lasted, on average, an<br />

hour and a half. The interviews took place all over Flanders, at the organization of<br />

the interviewee. Some interviewees came to our Center because it was more<br />

convenient <strong>for</strong> them. During the interviews I took notes, while my colleague asked<br />

the questions. At particular moments I joined in with supplementary questions or<br />

questions <strong>for</strong> clarification. This way of working allowed me to take extensive notes. I<br />

did not tape the interviews to foster trust and to avoid an intrusive presence. Some<br />

in<strong>for</strong>mants confirmed that a tape recorder would have inhibited them to talk openly.<br />

The drawback of this ‘implicit’ method was that I could not listen back to recorded<br />

data (e.g. listen to intonation of voices) or involve an external researcher (Gould,<br />

169


1991). The data were necessarily filtered, less accurate, and less detailed. This was<br />

compensated by the fact that I could consult my colleagues, as t<strong>here</strong> was always at<br />

least one colleague present. After each interview I immediately typed out my<br />

interview notes. I checked the notes with my colleague <strong>for</strong> accuracy and<br />

understanding.<br />

The interviews were semi-structured. We used open, guiding questions that made it<br />

easier to compare the data afterwards. The openness of the questions allowed the<br />

interviewees to tell their story. The questions <strong>for</strong> the stakeholder interviews were:<br />

- Who do you represent?<br />

- What do you know about this project in foster care?<br />

- What should be optimized in the way the collaboration is organized now?<br />

- What would be your dream <strong>for</strong> this project?<br />

- What are important conditions to arrive at a meaningful and realistic result <strong>for</strong><br />

the project?<br />

- What are potential obstacles and pitfalls?<br />

- Who are the critical partners who can influence results and whom have we<br />

<strong>for</strong>gotten?<br />

- Do you have experience with similar collaborative projects and what have you<br />

learnt from them?<br />

- What could you contribute to the project and how would you like to be involved?<br />

After the project I decided to do some extra interviews because I wanted to check<br />

some insights that were emerging. With retrospective interviews I aimed at checking<br />

my sense making with the key players in the project. T<strong>here</strong><strong>for</strong>e I decided to interview<br />

the members of the project group that had been involved in the project: the five<br />

managers of the foster care services (including a representative of the organization<br />

that stepped out of the project), the head of the Federation, and my three colleagues.<br />

170


Some months after the end of the project, I used critical incident interviews (Gabriel,<br />

1999; Chell, 2004). The aim of this phenomenological method was to mediate the<br />

inquiry process. This method encouraged the interviewees to engage in a search<br />

process of retrospective sense making, to generate associations, and to draw<br />

learnings from their experiences. The interview focused on the experiences of the<br />

interviewee in the project. The data were a mixture of ‘facts’ (the event, behavior of<br />

the interviewee, the behavior of the others involved, and the effects) and ‘subjective<br />

experiences’ (sense making, emotions, associations, fantasies, interpretations).<br />

The interview was semi-structured and lasted approximately an hour and a half. The<br />

interviews took place at the work place of the interviewees. I used a tape recorder<br />

since I was the only interviewer. I assumed that taping at that point in time, when the<br />

relationship was established, would not be experienced as intrusive and that the<br />

interviewees would talk openly about their experiences. No interviewee objected to<br />

the taping. This way of working (explicit data collection) allowed me to listen more<br />

carefully during the interviews and to listen back to the interviews. In addition, I<br />

took some notes. The guiding questions <strong>for</strong> the interviews were:<br />

- What, according to your experiences, were the most critical moments or events in<br />

the project (turning points)? What makes them meaningful <strong>for</strong> you?<br />

Additional questions:<br />

- What happened?<br />

- Who was involved?<br />

- What did you do?<br />

- What did you see the others do?<br />

- What did you think?<br />

- What did you feel?<br />

- What was the result?<br />

- How could it have turned out differently?<br />

171


- In what way did it set the direction of the collaboration?<br />

- What did you learn from the experience?<br />

- What, according to you, will be the main challenge <strong>for</strong> this collaborative in the<br />

future?<br />

After the interviews, I listened back to the tapes and typed out the most significant<br />

quotes, <strong>for</strong> potential use as case illustration in papers. In addition, I typed out the<br />

issues in a separate file (see data analysis).<br />

Journalizing<br />

I documented my subjective experiences by using journalizing notes. For instance, I<br />

made notes on premature hunches, such as “differences in ‘speed’ is not the issue; it<br />

seems to be about differences in objectives!” I also documented the choices I made<br />

and the tensions of doing the research. For instance, based on my notes, I could trace<br />

back the implicit assumptions that inspired my initial choice <strong>for</strong> doing interviews.<br />

My assumptions were that people are aware of the meaning they attribute to an<br />

important event, that they can put this into words, that people are motivated and<br />

willing to reveal their 'authentic' experiences. In that sense I adopted what Alvesson<br />

(2003) calls a 'romantic position'. It made me realize that I needed to focus more on<br />

the interactions as a source to document the ‘process’.<br />

Data analysis<br />

In order to arrive at robust interpretations grounded in empirical data, I followed a<br />

systematic method <strong>for</strong> data analysis. This is one of the five principles <strong>for</strong>warded by<br />

Clarke (2002) that I have adopted. Although I present the steps in data analysis as<br />

sequential, I did some of the analyses in parallel (e.g. reconstruct the process at the<br />

same time as doing the second order analysis of the stakeholder interviews). I used a<br />

double approach to analyze the data. First, I reconstructed a process overview in<br />

order to have a holistic and chronological perspective of the process over time.<br />

172


Secondly, I made a content analysis of the issues that were in the <strong>for</strong>eground based<br />

on three data sets:<br />

- Stakeholder interviews: this analysis represents the voice of a large group of<br />

stakeholder representatives in the domain of foster care and their perception of<br />

relevant issues at the beginning of the project.<br />

- Interactions: analysis of issues and tensions during the process (real time), based<br />

on field notes of participative observation.<br />

- Critical incident interviews: an analysis of the events and issues perceived by the<br />

key actors as a retrospective assessment of the process.<br />

With this approach I followed a ‘process logic’, because the analysis reflects the<br />

issues and dynamics at different moments in the process (beginning – during – after).<br />

Step 1: Analysis of stakeholder interviews<br />

Jointly with my colleague researcher, I analyzed the data of the stakeholder<br />

interviews. Two researchers, working independently, allowed <strong>for</strong> a more reliable<br />

analysis. We first made an analysis of the issues per stakeholder cluster. We<br />

identified 9 clusters of stakeholders based on the stakeholder analysis (see<br />

attachment 2). We used the structure of the questions to organize our analysis:<br />

- Present situation: perception of the way foster care is managed and organized<br />

today;<br />

- Desired future state: ideal picture of how foster care should be managed and<br />

organized;<br />

- Obstacles to collaboration;<br />

- Existing enablers and required facilitating conditions to foster collaboration.<br />

In the first order analysis we, each separately, categorized quotes <strong>for</strong> each issue. Then<br />

we compared our analysis, which resulted in an analysis we both agreed on. We<br />

173


made the analysis anonymous by using the number of the interview <strong>for</strong> each quote (1<br />

to 34). The result was a 37 page document with categories and literal quotes.<br />

Example: topic enablers/conditions <strong>for</strong> collaboration:<br />

“be prepared to give up certain things” (17)<br />

“core competencies and a clear mandate” (07, 09)<br />

“clarity: w<strong>here</strong> are the differences and similarities” (15, 17)<br />

Secondly, we made a general analysis of the issues that emerged over stakeholder<br />

groups. We only mentioned the name of the stakeholder cluster with a capital letter <strong>for</strong><br />

each quote (A-I). This provided a first order analysis, close to the interview data,<br />

made up of clustered literal quotes (10 pages).<br />

Example: topic relationship foster care with authorities and representatives<br />

“Foster care is light weight”; “foster parents are not taken into account” (H)<br />

“Foster care is an outsider”, “little research” (I)<br />

“Members play off the umbrella organizations against each other” (D)<br />

“What is the authority of the Federation?” (I)<br />

“Lots of extra work”; “few resources”; “external facilitation is not possible” (I)<br />

The interviews had generated a large amount of rich and interesting data. We spent a<br />

lot of time and ef<strong>for</strong>t to organize and structure the data and to find a manageable and<br />

appealing way to present our findings. To validate the findings we used the principle<br />

of ‘member check’ (Clarke, 2002). We organized feedback to different groups of<br />

participants and included the responses of the participants as additional data<br />

(Huberman & Miles, 1988). First we fed them back to the project group, then to the<br />

larger group of stakeholders (first stakeholder conference), and later to the<br />

Federation <strong>for</strong> Foster Care. We also discussed the general findings of our research in<br />

a workshop <strong>for</strong> a wide audience working in foster care during the week of foster care<br />

(Workshop 'Projects and Research in Foster Care', December 2004). We made a slide<br />

presentation with a summary of our main findings, using the structure of the<br />

interviews. We sent a report to all those stakeholders who had been interviewed, also<br />

to those who had not been invited to the first stakeholder conference. We wrote a<br />

report (May 2004) <strong>for</strong> the policy makers w<strong>here</strong> this analysis was presented. The data<br />

174


from the stakeholder interviews also allowed me to reconstruct the socio-political,<br />

historical and institutional context of the collaborative.<br />

It proved to be extremely difficult to share the in<strong>for</strong>mation from the interviews with<br />

the participants in the project because t<strong>here</strong> were too many issues. It took us, <strong>for</strong><br />

instance, two meetings of approximately three hours to present and discuss the<br />

issues in the project group (attachment 3 and 4). The presentation was ‘distant’<br />

because the participants had not been involved in the interviewing. The consequence<br />

was that the researchers became the ones who ‘knew’. We were held responsible <strong>for</strong><br />

representing the interests of the external stakeholders at the table. This put us in an<br />

awkward position (article 3). Sharing findings with the participants was a way to pay<br />

attention to the possibility of personal biases. It was also an intervention to make<br />

visible what the group did not know or tried to keep implicit (Schein, 1987).<br />

Although some of the in<strong>for</strong>mation was unexpected and unpleasant (e.g. the services<br />

<strong>for</strong> foster care were perceived as inefficient, not professional, and only defending the<br />

interests of foster parents), the members of the project group were interested to hear<br />

feedback from ‘outsiders’.<br />

Step 2: Analysis of issues in the stakeholder interviews<br />

On the basis of the first order analysis of the stakeholder interviews I made a further<br />

analysis of this data set. During the analysis I regularly went back to the original<br />

empirical data (34 interviews). I analyzed the data with a more focused question <strong>for</strong><br />

exploration: what issues related to collaboration in foster care emerge? I started to<br />

organize the data using the following provisional structure:<br />

- Content (substance): which issues are relevant <strong>for</strong> collaboration?<br />

- Procedure: how should collaboration be organized?<br />

- Relationships and process: how do they experience the relationships among the<br />

services and the wider group of stakeholders?<br />

175


- Context: in what way is the socio-economic context of the collaborative ef<strong>for</strong>t<br />

helping or hindering collaboration?<br />

After restructuring the raw data (quotes) in this structure, I developed broader, more<br />

meaningful categories in relation to the critical issues related to collaboration. I asked<br />

questions to the data and used the method of constant comparison to develop<br />

categories. This second order analysis represents categories of critical issues based on<br />

the perceptions of a wide group of stakeholders. The main results are presented in<br />

attachment 6.<br />

Step 3: Reconstruction of the collaborative process and analysis of issues during<br />

interaction moments<br />

As the process unfolded, I gradually developed a reconstruction of the collaborative<br />

process. This reconstruction was based on my field notes, documents, and<br />

journalizing notes. It provided a provisional overview <strong>for</strong> analysis and interpretation<br />

(Spradley, 1980). It also allowed <strong>for</strong> a ‘total immersion’ in the data, it helped to<br />

become intimately familiar with the case, and to keep the ‘wholeness’ of the data in<br />

mind (Eisenhardt, 1989; Hollway & Jefferson, 2000; Clarke, 2002). The overview<br />

<strong>for</strong>med the basis <strong>for</strong> the narrative of the case. The chronological overview was<br />

organized using the following structure: date, type of interaction or event, persons<br />

involved, content of the interaction, critical issues, and available data (see attachment<br />

7).<br />

In a first phase I used Atlas-ti to analyze the interaction moments. I introduced my<br />

field notes of the project group meetings and the stakeholder conferences into the<br />

software system. This provisional analysis helped me to organize and structure the<br />

data and to easily find back relevant quotes <strong>for</strong> the papers I was writing. It also<br />

allowed me to trace the life cycle of issues over time. I made links and looked <strong>for</strong><br />

similarities and differences in the material in a process of constant comparison,<br />

coding and categorizing (Strauss & Corbin, 1998). This provisional analysis resulted<br />

in a large number of categories (see attachment 8).<br />

176


In a second phase I decided to include the internal meetings of the consultants as<br />

data, because from the first provisional analysis of the data it appeared that the<br />

consultants played a critical role in direction setting. I also decided to analyze the<br />

issues more in detail, <strong>for</strong> each separate meeting. I made data summaries of the 13<br />

internal meetings of the consulting group, the 13 meetings of the project group, and<br />

of the three stakeholder conferences. I identified and structured the issues that were<br />

raised, and introduced these summaries in the process reconstruction (attachment 7).<br />

The analysis of the stakeholder conferences is presented in a separate file (attachment<br />

9), in order not to overload the process overview.<br />

To check and validate emergent interpretations, I consulted my colleagues <strong>for</strong> ‘peer<br />

debriefing’ (Clarke, 2002). This happened during <strong>for</strong>mal and in<strong>for</strong>mal conversation<br />

in the course of the project. T<strong>here</strong> was always at least one colleague present during<br />

interviews or meetings. They acted as sparring partners ('investigator triangulation',<br />

Patton, 1987). After the project, I organized a seminar to present my research findings<br />

and discussed it with them. I also shared my papers with my colleagues. The critical<br />

incident interviews helped me to validate my findings.<br />

Step 4: Analysis of issues from the critical incident interviews<br />

For the analysis of the critical incident interviews, I typed up the issues and<br />

structured the data in the following way: (1) what happened? (2) what meaning does<br />

the interviewee attribute to the event or issue? (3) In what way did the event or issue<br />

set the direction of the collaborative according to the interviewee? (effects,<br />

consequences)<br />

This analysis resulted in a large amount of critical incidents, some of which<br />

overlapped (see attachment 9). The withdrawal of the liberal service, <strong>for</strong> instance,<br />

was reported by all interviewees as a critical incident that set the direction of the<br />

process. The analyses of issues in the stakeholder interviews, during the interactions,<br />

177


and in the critical incident interviews, provided the basis <strong>for</strong> interpretation of the<br />

dynamics in the case (article 3 and 4).<br />

REFERENCES<br />

Alvesson, M. (2003). Beyond Neo-Positivists, Romantics and Localists: A Reflexive<br />

Approach to Interviews in Organization Research. Academy of Management Review,<br />

28 (1), 13-33.<br />

Chell, E. (2004). Critical Incident Technique. In Cassell, C. & Symon, G. (Eds.), Essential<br />

Guide to Qualitative Methods in Organizational Research. London: Sage, pp. 45-60.<br />

Clarke, S. (2002). Learning from experience: psycho-social research methods in the<br />

social sciences. Qualitative Research, 2 (2), 173-194.<br />

Eden, C. & Huxham, C. (1996). Action research <strong>for</strong> the study of organizations. In Clegg,<br />

S.R., Hardy, C. & Nord, W.R. (Eds.) Handbook of organization studies. London: Sage,<br />

pp.526-542.<br />

Eisenhardt, K.M. (1989). Building Theories from Case Study Research. Academy of<br />

Management Review, 14 (4), 532-550.<br />

Flick, U. (2002). An Introduction to Qualitative Research. Second Edition. London: Sage.<br />

Gabriel, Y. (Ed.) (1999). Organizations in Depth. The Psychoanalysis of Organizations,<br />

London: Sage.<br />

Gould, L. (1991). Using psychoanalytic frameworks <strong>for</strong> organizational analysis. In Kets<br />

de Vries, M.F.R. (Ed.), Organizations on the couch; clinical perspectives on organizational<br />

behavior and change. San Francisco: Jossey-Bass, pp. 25-44.<br />

Gray, B. (1989). Collaborating: Finding Common Ground <strong>for</strong> Multiparty Problems. San<br />

Francisco: Jossey Bass.<br />

Hollway, W. & T. Jefferson (2000). Doing Qualitative Research Differently: Free<br />

Association, Narrative and the Interview Method. London: Sage.<br />

Huberman, A.M. & M.B. Miles (1988). Assessing Local Causality in Qualitative<br />

Research. In Berg, D.N. & K.K. Smith (Eds.) The Self in Social Inquiry. Researching<br />

Methods. Newbury Park, Cali<strong>for</strong>nia: Sage Publications, pp. 351-381.<br />

Patton, M.Q. (1987). Qualitative Evaluation Methods. London: Sage.<br />

Schein, E.H. (1987). The Clinical Perspective in Fieldwork, Newbury Park, Cali<strong>for</strong>nia:<br />

Sage.<br />

178


Schein, E.H. (2000). The next frontier: Edgar Schein on organizatonal therapy. Academy<br />

of Management Executive, 14 (1), 31-49.<br />

Schwartzman, H.B. (1993). Ethnography in organizations. Qualitative Research Methods,<br />

volume 27. Newbury Park: Sage.<br />

Spradley, J.P. (1980). Participant Observation. New York: Holt<br />

Strauss, A. & J. Corbin, (1999). Basics of qualitative research: Techniques and procedures <strong>for</strong><br />

developing grounded theory. Second Edition, Thousand Oaks: Sage.<br />

Yin, R.K. (1994). Case Study Research. Design and Methods. Second Edition. Applied Social<br />

Research Methods Series, Volume 5, Thousand Oaks, Cali<strong>for</strong>nia: Sage Publications.<br />

FOR THE READER<br />

In the articles, papers and presentations I protected the identity of the actors, as the<br />

change process is still ongoing. I attributed codes to the organizations (see table 11)<br />

and to the consultants (see attachment 1). The quotes in the articles have been<br />

translated from Dutch. I have tried to express the essence of what people say.<br />

Sometimes it was hard to translate metaphors (e.g. ‘eenheidsworst’), dialect, humor,<br />

word games, or technical jargon (e.g. ‘receptiefunctie’). The subtitles are not<br />

numbered.<br />

Article 3 is accepted <strong>for</strong> publication by the Journal of Occupational and<br />

Organizational Psychology. It will be published in September 2006 (see also<br />

attachment 10). ‘Our’ refers to the four consultants engaged in the project. All of<br />

them were working at the Center <strong>for</strong> Organizational and Personnel Psychology<br />

(COPP) at the time of the project. ‘I’ refers to the researcher, the author of this paper.<br />

Article 4 was submitted to The Journal of Applied Behavioral Science on 17<br />

December 2005. The paper included in this work is a slightly longer version, as it<br />

contains more case material (see also attachment 10). ‘Our’ refers to the four<br />

consultants engaged in the project. All of them were working at the COPP at the time<br />

of the project. ‘I’ refers to the researcher, the principle author of this paper.<br />

179


THE PSYCHODYNAMIC PERSPECTIVE IN ORGANIZATIONAL RESEARCH:<br />

MAKING SENSE OF THE DYNAMICS OF DIRECTION SETTING IN<br />

EMERGENT COLLABORATIVE PROCESSES (ARTICLE 3)<br />

Silvia Prins<br />

Introduction<br />

In this paper I demonstrate how the psychodynamic perspective contributes to the<br />

study of organizing processes. Research from this perspective provides insight in<br />

how people deal with the emergent nature of a collaborative w<strong>here</strong> conventional<br />

processes and structures are no longer available. First, I address the specific nature<br />

and challenges of ‘multiparty collaboration’. Then I describe the characteristics of a<br />

psychodynamic approach in organizational research and the kind of theory it<br />

generates. I present a case study in the domain of foster care, w<strong>here</strong> five independent<br />

organizations tried to develop a scenario <strong>for</strong> future collaboration. In the case analysis<br />

I focus on how participants and consultants set the direction of the collaborative. I<br />

discuss some critical issues with which the participants were confronted and make<br />

sense of the dynamics that emerged. To conclude, I emphasize the benefits of using a<br />

psychodynamic perspective in the study of emergent organizing processes.<br />

Collaborative work and the challenges of direction setting<br />

Organizations and social groups are increasingly challenged to collaborate.<br />

Multiparty collaboration is an organizational strategy to develop sustainable<br />

solutions <strong>for</strong> societal and environmental 'meta-problems' (e.g. poverty, pollution)<br />

that require multidisciplinary and multi-organizational involvement (Gray, 1989;<br />

Huxham, 1996; Huxham & Vangen, 2005). Gray (1989: 5) defines multiparty<br />

collaboration as “(…) a process through which parties who see different aspects of a problem<br />

can constructively explore their differences and search <strong>for</strong> solutions that go beyond their own<br />

limited vision of what is possible”. Organizations, social groups and unorganized<br />

parties work across the boundaries to develop sustainable solutions <strong>for</strong> a problem<br />

180


domain. Gray (1989) distinguishes five characteristics of multiparty collaboration: (1)<br />

the stakeholders of the domain are interdependent; (2) solutions emerge by dealing<br />

constructively with differences; (3) joint ownership of decisions is involved; (4)<br />

stakeholders assume collective responsibility <strong>for</strong> the future direction of the domain;<br />

and (5) collaboration is an ‘emergent’ process. The assumption in this paper is that all<br />

five features of multiparty collaboration represent a challenge and a source of anxiety<br />

<strong>for</strong> those involved.<br />

A particular challenge of collaborative work is how to define ‘leadership’ in an<br />

organizational context w<strong>here</strong> hierarchy is not a valid organizing principle. Often<br />

t<strong>here</strong> is no <strong>for</strong>mal leader, authority relations are ambiguous, and the consensual<br />

nature of collaborative work inhibits the emergence of overt leadership. Clarity of<br />

structures, lines of accountability, and clear role boundaries are reduced or<br />

dismantled (Huffington, James & Armstrong, 2004). This study focuses on the<br />

dynamics of direction setting, inspired by Feyerherm’s (1997, 1) definition of leaders<br />

as persons “who influence the course of events, the ways issues get framed and resolved, and<br />

the people who influence the outcomes of the gathering”. Emergent <strong>for</strong>ms of organizing<br />

require a shift from hierarchically embedded authority to a more personal and<br />

laterally distributed exercise of leadership. The challenge is to mobilize new<br />

processes and structures to contain the tensions in<strong>here</strong>nt in collaborative work<br />

(Hirschhorn, 1997; Huffington et al., 2004). The multiparty literature stresses the need<br />

<strong>for</strong> a dynamic, process-oriented theory of inter-organizational relations and <strong>for</strong><br />

research on the quality of collaborative relationships, the emotional challenges posed<br />

by interdependent work, and defensive dynamics in ‘emergent’ processes (Gray,<br />

1989; Czander, 1993; Gould, Ebers & Clinchy, 1999; Page, 2003). In the next section I<br />

discuss the assumptions and framework that underpin research from a<br />

psychodynamic perspective.<br />

181


The psychodynamic perspective in organizational research<br />

Assumptions about collaborative work<br />

The theoretical framework underpinning this research is based on the pioneering<br />

work of the Tavistock Institute. This group of scholars engaged in action research<br />

and promoted an integration of insights from social sciences and psychoanalysis in<br />

the post-war period (Trist & Murray, 1990). In recent years a contemporary paradigm<br />

has been developed to address the challenges of new <strong>for</strong>ms of organizing (e.g.<br />

Gould, Stapley & Stein, 2001; Huffington, Armstrong, Halton, Hoyle & Pooley, 2004).<br />

The main assumptions of this paradigm can be summarized as follows:<br />

• Behavior is often the result of conscious and unconscious mental processes. In<br />

the study of organizing processes conscious and unconscious aspects have to<br />

be taken into account.<br />

• People create a subjective, emotional reality of the organization. Attribution of<br />

meaning, through social interaction, mediates between organizational reality<br />

and the human experience.<br />

• Individual and group behavior and the structural features of organizational<br />

life are in dynamic interaction: the organizational structures stimulate<br />

particular patterns of individual and group processes, and these processes, in<br />

turn, influence how particular features of the organization are developed.<br />

• Most human beings are inclined to avoid anxiety, uncertainty and threats to<br />

their self-esteem. T<strong>here</strong><strong>for</strong>e they try to achieve control, predictability and<br />

ways to enhance their self-esteem. 'Social defenses' emerge when a group<br />

unconsciously colludes to ward off the anxiety and tensions of the work place,<br />

often at the cost of task per<strong>for</strong>mance.<br />

• T<strong>here</strong> is an underlying assumption of a ‘healthy’ organization, characterized<br />

by wisdom, humanity, and the ability to help itself to overcome defenses<br />

(Neumann & Hirschhorn, 1999; Vansina, 2000; Amado & Ambrose, 2001;<br />

Driver, 2003; Diamond & Allcorn, 2003).<br />

The motive to start a collaborative can be conscious or rational, but the process is also<br />

influenced by hidden, emotional and unconscious motives. In an inter-organizational<br />

182


context, groups come to share collective, unconscious assumptions about other<br />

relevant groups. “These assumptions are manifested in both conscious and unconscious<br />

processes, including projections, attributions, and stereotyping which shape the ensuing<br />

quality and character of their intergroup relationships.” (Gould et al., 1999, 700)<br />

Participants in a collaborative are confronted with different sources of anxiety: the<br />

context, the nature of the process and the relationships with other stakeholders,<br />

which I will briefly discuss.<br />

First, a collaborative is usually embedded in a turbulent and complex context.<br />

Players in the context (e.g. constituent organizations, sponsors) influence the<br />

direction of the process, although they are not sitting at the table. Policymakers, <strong>for</strong><br />

instance, can take decisions that profoundly affect a collaborative (e.g. stop funding,<br />

change the law). Issues of power, politics, access to resources, and economic and<br />

technological concerns influence the dynamics in the collaborative. Secondly, a<br />

collaborative is an under-organized open system with few containing structures. It is<br />

difficult to establish the primary task, procedures, roles and membership in advance.<br />

Participants negotiate ‘psychological’ boundaries that are experienced and enacted in<br />

the interactions. These relate, <strong>for</strong> instance, to authority (who is in charge of what?),<br />

and identity (who is - and who is not - 'us') (Hirschhorn & Gilmore, 1992). The<br />

emergent nature of collaborative work stirs up anxiety and mobilizes exactly the<br />

kind of defensive responses that hinder effective collaboration (Krantz, 1990; 1998).<br />

When negative feelings and tensions are not contained, defensive dynamics, like<br />

premature <strong>for</strong>malizing of the process, are likely to occur. Finally stakeholders with<br />

different and sometimes conflicting interests are challenged to establish<br />

interdependent relationships. This requirement may provoke defensive responses.<br />

T<strong>here</strong> is usually little time <strong>for</strong> direct interaction and not much psychic energy<br />

available to foster interdependent relationships (Cooper & Dartington, 2004). The<br />

essence of collaborative work is to make use of the diversity in the system, but it is<br />

precisely such a confrontation with differences that increases the potential <strong>for</strong><br />

conflict. Stakeholders are faced with challenges to their identity (e.g. fear to be<br />

overpowered) and to their autonomy. Representatives need to deal with the paradox<br />

183


of entertaining a relationship based on ‘equality’ with partners who differ in power,<br />

size, access to resources, social status, etc. Participants need new skills, such as lateral<br />

influencing based on personal authority, the competences to build collaborative<br />

relationships, the ability to acknowledge and manage the uncertainties and<br />

ambiguities of roles, the capacity to share responsibility <strong>for</strong> direction setting, and to<br />

work creatively with sameness and difference (Hirschhorn, 1997; Page, 2003;<br />

Huffington et al., 2004).<br />

‘Understanding’ dynamics<br />

The system psychodynamic perspective was the organizing principle of my research.<br />

This approach to organizational study simultaneously maintains the systems view<br />

and the ‘life-world’ view (Anderson & White, 2000). The world is not completely<br />

subjective or completely objective (Heller, 2004). This frame explores the way in<br />

which subjective experiences and fantasies about organizational life influence<br />

feelings, thoughts and actions in the workplace (Menzies, 1988; Miller, 1997). The aim<br />

of my research was to understand (‘Verstehen’) phenomena in their complexity,<br />

wholeness and uniqueness, rather than explaining or predicting them (Edelson, 1988;<br />

Lapierre, 1991). My intention was to construct a ‘rich’ and contextualized<br />

understanding and to develop a ‘thick description’ of meaning grounded in<br />

empirical data (Geertz, 1973).<br />

I studied a ‘collaborative’ as an emergent process of organizing, because social reality<br />

is a dynamic process (ontological position). Pettigrew (1997, 338) defines ‘process’ as<br />

“a sequence of individual and collective events, actions, and activities unfolding over time in<br />

context”. The method <strong>for</strong> studying the change process was based on process<br />

narratives (epistemological position). This strategy involves the construction of a<br />

detailed story from raw data collected in real time and in retrospect. It reproduces<br />

the ambiguity that exists in the situation observed (Langley, 1999). The research<br />

design was set up to capture the variety of perspectives and the complexity of the<br />

subject. To study the effects of subjectivity on the process of organizing, I collected<br />

184


the accounts of multiple actors over time. Making sense of life experiences requires a<br />

longitudinal perspective (Dawson, 1997; Heller, 2004). I also focused on how the<br />

participants collectively made sense of the collaborative experience. I explored how<br />

unconscious meanings, conflicts, fears and beliefs were projected onto ‘others’ and<br />

how people collectively managed these dynamics (Krantz, 1990). To avoid the risk of<br />

‘psychological reductionism’, I included the history, context and system features of<br />

the collaborative (Pettigrew, 1997; Schonberg, 1998; Neumann & Hirschhorn, 1999). I<br />

constructed a narrative account of a process of organizing “by narrating emergent<br />

actions and activities by which collective endeavours unfold” (Van de Ven & Poole, 2005).<br />

The in-depth case study is a personalized account or ‘a confessional tale’ because it is<br />

a mixture of descriptions of the subject and my experiences in studying it (Van<br />

Maanen, 1988; Flick, 2002).<br />

I used an interpretivist frame: in order to understand the world of meaning of the<br />

participants I needed to interpret it (Schwandt, 1998). In a hermeneutic<br />

phenomenology “the aim is to construct an animating, evocative description of the human<br />

actions, behaviours, intentions, and experiences as we meet them in the life world” (Van<br />

Manen, 1990, 19). I searched <strong>for</strong> patterns and underlying dynamics in an iterative<br />

process of sense making. Interpretations emerged in a cyclic process of moving back-<br />

and-<strong>for</strong>th between data and theoretical understanding (Pettigrew, 1997). Inevitably I<br />

brought an intellectual pre-understanding to the case study, based on a review of the<br />

literature and two case studies in other domains (Prins, Craps & Taillieu, 2006). The<br />

conceptual framework of psychodynamics provided a hermeneutic grid <strong>for</strong><br />

understanding. At the same time I tried to observe the phenomena with a fresh look<br />

(Obholzer, 1999; Schein, 1987).<br />

The case analysis presents a psychodynamic reading of the phenomena in this project<br />

as a complementary view that can enrich other perspectives (Halton, 1994;<br />

Schonberg, 1998, Anderson & White, 2000). My aim was not to arrive at<br />

generalisability of the findings (Dawson, 1997). The challenge is to make the<br />

conceptualization of experiences in this particular collaborative relevant <strong>for</strong> similar<br />

185


contexts. A better understanding of the ordinary, routine or ritualistic dynamics that<br />

come to the surface can help to facilitate creative collaboration, change, and<br />

productivity in emergent organizational contexts.<br />

The case: from competition to collaboration<br />

The story<br />

This case study is based on a one year project in the domain of foster care in Flanders<br />

(Belgium). The foster care services were confronted with a lack of candidate foster<br />

families to take care of the growing number of children eligible <strong>for</strong> foster care. The<br />

services were rivals because subsidies were only granted to them after placement of a<br />

child in a family. T<strong>here</strong><strong>for</strong>e they were competing <strong>for</strong> resources and funding was<br />

unpredictable. A manager of a foster care service prepared a project to develop a<br />

‘network organization’ and asked our Center to facilitate the process. The project was<br />

a proactive response to new priorities in welfare policy (rationalization, regional<br />

organization of assistance, imposed mergers). The negotiated objectives with policy<br />

makers were: (1) develop a structural basis <strong>for</strong> collaboration among services <strong>for</strong><br />

foster care in one province in Flanders; and (2) develop a concept <strong>for</strong> a ‘reception<br />

function’ <strong>for</strong> foster care. The idea was that the experiences and results of the project<br />

could be used as a model <strong>for</strong> Flanders. A member of our Center, who was not<br />

involved in the project later on, designed it as an action research in a ‘multiparty’<br />

philosophy. The identified stakeholder groups were: users (parents and children),<br />

voluntary collaborators (foster families), professionals (personnel), relegating parties<br />

(e.g. social workers, juvenile court), and policy makers.<br />

Five services working in the same region agreed to participate. Their region was<br />

selected at a meeting of the Federation <strong>for</strong> foster care because the managers had set<br />

up a regional consultation plat<strong>for</strong>m ten years ago and already collaborated in ‘safe’<br />

domains (e.g. organize annual foster care week). The case analysis focuses on the<br />

‘project group’ (table 1) as the vehicle <strong>for</strong> collaboration and the plat<strong>for</strong>m w<strong>here</strong> the<br />

dynamics of the system were played out.<br />

186


Organization Represented by Characteristics of the organization<br />

FC service 1<br />

FC service 2<br />

FC service 3<br />

FC service 4<br />

Director (convener)<br />

187<br />

– Funded by Special Youth<br />

Care<br />

– Pluralistic (catholic, liberal<br />

and others)<br />

– Services in all regions of<br />

Flanders<br />

Regional coordinator – Funded by Special Youth<br />

Care and Care <strong>for</strong> the<br />

Handicapped<br />

– Pluralistic (catholic, liberal<br />

and others)<br />

– Services in all regions in<br />

Flanders<br />

Director – Funded by Special Youth<br />

Care and Care <strong>for</strong> the<br />

Handicapped<br />

– Pluralistic (catholic, liberal<br />

and others)<br />

– Services only in the region of<br />

the project<br />

Director – Funded by Special Youth<br />

Care<br />

– Catholic<br />

– Services only in the region of<br />

the project<br />

FC service 5 Regional coordinator and/or<br />

manager Flanders<br />

Federation <strong>for</strong><br />

foster care<br />

– Funded by Child & Family<br />

and Special Youth Care<br />

– ‘Liberal’ (service explicitly<br />

declaring itself as ‘nonconfessional’<br />

in the religious<br />

sense)<br />

– Services in all regions in<br />

Flanders<br />

Head of the Federation Represents all FC services in<br />

Flanders


Center <strong>for</strong><br />

Organizational<br />

Psychology<br />

– Coordinator: daily<br />

coordination, facilitation,<br />

research<br />

– Senior consultant: facilitation,<br />

scientific coordinator<br />

– Facilitator: facilitation of<br />

stakeholder conferences,<br />

work group, project group<br />

– Researcher: documentation<br />

(interviewing, observation),<br />

feedback, conceptualization<br />

of the experiences,<br />

participation<br />

188<br />

University center, specialized in<br />

multiparty collaboration and<br />

process facilitation<br />

Table 11: Membership of the project group and characteristics of the participating<br />

organizations.<br />

The project group identified a wide group of representatives in foster care <strong>for</strong><br />

interviewing. Together with my colleague I spent two months interviewing 34<br />

stakeholder representatives (e.g. foster parents; policy makers; residential<br />

institutions; judges and social workers; employees, board members and managers of<br />

the foster care services; umbrella organizations; experts). We made a structured<br />

overview of the critical issues in the domain of foster care and fed back our findings<br />

to the project group and the stakeholders. Their responses were integrated as<br />

additional data (Huberman & Miles, 1988). This ‘member check’ allowed me to verify<br />

the possibility of personal biases (Clarke, 2002). On the basis of our findings the<br />

project group designed a ‘stakeholder conference’. This provided a <strong>for</strong>um <strong>for</strong> direct<br />

interaction among the ‘internal’ stakeholders (employees, managers and boards of<br />

the services). The ‘external’ stakeholders were only invited in the morning. The<br />

internal stakeholders decided to focus on internal matters first and continued their<br />

discussions at a second stakeholder conference w<strong>here</strong> they established ‘work<br />

groups’. Over a period of three months groups of employees worked around specific<br />

organizational procedures: inflow of children and selection of foster parents. In<br />

parallel, the project group organized a meeting with their board members in order to


each an agreement in principle on collaboration. During this meeting one of the<br />

services (of liberal inspiration) stepped out of the project. All members of the project<br />

group identified this as the most critical event in the process. With only two months<br />

left be<strong>for</strong>e the deadline, the project group tried to obtain some concrete results <strong>for</strong> the<br />

final stakeholder conference. The managers discussed potential scenarios <strong>for</strong> the<br />

future, conditions <strong>for</strong> collaboration, and looked <strong>for</strong> additional funding. They invited<br />

the external stakeholders <strong>for</strong> the final part of the third stakeholder conference. The<br />

project group had not achieved the <strong>for</strong>mal objectives of the project. As t<strong>here</strong> was no<br />

clear scenario <strong>for</strong> future structural collaboration, the work groups and managers<br />

shared their experiences, ideas and learning with the external stakeholders.<br />

The research approach<br />

Action research<br />

The consulting team, of which I was part, was hired to coordinate and facilitate the<br />

process. My role was to document the action research. I observed interactions and<br />

collected data, while actively participating in the process. This position allowed me<br />

to balance between experiencing and observing and to 'sit on the boundary' (Smith,<br />

1995). I introduced data in the system to facilitate reflection on the change process.<br />

My assumption was that action research is more likely to produce reliable data,<br />

because the participants are involved in circumstances that really matter to them<br />

(Chisholm & Elden, 1993; Eden & Huxham, 1996). The aim of this action research<br />

was to improve the client system and at the same time develop emergent theory from<br />

practice.<br />

Data triangulation enabled a rich and contextualized understanding of the dynamics<br />

(Yin, 1994; Flick, 2002). Over a period of one year I systematically made field notes<br />

during meetings of the project group (13), internal meetings of the consultants (13),<br />

and stakeholder conferences (3 days). I considered meetings as ‘communication<br />

events’, embedded within a context, which the participants used to interact and to<br />

interpret events (Schwartzman, 1993). In this space the actors set the direction of the<br />

189


process. Documents and interview data enabled me to reconstruct the antecedents<br />

and context of the project. Six months after the project I interviewed the managers<br />

and consultants of the project group. My aim was to identify important events and<br />

issues in the process (critical incident interviews). I used this method as an<br />

unobtrusive, phenomenological method to mediate the inquiry process and to<br />

encourage the interviewees to reflect on their experiences (Gabriel, 1999).<br />

Subjectivity and inter-subjectivity in the research<br />

Doing fieldwork from a psychodynamic perspective is a subjective, inter-subjective<br />

and reflexive process. It is a dialogue and an interpretive endeavor, mediated by the<br />

minds of the participants and the researcher, and by unconscious processes (Hunt,<br />

1989). The subjective dimension of doing research from a psychodynamic perspective<br />

is reflected in different aspects of the research: the attitude of the researcher, the<br />

subjectivity of the researcher, and the use of dynamics in the research team and<br />

research relationship as data about the dynamics in the client system.<br />

In my interactions with the participants and during data analysis I adopted an<br />

‘interpretive stance’ (Shapiro & Carr, 1991). This attitude is characterized by<br />

introspection, reflexivity and sensitivity. I tried to pay an evenly divided attention to<br />

manifest and underlying dynamics. This means I had to listen with the 'third ear' and<br />

be sensitive to the ‘hidden music’ in the stories and to ‘clues’ (Reik, 1948; Gilmore &<br />

Krantz, 1985). “The odd, the out of place, the significant exception provide far more insight<br />

than large volumes of uni<strong>for</strong>m and unidirectional data” (Gabriel, 1999, 251). I paid<br />

attention to first impressions, the energy level, non-verbal cues, humor, issues that<br />

were avoided, colorful language, images, silence, and unexpected or strong<br />

emotions. This can point at themes that are expressed elsew<strong>here</strong> in the system.<br />

Example. The managers often made jokes to reduce the tension in the group. They repeatedly<br />

joked about our centre being part of a catholic university. As differences in ideology<br />

increasingly provoked tensions, it seemed as if the group displaced their struggle with ideology<br />

to the consulting team.<br />

190


In order to get in touch with the underlying meaning I had to ‘listen’ to the other and<br />

to my self. The 'self' is used as an instrument in sensing, observing and exploring the<br />

subjective and inter-subjective world of work (Diamond & Allcorn, 2003; Gardner,<br />

1989). I paid attention to my emotions (e.g. bored, enthusiastic), physical reactions<br />

(e.g. tired, nervous) and my assumptions. Whenever I experienced an uneasy feeling,<br />

I tried to sort out what is 'me' and what is 'not me' in the experience (Shapiro & Carr,<br />

1991).<br />

Example. During the two months of interviewing my colleague and I were extremely tired and<br />

it was remarkable how often we yawned while driving around. It seemed to express the issue of<br />

doing hard work that is not valued. The managers often complained how high the work load<br />

was and how important foster care was as a solution <strong>for</strong> children in problematic situations. One<br />

of the motives <strong>for</strong> the project was the frustration that policy makers did not understand the<br />

importance of foster care and did not treat foster care as an equal partner. We seemed to ‘carry’<br />

a lot <strong>for</strong> the system. (Note made during the data analysis, after the project)<br />

I had to tolerate the tension of ‘not knowing’ and of not being in control. The attitude<br />

of ‘negative capability’ (Bion, 1970) is opposed to the mentality of knowing and<br />

judging which prematurely closes of exploration and observation (Vansina-Cobbaert,<br />

2005).<br />

I systematically made journalizing notes to ensure a continuous process of<br />

'disciplined subjectivity' (Berg, 1988; Huffington & James, 1999; Bradbury &<br />

Bergmann Lichtenstein, 2000). Self monitoring helped to document how I produced<br />

data, to what extent my personal bias may have influenced interpretations, to see the<br />

link between issues in my personal life and the research, and how anxiety may have<br />

influenced the choice <strong>for</strong> a method or role (Devereux, 1967; Hunt, 1989; Clarke, 2002;<br />

Meek, 2003). It also helped me to choose a more appropriate method <strong>for</strong> data<br />

collection to document the ‘process’.<br />

Example. At the start of my research I concentrated on interviewing as preferred method of<br />

data collection, because I assumed people would be capable and willing to reflect on and talk<br />

about their experiences and the interview was a controlled setting. I realized, however, that<br />

only subjective accounts were not sufficient <strong>for</strong> a process analysis. I realized I had tried to<br />

reduce the complexity, emergence and ambiguity in the research setting, and that these issues<br />

were also predominant in my life at the time. T<strong>here</strong><strong>for</strong>e I shifted to participative observation as<br />

the main source of data. I also decided to pay explicit attention to the complexity of the context<br />

of the collaborative by integrating documents on the history and the institutional context. (Note<br />

three months after the start of the research).<br />

191


The underlying assumption in this research is that the roles assigned to the<br />

consultant or the dynamics in the consulting team recreate important and<br />

unconscious dynamics present in the client system. Transference and counter<br />

transference dynamics and parallel processes are important dynamics in the research<br />

relationship (Gilmore & Krantz, 1985; Hunt, 1989; Clarke, 2002; Diamond & Alcorn,<br />

2003). Strong emotions (e.g. anger, idealization) are a clue to detect transference<br />

reactions, which are essentially unconscious. In the data analysis I included field<br />

notes of our (i.e. the consultants) internal meetings, because I was aware that parallel<br />

dynamics were taking place. In this paper I demonstrate how the internal dynamics<br />

in the consulting team and the relationship between the consultants and the client<br />

system provided data on dynamics in the collaborative (Berg & Smith, 1988; Gabriel,<br />

1999). The quotes are from interviews and meetings.<br />

Critical issues and dynamics<br />

In order to make sense of the dynamics, I started with a reconstruction of the process<br />

(type of interaction, participants, content, and emergent issues) based on the<br />

available data. This allowed me to become intimately familiar with the case and to<br />

keep the wholeness of the data in mind (Eisenhardt, 1989; Clarke, 2002; Hollway &<br />

Jefferson, 2002). The reconstruction was a provisional overview <strong>for</strong> analysis and<br />

interpretation (Spradley, 1979). Secondly, I made a systematic analysis of the issues<br />

based on three sets of data: (1) stakeholder interviews, (2) field notes of interaction<br />

moments, and (3) critical incident interviews. I looked <strong>for</strong> links, similarities and<br />

differences in the material in a process of constant comparison, coding and<br />

categorizing (Strauss & Corbin, 1998). During in<strong>for</strong>mal conversations and internal<br />

meetings the consulting team systematically tried to make sense of what was<br />

happening (investigator triangulation, Patton, 1987). On a regular basis, I checked<br />

my interpretations with my colleagues (e.g. in<strong>for</strong>mal conversations, research<br />

seminar) and I discussed my findings with peers (supervisor, mentor, colleagues at<br />

conferences) to have an outside perspective. I paid attention to thematic unity and<br />

192


internal consistency and to a transparent approach to data analysis (Kets de Vries,<br />

1991; Gould, 1991; Levinson, 1991).<br />

Issue 1: role ambiguity and ownership<br />

The case analysis demonstrates, as Harold Bridger observed (Klein, 1976), that the<br />

beginning of the intervention contained the key issues and dynamics of the process.<br />

It was, however, not easy to immediately grasp the meaning of the data. I was<br />

particularly sensitive to the issue of ambiguity as I struggled with the ambiguity of<br />

my role. Was I an action researcher or documenting an action research? Was I<br />

concerned with improving the system or was I only observing it? Why was I more<br />

fascinated when things didn’t run smoothly? To what extent was I also responsible<br />

<strong>for</strong> the quality of the results?<br />

The starting conditions of the project were ambiguous. Unexpectedly policy makers<br />

had approved the project. A participant called the project an ‘accident de parcours’.<br />

Without preparation the five foster care services found themselves in a project to<br />

foster structural collaboration. The contract with policy makers was ambiguous: the<br />

expected results were predefined, but the design of the process was emergent and<br />

consequently the outcome could not be known in advance. The expected output, a<br />

concept <strong>for</strong> a ‘reception function’, provoked different assumptions and expectations.<br />

For one of the consultants this concept was strategic jargon to speak the language of<br />

policy makers in order to obtain funding. For the convener, however, it was the<br />

definite agenda of the project. The objective of structural collaboration was also<br />

ambiguous. T<strong>here</strong> was a tension between idealistic, rational, societal and moral<br />

motives <strong>for</strong> collaboration, and the emotional responses provoked by the prospect of<br />

future collaboration. Some participants idealized collaboration, while others<br />

experienced it as a threat (e.g. of a merger). In foster care the natural parents and<br />

foster parents are rivals who are <strong>for</strong>ced to collaborate in the best interest of the child.<br />

The issue of ‘<strong>for</strong>ced’ collaboration was mirrored in the collaborative process. Because<br />

the services had originated from a history of ideological conflicts and splits, their<br />

193


autonomy and identity were extremely important. Now they ‘had’ to collaborate<br />

with their rivals. Small services in particular, were afraid to be absorbed by bigger<br />

ones and to lose their identity. During the very first in<strong>for</strong>mal meeting of what was to<br />

become the ‘project group’, I took a note of a casual remark. One of the managers<br />

asked: ‘who is at the core of this project, the child or the foster care services?’ This<br />

turned out to be a critical field of tension in the process.<br />

The convener had a contract with the policy makers and the consultants<br />

subcontracted to her organization. It was not clear who our client was: policy<br />

makers, the convener, the project group, the internal stakeholders, or the<br />

stakeholders in the domain. The convener found herself in an ambiguous position.<br />

She spoke as foster mother, manager (business interests, responsible <strong>for</strong><br />

employment), convener of the process (in<strong>for</strong>mal leader), interest party (loyalty to<br />

constituent organization), spokesperson <strong>for</strong> policy makers (fear of losing face), and<br />

contractor of the consultants. With her enthusiasm she had initiated the project. She<br />

had brought in external consultants to be able to ‘sit on her chair’ and defend her<br />

agenda and the interests of her organization. She did not want to be addressed as the<br />

‘convener’ of the project and insisted on being ‘like the others’. When she retreated<br />

from her role as convener it was as if she had to deny her leadership capability in<br />

order to create a collaborative relationship with the other managers. She expected the<br />

consultants to take the lead and be the driving <strong>for</strong>ce of the process. It was as if we<br />

had to defend her agenda. During the process she kept pushing the reception<br />

function, although some participants and consultants did not share her vision.<br />

During the interviews my colleague and I announced we would drop the notion of<br />

‘reception function’, because it was a solution to a problem we were still exploring.<br />

The convener, however, indirectly reprimanded us <strong>for</strong> this intervention.<br />

“The objective is a reception function. It was not the idea to let go of this concept. Then we<br />

might as well all go home. (…) My concern is: policy has given us an opportunity. If we present<br />

this as result of the project we can <strong>for</strong>get it. I want to make the most of this opportunity, but I<br />

don’t want to over rush things either. (…) At this point in time we cannot reach the objectives as<br />

they have been agreed. I feel responsible. I don’t want to lose face as an organization.”<br />

(Convener, meeting project group 9)<br />

“What is the name of this project? I think we should call it ‘project reception function’.<br />

(Convener, meeting project group 13)<br />

194


The mandate and authority of the project group were ambiguous. Membership of the<br />

project group was not representative, as the members were managers representing<br />

the interests of their organization. The project group was not a plat<strong>for</strong>m representing<br />

the diversity of the stakeholders, w<strong>here</strong> solutions <strong>for</strong> the domain were developed.<br />

The managers had different mandates, as a consequence of their hierarchical<br />

position, the geographical presence of their organization, and the management<br />

culture. One manager, <strong>for</strong> instance, could take decisions on a Flemish level, while<br />

another was coordinator of a regional service and had to go back to her constituency<br />

<strong>for</strong> important decisions. As the liberal service was the biggest in the region, they felt<br />

compelled to participate. However, from the start they had been ambivalent about<br />

their membership. They were convinced that this project would weaken the position<br />

of foster care in negotiations with policy and that it would make it easier <strong>for</strong> policy<br />

makers to cut expenses. The project group did not open up the boundaries in order to<br />

create a steering group with wider representation. They wanted to stay in control.<br />

Because they were not working in the field, the discussions were often about abstract<br />

issues (e.g. values). This narrow membership rein<strong>for</strong>ced an internal focus on the<br />

change process.<br />

The role of the consultants was <strong>for</strong>malized in the contract and discussed with the<br />

project group: develop a methodology, facilitate and structure the process, and<br />

scientific monitoring (table 1). At the start of the second stakeholder conference, we<br />

stressed that as process facilitators we would establish the conditions in which the<br />

participants could find their own solutions. Initially t<strong>here</strong> was positive transference<br />

on the consultants. We were seen as neutral experts and our involvement gave the<br />

participants hope that this time they would finally move beyond the ‘intention to<br />

collaborate’ and beyond ‘safe domains’. The presence of an impartial outsider<br />

allowed the managers to speak <strong>for</strong> their organization. They trusted the facilitators<br />

would contain the anticipated tensions and conflicts. Over time it became clear they<br />

had different expectations from us. They assumed we would set the direction and<br />

hoped we would provide them with a blueprint scenario <strong>for</strong> collaboration.<br />

195


“T<strong>here</strong> has to be more steering towards the objective. The consultants have to steer on the<br />

content level.” (Convener, meeting project group 8)<br />

The managers repeated over and over that process facilitation was a critical condition<br />

<strong>for</strong> them and they emphasized that time <strong>for</strong> the ‘process’ was essential. I took a note:<br />

‘This focus on process and process facilitation is starting to sound like a mantra!!’<br />

Journalizing helped me to make sense of what I believed the managers were doing to<br />

us and the defensive dynamics that were starting to interfere with the task. A tension<br />

emerged between the necessity to produce concrete results, and the need to take time<br />

to develop collaborative relationships. The managers did not want to come up with<br />

quick results <strong>for</strong> the sponsors, but it did worry them in view of future funding. By<br />

stressing the importance of the process, the managers could defend against the<br />

anxiety to take task related decisions.<br />

“We can continue, but process facilitation is critical. If t<strong>here</strong> is no process facilitation, the<br />

product is jeopardized. (…) We are the ones who most need process facilitation. We will have to<br />

take decisions, set the direction.” (Manager 3, meeting project group 12)<br />

“Without process facilitation it is almost impossible.” (Manager 2, stakeholder conference 3)<br />

The consultants were sometimes frustrated by the dependency of the managers and<br />

issues of ownership emerged. One of the consultants, <strong>for</strong> instance, had the feeling he<br />

had to do all the ‘dirty’ work, be the driving <strong>for</strong>ce, and keep the participants<br />

enthusiastic and motivated. This issue was not discussed in the project group. After<br />

the project it seemed as if the managers blamed the consulting team <strong>for</strong> not achieving<br />

the <strong>for</strong>mal objectives. In the critical incident interviews they expressed some<br />

criticism: the facilitators had not given personal feedback to the individual managers,<br />

they had not helped them to make sense of their experiences, and they had failed to<br />

reassure them that what they were experiencing was ‘normal’. We should also have<br />

represented the voice of the external stakeholders around the table, because we had<br />

done the interviews. The managers also regretted t<strong>here</strong> had been little space to<br />

disagree.<br />

“We can deal with an open process, but you should have given us some landmarks! (…) Maybe,<br />

after all, you were not as experienced in this matter as we had presumed…” (Manager 1, critical<br />

incident interview)<br />

196


“We tended to circle around the differences and not discuss them openly. But now we are<br />

confronted with these differences anyway!” (Manager 2, critical incident interview)<br />

The project was consultant centered, since we made up 40% of the project group. The<br />

consulting team in itself was a multiparty collaboration because we had a different<br />

roles, interests and assumptions on how to design and manage the process. It was<br />

not always easy to find the time to talk things through, because of conflicting<br />

agendas. T<strong>here</strong> seemed to be a parallel dynamic between our team and the system:<br />

little time <strong>for</strong> the project and no exploration of the diversity around the table. The<br />

unexplored different theories-in-use (Schön, 1983) of the consultants added to the<br />

ambiguity. The ‘senior consultant’ was not familiar with the multiparty approach,<br />

promoted in the project. His colleague, who had made the initial design <strong>for</strong> the<br />

project, had transferred the project to the senior consultant because of his experiences<br />

in the domain of welfare. He clarified that he worked from the framework of conflict<br />

management and OD. For him the project was about aligning five different<br />

organizational cultures. He was reluctant to bring all stakeholders in a room, because<br />

of the difficulty to process the amount of in<strong>for</strong>mation and to find common ground. .<br />

He didn’t think it was helpful to put everything on the table. When interactions were<br />

tense he used bilateral contacts (‘shuttle diplomacy’). For instance, when t<strong>here</strong><br />

seemed to be disagreement around the organization of the first stakeholder<br />

conference, he asked the coordinator to call each of the five managers individually to<br />

‘take the temperature’ and to assess potential areas of disagreement. Some members<br />

of the project group experienced him as ‘too cautious’ and had the impression that<br />

the fundamental differences and hot issues could not be openly addressed.<br />

For the ‘facilitator’ the project was about changes in the domain of foster care as a<br />

system. He tried to promote stakeholder involvement and direct interaction between<br />

all parties. For him the most critical moment in the project was when the project<br />

group made a distinction between ‘internal’ and ‘external’ stakeholders and decided<br />

to focus on internal matters. He had pointed out that this choice would jeopardize<br />

197


the multi-stakeholder approach. He recalled that <strong>for</strong> him from that moment the<br />

project was no longer about foster care but about a reorganization of the services.<br />

“You work from a system perspective, but the system cannot be present!” (Facilitator, meeting<br />

project group 5)<br />

“We also have to look w<strong>here</strong> the input of the stakeholders influences the design of the process.”<br />

(Facilitator, meeting project group 7)<br />

“We say it is all about the children, but they are not <strong>here</strong>!” (Facilitator, stakeholder conference 1)<br />

The consulting team, as a microcosm, did not pay much attention to its own<br />

functioning, assumptions and learning. This seemed to reduce our effectiveness in<br />

the design and facilitation of the collaborative. Our internal differences mirrored a<br />

critical tension in the collaborative: the readiness to engage in an emergent, multi-<br />

stakeholder process with an unknown outcome, and the need <strong>for</strong> stability, control<br />

and predictability. The cautiousness and risk avoidance of the managers slowed<br />

down the process and they seemed to project these qualities on the consultants.<br />

The participants in this process needed to work in an ambiguous context, which was<br />

manifested in the starting conditions, the objectives, the roles of persons and<br />

subgroups, authority relations, and the assumptions about designing and facilitating<br />

a multi-stakeholder process. Ambiguity is an essential feature of such processes,<br />

because many issues cannot be clearly defined in advance. However, the ambiguous<br />

issues in this process were not thoroughly explored, negotiated or defined. This<br />

resulted in untested assumptions, confusion and defensive responses, hindering<br />

progress on the task.<br />

Issue 2: containment of the anxieties<br />

Most participants claimed that collaboration was necessary. They expressed motives<br />

such as a stronger impact on policy makers and judges, a more efficient use of<br />

resources, less shopping behavior, career opportunities <strong>for</strong> employees (e.g.<br />

specialization), a professional image, and higher chances of finding the optimal<br />

solution <strong>for</strong> the child. T<strong>here</strong> was tension between the intention to collaborate and the<br />

198


ambivalent emotional responses to the prospect of collaboration. The employees, <strong>for</strong><br />

instance, feared that working in a large, anonymous organization would lower the<br />

quality of assistance, creativity, diversity, motivation, and flexibility. They<br />

anticipated the loss of their job, their expertise, their identity, and established<br />

relationships. Collaboration, <strong>for</strong> them, implied they could no longer be ‘the best’.<br />

“T<strong>here</strong> is a <strong>for</strong>mal procedure. The quality is in the tailor made approach. (…) How can you then<br />

distinguish yourself? You want to make a difference. What if we collaborate more intensely? I<br />

don’t want to be stuck in routine. (…) I don’t want to give in too much, because I have been<br />

involved in developing our vision and procedure.” (Employee 2, interview)<br />

T<strong>here</strong> was external pressure on the managers to be ‘successful’. Policy makers<br />

expected a model <strong>for</strong> Flanders, the stakeholders in foster care had high hopes <strong>for</strong><br />

better solutions, and the other foster care services in Flanders were closely following<br />

the project because the results could have consequences <strong>for</strong> them. The managers<br />

were anxious about losing the identity and autonomy of their organizations. They<br />

were so preoccupied with their interpretation of the objective and intention of the<br />

project that the collaboration did not come off the ground (Huffington et al., 2004).<br />

They were afraid of conflict and did not want to endanger the collaborative<br />

relationships they had built over the last ten years. It often seemed as if talking about<br />

‘collaboration’ was a way to evade disagreement and discussion about the real<br />

differences.<br />

At the start some structures were established that contained the tensions in the<br />

process. The <strong>for</strong>mal terms of the contract (e.g. deadline) provided some landmarks.<br />

The ‘project’ was a transitional phenomenon (Winnicott, 1971) to deal with the<br />

anxiety of the change process that was much broader, fundamental, and longer than<br />

the scope of the project. Initially, the concept of a ‘reception function’ facilitated<br />

interaction around a shared theme; it served the function of a ‘transitional object’<br />

(Winnicott, 1971). The participants projected different fantasies on to the idea of a<br />

reception function (e.g. a ‘philosophical concept, a merger, a telephone line, a house,<br />

a strategic notion to obtain funding), but they never thoroughly explored the<br />

concept. The lack of a clear and shared primary task provoked tensions. As the<br />

199


process moved along it became obvious that the agenda of the convener was not<br />

shared by all and that the concept was too vague to mobilize energy.<br />

The relatively small project group and the presence of a facilitator provided<br />

containment and encouraged the managers to speak <strong>for</strong> their constituency and to talk<br />

about their concerns. The managers often used humor to reduce the tension and<br />

openly talked about their ‘anxiety’, ‘how a dream can turn into a nightmare’, and<br />

having ‘sleepless nights’. They were stunned by the boldness of their own ideas<br />

when they read them on paper. I did notice that the managers rarely shared and<br />

explored their feelings. At one point, <strong>for</strong> instance, the convener mentioned that<br />

maybe it would be interesting to reflect on their feelings and concerns, but this issue<br />

was not picked up by the group. Instead, they talked about the ‘resistance’ of their<br />

employees. Most meetings of the project group demonstrated an odd mixture of task<br />

orientation and off-task behavior. On the one hand the agenda was full, the meetings<br />

had to be ‘functional’ and timing was strict. T<strong>here</strong> was little time left <strong>for</strong> in<strong>for</strong>mal<br />

contact. On the other hand we were often surprised how difficult it was to keep the<br />

group focused on the agenda. Usually t<strong>here</strong> were lots of digressions, chatting about<br />

trivial subjects, and sometimes the meetings were chaotic. This seemed to serve the<br />

function of maintaining a good relationship, while at the same time it was used<br />

defensively. The members hardly used the time and space of the meetings as a<br />

‘potential space’ (Winnicott, 1971) w<strong>here</strong> they could explore their feelings and work<br />

them through, and engage in creative, playful experimentation and imagination of<br />

future scenarios without immediate binding consequences. Such ‘transitional spaces’<br />

facilitate change in emergent processes w<strong>here</strong> the outcome is uncertain (Amado &<br />

Ambrose, 2001; Amado & Vansina, 2005).<br />

The managers were surprised by the emotional responses of their staff to the project<br />

and established a minimal structure to contain the anxieties of their employees. They<br />

provided some guarantees (e.g. no job loss, no merger) and gave a clear mandate to<br />

the work groups (e.g. task, available time). The managers tried to be a model <strong>for</strong> their<br />

200


employees and talked about their personal dreams and worries and the struggle they<br />

were going through as ‘management group’.<br />

“The frame must be clear. Too many things are fuzzy now. I don’t feel good about that.”<br />

(Employee, interview)<br />

“You cannot know in advance w<strong>here</strong> you will end up, what the objective is. And when you<br />

start, you get overwhelmed with fears!” (Employee, stakeholder conference 3)<br />

The consultants made some procedural interventions to structure the process: a<br />

project plan with phases, reporting of meetings, a stakeholder analysis, and a<br />

structured representation of the critical issues. When tension was high the<br />

coordinator constructed an ‘objective’ overview of the differences and similarities<br />

between the services, based on their mission statements. Although this intervention<br />

was intended to contain the anxiety of discussing the differences between the<br />

services, some participants experienced it as a way to avoid direct interaction around<br />

difficult issues. The managers did not experience diversity as an added value or<br />

necessity <strong>for</strong> collaboration. During the preparation of the stakeholder conferences the<br />

managers made a difference between ‘internal’ and ‘external’ stakeholders. By<br />

excluding the external perspective they drifted away from the primary task. This<br />

decision, which was intended to reduce the complexity and tensions of the process,<br />

confronted the participants with new dilemmas. From that moment, the differences<br />

between the services came to the <strong>for</strong>eground. The ambivalence of the managers<br />

about collaboration was projected onto the liberal service. They were identified as<br />

‘difficult’ and became the scapegoat <strong>for</strong> the group. The ‘liberals’ stepped out,<br />

allegedly because of ‘ideological incompatibility’. The real reasons were not openly<br />

discussed. This ‘us and them’ dynamic further reduced the complexity,<br />

interdependence and diversity in the process.<br />

Towards the end of the project the process was <strong>for</strong>malized into ‘classic’<br />

organizational structures. Work groups were set up consisting of employees only.<br />

Their task was to work out solutions and propose them to ‘management’ (project<br />

group). This <strong>for</strong>malization maintained the hierarchical relationships between<br />

employees, managers, board members, and closed down the boundaries between<br />

201


internal and external stakeholders. On the one hand the work groups moved the<br />

project ahead, although t<strong>here</strong> was no clear intention or scenario <strong>for</strong> collaboration yet.<br />

On the other hand, this premature <strong>for</strong>malizing of the process closed off the process of<br />

exploration in the domain. The primary task had shifted from finding optimal<br />

solutions <strong>for</strong> the child and its environment to the intention to reorganize two<br />

procedures in four services, in the interest of organizational survival.<br />

A number of unintentional and deliberate facilitating structures and processes<br />

contained the anxiety in the process. However, the consultants and participants did<br />

not manage to establish conditions <strong>for</strong> a ‘transitional space’ to facilitate the change.<br />

T<strong>here</strong> was no <strong>for</strong>um w<strong>here</strong> the representatives of the domain could safely explore<br />

scenarios <strong>for</strong> the future of foster care. The direction of the domain was established by<br />

a restricted group of ‘internal’ stakeholders, who were locked in their positions.<br />

Issue 3: Inadequacy and failure<br />

As Mawson (1994) observed, in many work situations the main anxiety that needs to<br />

be contained is the experience of inadequacy. Parental failure to take care of a child is<br />

at the heart of foster care. The verdict of a judge to entrust a child to other people<br />

who will – temporarily – take over the parenting role is extremely hard <strong>for</strong> parents. It<br />

provokes feelings of inadequacy, shame, guilt, rivalry, and is a threat to the identity<br />

of the parents. The children and parents were not interviewed or invited to any<br />

meeting. The managers never gave us any names of children or parents <strong>for</strong> the<br />

interviews. The participants all ‘spoke <strong>for</strong>’ the child, as if the child did not have a<br />

voice of its own. The painful experiences of the foster child and the parents were shut<br />

out. The concerns <strong>for</strong> the child seemed to be displaced. It was striking, <strong>for</strong> instance,<br />

how the managers talked about board members ‘nurturing their child’, which<br />

referred to the ideology of the services. The four managers, all women, acted as<br />

protective mothers towards their employees.<br />

202


One of the motives to start the project was the failure of the services to take care of<br />

children in problematic home situations. Because potential candidate foster families<br />

were scarce, the managers feared that they, or the others, would lower their<br />

standards. This was morally unacceptable <strong>for</strong> them.<br />

“The project text states: each child that requests help should be placed in the family that<br />

provides the best fit. It is very crude, but in practice you try to couple the child with one of your<br />

own families.” (Manager 1, meeting project group 9)<br />

The issue of failure spilled over into the process. The convener and some of her<br />

colleagues had invested high hopes in the project. They were impatient and<br />

disappointed by the slowness of the process. They realized that organizational<br />

objectives were getting in the way. The managers did not succeed within the time<br />

frame of the project, to produce the expected results and to move beyond<br />

collaboration in safe domains, which they had been trying to do <strong>for</strong> so long.<br />

“The power of collaboration is the concern <strong>for</strong> the child, parents and foster parents and not the<br />

concern to maintain your organization” (Board member 2, interview)<br />

My sense of the relationship between the consulting team and the system was that<br />

the consultants were doing the work and that both sides were frustrated. It was as if<br />

the managers projected their negative experiences of failure and inadequacy onto the<br />

consultants. The call <strong>for</strong> process facilitation was like a plea from the managers to take<br />

care of them. It was as if both the managers and the consultants experienced the<br />

anxiety of a ‘parentless’ process. As the process moved along, the senior consultant<br />

started to over-function and to ‘take care’ of the managers. He accompanied them,<br />

<strong>for</strong> instance, to negotiations with policy makers about the follow-up of the project.<br />

The consultants were gradually drawn in a collusive relationship with the<br />

participants. They went along with some decisions made by the managers that<br />

moved the process away from the primary task. For instance, we did not emphasize<br />

the need to explore the problem be<strong>for</strong>e talking about solutions. We let the convener<br />

push her idea of a reception function. We did not sufficiently stress the necessity to<br />

include the voice of the children and parents. We did not clearly challenge the<br />

203


decision to focus on ‘internal matters’. Most stakeholders had claimed that the<br />

subsidizing system was the principal obstacle to collaboration, but we did not<br />

intervene when policy makers were not actively involved as critical stakeholder in<br />

the process. These examples demonstrate that the consultants colluded with the<br />

system at several moments.<br />

It seems important to address painful issues and experiences, because they are<br />

expressed in the system in different ways. Working through these issues can bring<br />

the participants closer to the core of their work and to the primary task they<br />

collectively need to work on. Those facilitating a collaborative process should watch<br />

the risk of being drawn into the system.<br />

Conclusion<br />

This paper demonstrates how the psychodynamic perspective can be adopted as the<br />

organizing principle in organizational research. It shows how an organizational<br />

researcher can use subjective experiences as additional data to tap into the<br />

underlying dynamics in the system. The dynamics in the action research were<br />

analyzed by taking into account subjective data, observations, as well as the context<br />

and history of the collaborative and its partners. The dynamics in the consulting<br />

team, the relationship between consultants and the system, and parallel dynamics in<br />

the system were discussed. The analysis emphasizes some defensive dynamics that<br />

hindered task oriented work, such as exclusion of ‘external’ stakeholders,<br />

scapegoating of a reluctant partner, and avoiding to deal with an important obstacle<br />

to collaboration in the context. This approach resulted in a rich and contextualized<br />

narrative of a dynamic process in its natural setting. The case analysis documents<br />

how the consultants were absorbed in the system and how small events resulted in a<br />

drift away from the primary task that was experienced as too threatening.<br />

Making sense of the inevitable tensions and conflicts is at the heart of collaborative<br />

work (Cooper & Dartington, 2004). From a psychodynamic perspective the role of a<br />

204


facilitator in a change process is to be a ‘com<strong>for</strong>ter’ and to – temporarily – contain the<br />

anxieties stirred up by the uncertainty and ambiguity of the process (Amado &<br />

Ambrose, 2001). A facilitator helps participants to adapt the rational knowing and<br />

emotional feelings to the emergent situation (Vansina, 2004). The ambiguous starting<br />

conditions, the contested role and implicit differences in assumptions of the<br />

consultants, dynamics of splitting and premature <strong>for</strong>malizing of the process, and the<br />

collusive relationship with the system, resulted in poor containment of the anxieties<br />

stirred up in the process. T<strong>here</strong><strong>for</strong>e it was hard to develop a shared task and to<br />

establish common ground. This case demonstrates that in the unfolding process of<br />

collaborative work, both participants and consultants needed to learn to ‘live with<br />

the mess’ and with the emergence of the process. The challenge in new <strong>for</strong>ms of<br />

organizing, characterized by fluidity, emergence and interdependence, is to develop<br />

new containing practices that enable anxiety and conflicts to be contained and<br />

worked through (Huffington et al., 2004). Other cross-functional, cross-disciplinary,<br />

and inter-organizational processes of organizing are confronted with similar<br />

challenges.<br />

The psychodynamic perspective provides additional insight in the study of what<br />

actually happens in an emergent organizational process, both on the manifest and<br />

latent level, and how subjectivity is expressed in the process. Addressing the<br />

underlying <strong>for</strong>ces also provides a deeper understanding of the dynamics that operate<br />

in the construction of the research environment (Clarke, 2002). The psychodynamic<br />

perspective offers insight in the phenomenon of 'collaborative inertia', or the<br />

observation that the output of collaborations is often slowed down or below the<br />

expectations (Huxham, 1996). This perspective makes us more aware of the<br />

emotional challenges of developing an environment <strong>for</strong> collaboration, defensive<br />

dynamics, and the facilitating conditions required <strong>for</strong> productive collaborative work<br />

(Gould et al., 1999; Long, Newton & Dalgleish, 2000; Page, 2003; Ring & Van de Ven,<br />

1994). Because the psychodynamic perspective also operates ‘below the surface’, its<br />

main contribution is a better understanding of the paradox between the intention<br />

and societal necessity <strong>for</strong> creative collaboration, and the emotional and defensive<br />

205


esponses when participants are confronted with the dilemmas and ambiguity of<br />

emergent collaborative processes.<br />

References<br />

Amado, G. & Ambrose, A. (Eds.) (2001). The transitional approach to change. London:<br />

Karnac.<br />

Amado, G. & Vansina, L. (Eds.) (2005). The Transitional approach in action. London:<br />

Karnac.<br />

Anderson, D. & White, J.D. (2000). Psychoanalytic organizational theory: Comparative and<br />

philosophical perspectives. Paper presented at the 13th Conference of the Public<br />

Administration Theory Network, Fort Lauderdale, January.<br />

Berg, D.N. (1988). Anxiety in the research relationships. In Berg, D.N. & Smith, K.K.<br />

(Eds.), The self in social inquiry. Researching methods (pp. 213-228). Newbury Park:<br />

Sage Publications.<br />

Berg, D.N. & Smith, K.K. (1988). The clinical demands of research methods. In Berg,<br />

D.N. & Smith, K.K. (Eds.), The self in social inquiry. Researching methods (pp. 21-34).<br />

Newbury Park: Sage Publications.<br />

Bion, W.R. (1970). Attention and interpretation. London: Karnac Books.<br />

Bradbury, H. & Bergmann Lichtenstein, B.M. (2000). Relationality in organizational<br />

research: exploring the space between. Organization Science, 11 (5), September-<br />

October, 551-564.<br />

Chisholm, R. & Elden, M. (1993). Features of emerging action research. Human<br />

Relations, 46 (2), 275-297.<br />

Clarke, S. (2002). Learning from experience: psycho-social research methods in the<br />

social sciences. Qualitative Research, 2 (2), 173-194.<br />

Cooper, A. & Dartington, T. (2004). The vanishing organization: Organizational<br />

containment in a networked world. In Huffington, C., Armstrong, D., Halton, W.,<br />

Hoyle, L. & Pooley, J.( Eds.), Working below the surface. The emotional life of<br />

contemporary organizations (pp. 127-150). London: Karnac.<br />

Czander, W.M. (1993). The psychodynamics of work and organizations. Theory and<br />

application. New York: Guil<strong>for</strong>d Press.<br />

Dawson, P. (1997). In at the deep end: Conducting processual research on<br />

organisational change. Scandinavian Journal of Management, 13 (4), 389-405.<br />

Devereux, G. (1967). From anxiety to method in the behavioral sciences. The Hague:<br />

Mouton & Co.<br />

206


Diamond, M. & Allcorn, S. (2003). The cornerstone of psychoanalytic organizational<br />

analysis: Psychological reality, transference and counter transference in the<br />

workplace. Human Relations, 56 (4), 491-514.<br />

Driver, M. (2003). Nothing clinical, just business? Reflections on psychoanalytically<br />

grounded organizational diagnosis and intervention. Human Relations, 56 (1), 39-59.<br />

Edelson, M. (1988). The hermeneutic turn and the single case study in psychoanalysis.<br />

In Berg, D.N. & Smith, K.K. (Eds.), The self in social inquiry. Researching methods (pp.<br />

71-104). Newbury Park, Cali<strong>for</strong>nia: Sage Publications.<br />

Eden, C. & Huxham, C. (1996). Action research <strong>for</strong> the study of organizations. In Clegg,<br />

S.R., Hardy, C. & Nord, W.R. (Eds.), Handbook of organization studies (pp. 526-542).<br />

London: Sage.<br />

Eisenhardt, K.M. (1989). Building theories from case study research. Academy of<br />

Management Review, 14 (4), 532-550.<br />

Feyerherm, A., (1997) Leading M.E.N.: Perspectives on leadership in multistakeholder<br />

environmental negotiations. Paper presented at the Academy of Management, Boston.<br />

Flick, U. (2002). An introduction to qualitative research. Second Edition. London: Sage.<br />

Gabriel, Y. (Ed.) (1999). Organizations in depth. The psychoanalysis of organizations.<br />

London: Sage.<br />

Gardner, M.R. (1989). Self inquiry. Hillsdale: The Analytic Press.<br />

Geertz, C. (1973). The interpretation of cultures. New York: Basic Books.<br />

Gilmore, T.N. & Krantz, J. (1985). Projective identification in the consulting<br />

relationship: Exploring the unconscious dimensions of a client system. Human<br />

Relations, 38 (12), 1159-1177.<br />

Gould, L. (1991). Using psychoanalytic frameworks <strong>for</strong> organizational analysis. In Kets<br />

de Vries, M. (Ed.), Organizations on the couch; Clinical perspectives on organizational<br />

behavior and change (pp. 25-44). San Francisco: Jossey-Bass.<br />

Gould, L.J., Ebers, R. & Mc Vicker Clinchy, R. (1999). The systems psychodynamics of a<br />

joint venture: Anxiety, social defenses and the management of mutual dependence.<br />

Human Relations, 52 (6), 697-722.<br />

Gould, L.G., Stapley, L.F. & Stein, M. (Eds.) (2001). The systems psychodynamics of<br />

organizations. Integrating the group relations approach, psychoanalytic, and open systems<br />

perspectives. London: Karnac.<br />

Gray, B. (1989). Collaborating: finding common ground <strong>for</strong> multiparty problems. San<br />

Francisco: Jossey Bass.<br />

207


Halton, W. (1994). Some unconscious aspects of organizational life: Contributions from<br />

psychoanalysis. In Obholzer, A. & Zagier Roberts, V. (Eds.), The unconscious at work<br />

(pp. 11-18). Routledge: London.<br />

Heller, F. (2004). Action research and research action: A family of methods. In Cassell,<br />

C. & Symon, G. (Eds.), Essential guide to qualitative methods in organizational research<br />

(pp. 349-360). London: Sage.<br />

Hirschhorn, L. (1997). Reworking authority. Leading and following in the post-modern<br />

organization. Cambridge Massachusetts: The MIT Press.<br />

Hirschhorn, L. & Gilmore, T. (1992). The new boundaries of the “boundaryless”<br />

company. Harvard Business Review, May/June, 70 (3), 104-115.<br />

Hollway, W. & Jefferson, T. (2000). Doing qualitative research differently: Free association,<br />

narrative and the interview method. London: Sage.<br />

Huberman, A.M. & Miles, M.B. (1988). Assessing local causality in qualitative research.<br />

In Berg, D.N. & Smith, K.K. (Eds.), The self in social inquiry. Researching methods (pp.<br />

351-381). Newbury Park, Cali<strong>for</strong>nia: Sage Publications.<br />

Huffington, C. & James, K. (1999). Issues in management research, and the value of a<br />

psychoanalytic perspective: A case study in organisational stress in a Japanese multinational<br />

company. Paper presented at the International Society <strong>for</strong> the<br />

Psychoanalytic Study of Organizations Symposium, June.<br />

Huffington, C., Armstrong, D., Halton, W., Hoyle, L. & Pooley, J.( Eds.) (2004). Working<br />

below the surface. The emotional life of contemporary organizations. London: Karnac.<br />

Huffington, C., James, K. & Armstrong, D. (2004). What is the emotional cost of<br />

distributed leadership? In Huffington, C., Armstrong, D., Halton, W., Hoyle, L. &<br />

Pooley, J.( Eds.), Working below the surface. The emotional life of contemporary<br />

organizations (pp. 67-82). London: Karnac.<br />

Hunt, J. (1989). Psychoanalytic aspects of fieldwork. Qualitative Research Methods.<br />

Volume 18. London: Sage.<br />

Huxham, C. (Ed.) (1996). Creating collaborative advantage. London: Sage Publications.<br />

Huxham, C. & Vangen, S. (2000). Leadership in the shaping and implementation of<br />

collaboration agendas: How things happen in a (not quite) joined-up world.<br />

Academy of Management Journal, 43, (6), 1159-1175.<br />

Huxham, C. & Vangen, S. (2005). Managing to collaborate. The theory and practice of<br />

collaborative advantage. London: Routledge.<br />

Kets de Vries (Ed.) (1991). Organizations on the couch. Clinical perspectives on<br />

organizational behavior and change. San Francisco: Jossey-Bass.<br />

Klein, L. (1976). A social scientists in industry. Epping, Essex: Gower Press.<br />

208


Krantz, J. (1990). Lessons from the field: An essay on the crisis of leadership in<br />

contemporary organizations. The Journal of Applied Behavioral Science, 26, (1), 49-64.<br />

Krantz, J. (1998). Anxiety & the New Order. In Klein, B. & Gabelnick, F. & Herr, P.<br />

(Eds.), The psychodynamics of leadership (pp. 77-107). Madison: Psychosocial Press.<br />

Langley, A. (1999). Strategies <strong>for</strong> theorizing from process data. Academy of Management<br />

Review, 24 (4), 691-710.<br />

Lapierre, L. (1991). Exploring the dynamics of leadership. In Kets de Vries (Ed.)<br />

Organizations on the couch. Clinical perspectives on organizational behavior and change<br />

(pp. 69-93). San Francisco: Jossey-Bass.<br />

Levinson, H. (1991). Diagnosing organizations systematically. In Kets de Vries (Ed.),<br />

Organizations on the couch. Clinical perspectives on organizational behavior and change<br />

(pp. 45-68). San Francisco: Jossey-Bass.<br />

Long, S., Newton, J. & Dalgleish, J. (2000). In the presence of the other: Developing<br />

working relations <strong>for</strong> organizational learning. In Klein, E.B., Gabelnick, F. & Herr,<br />

P. (Eds.), Dynamic consultation in a changing workplace (pp. 161-192). Madison,<br />

Connecticut: Psychosocial Press.<br />

Mawson, C. (1994). Containing anxiety in work with damaged children. In Obholzer,<br />

A. & Roberts, V. (Eds.), The unconscious at work. Individual and organizational stress in<br />

the human services (pp. 67-74). London: Routledge.<br />

Meek, H.W. (2003). The place of the unconscious in qualitative research. Forum<br />

Qualitative Social Research, 4 (2), May.<br />

Menzies, I. E. P. (1960). A case study in the functioning of social systems as a defense<br />

against anxiety. Human Relations, 13, 95-121.<br />

Miller, E. (1997). Effecting organisational change in large complex systems: A<br />

collaborative consultancy approach. In Neumann, J.E., Kellner, K. & Dawson-<br />

Sheperd, A. (Eds.), Developing organisational consultancy (pp. 187-212). Routledge:<br />

London.<br />

Neumann, J. & Hirschhorn, L. (1999). The challenge of integrating psychodynamic and<br />

organizational theory. Human Relations, 52 (6), 683-695.<br />

Obholzer, A. (1999). Managing the unconscious at work. In French, R. & Vince, R.<br />

(Eds.), Group relations, management and organization (pp. 87-97). Ox<strong>for</strong>d: University<br />

Press.<br />

Page, M. (2003). Leadership and collaboration challenges in not <strong>for</strong> profit partnerships.<br />

Organisational and Social Dynamics, 3 (2), 207-225.<br />

Patton, M.Q. (1987). Qualitative Evaluation Methods. London: Sage.<br />

209


Pettigrew, A.M. (1997). What is processual analysis? Scandinavian Journal of<br />

Management, 13 (4), 337-348.<br />

Prins, S., Craps, M. & Taillieu, T. (2006). Boundary dynamics in natural resource<br />

management: The ambiguity of stakeholder inclusion. Revue Gouvernance, 2 (2),<br />

January, 2-11.<br />

Reik, T. (1948). Listening with the third ear. The inner experience of a psychoanalyst. New<br />

York: Grove Press.<br />

Ring, P.S. & Van de Ven, A.H. (1994). Developmental processes of cooperative<br />

interorganizational relationships. Academy of Management Review, 19 (1), 90-118.<br />

Schein, E.H. (1987). The clinical perspective in fieldwork. Newbury Park: Sage.<br />

Schön, D. A. (1983). The reflective practitioner. How professionals think in action. New York:<br />

Basic Books.<br />

Schonberg, A. (1998). Two basic assumptions in the psychoanalytic study of organizations.<br />

Paper presented at the International Society <strong>for</strong> the Psychoanalytic Study of<br />

Organizations Symposium, June.<br />

Schwandt, T.A. (1998). Constructivist, interpretivist approaches to human inquiry. In<br />

Denzin, N.K. & Lincoln, Y.S. (Eds.), The landscape of qualitative research. Theories and<br />

issues (pp. 221-259). London: Sage.<br />

Schwartzman, H.B. (1993). Ethnography in organizations. Qualitative Research Methods,<br />

volume 27. Newbury Park: Sage.<br />

Shapiro, E.R. & Carr, A.W. (1991). Lost in familiar places. Creating new connections between<br />

the individual and society. New Haven: Yale University Press.<br />

Smith, K.K. (1995). On using the self as instrument. Lessons from a facilitator's<br />

experience. In Gillette, J & McCollom, M. (Eds.), Groups in context. A new perspective<br />

on group dynamics (pp. 276-294). Lanham: University Press of America.<br />

Spradley, J. (1980). Participant observation. New York: Holt, Rinehart & Winston.<br />

Strauss, A. & Corbin, J. (1998). The basics of qualitative research: techniques and procedures<br />

<strong>for</strong> developing grounded theory. Thousand Oaks, Cali<strong>for</strong>nia: Sage.<br />

Trist, E. & Murray, H. (1990). (Eds.) The social engagement of the social science. Volume 1:<br />

the socio-psychological perspective. London: Free Associations Books.<br />

Van de Ven, A.H. & Poole, M.S. (2005). Alternative approaches <strong>for</strong> studying<br />

organizational change. Organization Studies, 26 (9), 1377-1404.<br />

Van Maanen, J. (1988). Tales of the field: On writing ethnography. Chicago: University of<br />

Chicago Press.<br />

210


Van Manen, M. (1990) Researching lived experience: human science <strong>for</strong> an action sensitive<br />

pedagogy. London: Althouse.<br />

Vansina, L. (2000). The relevance and perversity of psychodynamic interventions in<br />

consulting and action research. Concepts and Trans<strong>for</strong>mation, 5 (3), 53-80.<br />

Vansina, L. (2004). Over zin en onzin van psychodynamiek voor organisatieadviseurs.<br />

In Varwijk, W. & R. van Zijl (Eds.), Strategie moet je samen doen. Visies op strategisch<br />

management uit theorie en praktijk (pp. 159-177). Ubbergen: Tandem Felix.<br />

Vansina-Cobbaert, M.J. (2005). A therapeutic community: A space <strong>for</strong> multiple<br />

transitional change. In Amado, G. & Vansina, L. (Eds.), The transitional approach in<br />

action (pp. 41-70). London: Karnac.<br />

Winnicott, D.W. (1971). Playing and reality. London: Routledge.<br />

Yin, R.K. (1994). Case study research. Design and methods. Second Edition. Thousand Oaks,<br />

Cali<strong>for</strong>nia: Sage Publications.<br />

211


FROM COMPETITION TO COLLABORATION: DYNAMICS OF DIRECTION<br />

SETTING IN MULTIPARTY COLLABORATION (ARTICLE 4)<br />

Silvia Prins & Tharsi Taillieu<br />

“Foster care is, in its method and essence, about making connections around the child, the foster<br />

parents and the parents. So the issue of connection is critical in our organizations and in this<br />

process.” (A manager of a foster care organization, interview)<br />

Introduction<br />

The aim of this paper is to understand how a collaborative, multi-stakeholder<br />

process gradually shifted away from its original intention. The paper begins with an<br />

outline of the organizational framework of multiparty collaboration. Then it<br />

discusses how the systems psychodynamic perspective can provide an<br />

understanding of how people deal with tensions that inevitably arise in collaborative<br />

work. The paper discusses a case study in the domain of foster care w<strong>here</strong> five<br />

independent organizations set out to develop structural collaboration. The case<br />

analysis draws attention to three issues with which the participants were struggling<br />

and the dynamics that emerged around those issues. The aim of the paper is to<br />

understand how these dynamics set the direction of the process and gradually<br />

moved it away from a stakeholder approach focused on the domain of foster care to<br />

an internal focus on the individual organizations.<br />

Conceptual background<br />

Multiparty collaboration: the challenges of direction setting<br />

Multiparty collaboration is “(…) a process through which parties who see different aspects<br />

of a problem can constructively explore their differences and search <strong>for</strong> solutions that go<br />

beyond their own limited vision of what is possible” (Gray, 1989, 5). The parties come<br />

together precisely because of their membership in other organizations or groups<br />

(Zagier Roberts, 1994). Stakeholders have vested interests in the domain and differ in<br />

perspective, in<strong>for</strong>mation, power and resources. T<strong>here</strong><strong>for</strong>e inter-group characteristics<br />

212


are predominant in collaborative work (Vansina, Taillieu & Schruijer, 1998).<br />

Stakeholders are compelled to collaborate, because incremental or bilateral ef<strong>for</strong>ts do<br />

not produce satisfactory results. The diversity of perspectives is essential to establish<br />

a comprehensive definition of the problem and to develop optimal, sustainable<br />

solutions that are widely supported. Gray (1989) distinguishes five characteristics of<br />

a collaborative: (1) the stakeholders in the domain are interdependent; (2) solutions<br />

emerge by dealing constructively with differences; (3) joint ownership of decisions is<br />

involved; (4) stakeholders assume collective responsibility <strong>for</strong> the future direction of<br />

the domain; and (5) collaboration is an ‘emergent process’. This paper illustrates how<br />

participants in a collaborative struggle with these issues.<br />

A particular challenge of collaborative work is how to define ‘leadership’ in a setting<br />

w<strong>here</strong> hierarchy is not a valid organizing principle. Traditional models of leadership<br />

are not suitable <strong>for</strong> the collaborative context and literature on leading and convening<br />

often overlaps. Leadership is emergent and in<strong>for</strong>mal and it is often shared by those<br />

involved (Huxham & Vangen, 2000). Because these concepts do not provide a<br />

satisfactory basis <strong>for</strong> understanding how the direction of a collaborative is set, this<br />

study focuses on ‘dynamics of direction setting’. This perspective is inspired by<br />

Feyerherm’s (1997, 1) definition of leaders as the persons “who influence the course of<br />

events, the ways issues get framed and resolved, and the people who influence the outcomes of<br />

the gathering”. Attempts at influencing the direction and outcome are particularly<br />

relevant when the authority structure is ambiguous, such as in a collaborative. In<br />

order to make sense of these dynamics I adopt the system psychodynamic<br />

perspective.<br />

The system psychodynamic perspective: understanding collaborative dynamics<br />

From the system psychodynamic perspective (Obholzer & Zagier Roberts, 1994;<br />

Gould, Stapley & Stein, 2001; Huffington, Armstrong, Halton, Hoyle & Pooley, 2004)<br />

working in a collaborative is influenced by conscious as well as by hidden and<br />

unconscious motives. The assumption is that in an inter-organizational context<br />

213


groups share collective, unconscious assumptions about other relevant groups which<br />

are manifested in conscious and unconscious processes (e.g. stereotyping). These<br />

assumptions influence the quality of the inter-group relationships (Gould, Ebers &<br />

Clinchy, 1999).<br />

Participants in a collaborative are confronted with different sources of anxiety that<br />

stem from the context, the nature of the collaborative process, and the relationships<br />

with other stakeholders in the domain. The organizational context is often<br />

ambiguous, turbulent and complex. Representatives have to adapt to the changing<br />

opportunities and restrictions in the environment. External events, such as a change<br />

in policy, can have a profound effect on the collaborative. The collaborative process<br />

is emergent and the outcome is unknown. A collaborative is often under-organized<br />

and t<strong>here</strong> are few containing structures and processes because these cannot be<br />

established in advance (e.g. task, roles, membership). ‘Psychological boundaries’ are<br />

experienced and enacted in the interactions among representatives. They relate, <strong>for</strong><br />

instance, to authority (who is in charge of what?) and identity (who is - and who is<br />

not - 'us') (Hirschhorn & Gilmore, 1992). The requirement to develop collaborative<br />

relationships confronts representatives with mutual dependency, diversity, the<br />

potential <strong>for</strong> conflict, and asymmetries between the parties. They have to deal with<br />

challenges to their identity (e.g. fear to lose one’s identity, to be excluded) and to<br />

their autonomy. These anxieties may provoke defensive responses. The pioneering<br />

work of Menzies (1960) on social defenses, has demonstrated that unconscious<br />

anxieties are often reflected in organizational structure and design, which function to<br />

defend against the uncontained anxieties in the workplace. According to Krantz<br />

(1998) the social defense theory is more relevant than ever. Multiparty collaboration<br />

as a new way of organizing requires new social defenses in order to balance the<br />

needs of the individuals, groups and organizations. In case analysis I emphasize the<br />

following phenomena. (1) The response of participants to issues or dilemmas that<br />

provoke tensions. (2) The relationship between task, relationships and system<br />

features: how the characteristics of the organizational context provoke particular<br />

dynamics and how these dynamics in turn shape the organizational context.<br />

214


The aim of this in-depth case study was to explore the way in which direction was<br />

established. It discusses how the participants made sense of the collaborative<br />

experience, both individually (accounts) and collectively (participative observation).<br />

The research was designed to capture the variety of perspectives, the complexity and<br />

the ambiguity of the subject (Langley, 1999). It focuses on the emergent process<br />

embedded in a context over time (Pettigrew, 1997; Dawson, 1997; Heller, 2004). I<br />

constructed a narrative account of a process of organizing “by narrating emergent<br />

actions and activities by which collective endeavors unfold” (Van de Ven & Poole, 2005).<br />

My aim was to arrive at an understanding (‘Verstehen’) of the phenomena in their<br />

complexity, wholeness and uniqueness, rather than to explain or predict them<br />

(Edelson, 1988). To avoid the risk of ‘psychological reductionism’ I included the<br />

history, context and system features of the collaborative (Pettigrew, 1997; Schonberg,<br />

1998; Neumann & Hirschhorn, 1999). The case study provides a rich and<br />

contextualized understanding of a collaborative process and constructs a ‘thick’<br />

description’ of meaning (Geertz, 1973). The insights are grounded in empirical data<br />

and the challenge of this paper is to provide a conceptualization that is potentially<br />

relevant <strong>for</strong> similar contexts (Chisholm & Elden, 1993; Eden & Huxham, 1996).<br />

The case: issues in direction setting<br />

The domain of foster care and antecedents of the project<br />

The case study is based on a project in the domain of foster care <strong>for</strong> children in a<br />

region in Flanders (Belgium). A foster family (temporarily) provides a safe family<br />

environment <strong>for</strong> children who cannot live at home. Most placements are the result of<br />

a decision by the juvenile court (‘mandatory’) or the Committee <strong>for</strong> special youth<br />

assistance (‘voluntary’). A small proportion of the placements (10%) are organized by<br />

private arrangement. The foster care services, the central organizations in this<br />

project, are private agencies under authorization of and subsidized by the Flemish<br />

Community. Their tasks are: recruitment, screening and training of foster families;<br />

matching the child to the foster family; monitoring of the placement situation;<br />

215


assisting the child and the foster parents; providing assistance to the parents. Each<br />

region counts several foster care services. The institutional landscape of foster care is<br />

intricate. The Federation <strong>for</strong> foster care represents all the services in Flanders. T<strong>here</strong><br />

are four subsidizing sectors: Special Youth Care (<strong>for</strong>ced or voluntary placement of<br />

children in a problematic situation), Care <strong>for</strong> the Handicapped, Mental Health<br />

(community psychiatry), and Child and Family (prevention). Each sector follows its<br />

rules and regulations. The domain of foster care is also characterized by differences<br />

in ideology (catholic, pluralistic, liberal) which are reflected, <strong>for</strong> instance, in the<br />

plat<strong>for</strong>ms representing employers’ interests.<br />

Several evolutions in the domain inspired practitioners to start a project. The foster<br />

care services were confronted with a lack of candidate families to take care of the<br />

increasing number of children eligible <strong>for</strong> foster care (1998-2002: 20% increase).<br />

Moreover, the problem situations around the child had become more severe and<br />

complicated due to, <strong>for</strong> instance, a growing number of divorces of both natural and<br />

foster parents. This required more specialized assistance and increased the number<br />

of players to be involved. The services were partly aware of how the field perceived<br />

them: a negative image, an unclear profile, a small player in welfare, an unknown<br />

offer, and no transparent or effective coordination of assistance. It frequently<br />

happened, <strong>for</strong> instance, that social workers asked three services at the same time to<br />

look <strong>for</strong> a family. Sometimes families or relegating parties played the services off<br />

against each other. This way of functioning led to a waste of time, energy and<br />

resources.<br />

The welfare policy moved towards a regional organization of services and an<br />

integrated approach of assistance. Foster care, as a small and separate sector, was<br />

seriously questioned. This implied a need to align with other <strong>for</strong>ms of assistance (e.g.<br />

mixed <strong>for</strong>ms), to develop a more varied offer, and to specialize. The environment<br />

was turbulent (e.g. a project to integrate assistance <strong>for</strong> children and adolescents). The<br />

foster care services realized that an imposed merger was likely. This was an<br />

important trigger to take an initiative. According to the managers of the services the<br />

216


subsidizing mechanism in foster care was the critical obstacle to collaboration.<br />

Subsidies were based on the number of placements organized by a service and were<br />

granted after placement of a child in a foster family. The managers realized they<br />

were competing <strong>for</strong> resources and clients.<br />

“The foster care services feel the need to collaborate in order to arrive at a more qualitative,<br />

differentiated and efficient offer that can respond to the multiple kinds of requests <strong>for</strong><br />

assistance. The competitive position, due to a survival reflex on the shrinking market of<br />

candidate foster families, and the present policy, make an effective collaboration very hard”<br />

(Project proposal).<br />

“We are all fishing in the same pond. (…) We have to change the subsidizing system because it<br />

provokes competition.” (Manager 4, meeting project group 2, January 2004)<br />

“You cannot grow too much, because it is always at the cost of another service.” (Manager 2,<br />

stakeholder interview)<br />

“The project text states: each child that requests help should be placed in the family that<br />

provides the best fit. It is very crude, but in practice you try to couple the child with one of your<br />

own families.” (Manager 1, meeting project group 9, July 2004)<br />

“It’s a perverse system.” (Manager 1, stakeholder interview)<br />

The story: the bumpy road to collaboration<br />

The convener, a manager of a foster care service, asked our Center to help her to<br />

develop a ‘network organization’. The convener wished to respond proactively to the<br />

changes in welfare policy. Her experiences as foster mother, as coach of foster<br />

families, and now as manager had convinced her that collaboration would lead to a<br />

‘higher quality in foster care’. For her, this referred to the ability to offer a broad<br />

variety of tailor made <strong>for</strong>ms of assistance, and to an optimization of efficiency and<br />

effectiveness of assistance by bringing together the know-how and resources of<br />

different services. She wrote a project proposal and contacted our Centre. In<br />

consultation with the convener, the project was designed in a multi-stakeholder<br />

perspective. The project was a ‘pilot’ and the idea was that the experiences and<br />

results could be used as a model <strong>for</strong> Flanders. The <strong>for</strong>mal objectives of the project<br />

were: (1) develop a structural basis <strong>for</strong> collaboration among foster care services in<br />

one region; (2) develop a concept <strong>for</strong> a ‘reception function’ <strong>for</strong> foster care. A year<br />

after submitting the project, funding was unexpectedly approved.<br />

“The project is an ‘accident de parcours’. It started because of a conjunction of circumstances.”<br />

(Head Federation, interview)<br />

217


A consultant team of four, of which I was part, was hired to coordinate and facilitate<br />

the process in an action research perspective. My task was documentation of the<br />

process. I observed meetings, made field notes and also actively participated in the<br />

project. This position allowed me to find a balance between closeness and distance, in<br />

order to ‘sit on the boundary' (Smith, 1995). My primary aim was discovery and<br />

learning from the collaborative experience, w<strong>here</strong>as the main aim of my colleagues<br />

was to support the participants to pursue their objectives. To arrive at an in-depth<br />

understanding of the emergent organizing process I used data triangulation (Yin,<br />

1994; Flick, 2002). At the start of the project I interviewed 34 stakeholder<br />

representatives, together with my colleague, to assess the perceptions of foster care in<br />

the domain. We presented an overview of the issues and discussed our feedback<br />

with the participants. Their comments were included as data (Huberman & Miles,<br />

1988). After the project I interviewed the nine members of the project group to assess<br />

the critical events in the process. I systematically made field notes of meetings of the<br />

project group (13), the internal meetings of the consultants (13), and the stakeholder<br />

conferences (3 days). I kept track of my personal experiences and feelings in<br />

journalizing notes.<br />

During a meeting of the Federation the convening organization and three other<br />

services volunteered <strong>for</strong> the project. Ten years ago they had set up a ‘regional<br />

consultation plat<strong>for</strong>m’, they had established a list of basic principles (e.g. a candidate<br />

foster family can only be involved in a selection procedure in one service at a time),<br />

and collaborated in ‘safe domains’ (e.g. organization of annual ‘foster care week’). In<br />

the case discussion we will see that moving beyond those ‘safe domains’ proved to<br />

be very difficult. The fifth service operating in the region, of liberal inspiration, was<br />

not present at the Federation. A few days later, they agreed to join.<br />

“We were contacted en we had two or three days to decide. When you read the project you<br />

cannot but agree. You were all much further in making it concrete than we were at the moment<br />

we stepped in.” (Manager 5, meeting project group 9)<br />

A ‘project group’ (see table 11, article 3) was set up and met on a monthly basis. This<br />

group was the main vehicle <strong>for</strong> collaboration and I assumed it was the plat<strong>for</strong>m<br />

218


w<strong>here</strong> the dynamics of the system were played out. From the multi-stakeholder<br />

perspective, foster care is an inter-organizational domain (Trist, 1983) with<br />

interdependent stakeholders. Accordingly, the project group identified a wide group<br />

of stakeholder representatives in foster care <strong>for</strong> interviewing. Together with my<br />

colleague, I spent two months interviewing. We constructed a diagnosis of the<br />

important issues in the domain of foster care. Based on discussion of our feedback<br />

the project group designed a ‘stakeholder conference’. This provided a <strong>for</strong>um <strong>for</strong><br />

direct interaction among the ‘internal’ stakeholders (employees, managers and<br />

boards of the services). The ‘external’ stakeholders were only invited in the morning.<br />

The internal stakeholders decided to focus on internal matters first and continued<br />

their discussions at a second stakeholder conference w<strong>here</strong> they set up work groups.<br />

Over a period of three months two groups of employees worked around specific<br />

organizational procedures: inflow of children and selection of foster parents.<br />

In parallel, ten months after the start of the project, the project group organized a<br />

meeting with the board members. They wanted to reach an agreement in principle on<br />

collaboration. During this meeting, the liberal service stepped out of the project. As<br />

t<strong>here</strong> were only two months left be<strong>for</strong>e the deadline, the project group tried to<br />

achieve some concrete results <strong>for</strong> the final stakeholder conference. The managers<br />

talked about potential scenarios <strong>for</strong> the future, conditions <strong>for</strong> collaboration, and<br />

looked <strong>for</strong> additional funding. They invited the external stakeholders <strong>for</strong> the final<br />

part of the third stakeholder conference. As t<strong>here</strong> was no clear scenario <strong>for</strong> future<br />

collaboration, the work groups and managers shared their experiences, ideas and<br />

learning. The project had an open end since t<strong>here</strong> was no certainty at that point if<br />

t<strong>here</strong> would be additional funding to continue the process.<br />

Sense making of the dynamics: drifting away from the inter-organizational domain<br />

In order to make sense of the dynamics, I made a reconstruction of the process based<br />

on the available data as a provisional overview <strong>for</strong> analysis and interpretation<br />

(Spradley, 1980). This allowed me to become intimately familiar with the case and to<br />

219


keep the wholeness of the data in mind (Eisenhardt, 1989; Clarke, 2002; Hollway &<br />

Jefferson, 2002). Secondly, I made a systematic analysis of the issues based on three<br />

sets of data: (1) stakeholder interviews, (2) field notes of interaction moments, (3)<br />

critical incident interviews. I looked <strong>for</strong> links, similarities and differences in the<br />

material in a process of constant comparison, coding and categorizing (Strauss &<br />

Corbin, 1998). I paid attention to thematic unity and internal consistency and to a<br />

transparent approach to data analysis (Gould, 1991; Levinson, 1991). During in<strong>for</strong>mal<br />

conversations and internal meetings the consulting team systematically tried to make<br />

sense of what was happening (investigator triangulation, Patton, 1987). After the<br />

project I checked my working hypotheses with my colleagues (critical incident<br />

interviews, research seminar). Moreover, I discussed my findings with peers<br />

(supervisor, mentor, colleagues at conferences) to have an outside perspective.<br />

For this paper I selected three issues with which the participants were struggling: (1)<br />

searching <strong>for</strong> direction; (2) dealing with complexity, diversity and interdependence;<br />

and (3) coping with the emergent nature of the process. Other relevant issues, such as<br />

the influence of the consultants and their relationship with the client system, are<br />

discussed elsew<strong>here</strong> (Prins, 2006, <strong>for</strong>thcoming). The issues are discussed separately,<br />

although they are intertwined. Each issue is discussed and documented with case<br />

material. The quotes are from interviews and observations.<br />

Issue 1: Searching <strong>for</strong> direction<br />

As the process unfolded, t<strong>here</strong> was a critical tension between the <strong>for</strong>mal objective<br />

and the process of negotiating a shared objective. The <strong>for</strong>mal objective of the project<br />

was to develop a concept <strong>for</strong> a ‘reception function’. This was in line with the ‘one<br />

stop shopping’ philosophy of policy makers, and t<strong>here</strong><strong>for</strong>e to some extent normative<br />

and influenced by an external authority. Initially, the concept of a reception function<br />

provided the managers with a reason or a ‘cover’ to sit around the table to talk about<br />

the future and to adapt their internal world to an anticipated external world<br />

(Vansina, 2004). For a while it served the function of a ‘transitional object’ (Winnicott,<br />

220


1971) because it helped the participants to deal with the uncertainty of the change<br />

process. The notion ‘reception function’ provoked different images and fantasies.<br />

Some suggested it referred to a foster care house, a telephone number, a joint intake<br />

procedure, a multi-organizational team, a first step towards a merger, and <strong>for</strong> one<br />

participant it was just a ‘philosophical concept’. One representative feared the output<br />

of the project would play into the hands of policy makers. He assumed it would<br />

weaken the position of foster care in negotiations and make it easier <strong>for</strong> policy to cut<br />

expenses. Still others stressed the concept had only been used <strong>for</strong> strategic reasons, to<br />

speak the language of the policy makers. The concept provoked different emotional<br />

responses ranging from hope to fear. As Turcotte and Pasquero (2001) suggest, this<br />

sort of ambiguity can be strategic because it deals with the diversity of objectives<br />

present in the system.<br />

“The objective is to make the services more client-oriented. This doesn’t necessarily mean one<br />

door per region, but it does mean the same message, the same approach, the same name, etc. I<br />

suspect t<strong>here</strong> could be a difference in opinion around this.” (Manager 1, stakeholder interview)<br />

During the stakeholder interviews, the interviewers decided to drop the idea of a<br />

reception function. We argued it was a solution <strong>for</strong> a problem that was not yet fully<br />

explored. Later in the project, however, the convener reintroduced it and stressed the<br />

centrality of the reception function. She even suggested using the name ‘project<br />

reception function’. This intervention marked a ‘point of power’ (Huxham & Vangen,<br />

2005) and can be seen as an attempt by the convener to push her agenda. The<br />

convener was an authority figure in the group. It was as if her agenda could not be<br />

questioned. Towards the end of the project the concept was still a socially desirable<br />

vision of the future that was not thoroughly explored. As it was an ‘imposed’<br />

transitional object it could no longer contain the anxiety in the group.<br />

“The objective is a reception function. It was not the idea to let go of this concept. Then we<br />

might as well all go home.” (Convener, meeting project group 9)<br />

“That reception function, I never really understood what that was all about!” (Director 5, critical<br />

incident interview)<br />

The aim of the first stakeholder conference was to arrive at an agreement in principle<br />

<strong>for</strong> collaboration. The representatives of the five services, who met <strong>for</strong> the first time,<br />

221


stressed the many areas w<strong>here</strong> they did not want to collaborate. They could hardly<br />

translate their objections into ‘conditions’ <strong>for</strong> collaboration. Some participants<br />

wondered what the benefit of collaboration would be and feared conflict, w<strong>here</strong>as<br />

others were very explicit about the necessity to collaborate. The managers had<br />

assumed the <strong>for</strong>mal objectives would mobilize all participants around a common<br />

aim. They were surprised by the resistance and different interpretations of the<br />

objective. The question ‘what do we want to achieve together?’ kept coming back<br />

until the end of the project and was not resolved within the time frame of the project.<br />

“I had the feeling we already had an agreement. It seemed like a step backwards.” (Manager 3,<br />

meeting project group 8)<br />

“I fear that the starting points are not shared by everyone in the same way. T<strong>here</strong> is enormous<br />

diversity in the individual responses.” (Director 5, stakeholder conference 2)<br />

“But we have made the choice! We have the money; it is all written down on paper. It is about a<br />

reception function!” (Manager 3, meeting project group 9)<br />

“We keep saying: do we want to collaborate or not?! We have started this project almost a year<br />

ago!!” (Manager 3, meeting project group 10)<br />

All participants claimed that collaboration was necessary. They expressed motives,<br />

such as more impact on policy makers and judges, a more efficient use of resources,<br />

less shopping behavior, more career opportunities <strong>for</strong> employees (e.g. specialization),<br />

a more transparent and professional image, efficient use of public money, and more<br />

chances of finding the optimal solution <strong>for</strong> the child.<br />

“If we would collaborate, we would have a wonderful offer and a big capacity. Now it is all<br />

scattered. I want t<strong>here</strong> to be a drive <strong>for</strong> foster care, <strong>for</strong> the children, and not <strong>for</strong> one’s<br />

organization. (…) If we collaborate we can have more impact on policy. We fight <strong>for</strong> the interest<br />

of the child, not of the parents. If we have more weight, maybe they will listen to us.” (Manager<br />

1, meeting project group 2)<br />

However, t<strong>here</strong> was a tension between the rationality, social desirability and rhetoric<br />

of collaboration and the ambivalent emotional responses to the prospect of<br />

collaboration. The managers realized that self-interests were getting in the way of<br />

collaboration. It was as if they assumed that changing their practices would<br />

jeopardize the identity of their organization.<br />

“I am not sure if all services are prepared to collaborate. It makes no sense to hang on to one’s<br />

identity and history. (…) The power of collaboration is the concern <strong>for</strong> the child, parents and<br />

foster parents and not the concern to maintain your organization” (Board member 2,<br />

stakeholder interview)<br />

222


“The discussion is very much focused on the organizations. (…) We have a great interest in<br />

collaborating. A foster mother said ‘it is a mess’. We are <strong>for</strong>ced to collaborate.” (Board member<br />

1, stakeholder conference 2)<br />

“It is about identity. They strongly feel owner of their service. That is an essential feeling. The<br />

reflex is: our service, our quality, our foster families. That is a strong feeling.” (Head Federation,<br />

meeting project group 9)<br />

“The first time I got an oppressed feeling was when we threw our objectives on the table during<br />

the meeting with the board members. I thought to myself, ‘Jesus, how am I going to sell this to<br />

my people?’ It is a great ambition. I did not have night mares, but I did have some sleepless<br />

nights.” (Manager 4, stakeholder conference 3)<br />

Obviously t<strong>here</strong> were different agendas, both manifest and hidden. Most external<br />

stakeholders hoped the project would result in more effective collaboration among<br />

the services. Some hoped foster care would open up the boundaries of their sector<br />

and collaborate with other <strong>for</strong>ms of assistance in the domain. Others hoped the<br />

project would lead to a merger. The employees were keen to collaborate because they<br />

felt the necessity in their daily work. Towards the end of the year most board<br />

members also committed to the project. The managers, who had known each other<br />

<strong>for</strong> many years, turned out to be the most hesitant. They had different agendas. The<br />

liberal service had not participated intentionally in the project and the idea of<br />

structural collaboration was new <strong>for</strong> them. The convening organization had been the<br />

driving <strong>for</strong>ce that started the project. The convener, and some allies, had invested<br />

high hopes in the project. She wanted to move fast towards her goal and was often<br />

impatient and disappointed. The managers talked about ‘differences in speed’<br />

between the services and between employees, board members and themselves.<br />

However, it was not always clear w<strong>here</strong> they were heading to.<br />

“The issues <strong>for</strong> improvement and themes exceed the services <strong>for</strong> foster care. It is also<br />

about collaboration with residential institutions. You have to see it in a broader<br />

perspective. It is also related to regulation and to the mentality.” (Policy maker,<br />

stakeholder conference 1)<br />

“I was very disillusioned after the first day. I had the feeling: what happens <strong>here</strong> should have<br />

happened be<strong>for</strong>e the start of the project! (…) We have an ambitious objective. (…) Differences<br />

are allowed. My ambitions were much higher.” (Manager 3, stakeholder conference 2)<br />

“Some are in favor of joint selection and want to create a pool of parents. That is impossible <strong>for</strong><br />

us. A pool would <strong>for</strong>ce us to refuse people we cannot refuse. Everybody has his own way of<br />

doing selections. Sometimes collaboration can go too far. (…) The employees are very<br />

enthusiastic about collaboration, but the managers in the regional consultation plat<strong>for</strong>m are<br />

223


very reserved. That is related to tactical issues. Decisions in the regional consultation plat<strong>for</strong>m<br />

are inspired by individual concerns of the organizations” (Manager 5, stakeholder interview)<br />

As the project progressed some participants seemed to idealize collaboration as an<br />

end in itself. Talking about ‘collaboration’ seemed like a way to avoid talking about<br />

disagreement and differences (Cooper & Dartington, 2004). A number of participants<br />

wondered if all parties really wanted to collaborate and some did realize that the<br />

purpose of collaboration was not clear. The managers presented a vague, potential<br />

scenario <strong>for</strong> the future, based on the existing collaboration between two of the five<br />

services. T<strong>here</strong> were no criteria to assess the added value of collaboration (e.g.<br />

shorter time cycle between demand and solution, more varied offer of assistance,<br />

more foster families, more efficient use of resources). The issue was raised but not<br />

solved.<br />

“You have to start from problems and bottle-necks if you want to collaborate. If t<strong>here</strong> is no goal,<br />

it is not meaningful. I am not inclined to collaborate if t<strong>here</strong> is no added value. (…) Just what is<br />

the reason <strong>for</strong> this project?” (Employee 5, stakeholder interview)<br />

“’Better foster care’ is too vague. You have to make operational what that means.” (Head<br />

Federation, meeting project group 13)<br />

“What are criteria to assess actions? What is quality?” (Head Federation, stakeholder conference<br />

3)<br />

The liberal service had been reluctant from the start. They gave several reasons <strong>for</strong><br />

their ambivalence. Their relationship with the four services was difficult due to the<br />

behavior of the previous director. At one point, <strong>for</strong> instance, they had been kicked<br />

out of the ‘regional consultation plat<strong>for</strong>m’ because they didn’t respect the<br />

agreements. At the start of the project they were having internal problems in their<br />

organization (e.g. newly appointed director, lay-offs, and a decrease in placements).<br />

According to them the discussions in the project were not based on facts and<br />

evidence (e.g. are all relegating parties in favor of collaboration?) and they felt<br />

attacked whenever they asked <strong>for</strong> clarification. After internal consultation the liberal<br />

service concluded that the project did not sufficiently benefit the children. They were<br />

concerned about more strategic issues, such as how to organize foster care in<br />

Flanders, how to deal with diversity and competition in the field, and how to balance<br />

the economical costs of care with the future of the children. They also experienced<br />

224


ambivalence in the other organizations. A representative of the liberal service vividly<br />

remembered a small but significant incident. Someone ‘closely involved in the<br />

project’ had said: ‘yes, but you are not going to discover my business secret’. He<br />

observed that it seemed easier <strong>for</strong> the services to take a big step (e.g. develop a<br />

reception function), than to take small steps (e.g. share the mission statements of the<br />

organizations). He wondered if they really wanted to collaborate. The managers of<br />

the other four services labeled the liberal service as ‘difficult’ and ‘slowing down’ the<br />

process.<br />

“A condition to commit to the project is to not constantly manifest resistance. Otherwise it is<br />

better not to join. Otherwise you become a burden <strong>for</strong> the process. You shouldn’t constantly say<br />

‘yes, but’.” (Manager 3, stakeholder conference 2)<br />

“During the discussions with the board members t<strong>here</strong> appeared to be a big gap in confidence.<br />

My question is: how far should we go to bridge that gap? I want to go very far, put it all on the<br />

table, if t<strong>here</strong> is a guarantee that… I understand the mistrust. It is related to our history. I want<br />

to involve everybody. But how long can we still wait?” (Manager 1, meeting project group 9)<br />

T<strong>here</strong> was a tension between moving on with only four services and investing time<br />

and energy to arrive at common ground between the five services. The liberal service<br />

seemed to serve the function of scapegoat <strong>for</strong> the group. It was obvious, however,<br />

that all parties were anxious to commit to the open change process.<br />

According to Gray (1989) the first phase in multiparty collaboration is focused on<br />

‘problem setting’ in order to establish direction. It seems obvious that working<br />

towards common aims provides the basis <strong>for</strong> collaboration. Huxham and Vangen<br />

(2000) observed that often it is extremely difficult to agree upon collaborative goals<br />

and that those involved frequently take action without clear specification of the<br />

desired outcome. The work of Sherif (2001) has demonstrated the importance of<br />

creating superordinate goals that one group cannot reach alone in order to foster<br />

collaboration and to reduce the tension among different groups that operate in the<br />

same domain. In the collaborative the variety of individual and organizational<br />

agendas and the asymmetry of stakeholder groups made it hard to develop common<br />

ground and to set the direction. The representatives invested a lot of time and energy<br />

in the ‘pairing dance’, stressing how much experience they had in collaboration and<br />

225


how good their relationship was. This prevented them, however, from putting their<br />

agendas on the table and engaging in ‘interest bargaining’ (Vansina, 2002). The<br />

awareness that this collaboration was indirectly imposed by policy makers and<br />

strongly influenced by the agenda of the convener may have provoked resistance.<br />

T<strong>here</strong> was a tension between the necessity and the risk to put the agendas on the<br />

table. In the discussion of the next issue we will see that open discussion about<br />

differences almost provoked a conflict.<br />

Issue 2: dealing with complexity, diversity and interdependence<br />

In the course of the collaboration some small events moved the process away from<br />

the inter-organizational domain of foster care. This resulted in a reduction of the<br />

complexity, diversity and interdependence in the process. This dynamic was<br />

influenced by the starting conditions of the project, by decisions made by the<br />

managers and by interventions of the consultants.<br />

A duality in the contract with policy makers produced ambiguous starting<br />

conditions. The need to achieve a pre-defined outcome reduced the possibility to<br />

engage in an emergent, multi-stakeholder process, as advocated in the contract.<br />

Secondly, the choice <strong>for</strong> one region and <strong>for</strong> the sector of foster care as the focus of the<br />

project reduced the scope of the change process from the start.<br />

“The fact that the project is about collaboration between services in that region is in itself a<br />

choice with which you exclude other options. It is, <strong>for</strong> instance, not a choice <strong>for</strong> collaboration<br />

across <strong>for</strong>ms of assistance, and it is not a choice <strong>for</strong> collaboration on a national level”<br />

(Representative of umbrella organization <strong>for</strong> employers, stakeholder interview).<br />

“What I observe is that a project proposal to obtain funding requires a procedural language.<br />

And I wonder if a procedural language can capture the process… I don’t think so. It is like<br />

broadcasting a video film through the radio. It is based on a structure and on pre-established<br />

outcomes. (…) The financing organizations look <strong>for</strong> certainty in structures. W<strong>here</strong>as the people<br />

involved in foster care look <strong>for</strong> certainty in collaborative relationships, on the basis of which<br />

they will develop and design new structures. How do you deal with that?” (Facilitator, critical<br />

incident interview).<br />

At the start a ‘project group’ was <strong>for</strong>med. It was composed of managers of the<br />

participating foster care services and the head of the Federation. T<strong>here</strong> were no<br />

representatives of employees, board members, or of foster care and welfare in<br />

226


general. The group did not act as a ‘steering group’ to drive a change process in the<br />

domain of foster care. From the start the restricted membership rein<strong>for</strong>ced the focus<br />

on the individual organizations. It made it harder <strong>for</strong> the managers and consultants<br />

to perceive the problem as a societal ‘meta-problem’ concerning the domain of foster<br />

care. Since the managers worked removed from the field the discussions were often<br />

abstract (e.g. values). The boundaries of the group were kept closed, because the<br />

managers wanted to stay in control.<br />

The project group started with a stakeholder analysis to identify the critical<br />

stakeholders in the domain. It was based on five stakeholder categories identified in<br />

the project proposal: users (parents and children); voluntary collaborators (foster<br />

families); professional employees; relegating parties; and policy makers. Foster<br />

children and parents, the central stakeholders, were not interviewed or invited at<br />

stakeholder conferences. We never received any names. The triangle in<strong>here</strong>nt in the<br />

client system (children, parents, and foster parents) was excluded from active<br />

participation in the process. With my colleague I spent two months interviewing all<br />

over Flanders. This resulted in a massive amount of data. We found it extremely<br />

hard to organize, communicate and share the issues with the managers. The<br />

consequence of this intervention was that the know-how based on interactions with<br />

the stakeholders was with the consultants and that we – temporarily – took over<br />

ownership. We found ourselves in the role of go-between, trying very hard to<br />

introduce a sense of urgency and ‘reality’ in the system. I took a note in my diary<br />

about how surprising it was that we were always yawning while we were driving<br />

around <strong>for</strong> the interviews. For a long time I could not make sense of our tiredness.<br />

Afterwards, we realized we found ourselves in the role of doing the work and<br />

carrying the wishes, worries and hopes of the system.<br />

“Instead of trying so hard to find ways of waking them up and encouraging them to reflect, it<br />

would have been easier to bring everybody together and just let them talk directly. (…) I was<br />

relieved it was over, because it was a very heavy project.” (Coordinator, critical incident<br />

interview)<br />

“That is the classic OD model: you start with collecting in<strong>for</strong>mation from individuals who are,<br />

in this project, representing an organization or community. And then the differences are written<br />

down in a report which is distributed. The report was the start of the process in the project<br />

group. And then the system is invited. (…) I observed how that contrasted with the approach of<br />

227


inging the system in a room and taking it from t<strong>here</strong>. As a way to simply bring all the<br />

perspectives together and to have a dialogue with everybody on the spot.” (Facilitator, critical<br />

incident interview)<br />

During the feedback of the interviews, we presented a stakeholder model (Eden,<br />

1996), based on two dimensions: the interest and perceived power of the<br />

organization or group in the domain (see attachment 4). This intervention was an<br />

attempt to deal with the complexity of the process. Because, as conventional, it was<br />

presented in terms of power, we introduced an implicit hierarchy in the stakeholders.<br />

In the organizational logic of multiparty collaboration all stakeholders are legitimate<br />

and equal partners in the process. The model emphasized the central position of the<br />

services and further marginalized the children and parents. A consequence was that<br />

the services made plans <strong>for</strong> the future and only involved stakeholders when they<br />

thought it was necessary. This narrow focus undermined the exploration of interests,<br />

needs, and resources in the domain.<br />

The managers made some decisions that set the direction of the process. During the<br />

first meetings of the project group they decided not to organize the two-day,<br />

residential search conference as <strong>for</strong>eseen in the design. Allegedly, this was not ‘part<br />

of the culture’ in foster care. The managers assumed that most ‘external’ stakeholders<br />

would not be willing to dedicate so much time to foster care anyway.<br />

“The culture is from 9 to 4 and then a drink.” (Manager 5, meeting project group 6)<br />

(About the external stakeholders) “They will not come and they are not going to say anything!”<br />

(Manager 4, meeting project group 7)<br />

During the preparation of the stakeholder conferences the managers made a<br />

pragmatic choice and decided to organize two separate days. They expressed their<br />

worries about what stakeholders might hear and what they might say. They did not<br />

want to show their ‘dirty laundry’ to the outside world and assumed that people<br />

would not speak up in the presence of outsiders. The managers started talking about<br />

what they called ‘internal’ and ‘external’ stakeholders. Encouraged by the facilitator<br />

they remained open to the idea of letting the stakeholder play their role. In the next<br />

meeting, facilitated by the senior consultant, the group decided to only invite the<br />

228


‘external’ stakeholders <strong>for</strong> the morning of the first stakeholder conference. The<br />

second stakeholder day was <strong>for</strong> internal stakeholders only. Although the managers<br />

realized it was essential to include external stakeholders, they settled on keeping the<br />

boundaries closed to focus on ‘internal matters’ first. For the facilitator, who had not<br />

been present when this was decided, these choices were critical and moved the<br />

process away from a stakeholder approach. He recalled that <strong>for</strong> him from that<br />

moment the project was no longer about foster care as a system, but about a<br />

reorganization of the services. The stakeholders could not take part in the dialogue<br />

and were only consulted and in<strong>for</strong>med. This critical incident also demonstrates the<br />

differences in assumptions between the two consultants.<br />

“The list of participants <strong>for</strong> the stakeholder meeting is too internal. The basic philosophy of<br />

multiparty collaboration is that you, ideally, involve all stakeholders in the process. (…) If you<br />

involve others, you end up with different findings. (…) You work from a system perspective,<br />

but the system cannot be present!” (Facilitator, meeting project group 5).<br />

“I think it is easier <strong>for</strong> people to leave their chair if you involve other stakeholders. That makes<br />

it easier to think broadly. Then you think <strong>for</strong> foster care. If you only meet with internal<br />

stakeholders, you provoke the reflex ‘my service!!’.” (Manager 3, meeting project group 5)<br />

“The stakeholders are systematically kept out! They are afraid of them.” (Facilitator, internal<br />

meeting 8)<br />

The first stakeholder conference provided an opportunity <strong>for</strong> a wide group of<br />

stakeholder representatives to discuss the findings of the interviews. Carefully<br />

designed subgroups with a maximum degree of diversity exchanged experiences.<br />

The external stakeholders gave first hand in<strong>for</strong>mation on the problems and needs in<br />

the domain of foster care. As long as the external stakeholders were present the<br />

internal stakeholders felt unified as ‘foster care’. As soon as they left, the differences<br />

between the services came to the <strong>for</strong>eground. The external stakeholders were not<br />

involved during the following six months of the project. At the second ‘stakeholder<br />

conference’, which was entirely internal, the participants set up work groups made<br />

up of employees. The aim was to get to know one another, to exchange experiences<br />

and to propose ideas <strong>for</strong> collaboration. This choice further stressed the internal focus<br />

of the process.<br />

“The outsiders made a constructive contribution. (…) In the afternoon things were narrowed<br />

down. We withdrew on ourselves. (…) Because the outsiders were no longer present, my<br />

229


director could claim that ‘the relegating parties thought it was going well’. That could no longer<br />

be contradicted by the relegating parties themselves.” (Manager 2, meeting project group 8)<br />

“T<strong>here</strong> was a constructive atmosp<strong>here</strong> and people talked about foster care. In the afternoon we<br />

thanked the external stakeholders. (…) They left and in the afternoon the bickering between the<br />

five services came to the <strong>for</strong>eground.” (Facilitator, critical incident interview)<br />

“We stick together when the outside world is present, but not when we are alone.” (Employee,<br />

stakeholder conference 2)<br />

“We have kept up appearances <strong>for</strong> the outside world.” (Manager 1, meeting project group 8)<br />

The starting conditions, the narrow composition of the project group, the decision<br />

not to organize a search conference, the split between internal and external<br />

stakeholders and the close boundary that was drawn around the internal<br />

stakeholders were small events that, unintentionally, made the process drift away<br />

from the intended stakeholder approach. The managers set the agenda, and the<br />

consultants were getting absorbed in the client system. The result was that<br />

stakeholders were not actively involved in the process and that responsibility <strong>for</strong> the<br />

domain was not kept shared around the table. The boundary blocked off the capacity<br />

of the participants to relate, empathize, and deal appropriately with ‘outsiders’<br />

(Stein, 2004). This boundary redefined the topic of the collaborative ef<strong>for</strong>t: the focus<br />

shifted from the domain of foster care to the foster care services.<br />

“I heard people in the work groups explicitly remind themselves that ‘foster care’ was to<br />

remain the central objective.” (Facilitator, critical incident interview)<br />

Now that the boundary of the system was narrowed down to the internal<br />

stakeholder in order to enable productive work, a different issue emerged. ‘Solving’<br />

one issue resulted in a different issue that had to be managed (Huxham & Vangen,<br />

2005). The managers soon realized that the ‘internal’ stakeholders were also strangers<br />

to each other. Paradoxically the choice <strong>for</strong> an internal focus accentuated the need to<br />

protect one’s identity. Dealing with diversity and the ambiguity of differences and<br />

similarities among the services became the central issues. Many participants claimed<br />

that ‘not knowing each other’ was a major obstacle to collaboration. Some<br />

participants pointed at the similarities (e.g. shortage of candidate foster families,<br />

heavy work load), w<strong>here</strong>as many stressed the differences between the services.<br />

Differences related to interests, procedures, ideology, management style, culture,<br />

230


mandate, organizational structure, size, role of the boards, and individual<br />

differences. The participants discussed questions such as: are we too different to<br />

collaborate? Are we only different in theory but not in our daily practices, or is it the<br />

other way around? Are differences a source of conflict or a potential enrichment?<br />

“That is exactly the problem. We don’t know to what extent we are different, because we don’t<br />

know the others. (…) I have the feeling they want to collaborate while maintaining their<br />

identity. How can you do that? Then you must first figure out what your uniqueness is.”<br />

(Employees 3, stakeholder interview).<br />

“So far I have never seen fundamental differences between the services. T<strong>here</strong> are different<br />

nuances. We also experience differences in culture. That is precisely the richness of the Flemish<br />

landscape. The services have sufficient elements in common.” (Head Federation, meeting<br />

project group 10)<br />

“We have a lot in common. I often have the feeling ‘we do that too!’.” (Board member 1,<br />

meeting project group 10)<br />

Diversity is an essential condition <strong>for</strong> collaborative advantage and collaboration is<br />

based on accepted differences. In confrontation with diversity groups try to confirm<br />

their social identity and accentuate their distinctiveness from others. The sheer<br />

presence of different interest groups seems to threaten the ‘survival’ and self-esteem<br />

of the groups involved (Vansina 2002). The participants found it hard to openly<br />

explore the differences. It was as if the internal stakeholders collectively assumed<br />

that the differences between their services were an obstacle to collaboration. On the<br />

other hand, being too similar accentuated the competitive nature of the relationships<br />

and seemed like a threat to the survival of the organizations. One representative<br />

jokingly observed that competition seemed easier than collaboration. Collaboration<br />

requires a strong identity that can survive the confrontation with other groups and<br />

organizations. However, precisely defining the core values and competences of the<br />

services was a difficult exercise.<br />

“It is confronting to communicate what you stand <strong>for</strong>. It may appear that we are not so special<br />

after all. Then we will have an identity crisis! (Laughing)” (Manager 5, in<strong>for</strong>mal conversation)<br />

“It took us time to accept the awareness that we were not, also in our pedagogy, so different<br />

from the others.” (Director 5, critical incident interview)<br />

“You all seem surprised that we don’t find differences. That in itself is maybe a problem!<br />

(Laughter) When the differences are substantial, it might be easier to collaborate. Then at least it<br />

is clear. Then you can work in a complementary way.” (Director 2, meeting project group 10)<br />

231


Two months be<strong>for</strong>e the deadline of the project tension was high because the project<br />

group had made little progress and t<strong>here</strong> was no <strong>for</strong>mal commitment from all<br />

participating organizations. The project group organized a first meeting with the<br />

board members. To facilitate open discussion the consultants had prepared an<br />

‘objective’ overview of the similarities and differences based on the mission<br />

statements of the five services. The aim of the meeting was to decide if, after<br />

comparing the visions, operational collaboration was possible. The managers and<br />

board members of the services commented on the matrix. Systematically the senior<br />

consultant concluded with the observation that apparently t<strong>here</strong> were ‘no<br />

fundamental differences’. The representatives of the liberal service got upset. They<br />

protested that the issue of differences was strongly reduced to ‘crosses on a matrix’<br />

and that the consultants avoided open discussion. In the critical incident interviews<br />

some managers also blamed the consultants <strong>for</strong> covering up the ‘real differences’.<br />

“I have the impression that ‘the importance of the child’ can be very different from service to<br />

service. On paper it looks very similar, a line with crosses. I am not certain we are talking about<br />

the same thing. (To the senior consultant) You summarized by saying ‘t<strong>here</strong> are no differences’.<br />

But that is only appearance. (…) A condition <strong>for</strong> collaboration is that you are able to understand<br />

the consequences of being different. (…) When I read ‘Christian inspiration’, I wonder what it<br />

means.” (Board member 5, meeting project group 10)<br />

The president of the board of the liberal service emphasized the specific nature of<br />

their ‘pedagogical project’. The other services, however, did not perceive differences<br />

in daily practice. It never became clear what care <strong>for</strong> children from a liberal<br />

perspective meant.<br />

“In the liberal principles I recognize things that are important <strong>for</strong> us too. I cannot grasp how<br />

that can be of importance in foster care. I don’t understand how you do things differently than<br />

we do.” (Manager 3, meeting project group 10)<br />

At one point in the meeting two board members stopped the discussion. They<br />

suggested it was time to speak up and commit to the project or to step out. After a<br />

time out, the liberal service announced they withdrew from the project. They said<br />

they felt like strangers in the group and had the feeling they were not taken<br />

seriously. They judged it was too early and risky to engage in structural collaboration<br />

and feared conflict would blow up the existing relationships. All interviewees<br />

232


eferred to this incident as the major critical event in the project. The discussion was<br />

focused on ‘ideology’ as a narrow interpretation of identity. The underlying reasons<br />

<strong>for</strong> stepping out were not openly discussed. It seemed as if the issue of ideology was<br />

used as a smoke screen to avoid talking about what really concerned the managers.<br />

The departure of the liberal service further reduced the diversity in the system.<br />

“I thought: he is the president of the board. I found it hard to decide in his place. And when he<br />

referred to the pedagogical project, I didn’t want to stress that other issues were also important.<br />

I did not want him to lose face.” (Director 5, critical incident interview)<br />

“Suppose the focus had not been on the services, but on foster care, would the same thing have<br />

happened?” (Facilitator, critical incident interview)<br />

Now that the four seemingly ‘like minded’ services no longer had a ‘common<br />

enemy’, the managers were confronted with the challenge to take decisions about the<br />

future and to achieve quick results be<strong>for</strong>e the deadline. Often, external <strong>for</strong>ces, such as<br />

a funding deadline, introduce a sense of urgency and set a group in motion (Huxham<br />

& Vangen, 2000). Holding on to the organizational identity and autonomy of the<br />

services became major issues. Flanders is a region with a history of emancipation<br />

from French speaking nationals and from catholic domination. This history has led to<br />

a society w<strong>here</strong> ideological power centers are still important and reflected in<br />

institutions (e.g. education, unions). The history of foster care itself was also<br />

characterized by ideological conflicts, splits and a process of emancipation. T<strong>here</strong><strong>for</strong>e<br />

the autonomy and identity of the services were important.<br />

“In foster care all the services have emerged from one single service. T<strong>here</strong> has been a conflict<br />

which led to a split and to the creation of (service 2) and later also (service 3). This resulted in a<br />

strong sense of autonomy of the services, the feeling that their service is better than the others<br />

and a strong identification with their service” (policy representative, stakeholder interview)<br />

Collaboration implied being dependent upon the other services <strong>for</strong> success: ‘all going<br />

up, or all going down’. The consequence of collaboration was that it was no longer<br />

possible to achieve individual growth of the organization based on hard work,<br />

loyalty, and on ‘being the best’.<br />

“Now you know that if you work hard, you have more placements.” (Employee 2, stakeholder<br />

interview)<br />

“If you lose your identity… Then you lose your drive. Then you are not prepared to think with<br />

the organization anymore.” (Employee and manager 4, stakeholder interview)<br />

233


The essence of collaborative work is to use the diversity in the system to establish an<br />

encompassing definition of the problem domain, to develop sustainable solutions<br />

and to increase the chances of implementation of the solutions. A challenge of<br />

collaborative work is to what extent participants are able to relinquish the identity,<br />

control and safety of their home-based organizational boundaries and locate<br />

themselves within the uncertain boundaries of a new collaborative enterprise (Gould<br />

et al, 1999). Can they accept the diversity of interests and perspectives and are they<br />

capable of developing interdependent relationships? Although t<strong>here</strong> were attempts<br />

to involve ‘external’ stakeholders, these critical partners were not actively involved<br />

in the process. The services were used to operate in a context w<strong>here</strong> competition and<br />

independent action were necessary <strong>for</strong> survival. Since the subsidizing mechanism<br />

did not change it may have been too risky to make a move towards interdependent<br />

work. Confronted with ‘internal’ stakeholders only, the familiar competitive way of<br />

relating seemed safer than engaging in a new relationship based on trust, openness,<br />

interdependence and accepting differences as a benefit.<br />

Issue 3: dealing with the emergent nature of the process<br />

The openness of the change process and the uncertain outcome provoked anxiety.<br />

The employees anticipated many losses. They were afraid to lose contact with the<br />

‘essence’ of their work and to give up their expertise and the relationships they had<br />

developed over the years. Many had had long careers in foster care and strongly<br />

identified with their service. They were worried about losing their job or having to<br />

work at a different location or in an anonymous institution as a result of structural<br />

collaboration. However, they were willing to collaborate and asked their managers<br />

<strong>for</strong> clarity.<br />

“You cannot know in advance w<strong>here</strong> you will end up, what the objective is. And when you<br />

start, you get overwhelmed with fears!” (Employee, stakeholder conference 3)<br />

“The frame must be clear. Too many things are fuzzy now. I don’t feel good about that.”<br />

(Employee 1, stakeholder interview)<br />

234


The managers tried to come up with a minimal structure to contain the anxieties.<br />

During the morning of the final stakeholder conference, they emphasized that the<br />

purpose was not a merger, and that t<strong>here</strong> was no hidden agenda. They guaranteed<br />

the process would continue regardless of external funding, and that t<strong>here</strong> would be<br />

no job losses. The managers presented their experiences as a model and talked about<br />

their personal dreams, worries and hopes <strong>for</strong> the future and their struggle as<br />

‘management group’. However, they also realized that it was paradoxical to give<br />

solid guarantees in an ‘emergent’ process.<br />

The <strong>for</strong>mal characteristics of the project (e.g. deadline, output) provided a minimal<br />

structure <strong>for</strong> the managers. The project, which was a ‘paid episode’ in an ongoing<br />

process, helped the managers to cope with the transition of the change process that<br />

was broader than the scope of the project. The managers seemed to experience the<br />

project as separate from their daily work and from the organizing process in their<br />

respective organizations, as if it was not ‘real’. They often stated they had ‘no time’<br />

<strong>for</strong> the project and expected the consultants to do the work and drive the process.<br />

One manager imagined the change process could simply be ‘stopped’ if t<strong>here</strong> was no<br />

additional funding, as if the organizational dynamics that were triggered by the<br />

initiative could simply be brought to a standstill.<br />

The presence of a facilitator helped the managers to deal with the tensions provoked<br />

by the change process (e.g. fear <strong>for</strong> conflict). It allowed them to ‘sit on their chair’ and<br />

speak <strong>for</strong> their constituency. They often used humor to reduce the tensions and<br />

openly used the word ‘anxiety’. They talked about ‘how a dream can turn into a<br />

nightmare’, and having ‘sleepless nights’. They were stunned by the boldness of their<br />

ideas and actions. We did notice, however, that they seemed to avoid opportunities<br />

to share and explore their feelings, and work them through. For instance, at the end<br />

of the 11th meeting of the project group, while they were discussing the resistance of<br />

their employees, one of the managers suggested that maybe they should also talk<br />

about their own worries. One manager had to leave and the meeting suddenly<br />

stopped. The question remained unanswered and, even though the facilitator tried to<br />

235


aise the issue in the next meeting, it was not taken up later in the process. The<br />

meetings of the project group left little time <strong>for</strong> in<strong>for</strong>mal contact. The members, all<br />

women, insisted on punctual ending in order to be home in time. Most meetings<br />

demonstrated an odd mixture of task orientation and off-task behavior. On the one<br />

hand, t<strong>here</strong> was a full agenda, the meetings had to be ‘functional’ and timing was<br />

strict. On the other hand, we were often surprised how difficult it was to keep the<br />

group focused on the agenda. Usually t<strong>here</strong> were many digressions, chatting about<br />

trivial subjects, and sometimes the meetings were chaotic. The members did not use<br />

the space of the meetings as a ‘potential space’ (Winnicott, 1971) w<strong>here</strong> they could<br />

engage in creative, playful experimentation and imagination of future scenarios<br />

without immediate binding consequences.<br />

“We did not spend so much time together, not even in the project group. (…) It was always<br />

very task oriented more or less three hours per month.” (Coordinator, critical incident<br />

interview)<br />

The consultants offered some structuring interventions (e.g. action plan, stakeholder<br />

model, structured feedback, comparative matrix) to deal with the emergent nature of<br />

the process. However, these interventions often seemed to serve the function of<br />

avoiding or controlling direct interaction. The stakeholder interviews, <strong>for</strong> instance,<br />

were a time consuming substitute <strong>for</strong> a search conference with all stakeholder of the<br />

domain. The idea to set up work groups structured the process and moved things<br />

ahead, even when the future scenario was not yet known. However, these groups<br />

rein<strong>for</strong>ced the internal focus of the process and maintained the existing boundaries:<br />

work groups <strong>for</strong> employees and the project group <strong>for</strong> the managers. The boards<br />

<strong>for</strong>med a third organizational layer. This premature <strong>for</strong>malizing and structuring<br />

seemed like a defensive dynamic to deal with uncontained negative feelings.<br />

In the course of the project the managers realized that the scope and consequences of<br />

the change process were much broader than they had <strong>for</strong>eseen. They were aware of<br />

the expectations they had created, both with internal and external stakeholders. They<br />

realized the consultants could not offer them a blueprint scenario. As the pressure to<br />

take decisions was rising, the managers started to focus on the ‘process’. A field of<br />

236


tension emerged between the need to invest time in establishing collaborative<br />

relationships and the requirement to obtain results be<strong>for</strong>e the deadline. However, the<br />

managers did not want to come up with quick results <strong>for</strong> the sponsors, but it also<br />

worried them in view of future funding.<br />

“We may and must go through a process, but t<strong>here</strong> must be a result. I don’t want to hear at the<br />

end of the year: ‘t<strong>here</strong> is an intention to collaborate’. We have said that <strong>for</strong> the last two years.”<br />

(Manager 4, stakeholder interview)<br />

“If we present this as result of the project we can <strong>for</strong>get it. I want to make the most of this<br />

opportunity, but I don’t want to rush things either. (…) At this point in time we cannot reach<br />

the objectives as they have been agreed. I feel responsible. I don’t want to lose face as an<br />

organization.” (Manager 1, meeting project group 9)<br />

The managers insisted on external process facilitation as a condition to continue the<br />

process. I took a note saying the emphasis on ‘process’ and ‘process facilitation’<br />

almost became like a mantra. The excessive focus on the process and the dependency<br />

on external facilitators seemed like defensive responses to the threat of taking<br />

decisions and sharing responsibility <strong>for</strong> the future.<br />

“We have to do something as soon as possible. The phase of acquaintance cannot take too long.<br />

(…) We must have something concrete by November.” (Head Federation, meeting project<br />

group 9)<br />

“We can continue, but process facilitation is critical. If t<strong>here</strong> is no process facilitation, the<br />

product is jeopardized. (…) We are the ones who most need process facilitation. We will have to<br />

take decisions, set the direction.” (Manager 3, meeting project group 12)<br />

The managers had engaged in an emergent change process with few stable<br />

structures. According to Krantz (1998) this openness stirs up anxiety and mobilizes<br />

exactly the kind of defensive responses that hinder effective collaboration. The<br />

project resulted in an intention to collaborate in specific, well defined areas: inflow of<br />

children and selection of candidate foster parents. T<strong>here</strong> were few boundary crossing<br />

structures or interactions. The managers wanted to hold on to the existing services as<br />

separate and autonomous organizations. This ‘survival reflex’ had been the obvious<br />

mode of functioning <strong>for</strong> many years in a competitive environment. For a year the<br />

managers had tried to move beyond collaboration in ‘safe domains’ and beyond the<br />

‘intention’ to collaborate, but the road was more bumpy than they had expected.<br />

237


Some reflections<br />

Menzies (1960) demonstrated how the anxieties provoked by the task trigger<br />

defensive processes and structures to cope with the tension in the workplace. The<br />

findings discussed in the case can be related to her findings. The nature of the task<br />

and relationships provoked tensions which resulted in defensive dynamics (e.g.<br />

exclusion, blaming) and defensive structuring (e.g. non representative project group,<br />

workgroups with only employees). Traditionally the ‘primary task’ refers to the task<br />

the organization has to per<strong>for</strong>m in order to survive (Rice, 1958; Miller, 1993). This<br />

concept, however, is no longer relevant in turbulent environments. In emergent and<br />

dynamic <strong>for</strong>ms of organizing the core leadership task is to ensure that the primary<br />

task is constantly reviewed and adapted in the light of a changing environment<br />

(Obholzer & Miller, 2004). In a context w<strong>here</strong> leadership is a shared phenomenon, all<br />

those involved need to pay attention to the relevance of the primary task in relation<br />

to, <strong>for</strong> instance, changes in membership or events in the context. In the case study the<br />

task had shifted because the boundaries around the collaborative were narrowed<br />

down and the notion of ‘stakeholder’ was redefined. The instrumental,<br />

organizational interests of the services gradually prevailed over concerns <strong>for</strong> the<br />

child and its environment and over societal interests.<br />

Working on a task always requires people, as individuals and as organizations, to<br />

deal with the mental pain provoked by the task. People collectively develop defenses<br />

against realities that are too painful by establishing rules and procedures. This helps<br />

them to cope with the task, as long as it does not interfere with it (Mawson, 1994).<br />

Foster care is a radical <strong>for</strong>m of assistance with a high threshold. The verdict from a<br />

judge to entrust a child to people who will – temporarily – take over their parenting<br />

role is extremely hard <strong>for</strong> parents. It implies failure of parents to take care of their<br />

child and provokes feelings of inadequacy, shame, rivalry, and it represents a threat<br />

to the identity of the parents. In addition, the services had not been capable to<br />

provide optimal solutions <strong>for</strong> the children in distress, because t<strong>here</strong> were few<br />

families available and because they often felt <strong>for</strong>ced to choose a solution in the<br />

interest of their organization. The painful aspects of ‘failure’ to take care of the child,<br />

238


oth of the parents and of the foster care services, were not present in the process.<br />

The voice of the central stakeholders was not heard. The participants ‘spoke <strong>for</strong>’ the<br />

child and parents. It was as if direct confrontation with the pain of the child and<br />

parents was being avoided.<br />

During the very first in<strong>for</strong>mal meeting, one of the managers had made a casual<br />

remark: "Who is at the core of this project: the foster care services or the child?” This<br />

turned out to be a critical tension in the project. A distinction between different<br />

aspects of the primary task, proposed by Lawrence and Robinson (1975), may help to<br />

make sense of what was happening. The ‘existential’ primary task of the services, or<br />

the task the participants believed they were carrying out, was to couple the child to<br />

the best foster family available. That hope or belief had driven the convener to<br />

choose a collaborative approach. The ‘normative’ primary task was the task they<br />

ought to be working on, dictated by an external authority: develop structural<br />

collaboration. At the same time, however, the subsidizing mechanism that triggered<br />

rivalry was not questioned or changed. T<strong>here</strong> was no alignment between the<br />

existential and the normative task. T<strong>here</strong><strong>for</strong>e a ‘phenomenal’ task, or the task they<br />

were actually engaged in, emerged (Hoyle, 2004). This task, also called ‘resistance to<br />

change’, manifested itself in dynamics to protect the identity and autonomy of the<br />

organizations.<br />

Engaging in an open change process implied the readiness to let go of old beliefs, to<br />

abandon current practices, to put jobs at stake, and to question the current<br />

organizational boundaries and relevance of foster care as a separate field. The<br />

process was prematurely <strong>for</strong>malized which rein<strong>for</strong>ced the internal focus. The<br />

structures that were established strengthened the existing boundaries and generated<br />

dynamics that moved the group away from its intention. It seemed hard to establish<br />

a temporary ‘transitional’ space w<strong>here</strong> the participants could safely express and<br />

work through their anxieties, experiment with scenarios <strong>for</strong> the future, and learn<br />

from their experiences and from each other.<br />

239


The evolution of the relationships was influenced by the fear to lose one’s identity<br />

and autonomy. Gradually the diversity, interdependence and complexity in the<br />

process were reduced. In the course of the process the ‘external’ stakeholders were<br />

excluded from active participation. The foster parents were interviewed but kept out<br />

of the ongoing dialogue. The policy makers, the most critical stakeholder in the<br />

process, were not actively involved in the process even though all participants had<br />

stressed the need to change the subsidizing system. The contract with policy makers<br />

was bounded and the output defined. T<strong>here</strong><strong>for</strong>e the managers could not question the<br />

subsidizing mechanism as the critical obstacle to collaboration. In the group of<br />

internal stakeholders, inter-group dynamics and rivalries emerged, masking<br />

defensive processes and the flight from work (Obholzer & Miller, 2004). The<br />

relationships were also characterized by ambiguous authority relations. No one had<br />

the authority to take decisions based on positional power. The convener had<br />

substantial influence on the direction of the process. Based on her agenda, she had<br />

written a project. She was a very enthusiastic and convincing woman, with authority<br />

in the group based on her seniority and a clear mandate to take decisions <strong>for</strong> her<br />

organization. Because she realized she only represented ‘one of the participating<br />

organizations’, she had openly stepped back from her leading role and trusted the<br />

consultants to drive the process.<br />

One of the meanings of the word ‘collaboration’ is working with the enemy. In this<br />

project <strong>for</strong>mer rivals unintentionally found themselves in a project to develop a<br />

collaborative partnership. The managers, however, seemed reluctant to change their<br />

way of working and organizing. They were pressured by changing external<br />

circumstances (e.g. welfare policy, nature of the problems, higher demands) to<br />

collaborate in the best interest of the child. This mirrors a dynamic in the client<br />

system of foster care w<strong>here</strong> foster parents are <strong>for</strong>ced to collaborate with the natural<br />

parents. Collaboration proved to be more difficult than competition and seemed to<br />

turn into a purpose in itself. However, it remained unclear what collaborative<br />

advantage the participants expected. Why would the services bother to engage in a<br />

difficult, lengthy and risky process, if the benefits were not specified? Was it only to<br />

240


make a good impression and to be one step ahead of policy makers? It seemed<br />

paradoxical to develop collaborative relationships in an institutional context<br />

governed by rivalry <strong>for</strong> resources. The participants and consultants seemed to be<br />

caught in a collusive relationship w<strong>here</strong> everybody talked about ‘collaboration’ as a<br />

cover <strong>for</strong> ongoing competitive relationships.<br />

Conclusions<br />

This paper gives a rich account of a collaborative process in a natural setting based<br />

on observations and accounts. It describes how a group of representatives and<br />

consultants tried to establish the future of foster care. The surprising conclusion of<br />

this case study is that a number of small, seemingly insignificant decisions, events<br />

and interventions, gradually moved the process away from its original intention. The<br />

elements present at the start of the process were a precursor of the issues with which<br />

both participants and consultants were struggling. The paper demonstrates how the<br />

group drifted away from the intention to find the best solution <strong>for</strong> the child in a<br />

process w<strong>here</strong> all relevant stakeholders were to be involved, and how the interests<br />

and the survival of the organizations started to prevail.<br />

The system psychodynamic perspective on collaborative work allows <strong>for</strong> an<br />

exploration of the interconnection between the nature of the task, the development of<br />

the relationships, and the emergent organizing process. It provides a complementary<br />

view on the phenomenon of 'collaborative inertia' (Huxham, 1996), or the<br />

observation that the output of collaborations is often slowed down or below the<br />

expectations. It helps to understand seemingly ‘irrational’ or emotional behavior<br />

which is often labeled as ‘resistance’ to change, because it points at the emotional and<br />

relational challenges of developing an environment <strong>for</strong> collaboration (Gould et al.,<br />

1999; Long, Newton & Dalgleish, 2000; Page, 2003; Ring & Van de Ven, 1994). Further<br />

research is required to understand the nature and challenges of collaborative<br />

processes in order to develop adequate containing practices and transitional<br />

experiences to facilitate productive and creative change.<br />

241


References<br />

Chisholm, R. & Elden, M. (1993). Features of emerging action research. Human<br />

Relations, 46 (2), 275-297.<br />

Clarke, S. (2002). Learning from experience: psycho-social research methods in the<br />

social sciences. Qualitative Research, 2 (2), 173-194.<br />

Cooper, A. & Dartington, T. (2004). The vanishing organization: organizational<br />

containment in a networked world. In Huffington, C., Armstrong, D., Halton, W.,<br />

Hoyle, L. & Pooley, J.( Eds.) (2004). Working below the surface. The emotional life of<br />

contemporary organizations. London: Karnac, pp.127-150.<br />

Dawson, P. (1997). In at the deep end: conducting processual research on<br />

organisational change. Scandinavian Journal of Management, 13 (4), 389-405.<br />

Edelson, M. (1988). The hermeneutic turn and the single case study in psychoanalysis.<br />

In Berg, D.N. & Smith, K.K. (Eds.), The self in social inquiry. Researching methods.<br />

Newbury Park, Cali<strong>for</strong>nia: Sage Publications, pp. 71-104.<br />

Eden, C. (1996). The stakeholder/collaborator strategy workshop. In Huxham, C. (Ed.)<br />

Creating collaborative advantage. London: Sage, pp. 44-56.<br />

Eden, C. & Huxham, C. (1996). Action research <strong>for</strong> the study of organizations. In Clegg,<br />

S.R., Hardy, C. & Nord, W.R. (Eds.) Handbook of organization studies. London: Sage,<br />

pp.526-542.<br />

Eisenhardt, K.M. (1989). Building theories from case study research. Academy of<br />

Management Review, 14 (4), 532-550.<br />

Feyerherm, A., (1997). Leading M.E.N.: Perspectives on leadership in multi-stakeholder<br />

environmental negotiations. Paper presented at the Academy of Management, Boston.<br />

Flick, U. (2002). An introduction to qualitative research. Second Edition. London: Sage.<br />

Geertz, C. (1973). The Interpretation of Cultures. New York: Basic Books.<br />

Gould, L. (1991). Using psychoanalytic frameworks <strong>for</strong> organizational analysis. In Kets<br />

de Vries, M. (Ed.), Organizations on the couch; clinical perspectives on organizational<br />

behavior and change. San Francisco: Jossey-Bass, pp. 25-44.<br />

Gould, L.J., Ebers, R. & Mc Vicker Clinchy, R. (1999). The systems psychodynamics of a<br />

joint venture: anxiety, social defenses and the management of mutual dependence.<br />

Human Relations, 52 (6), 697-722.<br />

242


Gould, L.G., Stapley, L.F. & Stein, M. (Eds.) (2001). The systems psychodynamics of<br />

organizations. Integrating the group relations approach, psychoanalytic, and open systems<br />

perspectives. London: Karnac.<br />

Gray, B. (1989). Collaborating: finding common ground <strong>for</strong> multiparty problems. San<br />

Francisco: Jossey Bass.<br />

Heller, F. (2004). Action research and research action: a family of methods. In Cassell,<br />

C. & Symon, G. (Eds.). Essential guide to qualitative methods in organizational research.<br />

London: Sage, pp. 349-360.<br />

Hirschhorn, L. & Gilmore, T. (1992). The new boundaries of the “boundaryless”<br />

company. Harvard Business Review, May/June, 70 (3), 104-115.<br />

Hollway, W. & Jefferson, T. (2000). Doing qualitative research differently: free association,<br />

narrative and the interview method. London: Sage.<br />

Hoyle, L. (2004). From sycophant to saboteur – responses to organizational change. In<br />

Huffington, C., Armstrong, D., Halton, W., Hoyle, L. & Pooley, J.( Eds.) Working<br />

below the surface. The emotional life of contemporary organizations. London: Karnac, pp.<br />

87-106.<br />

Huberman, A.M. & Miles, M.B. (1988). Assessing local causality in qualitative research.<br />

In Berg, D.N. & Smith, K.K. (Eds.) The self in social inquiry. Researching methods.<br />

Newbury Park, Cali<strong>for</strong>nia: Sage Publications, pp. 351-381.<br />

Huffington, C., Armstrong, D., Halton, W., Hoyle, L. & Pooley, J.( Eds.) (2004). Working<br />

below the surface. The emotional life of contemporary organizations. London: Karnac.<br />

Huxham, C. (Ed.). (1996). Creating collaborative advantage. London: Sage, 1996.<br />

Huxham, C. & Vangen, S. (2000). Leadership in the shaping and implementation of<br />

collaboration agendas: how things happen in a (not quite) joined-up world.<br />

Academy of Management Journal, 43, (6), 1159-1175.<br />

Huxham, C. & Vangen, S. (Eds.) (2005). Managing to collaborate. The theory and practice of<br />

collaborative advantage. London: Routledge.<br />

Krantz, J. (1998). Anxiety & the New Order. In Klein, B. & Gabelnick, F. & Herr, P.<br />

(Eds.), The psychodynamics of leadership. Madison: Psychosocial Press, 77-107.<br />

Langley, A. (1999). Strategies <strong>for</strong> theorizing from process data. Academy of Management<br />

Review, 24 (4), 691-710.<br />

Lawrence, W.G. & Robinson, P. (1975). An innovation and its implementation: issues of<br />

evaluation, document no. CASR 1069, Tavistock Institute of Human Relations<br />

(unpublished). (cf. Miller, E. (1993). From dependency to autonomy. Studies in<br />

organization and change. London: Free Association Books.)<br />

243


Levinson, H. (1991). Diagnosing organizations systematically. In Kets de Vries (Ed.)<br />

Organizations on the couch. Clinical perspectives on organizational behavior and change.<br />

San Francisco: Jossey-Bass, pp.45-68.<br />

Long, S., Newton, J., & Dalgleish, J. (2000). In the presence of the other: developing<br />

working relations <strong>for</strong> organizational learning. In Klein, E, Gabelnick, F. & Herr, P.<br />

(Eds.) Dynamic consultation in a changing workplace, pp. 161-192.<br />

Mawson, C. (1994). Containing anxiety in work with damaged children. In Obholzer,<br />

A. & Zagier Roberts, V. (Eds.) The unconscious at work. London: Routledge, pp. 67-<br />

74.<br />

Menzies, I. E. P. (1960). A case study in the functioning of social systems as a defense<br />

against anxiety. Human Relations, 13, 95-121.<br />

Miller, E. (1993). From dependency to autonomy. Studies in organization and change.<br />

London: Free Association Books.<br />

Miller, E. (1997). Effecting organisational change in large complex systems: a<br />

collaborative consultancy approach. In Neumann, J.E., Kellner, K. & Dawson-<br />

Sheperd, A. (Eds.) Developing organisational consultancy. Routledge: London, pp.<br />

187-212.<br />

Neumann, J. & Hirschhorn, L. (1999). The challenge of integrating psychodynamic and<br />

organizational theory. Human Relations, 52 (6), 683-695.<br />

Obholzer, A. & Zagier Roberts, V. (Eds.) (1994). The unconscious at work. London:<br />

Routledge.<br />

Obholzer, A. & Miller, S. (2004). Leadership, followership, and facilitating the creative<br />

workplace. In Huffington, C., Armstrong, D., Halton, W., Hoyle, L. & Pooley, J.(<br />

Eds.) Working below the surface. The emotional life of contemporary organizations.<br />

London: Karnac, pp. 33-48.<br />

Page, M. (2003). Leadership and collaboration challenges in not <strong>for</strong> profit partnerships.<br />

Organisational and Social Dynamics, 3 (2), 207-225.<br />

Patton, M.Q. (1987). Qualitative Evaluation Methods. London: Sage.<br />

Pettigrew, A.M. (1997). What is processual analysis? Scandinavian Journal of<br />

Management, 13 (4), 337-348.<br />

Prins, S. (2006, <strong>for</strong>thcoming). The psychodynamic perspective in organizational<br />

research: making sense of the dynamics and emotional challenges of collaborative<br />

work. Journal of Occupational and Organizational Psychology, Special Section ‘Beyond<br />

Positivism and Statistics: Neglected Approaches to Understanding the Experience<br />

of Work’.<br />

Rice, A.K. (1958). Productivity and social organization: the Ahmedabad experiment.<br />

Tavistock. Reprinted, New York and London: Garland Publishing, 1987.<br />

244


Ring, P.S. & Van de Ven, A.H. (1994). Developmental processes of cooperative<br />

interorganizational relationships. Academy of Management Review, 19 (1), 90-118.<br />

Schonberg, A. (1998). Two basic assumptions in the psychoanalytic study of organizations.<br />

Paper presented at the International Society <strong>for</strong> the Psychoanalytic Study of<br />

Organizations Symposium, June.<br />

Sherif, M. (2001). Superordinate goals in the reduction of intergroup conflict. In Hogg,<br />

M.A. & Abrams, D. (Eds.) Intergroup relations. Philadelphia: Psychology Press, pp.<br />

64-70.<br />

Smith, K.K. (1995). On using the self as instrument. Lessons from a facilitator's<br />

experience. In Gillette, J & McCollom, M. (Eds.) Groups in context. A new perspective<br />

on group dynamics. Lanham: University Press of America, pp. 276-294.<br />

Spradley, J. (1980). Participant observation. New York: Holt, Rinehart & Winston.<br />

Stein, M. (2004). Theories of experiential learning and the unconscious. In Gould, L.J.,<br />

Stapley, L.F. & Stein, M. (Eds.) Experiential learning in organizations. Applications of<br />

the Tavistock group relations approach. London: Karnac, pp. 19-36.<br />

Strauss, A. & Corbin, J. (1998). The basics of qualitative research: techniques and procedures<br />

<strong>for</strong> developing grounded theory. Thousand Oaks, Cali<strong>for</strong>nia: Sage.<br />

Trist, E. (1983). Referent organizations and the development of inter-organizational<br />

domains. Human Relations, 36 (3), 269-284.<br />

Turcotte, M.F. & Pasquero, J. (2001). The paradox of multi-stakeholder collaborative<br />

roundtables. The Journal of Applied Behavioral Science, 37 (4), December, 447-464.<br />

Van de Ven, A.H. & Poole, M.S. (2005). Alternative approaches <strong>for</strong> studying<br />

organizational change. Organization Studies, 26 (9), 1377-1404.<br />

Vansina, L. (2002). Making the best of diversity: working towards collaboration between<br />

different interest groups. paper presented at the ISPSO symposium, Melbourne,<br />

Australia, June.<br />

Vansina, L. (2004). Over zin en onzin van psychodynamiek voor organisatieadviseurs.<br />

In Varwijk, W.G.J.M. & van Zijl, R.M.H.J. (Eds.). Strategie moet je samen doen. Visies<br />

op strategisch management uit theorie en praktijk. Ubbergen: Tandem Felix Uitgevers,<br />

pp. 159-177.<br />

Vansina, L., Taillieu, T. & Schruijer, S. (1998). “Managing” multiparty issues: learning<br />

from experience. In Pasmore, W. & Woodman, R. (Eds.). Research in Organizational<br />

Change and Development. (vol. 11). Greenwich, Connecticut: JAI Press Inc., pp. 159-<br />

181.<br />

Winnicott, D.W. (1971). Playing and Reality. Routledge: London.<br />

245


Yin, R.K. (1994). Case study research. Design and methods. Second Edition. Thousand<br />

Oaks, Cali<strong>for</strong>nia: Sage Publications.<br />

Zagier Roberts, V. (1994). Conflict and collaboration. Managing inter-group relations.<br />

In Obholzer, A. & Zagier Roberts, V. (Eds.), The unconscious at work. London:<br />

Routledge, pp. 187-196.<br />

246


PART 4: A SYSTEM PSYCHODYNAMIC PERSPECTIVE ON<br />

DIRECTION SETTING IN COLLABORATIVE WORK<br />

In this research, my aim was to understand the phenomenon of ‘group locomotion’<br />

(Cartwright & Zander, 1960), the nature of ‘the mechanisms that make things<br />

happen’ (Huxham & Vangen, 2000), and identify what makes progression come<br />

about in multiparty collaboration. During the pilot case, it soon became clear that the<br />

notion of ‘distributed leadership’, which I initially adopted to label the phenomenon<br />

I was exploring, was too restricted. For the two following case studies, I used the<br />

more general concept of ‘direction setting’. I explored direction setting by focusing<br />

on the issues and dilemmas characteristic of collaborative work. I defined ‘issue’ as a<br />

theme or dilemma with which participants are confronted as the process unfolds<br />

(Ring & van de Ven, 1994; Huxham & Vangen, 2005). An issue may provoke<br />

questions, tensions or anxiety in the participant(s) or in the collaborative. Unlike<br />

Gray (1989), who identifies direction setting as the second phase of collaborative<br />

<strong>for</strong>mation, I assumed that direction setting was an ongoing process.<br />

I studied three projects in which the conveners wished to develop solutions <strong>for</strong> a<br />

particular problem that they could only solve by involving stakeholder<br />

representatives in some way. I documented how the group of key actors responsible<br />

<strong>for</strong> steering the process (‘project group’) dealt with those issues (observations) and<br />

how the individual participants made sense of issues that were relevant to them<br />

(subjective accounts). This approach allowed me to document fields of tension that<br />

emerged in the process, and how these dynamics influenced the direction and<br />

outcome of the process.<br />

247


The three cases were based on ‘projects’ funded by policy makers and described in<br />

<strong>for</strong>mal contracts. The starting conditions (e.g. the <strong>for</strong>mal task description, deadline)<br />

influenced the process be<strong>for</strong>e the collaborative endeavor <strong>for</strong>mally started. In the<br />

analyses, it became apparent that <strong>for</strong>ces other than the interventions of individuals<br />

taking up a leading function had an influence on the direction and outcome of the<br />

process. The issues I have identified in this research relate to the starting conditions<br />

and context of the collaborative, the task and objectives, the way in which the process<br />

was organized, and to the nature and development of the relationships between the<br />

participants (see table 12). By using the systems psychodynamic perspective in the<br />

study of direction setting, I was able to develop a complex and systemic perspective<br />

on direction setting in collaborative practice. This framework allowed me to<br />

interconnect the different types of issues: the task, the relationships, the system<br />

features, and the particular context in which the collaborative was embedded.<br />

Issues in direction<br />

setting<br />

Context and starting<br />

conditions<br />

Task and collaborative<br />

aims<br />

248<br />

Sub-issues<br />

- Antecedents of the collaborative ef<strong>for</strong>t<br />

- Characteristics of the domain<br />

- Players in the context<br />

- Events and changes in the environment<br />

- Shared sense of urgency<br />

- Normative primary task<br />

- Existential task<br />

- Phenomenological task


Structuring of the<br />

process and boundary<br />

management<br />

Collaborative<br />

relationships,<br />

relatedness and<br />

dynamics<br />

- Minimal structure<br />

- Structuring of the domain: stakeholder analysis and<br />

involvement<br />

- Formal and in<strong>for</strong>mal roles<br />

- Formal and in<strong>for</strong>mal structures and interventions<br />

- Working with diversity<br />

- Developing an interdependent relationship<br />

- Collusive behavior<br />

Table 12: Issues and sub-issues in direction setting.<br />

In this concluding chapter, I describe each issue and illustrate it with case material<br />

from the three cases. I discuss how the participants in the different cases made sense<br />

of them, and how this influenced the direction of the process. Although I discuss the<br />

issues separately, in practice they are closely interconnected. By comparing the cases<br />

my aim is to draw conclusions that point at commonly observed themes and<br />

dilemmas in collaborative work. In the discussion, I balance the contextualized<br />

insights specific <strong>for</strong> a particular case, with more general conclusions that can be<br />

relevant <strong>for</strong> similar contexts. The case examples used in this concluding chapter, are<br />

based on the case discussions in the four articles included in this work. I conclude<br />

this final part with some reflections on new requirements <strong>for</strong> designing and<br />

facilitating emergent inter-organizational processes.<br />

1. CONTEXT AND STARTING CONDITIONS<br />

All cases demonstrated that the starting conditions and the context in which the<br />

collaborative ef<strong>for</strong>t took place influenced direction setting. The ‘context’ refers to<br />

249


different sub-issues of contextual influence that represent the ‘t<strong>here</strong>-and-then’<br />

influencing the ‘<strong>here</strong>-and-now’ of the process.<br />

1.1. Antecedents of the collaborative ef<strong>for</strong>t<br />

Often the collaborative project was a ‘paid episode’ in an ongoing process.<br />

Sometimes it also brought people around the table who had never worked together.<br />

T<strong>here</strong><strong>for</strong>e, it was critical to assess the historical context and the events leading up to<br />

the start of the projects to understand how this may have influenced the process.<br />

In foster care the project was intended to intensify ongoing attempts to collaborate and to move<br />

collaboration beyond ‘safe domains’. The individual drive of the convener started the process.<br />

A welfare policy moving towards rationalization, a regional organization of assistance, and the<br />

possibility of imposed mergers, helped the convener to convince the parties in the project that<br />

collaboration was necessary and inevitable in the future. The good relationships between the<br />

managers, the regional consultation plat<strong>for</strong>m, and established agreements helped the project to<br />

come off the ground. The close collaboration that existed between two of the five services was<br />

helpful (model function). A dramatic shortage of foster families increased political interest in<br />

foster care. However, the participants experienced the unexpected start as a drawback; they felt<br />

unprepared and taken by surprise. Some incidents between the liberal service and the other<br />

services had resulted in caution and suspicion. The position of foster care in welfare influenced<br />

the way in which the representatives of foster care positioned themselves in relation to the other<br />

players in the domain (‘underdog position’). For instance, the managers were reluctant to<br />

involve stakeholders, supposedly because stakeholders were not going to be interested, they<br />

would be critical, or not show up at all. As demonstrated in the case analysis, this assumption<br />

influenced the exclusion of stakeholder representatives from active participation in the process.<br />

The foster care services participating in the collaborative had emerged from conflicts and splits<br />

based on ideological differences. Their sense of autonomy and identification with their<br />

organization was exacerbated by a context w<strong>here</strong> rivalry <strong>for</strong> resources was installed by the<br />

subsidizing logic of the government. These proved to be big obstacles to structural<br />

collaboration.<br />

In the erosion case the ‘connections’ of the convener facilitated the conception of the project. He<br />

had strong business relationships with the municipalities, he personally knew a political<br />

representative, and he knew how to apply <strong>for</strong> European funds. Heavy rainfall had put erosion<br />

on the agenda of local politicians. However, other antecedents made it hard to move the project<br />

ahead. For instance, the farmers had had bad experiences with similar projects. They were<br />

skeptical about the good intentions of the engineers and about their potential benefits. Many<br />

were reluctant to sign up <strong>for</strong> the project. This seriously jeopardized the project, because<br />

participation of the farmers was critical to achieve success.<br />

The river valley project profited from an increased societal and political awareness of the<br />

importance of ecological values, ongoing studies in the valley, severe flooding in 1998, and a<br />

European policy stressing the environmental agenda. A Minister from the ecologic party had<br />

approved the project. Moreover, the convening organizations trusted each other and had had<br />

good experiences in other projects. The conveners were confident to take the lead of the project,<br />

because they assumed that the transfer of authority over the river to their administration was<br />

imminent. Initially this facilitated the process. Other antecedents hindered collaboration. The<br />

relationship between the convening organizations and some stakeholders in the valley (e.g.<br />

municipalities, farmers) had been troubled by conflicts. This had damaged the reputation of the<br />

conveners to some extent and t<strong>here</strong> was mutual stereotyping. Their relationship with the<br />

250


authority over the river was also antagonistic due to, <strong>for</strong> instance, severe conflicts over the<br />

illegal construction of dams in the valley. This increased the potential <strong>for</strong> conflict in the project.<br />

It is important to assess the antecedents and starting conditions of a project or<br />

collaborative enterprise. The convener, who is closely involved in the start-up of a<br />

collaborative, can help to raise those issues in the <strong>here</strong>-and-now discussions in the<br />

collaborative as a basis <strong>for</strong> establishing common ground.<br />

1.2. Characteristics of the domain<br />

The specific nature of the inter-organizational domain also influenced the evolution<br />

of the process. In all cases, the domains were turbulent, complex and the<br />

stakeholders in the domain were interdependent.<br />

During an in<strong>for</strong>mation session in the erosion project, the farmers were relieved that they were<br />

not the only party held responsible or blamed <strong>for</strong> the problem of erosion. The collective<br />

problem analysis demonstrated the interdependent nature of the problem domain. The analysis<br />

on visual cards on the walls showed how at different points in the chain different actors were<br />

responsible <strong>for</strong> the problem and how each could contribute to solving the problem. This<br />

increased commitment of the stakeholders, at least in the initial phase.<br />

In the foster care case, the stakeholder analysis helped to visualize the stakeholders in the<br />

domain, the way they were interconnected, and the place of the services in the intricate web of<br />

connections. It convinced the managers of the project group that it was important to hear the<br />

voice of all relevant stakeholder representatives. By listening to the hopes, worries and<br />

suggestions of the stakeholders, the reality of the domain was introduced in the process.<br />

The river valley case took place in the domain of natural resources, with a high potential <strong>for</strong><br />

conflict. Turbulence in the environment disturbed the process. Many changes were occurring at<br />

the same time. The administrations in the domain were in the middle of reorganization. T<strong>here</strong><br />

was a change in political leadership in the domain that reduced the importance of the ecologic<br />

agenda. During the meetings, the participants hardly talked about these issues and how they<br />

may have affected the collaborative.<br />

Although the participants often had little influence on issues in the wider domain, a<br />

better awareness of the nature of the domain could help them to understand why, <strong>for</strong><br />

instance, it was sometimes hard to move things ahead. It was obvious in most cases<br />

that participants had difficulty to deal with the complexity, interdependence and<br />

turbulence of the domain. As demonstrated in the group dynamic literature, groups<br />

tend to be solution and action-oriented (Maier, 1963). In many cases, the key actors<br />

shut out part of reality in an attempt to move the process ahead (e.g. internal focus in<br />

foster care). Group members did not spontaneously engage in a broad analysis of the<br />

251


problem or an exploration of the context in which the group was embedded.<br />

However, system awareness is critical in a process that is strongly influenced by<br />

external issues.<br />

1.3. Players in the context<br />

In all projects, players in the context influenced the process. These so-called ‘invisible<br />

ghosts’ were sitting at the table and represented the ‘unknown’. In a collaborative,<br />

this often leads to speculations and assumptions about intentions, resources and<br />

power of these players (Vansina, 2002). In the three cases, the representatives<br />

assumed that <strong>for</strong>ces from the outside influenced the agenda or outcome of the<br />

process. Different kinds of players can influence the collaborative from the outside.<br />

1.3.1. Absent stakeholders: authorities in the environment<br />

In the cases, the participants believed authorities and institutions in the environment<br />

holding power influenced the process.<br />

In foster care many employees believed that the hidden agenda of policy makers was a merger<br />

of the services. Some feared the project would weaken the position of foster care in negotiations<br />

with policy makers and that it would make it easier <strong>for</strong> policy to cut expenses<br />

In the river valley case participants speculated that the results of the project could easily be put<br />

aside. Some feared that politicians would throw away their work in the interest of their<br />

personal agenda.<br />

In the three cases, the most influential invisible player was the sponsoring<br />

administration or organization. On the one hand, funding organizations provided<br />

opportunities: resources to solve a problem, space <strong>for</strong> experimentation and<br />

discovery, the chance to learn from each other, or the opportunity to realize a dream.<br />

On the other hand, sponsors also imposed their restrictions, such as a tight deadline,<br />

a predefined output, insufficient time <strong>for</strong> meetings, or high demands in terms of<br />

reporting. They had the power to stop or extend funding, to implement the solutions<br />

or not, to support the process or to obstruct it. The participants were accountable to<br />

these commissioners. The sponsors thus maintained power over the domain.<br />

The objectives of the foster care project (‘reception function’) reflected the agenda of the policy<br />

makers. They granted resources to the services (e.g. external facilitation), but also imposed the<br />

252


equired output. The procedural nature of the contract was in contradiction with the emergent<br />

stakeholder approach proposed in the project. This resulted in paradoxical starting conditions.<br />

The participants were bounded by the contract with the sponsors. They felt the tension between<br />

the need to fulfill the requirements of the contract (e.g. produce results be<strong>for</strong>e the deadline) and<br />

the necessity to take time <strong>for</strong> the process and work out what they really wanted to achieve<br />

together. The authorities had created an ironic situation. On the one hand, they funded a project<br />

to develop structural collaboration, but on the other hand, they did not question or change the<br />

subsidizing mechanism that rein<strong>for</strong>ced rivalry <strong>for</strong> resources. By creating this paradoxical<br />

situation, the authorities remained in control and played the services off against each other. The<br />

managers of the project group felt deserted by the policy makers. In the interviews, many<br />

‘internal’ stakeholders expected support and facilitating conditions from the authorities. They<br />

hoped policy makers would provide a clear framework, assess the quality of assistance in foster<br />

care, reward collaboration, and change the ‘perverse’ subsidizing mechanisms.<br />

The contract with authorities in the environment influenced the daily work of the<br />

collaborative. It was not always clear, however, to what extent the participants<br />

needed to strictly follow the contract. It was as if they could not question, adapt or<br />

renegotiate the initial contract terms with the sponsors. The sponsoring organization,<br />

as a critical party, was not involved in the process.<br />

In the stakeholder interviews in the foster care case most interviewees identified the subsidizing<br />

logic as the main obstacle to collaboration between the services. However, the managers did not<br />

discuss this with the policy makers. They were not involved in the process. The managers soon<br />

realized that the <strong>for</strong>mal objectives of the project were unrealistic. However, they carried on and<br />

decided to focus on process objectives (e.g. get to know one another, learn from each other).<br />

They suggested setting up a meeting with the sponsoring organizations, but this never<br />

happened. Only at the very end of the project, they reported to the funding organizations. The<br />

managers strongly felt they needed to justify why they did not meet the <strong>for</strong>mal objectives of the<br />

project.<br />

Usually t<strong>here</strong> was only direct contact between conveners of the collaborative and the<br />

sponsors be<strong>for</strong>e the start (negotiation of contract) and after the project (reporting and<br />

evaluation). The sponsors were not involved in the daily operations of the projects.<br />

Often, the participants complained about shortcomings of funding, in<strong>for</strong>mation or<br />

other resources, as if otherwise the task would have been easy to accomplish. The<br />

participants often seemed to deny the impact of external players, which may have<br />

been a defense against feeling powerless and vulnerable.<br />

As a collaborative process is emergent, it is recommended to establish space <strong>for</strong><br />

renegotiation during the process in order to adapt to changes within the<br />

collaborative and in the environment. Inclusion of a representative of the sponsoring<br />

253


organization in a ‘steering group’, <strong>for</strong> instance, can establish a closer link with the<br />

sponsors as stakeholders. This would allow <strong>for</strong> feedback and adaptation on a regular<br />

basis. This finding also points at the need to engage in collaborative ‘thuggery’,<br />

which includes ‘playing politics’ in order to move the process <strong>for</strong>ward (Huxham &<br />

Vangen, 2003). The participants need to be in contact (in<strong>for</strong>mation, consultation,<br />

active involvement) with players in the context and thus influence the process by<br />

working across the boundaries of the collaborative.<br />

1.3.2. Absent stakeholders: assumed power centers<br />

Sometimes still different authorities, not <strong>for</strong>mally represented in the collaborative,<br />

influence the process. The participants assume that these so-called ‘super-ghosts’<br />

organize, fund or control some stakeholders behind the scene (Vansina, 2002).<br />

In the interviews in the foster care case some speculated that the ‘institutional lobby’ or the<br />

‘invisible liberal network in welfare’ were in control behind the scenes. These speculations were<br />

not openly discussed and made some cynical about the chances <strong>for</strong> success.<br />

Such assumptions may provoke tensions, a decrease in motivation, suspicion or<br />

distrust. The participants can also use those invisible power centers to blame them<br />

<strong>for</strong> the lack of success or progress on the task. Conveners or facilitators can try to<br />

check the speculations in order to test reality and take away the influence of those<br />

invisible partners over the process.<br />

1.3.3. The constituencies of the representatives in the collaborative<br />

A ‘ghost’ may also refer to the constituencies of the representatives that influence the<br />

process (Vansina, 2002). In all cases, the representatives experienced the presence of<br />

their constituency.<br />

In the river valley case, some participants were cynical about experimenting with participative<br />

methods. The head of their department was openly critical about actively involving<br />

stakeholders in the process. In his opinion, the multiparty perspective represented by the<br />

researchers was ‘academic’ and unrealistic.<br />

I will discuss the specific role of representatives in relation to their constituency in<br />

the section on ‘roles’.<br />

254


1.3.4. Absent stakeholders: excluded voices<br />

The case studies also demonstrated another kind of absent party. In most cases, the<br />

voice of a number of legitimate stakeholders was not heard and not <strong>for</strong>mally<br />

represented in the collaborative.<br />

In the foster care project the foster children and natural parents were not heard and not invited<br />

or included in any other way even though they were the core stakeholders (‘users’) in the<br />

domain. They represented the emotional aspects of what was happening in the field and the<br />

pain of failure to take care of children in a problematic situation, both by the natural parents<br />

and by the services. The key actors seemed to have shut them out from the process because a<br />

confrontation could have been too hard to deal with.<br />

In the river valley case the public was not represented. Although the conveners argued that the<br />

local authorities <strong>for</strong>mally represented the voice of their community, they admitted at the same<br />

time that in practice these did not speak in the interests of the public. They expected citizens<br />

who did not agree, to turn to the <strong>for</strong>mal procedure that was set up after the plans were finalized<br />

(‘public hearing’).<br />

It seems paradoxical, but often the critical stakeholders were not actively included or<br />

represented in the collaborative (e.g. clients, users, sponsors). The danger of not<br />

including important stakeholders is that they jeopardize the implementation of the<br />

solutions or sabotage the ef<strong>for</strong>ts of the collaborative.<br />

1.4. Events and changes in the environment<br />

Events and changes in the context that occurred during the process frequently<br />

proved to be important <strong>for</strong> the collaborative. Sometimes changes in the environment<br />

gave a boost to the process.<br />

The success of a neighboring project in welfare supported the foster care project. The new<br />

Minister of welfare who was appointed during the project, demonstrated interest in foster care.<br />

For instance, she unexpectedly turned up at a meeting of the Federation <strong>for</strong> foster care.<br />

In the erosion case the approaching local elections initially helped to involve the local<br />

authorities in the project. One political representative, <strong>for</strong> instance, invited over 100 farmers to<br />

the in<strong>for</strong>mation session at his municipality.<br />

However, many times external events disrupted the process. In all cases, t<strong>here</strong> was a<br />

change in political representation that jeopardized the work. Turnover always means<br />

a restarting of the clock, which slows down the process (Ring & van de Ven, 1994).<br />

255


In the erosion case t<strong>here</strong> was no decision making <strong>for</strong> nine months after the new representatives<br />

of a different political party had taken over (municipal elections). Another external event<br />

seriously disrupted the process. The corporation of the technical engineers was restructured. It<br />

had acquired the small firm of the participative engineers, also involved in the project.<br />

Management decided to hand over project leadership to the participative engineers. This<br />

further emphasized the rivalry between the two engineering groups. The participative<br />

engineers had to facilitate a process they had not designed. They had not chosen the partners,<br />

nor negotiated with the local authorities. Half way the project, the Flemish authorities issued a<br />

new erosion policy. It offered more financial compensation to the farmers (75%) than the<br />

European project (50%), which made participation in the project less attractive <strong>for</strong> the farmers.<br />

A Minister from the ecologic party had approved the river valley project. During the project, a<br />

new Minister from a different party, was elected. This blew away all the hope of the conveners<br />

that authority over the river would be transferred to their administration. It undermined the<br />

authority of the conveners and represented a threat to the study. Some started to doubt whether<br />

the plan would ever be approved or implemented. One of the representatives considered<br />

changing jobs, because he was daunted by the influence of politicians on his work. He found it<br />

hard to accept that the work of so many people, over so many months, could simply be put<br />

aside.<br />

This demonstrates the importance of paying attention to the effects of turnover and<br />

changes in representation. Careful briefing and contracting can help to ensure<br />

continuity. Changes in political representation are much harder to deal with because<br />

newly elected or appointed politicians usually have little respect <strong>for</strong> the work of their<br />

predecessors.<br />

Handbooks on participation promote the idea of external communication and public<br />

relations in order to reach out and foster support in the environment (e.g. ‘outreach’,<br />

HarmoniCop, 2005).<br />

The workgroup ‘recreation’ in the river valley project visited a similar project in Flanders. They<br />

learned that communication with the public is critical to create goodwill. The project leader of<br />

this initiative emphasized the importance of having a ‘brand name’ and an appealing vision <strong>for</strong><br />

the future to facilitate acceptance of unpopular decisions (e.g. close a road going through a<br />

natural park). Later in the project, the conveners set up a public website and produced some<br />

newsletters and articles.<br />

It is important <strong>for</strong> a collaborative to build relationships across the boundary of the<br />

initiative and to pay attention to <strong>for</strong>ces in the external environment that can either<br />

help or hinder the process.<br />

256


1.5. Shared sense of urgency<br />

The initial motivation to start up a collaborative often originates in the environment.<br />

Policy makers, organizations or social groups become aware of a problem in the<br />

domain and experience some sense of urgency. Vansina (2002) refers to the<br />

‘emotional context’ of a collaborative: the felt urgency to solve a problem and the<br />

shared level of awareness that a collaborative approach is required to solve it. The<br />

motive <strong>for</strong> collaborating can be an urgent or important problem in the domain (e.g. a<br />

severe flood, a sudden shortage of foster families). However, other motives can also<br />

trigger a collaborative initiative. These include, a charismatic and committed<br />

convener, the availability of funding, a crisis in the environment, the threat of<br />

survival <strong>for</strong> single organizations, circumstances, or existing relationships based on<br />

previous collaborative experiences.<br />

As demonstrated in the erosion case t<strong>here</strong> was no shared sense of urgency to solve the problem<br />

of soil erosion because many participants did not experience it as a problem. T<strong>here</strong> had been<br />

erosion in the area <strong>for</strong> hundreds of years. Only the soil experts were worried about the loss of<br />

fertile soil because of the impact on the wider environment and the loss of the ‘history’<br />

represented in the different layers of soil.<br />

Initially t<strong>here</strong> was a sense of urgency in foster care. The convener was convinced it was critical<br />

to collaborate with the stakeholder groups identified in the project proposal. Her personal drive<br />

and enthusiasm helped to set up the project in order to make her dream come true. She<br />

understood that a proactive response could avoid an imposed merger. However, as the process<br />

unfolded, the sense of urgency dropped. The consultants tried to introduce a sense of urgency<br />

in the system, by presenting the results from the stakeholder interviews. At one point, they<br />

became the driving <strong>for</strong>ce, convincing the managers that collaboration was critical. T<strong>here</strong> were<br />

no meetings during the summer months. The approaching deadline (an external element) put<br />

pressure to move on and take decisions.<br />

In the river valley case the conveners were convinced that the problem they were trying to solve<br />

was important and urgent. They talked about the ‘ultimate study’ as if it would solve all the<br />

problems in the valley <strong>for</strong>ever. The conveners were passionate about their project and spent<br />

much more time than <strong>for</strong>eseen to make things happen. They were also aware of the need to<br />

involve stakeholders in order to foster support <strong>for</strong> their plan. However, they were uncertain on<br />

how to organize participation. They also gradually realized that <strong>for</strong> other parties the study was<br />

not as critical or urgent.<br />

A shared sense of urgency helps a collaborative to get started. In the course of the<br />

process, the participants have to deal with their individual motives <strong>for</strong> engaging in<br />

the collaborative. They often realize that they are ‘doomed to work together’ which<br />

may help to enhance the motivation <strong>for</strong> change and the sense of urgency. An<br />

important role <strong>for</strong> those leading or facilitating a collaborative is to stress the<br />

257


elevance, importance and sense of urgency of the change by using a collaborative<br />

strategy and to maintain this awareness during the process.<br />

In this research, I assumed that the members of the ‘project group’ played out the<br />

dynamics of the wider system in which the group was embedded (Vansina, 2007).<br />

The constituencies and other players in the environment represent multiple<br />

stakeholders in the context that powerfully influence the dynamics within the<br />

collaborative. By focusing on the system-in-interaction (e.g. meeting of a project<br />

group), it is difficult to capture the dynamics in the context and to assess how they<br />

influence the dynamics within the boundaries of the system. Those in charge of<br />

leading the process can increase contextual understanding by, <strong>for</strong> instance,<br />

interviewing stakeholders, organizing large group interventions w<strong>here</strong> the<br />

representatives of the domain are all present in a room (e.g. search conference), or by<br />

engaging in a ‘system-oriented assessment’ (Levinson, 2002; Harrison, 2005). The<br />

findings in this research point at the relevance of focusing on adaptive processes in<br />

collaborative groups or how members respond to the events and changes in the<br />

embedding system of ‘boundary-less’ work systems (Hirschhorn & Gilmore, 1992;<br />

McGrath & Tschan, 2004; Vansina, 2007).<br />

2. TASK AND COLLABORATIVE AIMS<br />

It seems obvious that clear and shared objectives and an agreed upon direction are<br />

conditions to move a collaborative process <strong>for</strong>ward. T<strong>here</strong> is, however, a difference<br />

between this common wisdom and common practice, which demonstrates that<br />

lasting agreement on the direction is difficult to establish (Huxham & Vangen, 2005).<br />

The cases show that the task and aims of the collaborative were often ambiguous.<br />

Making sense of the task was a critical dynamic in the projects.<br />

In the system psychodynamic tradition, the ‘primary task’ refers to the task the<br />

organization has to per<strong>for</strong>m in order to survive (Rice, 1958; Miller, 1993). This<br />

258


concept, however, is no longer relevant in organizing processes in a turbulent<br />

environment. A critical difference between organizations and multiparty<br />

collaboration is the self-designing nature of the task. Even though t<strong>here</strong> usually is a<br />

<strong>for</strong>mal task (e.g. written down in a project text), participants need to make sense of,<br />

negotiate and define the task they want to be working on. In emergent and dynamic<br />

<strong>for</strong>ms of organizing, such as multiparty collaboration, the primary task also needs to<br />

be constantly reviewed and adapted in the light of the changing environment and<br />

changes within the collaborative. Feyerherm (1994) refers to the importance of ‘going<br />

back to base camp’ in order to (re)interpret the purpose of collaboration. For instance,<br />

when membership changes the participants need to reconsider the collaborative<br />

aims. T<strong>here</strong> is a mutual influence between the nature of participating organizations<br />

and the goal of the collaboration: the focus defines the participants and the<br />

participants define the focus (Huxham & Vangen, 1996).<br />

In the river valley case the conveners needed to adapt their agenda from the moment they<br />

invited the administration responsible <strong>for</strong> the river under study (civil engineers) to the<br />

coordination committee. The aims turned to a more realistic scenario integrating the needs and<br />

expectations of, <strong>for</strong> instance, the municipalities (safety against flooding) and farmers (financial<br />

compensation). The presence of the civil engineers made the conveners realize they had to take<br />

the technical feasibility, the restrictions, and the financial consequences of potential<br />

interventions into account.<br />

A distinction between different aspects of the primary task, proposed by Lawrence<br />

and Robinson (1975), helps to make sense of what happened to the task in the<br />

different projects. In this research, I was primarily interested in the differences<br />

between what people say they are doing or would like to do, and what they actually<br />

do in practice. This was an important issue in the three projects. The ‘normative’<br />

primary task is the task on which representatives in the collaborative should be<br />

working. External authorities (e.g. sponsoring organization) often dictate the<br />

normative task. The ‘existential’ primary task is the task the participants believe they<br />

are carrying out, which is often reflected in the rhetoric they use (e.g.<br />

“participation”). The ‘phenomenal’ task is the task representatives are actually<br />

engaged in (Hoyle, 2004). This task emerges as a result of how participants make<br />

sense of the task, which is enacted in their interactions and in the way in which they<br />

259


organize the process. This distinction between different aspects of the primary task<br />

helps to clarify the observed changes in the task, and the way in which participants<br />

dealt with the primary task.<br />

2.1. The normative primary task<br />

The <strong>for</strong>mal objective, or the task the representatives should be working on, was<br />

written down in the contract with the sponsoring organization. In most cases, the<br />

convener(s) proposed a task description to convince funding organizations to<br />

provide resources. T<strong>here</strong><strong>for</strong>e, it was usually phrased in ‘politically correct’ terms. For<br />

instance, in the erosion and foster care cases the conveners used specific jargon with<br />

a strategic aim. Both conveners and funding agencies t<strong>here</strong><strong>for</strong>e had a strong impact<br />

on the normative primary task, which set the agenda from the start. Huxham and<br />

Vangen (2005) talk about ‘external’ aims, because collaborative aims are often related<br />

to government policy drives or other external pressure. Conveners also used the<br />

normative task to convince stakeholders to participate in the process. It provided a<br />

trigger or reason to assemble representatives around the table.<br />

In the foster care project the normative task (development of a ‘reception function’) which was<br />

introduced in a project proposal, was the starting point. This objective was aligned with the<br />

one-stop shopping philosophy of policy makers. It set the agenda of the project and strongly<br />

influenced the direction of the process.<br />

At the start of a process, participants assess whether the task is sufficiently<br />

interesting to commit themselves (Mills, 1967). They need to figure out what they can<br />

potentially get out of participation: ‘what’s in it <strong>for</strong> me?’ (Gray, 1989). The normative<br />

task is the starting point <strong>for</strong> exploration of individual and collaborative aims. A<br />

‘plan’ or <strong>for</strong>malized objective provides participants with a reason to sit around the<br />

table to talk about the future. While participants explore what the collaborative is<br />

about and whether they want to commit themselves, they are in the process of<br />

building a relationship. Participants usually assume t<strong>here</strong> is agreement on the task,<br />

but often this is not the case.<br />

260


A striking observation was that in some cases the <strong>for</strong>mal task, which was expressed<br />

in terms of a solution, was not thoroughly explored.<br />

In the foster care project the consultants realized that a ‘reception function’ was a solution <strong>for</strong> a<br />

problem that had not yet been systematically explored and t<strong>here</strong> was no agreement on the<br />

problem definition. The interviewers decided to stop talking about the reception function. Soon<br />

after, however, the convener reprimanded the interviewers; she argued that the notion<br />

‘reception function’ was the reason <strong>for</strong> being engaged in the project in the first place. Some<br />

interviewees did wonder <strong>for</strong> what problem the reception function was going to be the solution.<br />

The <strong>for</strong>mal objective of the river valley study was to develop an ‘integrated’ plan <strong>for</strong> the valley.<br />

The conveners were hoping <strong>for</strong> an ‘ideal’ plan. This implied a future scenario <strong>for</strong> the valley,<br />

which maximally guaranteed their interests. The ecological agenda was dominant and their<br />

objectives could not be questioned.<br />

In some cases (e.g. foster care) the normative task was ambiguous. Turcotte and<br />

Pasquero (2001) argue that a certain degree of ambiguity can be strategic in the sense<br />

that it deals with the diversity of objectives present in the system.<br />

In the first phase of the erosion project, the second project leader constructed a joint problem<br />

definition with interested stakeholders in the area, based on the <strong>for</strong>mal task description.<br />

However, in the project group t<strong>here</strong> was no agreement between the two consulting firms on the<br />

meaning of the task of the project. As the group did not openly discuss this, it resulted in<br />

polarization and sub-grouping.<br />

The task, which in itself is neutral, can function as a ‘transitional object’ (Winnicott,<br />

1971) and acquire an emotional meaning. It can help those involved in a change<br />

process to deal with the uncertainty and openness of the process, connect them to<br />

each other, feel committed to a joint enterprise, and adapt their internal world to an<br />

anticipated external world (Vansina, 2004).<br />

The normative task in foster care was to develop a ‘reception function’. Initially this concept<br />

gave an identity to the collaborative ef<strong>for</strong>t and helped to start discussions on the desirable<br />

future. As the process unfolded, it became clear t<strong>here</strong> was no agreement or shared meaning of<br />

the notion reception function. It generated different images and fantasies and provoked<br />

different emotional responses ranging from hope to fear. The question ‘what do we want to<br />

achieve together’ remained unresolved.<br />

This points at common group phenomenon; participants assume they share the same<br />

assumptions about the nature of the task. Often they do not openly explore the<br />

different perspectives on the task. Group members and consultants escape in an<br />

inspiring vision of the future and try to convince participants to endorse the vision<br />

(Vansina, 2002). This enables them to avoid the tensions in the ‘<strong>here</strong>-and-now’ as a<br />

261


esult of exploring how the interests of all participants can be integrated. In the cases,<br />

the groups colluded in a shared, implicit assumption that they knew what they were<br />

working on.<br />

2.2. The existential task<br />

The existential task was the task the participants believed they were working on. In<br />

the cases, it became apparent that different stakeholders made different sense of the<br />

task. Sometimes they openly talked about it and sometimes they left it implicit.<br />

In foster care most participants believed they were in the process of establishing collaborative<br />

relationships in order to provide better solutions <strong>for</strong> the children. However, some thought they<br />

were merely engaged in a research project to assess the possibilities of collaboration. Others<br />

postponed their plans to move building because they expected changes that would affect the<br />

location of their personnel.<br />

In the erosion case the participative engineers and psychologists thought they were facilitating<br />

a multi-stakeholder process in order to experiment with new anti-erosion measures and to learn<br />

from those experiences. The technical engineers and representatives of the municipalities<br />

believed they were developing technical solutions (e.g. large water basins) <strong>for</strong> real problems.<br />

From their perspective, consultation of stakeholders was only meant to improve their technical<br />

plans.<br />

This refers to the process of ‘issue framing’. A frame is determined by the<br />

(professional, social) group to which stakeholders belong and by the context. As<br />

different actors perceive a situation with a different frame, they consider different<br />

aspects as problematic and propose different solutions. Parties in a joint initiative<br />

will position themselves and others by the way in which they frame, and eventually<br />

reframe, the issue under consideration. In the interactions, some frames can be more<br />

dominant than others (e.g. Dewulf, Craps, Bouwen, Taillieu & Pahl-Wostl, 2005).<br />

For the conveners in the river valley case the study was an ‘engineering contract’ <strong>for</strong> policy<br />

preparation. They did not see it as a project focusing on ‘facilitation of a process’. The project<br />

proposal reflected this assumption. T<strong>here</strong> was no budget or plan <strong>for</strong> ‘communication’. For the<br />

engineers it was a technical study; <strong>for</strong> the municipalities it was about flood prevention; <strong>for</strong> the<br />

administrations in the domain of nature and <strong>for</strong> non-governmental organizations, the task was<br />

about nature conservation or even nature development.<br />

The rhetoric used by the participants revealed the perspectives on the existential<br />

task.<br />

The conveners of the river valley study often publicly talked about participation and the<br />

importance of an ‘integrated’ and broadly supported plan. They believed they were involving<br />

262


the stakeholders. However, their tight control over the process, the rare opportunities <strong>for</strong> direct<br />

interaction, and the structured nature of the meetings with stakeholder representatives reduced<br />

the impact of the stakeholders. T<strong>here</strong> was a contradiction between the rhetoric of organizing a<br />

participatory process and the underlying assumption of the conveners that the objectives of the<br />

study could under no circumstances be questioned.<br />

The managers and consultants in foster care talked about ‘stakeholders’; however, the meaning<br />

of that word was reduced to the persons working in the foster care services. During the second<br />

‘stakeholder conference’, <strong>for</strong> instance, no external stakeholders were invited.<br />

It seems critical to explore the meaning behind of words that are used in a<br />

collaborative by, <strong>for</strong> instance, the convener, sponsoring organizations or consultants.<br />

Different assumptions and sense making of words (e.g. ‘participation’) has<br />

consequences <strong>for</strong> the way in which the process is organized. A shared understanding<br />

of words or jargon can help to avoid empty rhetoric that creates unfulfilled<br />

expectations. If participants negotiate the existential task, this can result in a shared<br />

and agreed task (common ground). If this shared existential task aligns with the<br />

phenomenological task and with the normative task, it has the potential to mobilize<br />

the group and set the direction of the process.<br />

2.3. The phenomenological task<br />

The phenomenological task is the task in which the participants are actually engaged.<br />

Based on my observations and on interviewing, I was able to make sense of the<br />

phenomenological task that emerged as the process unfolded. It revealed the<br />

differences between what people claimed they were doing and what they were<br />

actually doing. In the case analyses, I have used the system psychodynamic<br />

framework to make sense of this phenomenon.<br />

In foster care the phenomenological task that gradually came to the <strong>for</strong>eground was a<br />

reorganization of the services. The managers were not prepared to give up their autonomy or to<br />

jeopardize their identity with the change. The existential task, finding optimal solutions <strong>for</strong> the<br />

child, disappeared in the background.<br />

Gradually the convener in the river valley project realized t<strong>here</strong> was no ‘best’ solution. The<br />

names of the scenarios that were developed reflected this evolution; these changed from ‘ideal’<br />

to ‘optimal’ to ‘compromise’ scenario. The conveners admitted, towards the end of our research,<br />

that they had hoped and assumed that a technically perfect scenario would provide the<br />

solution. They said they had secretly hoped a waterproof plan would avoid conflicts with the<br />

stakeholders in the valley.<br />

263


The cases demonstrated a tension between the need to clarify and define the task in<br />

order to develop common ground, and the risk and reluctance to make the<br />

individual perceptions on the task explicit. Some participants argued they were<br />

afraid of a conflict that could endanger their participation in the collaborative or<br />

could be embarrassing others. For the facilitators of the process it was not always<br />

easy to deal with this. An explicit intervention referring to ‘hidden agendas’, <strong>for</strong><br />

instance, can do more harm than good, especially if trust is not yet developed<br />

(Harrisson, 1970). In the foster care case, the pressure to put the cards on the table led<br />

to the exclusion of one key actor. Huxham and Vangen (2005) also observed that<br />

explicit sharing of understanding of the task and the attempt to <strong>for</strong>mulate<br />

collaborative aims sometimes reveals differences that are hard to bridge. This may<br />

lead to greater inertia instead of setting the direction <strong>for</strong> constructive, collective<br />

action.<br />

The participants often experienced the latent tension between individual and<br />

collaborative aims.<br />

In the erosion project t<strong>here</strong> was a shift in the task. As the technical engineers had more power<br />

and became dominant again towards the end of the project, their influence on the task<br />

increased. It changed from experimentation with state of the art anti-erosion measures at the<br />

source of the problem (farmland), to solving real problems downstream in the villages.<br />

Individual objectives of some participants gradually prevailed over the objectives stated in the<br />

project proposal. The project group had failed to construct a shared task that could mobilize the<br />

group. Few farmers participated and t<strong>here</strong> were hardly any visible results on farmland.<br />

Eventually the members of the project group could no longer deny the failure of the project.<br />

They called it a ‘low end version’. This seemed to be a socially desirable way of saying: we<br />

failed to reach the objectives. The project ended in inertia.<br />

Usually the task was predominant in the interactions and the participants found it<br />

hard to talk about the process and relationships. In the foster care case, however, the<br />

managers were mainly concerned with establishing collaborative relationships.<br />

However, as Vansina (2002) observes, collaboration as such cannot be the primary<br />

goal, because it is an organizational strategy to solve a ‘meta-problem’.<br />

In foster care the managers emphasized the ‘process’. They took a long time <strong>for</strong> the ‘pairing<br />

dance’ and stressed that getting to know one another was important. This seemed a defense<br />

against the anxiety of putting their cards on the table and taking decisions about the future<br />

(task). Moreover, collaboration became a goal in itself. Several stakeholder representatives<br />

wondered <strong>for</strong> what problem collaboration was going to be the solution. The managers and their<br />

264


oards did not specify what the benefit of collaboration was going to be (e.g. criteria, quality<br />

standards).<br />

If those in charge of leading or facilitating a collaborative can align the three types of<br />

tasks, this can be a powerful intervention to set the direction. It is important to work<br />

on a shared task definition to counter the tendency of pursuing individual objectives.<br />

Overarching objectives and a shared sense of common ground may help to foster<br />

productive, task-oriented work. However, when the task and objectives are defined<br />

at the start of the process, t<strong>here</strong> may be less space <strong>for</strong> innovation and creativity.<br />

Participants and facilitators need to find a balance between sufficient common<br />

ground to mobilize the collaborative and sufficient adaptability of the task.<br />

3. STRUCTURING AND FORMALIZING OF THE PROCESS<br />

An appropriate organization of the process is required to allow task-oriented work.<br />

Procedural interventions and structures can support the process (Bouwen & Taillieu,<br />

2004). Collaborative processes are usually ‘emergent’, and participants cannot<br />

establish structures or processes in advance (Gray, 1989). A collaborative does not<br />

have clear organizational structures, rituals, routines, procedures and authority<br />

relations. Feyerherm (1994) refers to an expedition or a journey ‘without much of a<br />

road map’. From the psychodynamic perspective this implies that anxieties that used<br />

to be contained in structures and authority embedded in that structure, are stirred up<br />

by the unknown conditions with which the stakeholders are confronted (Krantz,<br />

1998). Such emergent <strong>for</strong>ms of organizing require new ways of designing and<br />

facilitating. Particularly since no one is <strong>for</strong>mally ‘in charge’, conveners, participants,<br />

facilitators and sponsoring organizations need new skills and scripts to organize<br />

effective collaborative processes. When a collaborative is <strong>for</strong>malized too soon or too<br />

rigidly, t<strong>here</strong> is a tendency to lose the benefits of inter-organizational collaboration.<br />

Trist (1983) calls it a referent organization taking ‘the wrong path’ by establishing<br />

bureaucratic principles, central power, and hierarchical <strong>for</strong>ms of organizing. The<br />

result is a sub-optimization of diversity and inter-dependence. Defensive dynamics<br />

265


like ‘over-structuring’, ‘under-structuring’ or premature <strong>for</strong>malizing of collaborative<br />

relationships are likely to occur when negative feelings around uncertainty,<br />

interdependence and complexity are not contained.<br />

When <strong>for</strong>mal structures are lacking, so-called ‘psychological boundaries’ need to be<br />

negotiated (Hirschhorn & Gilmore, 1992). Doing so can contain the anxiety of<br />

collaborative work and provide some predictability and reassurance. Closing off too<br />

soon is a means to reduce uncertainty. A premature development of structures can be<br />

a defense against the openness of the situation; boundaries thus become barriers. It<br />

is, however, important to keep options open long enough and to explore alternatives<br />

(Taillieu et al., 2000). Excessive <strong>for</strong>malization may also lead to conflict and distrust<br />

among the parties (Ring & Van de Ven, 1994). Boundaries that are both firm and<br />

flexible allow <strong>for</strong> productive work on the task. In the face of uncertainty, the risk is<br />

that participants make an inappropriate or premature choice, influenced by socio-<br />

emotional needs rather than by the task itself (Menzies, 1988).<br />

In the river valley case the process was over-structured and controlled from the start.<br />

Consequently, many stakeholders felt excluded from the process and wondered what the<br />

administrations and consultants were up to.<br />

The way in which the key actors wanted to involve the stakeholders influenced the<br />

organization of the process. The issue of inclusion and exclusion was predominant in<br />

all cases. Different interpretations of ‘participation’ or ‘multi-stakeholder<br />

involvement’ resulted in different ways of structuring the process. In most cases, the<br />

process was already structured be<strong>for</strong>e the project started.<br />

In the river valley project membership of the steering group and the number of times the group<br />

was supposed to meet was set in advance. This was influenced, as it often was, by external<br />

factors. In this case, legal procedures in the domain of nature conservation determined the<br />

structures that were set up and the legitimacy of membership of those subgroups.<br />

In most cases the participants failed to apply common insights from project<br />

management, such as establish a problem definition be<strong>for</strong>e working out solutions.<br />

They seemed overwhelmed by the complexity of the endeavor. It is also common<br />

knowledge, <strong>for</strong> instance, that it is important to in<strong>for</strong>m people about progress in a<br />

266


project. The question in emergent processes is: in<strong>for</strong>m them about what precisely,<br />

when t<strong>here</strong> is ‘nothing’ to report yet? The cases also demonstrated that different<br />

parties (e.g. conveners, facilitators) organize a collaborative with ‘models’, ‘scripts’ or<br />

‘work methods’ that originate from other domains and that may not be adapted to<br />

the non-hierarchical nature of multiparty collaboration.<br />

3.1. Minimal structure<br />

A minimal structure provides basic conditions <strong>for</strong> productive, task oriented work. As<br />

previously discussed, a provisional ‘plan’ can provide focus and facilitate<br />

commitment and exploration to get the collaborative off the ground. A minimal<br />

structure also refers to establishing ground rules. These rules can relate to task<br />

aspects (e.g. we share all available in<strong>for</strong>mation), procedures (e.g. the work groups<br />

propose solutions, the project group decides) and relations (e.g. we respect<br />

differences). A minimal structure may provide some predictability and trust among<br />

the participants.<br />

The project <strong>for</strong>m provided some basic conditions, such as <strong>for</strong>mal objectives or a<br />

deadline, negotiated with the sponsor. In most projects t<strong>here</strong> was some <strong>for</strong>m of plan<br />

with steps and phases.<br />

In river valley case the process was structured in three phases (inventory, visioning, planning).<br />

In the foster care project the consultants proposed a project plan to organize the work (e.g.<br />

stakeholder interviews, feedback, stakeholder conferences).<br />

In none of the projects, explicit ground rules were negotiated at the start. In general,<br />

t<strong>here</strong> was little reflection on how the project groups were working together or how<br />

they wanted to work together. Sometimes rules did emerge during the process<br />

because participants were confronted with a problem.<br />

The project group in the foster care project made very few agreements. Over time they were<br />

confronted with a number of problems. In response, they decided on some clear ground rules.<br />

For instance, when the liberal service stepped out of the project, they stated that all the<br />

documents related to the services were to be treated as confidential. They also agreed that if a<br />

service stepped out of the project, it would still be a member of the regional consultation<br />

plat<strong>for</strong>m. At the end of the year, the managers decided to give their employees some minimal<br />

guarantees (e.g. no merger, no job loss) to contain the anxieties stirred up by the change.<br />

267


A convener or facilitator can help group development by establishing some basic<br />

rules <strong>for</strong> its functioning. Contracting can result in agreement on roles (of individuals<br />

or groups), mandate, and status of the results of the process. Over-structuring the<br />

process may even result in distrust (Ring & van de Ven, 1994). However, it is<br />

impossible to negotiate everything in the initial phase of the process. An important<br />

function of those facilitating the process is to create a climate w<strong>here</strong> the participants<br />

can discuss the way they are working together (meta-communication). This creates<br />

the opportunity to adapt the way of working or to establish ground rules during the<br />

process. In absence of <strong>for</strong>mal agreements or ground rules, the participating<br />

organizations have to rely on trust.<br />

3.2. Structuring of the domain: stakeholder analysis and<br />

stakeholder involvement<br />

In a multi-stakeholder process, it is critical to identify the parties that have a stake in<br />

the domain. In the multiparty logic, all parties with a stake in the domain are<br />

legitimate and ‘equal’. A process usually starts with establishing membership: whose<br />

voice will be heard, and whose voice is shut out? Hirschhorn and Gilmore (1992)<br />

refer to the boundary of identity: who is ‘us’ and who is not ‘us’? The group of<br />

representatives that emerges, sets out to define the task, which is a critical aspect in<br />

direction setting. In some projects membership was established in advance.<br />

Initially the conveners of the river valley study only accepted the members of the preestablished<br />

steering group (stakeholders) and planning group (representatives of<br />

administrations) as legitimate stakeholders. They only wanted to talk to and negotiate with<br />

representatives of organized stakeholder groups and colleagues from other administrations. In<br />

doing so, they excluded the public and unorganized interest groups. Later in the process, when<br />

they decided to set up work groups, they also allowed others into the collaborative.<br />

In foster care the convener had understood she needed to involve the ‘bad fairy’ (referring to<br />

the tale ‘the sleeping beauty’), an internal stakeholder, in the process. Otherwise, she would<br />

‘bewitch’ the collaborative. When the liberal service stepped out, t<strong>here</strong> was no conflict and<br />

relationships were safeguarded.<br />

In one case, the key actors made an explicit stakeholder analysis. It helped them to<br />

identify the relevant players in the domain, to understand the links between all<br />

stakeholders, and to position their organizations in the domain.<br />

268


In the foster care project the first step was a <strong>for</strong>mal stakeholder analysis. It helped the group to<br />

draw a list of stakeholder representatives <strong>for</strong> interviewing. This intervention also contained the<br />

anxiety stirred up by the complexity of the context in which the project was embedded.<br />

Stakeholder analyses (e.g. Eden, 1996) are usually based on power. If they are used to<br />

evaluate the importance or relevance of stakeholders, it can result in a tension<br />

between the rhetoric of equality and legitimacy of the stakeholders and the obvious<br />

asymmetries among the stakeholders.<br />

In foster care the researchers presented a stakeholder model which introduced an implicit<br />

hierarchy in the stakeholders. This intervention seemed to legitimize the marginalization of the<br />

foster children and parents. The asymmetry and inequality between internal and external<br />

stakeholders was also accentuated by this intervention.<br />

Finn (1996) draws a distinction between ‘internal stakeholders’, those involved in the<br />

process, and ‘external stakeholders’, those who have a stake in the domain but are<br />

not part of the process. In the projects, the boundary between these two types of<br />

stakeholders was a critical issue. Sometimes the distinction was explicit; sometimes<br />

the difference was more implicit.<br />

In foster care the classification and labeling of ‘internal’ and ‘external’ stakeholders occurred<br />

spontaneously. While the managers were preparing the stakeholder conferences they discussed<br />

who was to be invited, at what moment during the conference, and with what specific purpose.<br />

They decided to only invite the ‘external’ stakeholders during the morning of the first day. This<br />

distinction was maintained throughout the process. It changed the task of the project.<br />

In the other projects, a similar phenomenon emerged. ‘Internal’ stakeholders<br />

involved ‘external’ stakeholders as a technique to avoid resistance to the plans of<br />

those leading the initiative. The key actors (e.g. conveners, project leaders,<br />

facilitators, members of the project group) were willing to share their power with<br />

stakeholders under specific conditions. The assumption was, however, that they<br />

could take this power back. The motive <strong>for</strong> stakeholder involvement was usually not<br />

to take decisions <strong>for</strong> the domain from a shared power base (Vansina, 2002; Bouwen &<br />

Taillieu, 2004). In the projects, it was clear that the motive was to reduce resistance, to<br />

‘sell’ a plan, or to obtain in<strong>for</strong>mation or feedback on proposed plans from<br />

stakeholder representatives in order to improve them.<br />

In the river valley case the conveners only wanted a ‘modest’ <strong>for</strong>m of participation. They<br />

assumed it was their task to propose an ‘ideal’ plan to the stakeholders. They were obviously<br />

269


scared <strong>for</strong> direct interaction with a group of stakeholder representatives because they feared<br />

conflict, attack and criticism. They had learned, however, that it was important to listen to<br />

stakeholders. T<strong>here</strong><strong>for</strong>e they organized a ‘sector analysis’ and an individual survey of all the<br />

farmers in the valley.<br />

Also in foster care, the stakeholders were only involved to give in<strong>for</strong>mation, provide feedback<br />

or listen to the results of the project that had been developed without their participation.<br />

As a consequence the key actors had a strong influence on direction setting of the<br />

process in the three projects. In retrospect, the influence of managers, experts and<br />

consultants was predominant. They did consult the external stakeholders (e.g. sector<br />

analysis, stakeholder interviews), but it was hard to share and integrate the<br />

in<strong>for</strong>mation and to involve them in the process. The input of the ‘external’<br />

stakeholders was filtered, summarized and reduced, and often ended up in a report.<br />

By bringing the stakeholders in one room (‘search conference’), chances are higher<br />

that the leading actors integrate the direct input of the external stakeholders in the<br />

process. Such interventions increase the awareness of interdependence and diversity<br />

in the domain, and they rein<strong>for</strong>ce the sense of urgency to work collaboratively.<br />

3.3. Formal and in<strong>for</strong>mal roles<br />

An important aspect of structuring is role negotiation. Role negotiation is essential to<br />

enable participants in the process to make sense of their potential contribution. This<br />

process of contracting occurs at the implicit and explicit level and is shaped by the<br />

actions and interpretations of the stakeholders (Ring & Van de Ven, 1994). If<br />

participants are not open to negotiation, the project depends on ongoing power<br />

negotiation of competing stakeholders (Vansina, Taillieu & Schruijer, 1998). When<br />

the participants map out the interdependencies among the roles, this enables each<br />

stakeholder to connect his authority with that of others (Hirschhorn, 1988; Krantz,<br />

1998). When actors take up a meaningful role, they can share leadership <strong>for</strong> the<br />

future of the domain. A requirement <strong>for</strong> role negotiation is an accepted and shared<br />

primary task.<br />

270


In a collaborative ‘task authority gaps’ may emerge, because three interdependent<br />

systems are not available in advance. T<strong>here</strong> is no ‘official-role system’ (<strong>for</strong>mal<br />

organizational structure), no ‘task-role system’ (who does what and with whom), or<br />

‘authority-role system’ (who has the legal authority to make what types of decision)<br />

(Mackenzie, 1986). As the process emerges, the participants negotiate the<br />

psychological ‘task boundary’ (who does what?) and the ‘authority boundary’ (who<br />

is in charge of what?) (Hirschhorn & Gilmore, 1992). As previously discussed, the<br />

primary task of a collaborative is often not clearly defined and it is subject to change.<br />

T<strong>here</strong><strong>for</strong>e, participants may take up in<strong>for</strong>mal or self-attributed roles, driven by the<br />

need to get a grip on the situation or to move things ahead. Consistent attention <strong>for</strong><br />

the dynamic relation between task and roles is an important issue in facilitating<br />

work.<br />

In the erosion project the project leaders (consulting firms) did not exchange their expectations<br />

and assumptions with the local authorities. The latter were critical partners in the process<br />

because they were supposed to ensure the relationship with the farmers. T<strong>here</strong> was no<br />

contracting of roles and contributions. This resulted in ambiguity, disappointment, mutual<br />

blaming, an authority vacuum and inertia in the project. In the project group the consultants<br />

did try to exchange expectations and to negotiate the roles of the members of the group.<br />

However, this <strong>for</strong>mal intervention had little effect. Most members of the project group<br />

struggled with their role and found it hard to contribute in a meaningful way.<br />

In the foster care project the consultants clarified their role during the first meeting. However,<br />

as the process unfolded, it became clear that the managers expected a different contribution<br />

from the consultants. Projecting expectations of leadership on the consultants seemed like a<br />

defensive response to the anxiety of having to take decisions <strong>for</strong> the future of the domain.<br />

In the three projects, the participants took up different <strong>for</strong>mal and in<strong>for</strong>mal roles.<br />

Sometimes the roles overlapped or were shared by more than one person or<br />

organization. In all cases, whenever a person, group or organization took up a<br />

leading role, they became the subject of projected expectations. The way in which the<br />

participants made sense of their role, stereotype assumptions of leadership, and<br />

dependency needs prevented many participants from taking up their authority.<br />

These phenomena also hindered the development of shared leadership and joint<br />

responsibility <strong>for</strong> the future of the domain.<br />

271


3.3.1. Convener<br />

The role of the convener is to bring to stakeholders around the table and to provide<br />

the starting conditions (e.g. funding, organize a meeting). This party creates a<br />

plat<strong>for</strong>m <strong>for</strong> dialogue and negotiation <strong>for</strong> the stakeholder. As Gray (1996) points out,<br />

conveners use different ways of influencing the process: legitimation, facilitation,<br />

mandate and/or persuasion.<br />

In the erosion case the convener was both powerful and credible. His consulting firm had an<br />

established reputation in the area. He used his personal and business relationships to convince<br />

three municipalities to sign up <strong>for</strong> the project. This took him almost one year. Later in the<br />

process a civil servant from one of the municipalities claimed that the convener had talked the<br />

municipalities into the project; they had not realized what the consequences would be (e.g.<br />

amount of energy and time). The convener, however, was not perceived as a neutral party. His<br />

business interests and reputation in the area were at stake. Even though the convener had<br />

handed over project leadership to his colleague, he influenced the process from behind the<br />

scenes.<br />

Initially the convener of the foster care project was the drive behind the process. She was a very<br />

passionate and persuasive person. She spoke from different positions: as foster mother,<br />

manager (business interests, responsible <strong>for</strong> employment), convener of the process (in<strong>for</strong>mal<br />

leader), interest party (loyalty to constituent organization), spokesperson <strong>for</strong> policy makers (fear<br />

to lose face), and contractor of the consultants. When she ended up being a participant in the<br />

project, she stepped back. She insisted that she was ‘only one of the five parties’ and refused to<br />

play the role of convener. She wanted to defend the interests of her organization and relied on<br />

the consultants to lead the process. On a regular basis, however, she put her agenda (reception<br />

function) back on the table.<br />

In the river valley case the conveners struggled with their double role. They wanted to defend<br />

the interests of their administrations but also found themselves in the role of convener of the<br />

process. They felt uncertain because this role was unfamiliar to them and they lacked the skills<br />

and experience to facilitate a multi-stakeholder process. They did have the mandate, but many<br />

stakeholders did not perceive them as neutral or credible facilitators. Eventually they split up<br />

the two roles.<br />

It is important, especially in the initial stages of collaboration, that the representatives<br />

perceive the conveners as neutral, credible, trustworthy, powerful and fair (Gray,<br />

1989; 1996). The convener, who may be one of the participants, is or becomes a<br />

stakeholder in the success of the endeavor. As the cases have demonstrated, the role<br />

of the convener can be very different. The shift from convening to leading or<br />

facilitating, which is not well documented in the literature, also takes different <strong>for</strong>ms.<br />

272


3.3.2. Coordinator<br />

In all projects, t<strong>here</strong> were one or more persons or organizations in the <strong>for</strong>mal position<br />

of ‘coordinator’ or ‘project leader’. Their role was to assure daily management of the<br />

project (e.g. finances, project planning, reporting). In some cases, the parties in a<br />

leading role also had a stake in the problem domain. Because they were wearing<br />

‘double hats’, others could not always perceive them as being ‘neutral’ and impartial.<br />

The person or organization in the role of coordinator may be perceived as having<br />

more decision-making authority than the others (Himmelman, 1996), which was<br />

often true in the cases.<br />

In the river valley case the initiators were not perceived as neutral or credible coordinators of<br />

the project. Many stakeholders perceived the study as a vehicle from the administration to push<br />

the environmental agenda. Some feared it was private business between the engineers and the<br />

administrations. The conveners in their role of coordinators, did have a great influence on the<br />

process (e.g. decide if, when, and how to organize a meeting of the steering group).<br />

The participants sometimes fell back on stereotypes of leadership and projected<br />

traditional leadership expectations on the coordinator(s). The members of the project<br />

groups were often dependent on those taking the lead, as if they hoped an<br />

omnipotent and omniscient authority would tell them what to do and w<strong>here</strong> to go.<br />

The members of the project group in the erosion project had expected clear decisions and<br />

directives from the project leaders. Some were waiting <strong>for</strong> instructions, while others argued<br />

they needed clear guidelines to be able to do their work. The two shifts in project leadership in<br />

this project were disturbing because each coordinator had a different interpretation of his role.<br />

One focused on task leadership, w<strong>here</strong>as another viewed himself as a process facilitator. This<br />

prevented the group, at some point, from making and implementing decisions.<br />

In foster care the coordinator, a member of the consulting team, had the impression he had to<br />

drive the project, motivate the managers, do all the practical work, bring a sense of urgency in<br />

the project and make sure t<strong>here</strong> were results.<br />

Sometimes participants tried to question the legitimacy or competence of the<br />

coordinators by colluding and making them responsible <strong>for</strong> the failure of the<br />

collaborative.<br />

In the erosion case most members of the project group turned against the second project leader<br />

after he had left. They had fostered unrealistic expectations of his leadership (omnipotence) and<br />

blamed him <strong>for</strong> the lack of results. It seemed as a defense against the dysfunctioning of the<br />

project group as the group responsible <strong>for</strong> setting the direction of the process.<br />

273


3.3.3. External facilitator<br />

External facilitators usually lead the process, focus on group development, and<br />

create the conditions under which the participants can productively work together.<br />

In two cases, t<strong>here</strong> was an external or ‘third party’ to facilitate the process (Schuman,<br />

1996).<br />

External process facilitation was a critical condition <strong>for</strong> the managers in foster care. As they<br />

feared conflict and did not want to endanger the existing collaborative relationships between<br />

the five organizations, they insisted on having a neutral party to facilitate interactions. This also<br />

allowed them to defend the interests of their constituency. The facilitators had a clear mandate<br />

to focus on the process. After the project, some managers blamed the consultants <strong>for</strong> the slow<br />

progress in the project. They had failed to give personal feedback, they had not helped the<br />

managers to make sense of their experiences, they had not sufficiently represented the voice of<br />

the ‘external’ stakeholders, and they had provided little space to disagree. The managers had<br />

expected the facilitators to reassure them that what was happening in the project was ‘normal’<br />

because it was a ‘phase’ in such processes. They had missed ‘landmarks’ and felt ‘left in the<br />

dark’.<br />

In the erosion case the organizational psychologists, hired to facilitate the process, could never<br />

really take up this role. Since the second project leader emphasized process facilitation, he cut<br />

the ground from under the psychologists’ feet. After he had left, his successor did not allow the<br />

psychologists to facilitate the process. They had lost some of their credibility and neutrality by<br />

teaming up with the second project leader.<br />

Researchers in the role of action researcher or participative observer also influenced<br />

the process. They helped the participants to find their solutions by, <strong>for</strong> instance,<br />

facilitation of interactions, and organization and design of the process. They also<br />

brought reflection in the system, <strong>for</strong> instance by giving feedback of their findings.<br />

This helped the participants to become aware of their assumptions, experiences, and<br />

what they learned from them (article 3). A critical condition <strong>for</strong> success was clear<br />

contracting of roles on a regular basis.<br />

3.3.4. ‘External’ and ‘internal’ stakeholder representatives<br />

Stakeholder can share in direction setting of the process, when they have the<br />

authority, potential, capacity and permission to act. However, in the cases the<br />

‘external’ stakeholders could never really take up a critical and meaningful role or<br />

take joint decisions <strong>for</strong> the domain.<br />

The conveners in the river valley project clearly stated they only wanted to negotiate with<br />

organized stakeholder groups. They did not believe that parties who could not understand the<br />

technical details of the plans could make sensible, well-in<strong>for</strong>med choices. During the workshop<br />

the participants became aware they had missed an opportunity. They realized t<strong>here</strong> had not<br />

274


een any negotiation or contracting with the stakeholders about their role or contribution. The<br />

stakeholders had assumed the conveners and consultants would decide on the future of the<br />

valley and were frustrated. Meanwhile, the conveners had expected the <strong>for</strong>mal representatives<br />

in the subgroups to play their role of ‘stakeholder representative’ without clarifying what that<br />

actually implied.<br />

In the projects representatives of the ‘internal’ stakeholders, or ‘partners’<br />

(Himmelman, 1996), were usually actively involved in the process.<br />

In foster care representatives of the services actively participated during three stakeholder<br />

conferences and some were member of the work groups. The employees in particular engaged<br />

in the work with a lot of enthusiasm and hope. The managers realized that the members of the<br />

boards should have steered this sort of change process, as they had a more strategic view on the<br />

domain. However, these people (volunteers) did not have the time, and some not the<br />

competence, to invest time and energy in this process.<br />

In the river valley case it was not clear who the ‘internal’ stakeholders were. The conveners<br />

drew the boundary of identity closely around their small core group, which made it harder <strong>for</strong><br />

others to contribute. The planning group, made up of public officers from colleague<br />

administrations, did not have much influence on the process. The coordination committee was<br />

split in subgroups, which took away some of the authority of the group.<br />

The essence of multiparty collaboration is that a collaborative is composed of<br />

representatives who speak <strong>for</strong> their constituency. Huxham and Vangen (2005)<br />

discuss the ambiguity in representativeness. Are the ‘members’ of a collaboration the<br />

individuals who work together in a collaborative group, or the organizations that<br />

they represent? The representatives were confronted with a number of issues in their<br />

role as representative.<br />

In the foster care case the president of the board of the liberal organization (FC5) put pressure<br />

on those representing his organization in the project. He insisted on the importance of a liberal<br />

perspective on educational activities. The manager of FC4 also found herself squeezed between<br />

the agenda of her board (collaboration across the boundary of foster care) and the objectives she<br />

was supposed to be working on in the project group (collaboration between the services in two<br />

specific areas). This took away her authority to act and weakened her mandate in the project<br />

group. T<strong>here</strong> was a marked difference between the mandates of the five managers in the project<br />

group. Some represented a small, regional service and had to go back to their constituency <strong>for</strong><br />

decisions. Another manager represented a large Flemish organization and could autonomously<br />

take decisions. This weakened the capacity of the project group to take quick decisions.<br />

Moreover, t<strong>here</strong> was a difference between the management culture of the services (top-down or<br />

participative), and between the composition, role and power of the boards. These issues came<br />

up in the project group on a regular basis.<br />

The representatives were confronted with their mandate and the authority to take<br />

decisions <strong>for</strong> their constituency. They were not always sufficiently in<strong>for</strong>med to<br />

275


epresent their organization. Sometimes t<strong>here</strong> were conflicts of loyalty between the<br />

representative and his or her constituency, due to differences in vision.<br />

3.3.5. Experts<br />

In order to solve complex environmental ‘meta problems’ the involvement of<br />

external experts becomes critical (Koppenjan & Klijn, 2004). T<strong>here</strong><strong>for</strong>e, dependency<br />

on experts is likely and maybe inevitable. Particularly in the environmental and<br />

technical projects, the experts took up an important role. Because of the complex<br />

technical level of measures and solutions, other participants gave them a central role.<br />

In the river valley case the technical experts were critical partners. They modeled solutions and<br />

measured potential scenarios <strong>for</strong> flooding. They were also the ones talking to all stakeholders<br />

(‘sector analysis’). The technical discourse dominated the process. The instruments and models<br />

were not designed <strong>for</strong> communication, thus shutting out many stakeholders. The conveners,<br />

who were also experts in the domain, were critical about the work and proposals of the external<br />

experts and tried to be an ‘equal’ partner in the process.<br />

In the two cases in the domain of natural resources, the experts made technically<br />

solid plans <strong>for</strong> the stakeholders in the domain. However, they were confronted with<br />

problems and resistance when they tried to ‘sell’ their plans. A critical issue is the<br />

capability to bridge the technical experts and the non-experts or nonprofessionals.<br />

3.3.6. In<strong>for</strong>mal leaders<br />

Sometimes in<strong>for</strong>mal leaders, involved as representatives in the process, competed <strong>for</strong><br />

influence in covert ways. They relied on different sources of authority to exercise<br />

their influence (e.g. expertise, political relations, status, in<strong>for</strong>mation, access to<br />

financial resources, social network).<br />

In the erosion case the powerful convener, who had stepped back from the moment the project<br />

started, closely followed the project behind the scene. When the project was in danger, he came<br />

to the <strong>for</strong>eground and took over. Even though consultants of the other consulting firm were in<br />

charge of the project, he demonstrated on a regular basis that he was still in control. It was ‘his’<br />

project. He used his political connections to restore confidence in the project. The members of<br />

the project group perceived his interventions on the one hand as ‘saving’ the project, while on<br />

the other hand they were aware that he was mainly defending his business interests.<br />

276


This manifestation of tactical leadership is usually in the interests of one or a few<br />

parties (Vansina, 2002). As ‘leadership’, by definition, was an ambiguous notion in all<br />

cases, the influence of in<strong>for</strong>mal leaders added to the confusion among the<br />

participants. By using power, in<strong>for</strong>mal leaders may endanger the collaborative<br />

character of the process and the shared nature of leadership.<br />

3.3.7. Funding agencies and context leaders<br />

The sponsors and other influential players in the context were invisible in the<br />

projects. The participants indirectly experienced their presence and influence by the<br />

requirement, <strong>for</strong> instance, to submit reports, to present timely results, or to justify<br />

expenses. Direct contact with those leaders was, however, scarce.<br />

At one point, t<strong>here</strong> was a festive event in foster care. The Minister was present at the meeting.<br />

The managers missed an opportunity to make the Minister speak about their project. One of the<br />

consultants reported that it struck him how timid the managers were whenever they took up a<br />

role in public. Also at the final stakeholder conference, when a representative from the cabinet<br />

was present to listen to the results of the project, the managers did not reach out to this person.<br />

In order to involve all relevant players in the field, it seems critical to clearly identify<br />

the sponsoring organization as a ‘stakeholder’ in the process, and to make sure this<br />

party is represented in the collaborative. This may help to adapt the contract with the<br />

sponsor in the course of events. Himmelman (1996) also argues that funding<br />

organizations often fail to understand that a collaborative is more than a proposal to<br />

which organizations attach letters of endorsement. Particularly, sponsors do not<br />

realize that it takes time to develop a well designed collaborative with trusting and<br />

respectful relationships. They often expect results be<strong>for</strong>e the participants have had<br />

the time and opportunity to develop the collaborative fully.<br />

3.4. Formal and in<strong>for</strong>mal structures and interventions<br />

The central structure in all projects was the ‘project group’. Regular face-to-face<br />

meetings of this ‘core group’ helped the key actors to stay connected to the project, to<br />

each other, and to feel committed to the task. These meetings were a powerful<br />

vehicle to set the direction of the process. The members of the project groups played<br />

277


out the dynamics in the wider system. The role and status of this group was,<br />

however, not always clearly negotiated.<br />

In foster care the project group met on a monthly basis. In these meetings, the members of the<br />

project group designed the process, discussed critical issues, explored potential scenarios <strong>for</strong> the<br />

future. The group was the ‘motor’ of the process, although they were aware that the board<br />

members should take the final decisions <strong>for</strong> the future.<br />

In the erosion case the name 'project group' was used <strong>for</strong> different constellations and mixed up<br />

with other names. Juniors took over from seniors. Some representatives joined and some left.<br />

T<strong>here</strong> was no open contracting and t<strong>here</strong> were no clear ground rules. The members did not<br />

clarify the mandate of the group. It was not clear whether it was the group w<strong>here</strong> decisions<br />

were taken, w<strong>here</strong> in<strong>for</strong>mation was shared, or w<strong>here</strong> advise was prepared. The third project<br />

leader did not think the meetings of the project group were still relevant when he took over<br />

project management. He argued that the budget <strong>for</strong> meetings was used and that the meetings<br />

were only used <strong>for</strong> ‘chatting’. When the project group stopped to meet in person, the members<br />

worked on their objectives or simply stopped contributing.<br />

In some cases, the <strong>for</strong>mal structures to organize participation were established in<br />

advance. The structures were a way to <strong>for</strong>malize membership and to legitimize the<br />

stakeholder representatives.<br />

In the river valley case the <strong>for</strong>mal structures were established be<strong>for</strong>e the project started. They<br />

consisted of the typical project substructures, such as a ‘project group’ and a ‘steering group’.<br />

These structures were based on legal procedures in the domain of natural resources. In this<br />

way, the conveners wanted to make sure that decisions taken by the <strong>for</strong>mal groups were<br />

legitimate <strong>for</strong> the Ministry. The planning and steering group consisted of a wide group of<br />

stakeholder representatives. The choice <strong>for</strong> these two subgroups had been deliberate. The<br />

conveners did not want representatives of civil actors (steering group) to discuss with public<br />

authorities directly (planning group). The steering group was only convened twice in one year.<br />

It was merely used to share in<strong>for</strong>mation, present results ask <strong>for</strong> feedback on a plan that was<br />

thoroughly worked out.<br />

In the foster care case t<strong>here</strong> was no <strong>for</strong>mal structure representing the stakeholders in the<br />

domain. The project group was only composed of managers of the services and the head of the<br />

Federation. They did not act as a steering group representing the general interests of the<br />

domain. This resulted in a narrow focus on internal stakeholders. The external stakeholders<br />

could only show up twice <strong>for</strong> a conference.<br />

In the three cases the ‘work groups’ were most effective. Since those groups were<br />

small, which allowed <strong>for</strong> direct interaction, it helped the participants to develop a<br />

relationship. They worked on specific and concrete issues, which made it easier to<br />

contribute, make progress and take up joint responsibility.<br />

Sometimes in<strong>for</strong>mal ‘subgroups’ emerged, which made it easier to talk about the<br />

worries and questions of the participants (e.g. in<strong>for</strong>mal drink, field visit, car drive).<br />

278


Opportunities <strong>for</strong> in<strong>for</strong>mal interaction or shared experiences helped to foster<br />

ownership and commitment to the project.<br />

In the river valley case an in<strong>for</strong>mal subgroup emerged: the ‘petit comité’. It was a space w<strong>here</strong><br />

the conveners, consultants and researchers discussed the difficulties of organizing participation.<br />

They also talked about the findings of the stakeholder interviews. For a while this small<br />

in<strong>for</strong>mal group was a facilitating structure that helped the conveners to deal with the<br />

uncertainty of the process.<br />

In the three cases, my colleagues and I tried to encourage the leading actors to<br />

organize some <strong>for</strong>m of search conference (‘all in a room’). The aim of such a<br />

‘structured’ process is to hear the voice of all relevant stakeholders, to integrate<br />

in<strong>for</strong>mation, to foster interdependence, and to encourage ownership and joint<br />

decision-making.<br />

In the foster care project the managers did not want a search conference, as proposed in the<br />

contract. They thought stakeholders would not be interested to invest so much time in foster<br />

care. They claimed it was not part of the culture in foster care to organize residential seminars.<br />

Instead, they invited the external stakeholders to one morning and one afternoon of their<br />

‘stakeholder conferences’ (3 separate days). One of the consultants worried about discussing<br />

with a large group. He was afraid that it would be hard to deal with so much in<strong>for</strong>mation and<br />

to integrate the perspectives of all stakeholders. Although the managers had been hesitant of<br />

directly talking to external stakeholders, they experienced the interactions as constructive and<br />

helpful.<br />

In the river valley case the conveners were anxious to openly talk with a large group of<br />

stakeholder representatives. They claimed that meetings with such a large group were<br />

‘impossible’. When they convened the steering and planning group together to share the results<br />

of the first phase (approximately 50 persons), they tightly structured and controlled the<br />

meeting. They feared conflict and an open attack on their plans.<br />

The main interventions initiated by external facilitators were typical OD<br />

interventions: individual interviewing, feedback, written reporting, reporting to the<br />

larger system, and setting up work groups. Bringing the system in one room may<br />

have been more appropriate than such classical interventions. I will further discuss<br />

the implications <strong>for</strong> OD at the closure of this chapter. In the three cases, the<br />

researchers organized feedback meetings to share their findings with the group.<br />

Sometimes this fostered learning, but sometimes the participants experienced it as a<br />

threat.<br />

In the river valley case the requirement of the European project (HarmoniCOP) to organize a<br />

‘stakeholder workshop’, helped to motivate several participants to spend one day to reflect on<br />

their experiences. This was a constructive and fruitful experience w<strong>here</strong> the participants openly<br />

discussed their assumptions, hope and fears with each other.<br />

279


In the erosion case the feedback from the interviews was interpreted as criticism. Although<br />

<strong>for</strong>mally the organizational psychologists were supposed to facilitate the process, they<br />

wondered if they had the mandate from the members of the project group to feed back their<br />

observations and findings.<br />

In some instances, technical interventions and tools were prominent. These work<br />

<strong>for</strong>ms were used to enhance the credibility of the solutions, to exert power, or to<br />

convince stakeholders of a solution, plan or vision. This often resulted in an<br />

exclusion of those who could not understand the technical jargon.<br />

The conveners in the river valley case used models, simulations and measures to convince the<br />

stakeholders of their solution <strong>for</strong> the valley. The technical discourse dominated the process. The<br />

instruments and models were sometimes too technical to be effective. The members of the<br />

planning group, all experts in nature and river management, complained after the presentation<br />

of the provisional plan, that it had been too technical and difficult.<br />

Participative structures and procedures are no guarantee <strong>for</strong> stakeholder<br />

involvement; they only provide conditions <strong>for</strong> participation. In the three cases, the<br />

meetings of the <strong>for</strong>mal groups (e.g. steering group) were not used to share<br />

responsibility <strong>for</strong> decisions about the future of the domain. Although the project<br />

proposals specified the <strong>for</strong>mal role and mandate of these groups, the conveners or<br />

leading actors rarely negotiated their assumptions and expected contribution of the<br />

stakeholder representatives with the members of these groups. This procedural<br />

approach reduced the participative structures to <strong>for</strong>mal bodies. It often gave people<br />

the feeling of going ‘through the ceremony’. The key actors (project group) colluded<br />

in the sense that they did observe what was happening, but they did not raise the<br />

issue.<br />

Participants need to find a balance in the way they organize the process. T<strong>here</strong><br />

should be sufficient structuring to provide containment and predictability. On the<br />

other hand, it is essential to keep the process flexible in order to adapt it to changing<br />

circumstances both within the collaborative and in the environment.<br />

It is not sufficient to consider issues in the environment, to establish conscious<br />

agreements on the task, to negotiate roles, and to organize the process. It is also<br />

280


critical to develop collaborative relationships. In the following paragraph, I discuss<br />

the main relational issues and dynamics observed in the cases.<br />

4. COLLABORATIVE RELATIONSHIPS, RELATEDNESS AND DYNAMICS<br />

The literature emphasizes the need to develop a ‘collaborative state of mind’. This<br />

mind set, which seems like a normative ideal, is characterized by trust, the capability<br />

to work with different power relations, the capacity to work in a situation of 'not<br />

knowing' and the will to learn from the experience of collaborating. Several authors<br />

assume that mature inter-group relations, as opposed to defensive relationships,<br />

foster a collaborative work group culture resulting in productive, task-oriented work<br />

(Long et al., 2000; Gould et al., 1999; Ring & van de Ven, 1994). Representatives in a<br />

collaborative need to be able to deal with the inevitable tensions that arise in<br />

collaborative work and cope with the emotional challenges it provokes. A condition<br />

<strong>for</strong> developing mature working relationships is the opportunity <strong>for</strong> face-to-face<br />

interaction. In direct interaction, participants can share their knowledge, ideas, and<br />

perspectives and contest those (Bouwen & Taillieu, 2004). Facilitation of the<br />

interactions and fostering group development are critical conditions.<br />

By adopting the system psychodynamic perspective in this research, I focused on the<br />

consequences of the anxiety and ambivalence provoked by the relationships between<br />

the participants. I assumed that conscious as well as unconscious motives drive<br />

behavior. The concept ‘relatedness’ refers to the emotional and unconscious nature of<br />

relationships. The internalized relationships and quality of connection based on<br />

processes of mutual projection, splitting, introjection, and projective identification<br />

influence how people relate to one another (Triest, 1999; Gould et al., 1999). As<br />

demonstrated in the case analyses, phenomena such as paranoid concerns, mutual<br />

stereotyping, and fantasies about the lack of equity or the fear to be absorbed by<br />

powerful organizations, often emerged in collaborative relationships.<br />

281


4.1. Working with diversity<br />

In the multiparty collaboration logic, the essence is to work with representatives<br />

from different organizations and groups, precisely because they have a different<br />

perspective (Zagier Roberts, 1994). The challenge is to work in the <strong>here</strong>-and-now with<br />

the differences and similarities represented in the collaborative. It is critical to discuss<br />

and explore the different interests and objectives of the participants, because<br />

collaboration is based on real and accepted differences. In practice, however, the<br />

presence of representatives holding different perceptions, in<strong>for</strong>mation and interests<br />

is a threat to the self-esteem of the participants (Vansina, 2002). This perceived<br />

menace may result in exclusion, denial, or assimilation of diversity. On the other<br />

hand, participants can also perceive the situation as an opportunity. This creative<br />

tension emerges when parties have different interests and objectives which they<br />

cannot completely achieve because of the presence of others, but which they cannot<br />

achieve without the other party’s presence and contribution. The power paradox<br />

arises from the fact that each party has the power to either prevent the other parties<br />

from achieving their objective, or assist them to do so (Carlisle & Leary, 1981).<br />

In the cases, the key actors often experienced the perceived diversity and differences<br />

as a threat or an obstacle to collaboration. It seemed as if they were afraid to include<br />

different voices, because that would question their objectives or endanger their<br />

identity. They were reluctant to deal with the diversity of perspectives in the <strong>here</strong>-<br />

and-now. Many expressed the fear <strong>for</strong> conflict if the ‘real’ differences would become<br />

apparent. T<strong>here</strong> was little collective exploration of the differences in perspective,<br />

expectations, or potential contribution. In most cases, the different perspectives were<br />

assessed (e.g. interviews, bilateral meetings) in an individual or bilateral way. This<br />

could have maintained the illusion that collaboration is an adding up of individual<br />

interests. If diversity is not represented around the table, the stakeholders cannot<br />

realize that their claims, interests and objectives need to be aligned and integrated<br />

with those of others.<br />

In the river valley project the conveners were defensive and expected most stakeholders to be<br />

against their plans. They believed their goals and those of the stakeholders in the valley were<br />

incompatible. They used their power to structure and organize the process with the aim of<br />

282


protecting their objectives and interests. T<strong>here</strong><strong>for</strong>e they were reluctant to bring stakeholders<br />

with different perspectives in one room.<br />

In foster care the external stakeholders were only marginally involved. The managers were<br />

defensive because of previous experiences. They talked about not being heard or taken<br />

seriously by policy makers and bigger players in the domain (e.g. residential institutions), they<br />

felt they were in an underdog position and expected the external stakeholders to be<br />

uninterested and critical. Although some participants were aware of the importance and<br />

relevance to include the voice of the stakeholders, they shut them out of the process out of fear<br />

and tactical considerations.<br />

Often t<strong>here</strong> was a regressive pull to reduce the diversity in the process. This<br />

frequently resulted in ‘us and them’ dynamics, blaming, splitting, rivalry or<br />

exclusion.<br />

In foster care a first reduction of diversity was the split that was established between internal<br />

and external stakeholders. Secondly, the differences between the services were not thoroughly<br />

explored. The managers got stuck in abstract discussions about differences in values and<br />

identity. The liberal service, identified as ‘different’ from the start, stepped out. This further<br />

reduced the diversity in the process. Afterwards, some managers blamed the consultants <strong>for</strong><br />

covering up the differences and <strong>for</strong> stressing compromise and similarities.<br />

In the erosion project t<strong>here</strong> was polarization and rivalry between the two engineering groups.<br />

For instance, both groups had a different perspective on the nature of the problem, the best way<br />

to solve it, their role in the process, and the role of the stakeholders and the local authorities.<br />

T<strong>here</strong> was little integration of their perspectives and expertise. They ended up working<br />

separately.<br />

In the river valley case the relationship between the conveners and administration responsible<br />

<strong>for</strong> the river was antagonistic. At first, the administration responsible <strong>for</strong> the river was not<br />

included in the coordination committee. T<strong>here</strong> was splitting: the conveners represented the<br />

‘new’ and the authority over the river the ‘old’ vision on river basin management. Initially both<br />

parties hardly communicated and t<strong>here</strong> was mutual stereotyping and blaming (e.g. ‘unrealistic’,<br />

‘backwards’). Both parties seemed locked up in their identities, which resulted in sub-grouping<br />

in the coordination committee.<br />

Differences in interests often mobilize power to safeguard the survival of the group<br />

(Vansina, 2002). In the cases, the key actors made interventions to protect the<br />

interests or identity of their constituency. Mobilization of power was detrimental <strong>for</strong><br />

the collaborative nature of the process. It endangered the necessity to keep<br />

responsibility shared around the table.<br />

The managers in foster care used their mandate and authority to decide on an internal focus.<br />

Their decision to keep the external stakeholders out of the process seemed driven by the<br />

underlying aim to protect the survival of the five organizations. Later in the process when the<br />

services were exploring their interests and objectives, many accentuated the differences as a<br />

way to confirm and protect their identity.<br />

283


In the erosion project the convener, the manager of a powerful engineering firm, used his power<br />

to safeguard the implementation of his contract with the municipalities (civil engineering<br />

constructions). The members of the project group perceived him as manipulating the process.<br />

At one point in the river valley case the administration responsible <strong>for</strong> the river mobilized<br />

power in an attempt to take over control of the process. They had come to the coordination<br />

committee with five representatives instead of one or two. A high-ranking manager <strong>for</strong>cefully<br />

stated that he wished to stop the process and duplicate the measures and modeling carried out<br />

by the consultants. The conveners, however, did not give in. They continued their consultation<br />

tour and invited a representative of the administration responsible <strong>for</strong> the river to join them.<br />

In some instances, as collaborative relationships were developed, the actors<br />

discovered the qualities and perspectives of others and of themselves. They realized<br />

they needed a strong identity as a condition <strong>for</strong> collaboration.<br />

For a long time the services in the foster care case struggled with the nature, relevance and<br />

consequences of being similar of different. When they engaged in exploration of their<br />

differences, the services became more aware of their identity and values. The liberal service, <strong>for</strong><br />

instance, was convinced it was ‘different’ from the other services. This had provided them with<br />

their identity in relation to the other organizations. In the process, however, they discovered<br />

they were not so ‘special’ after all. This was hard to accept <strong>for</strong> them, especially <strong>for</strong> the president<br />

of the board who embodied the ideology and values promoted by his organization. The services<br />

realized that a first step in collaboration was to identify their strengths and uniqueness. Identity<br />

could not only be based on the <strong>for</strong>mal ideology of the service (pluralistic, catholic or liberal), but<br />

also needed to refer to the expertise, professional practices, and quality of assistance of the<br />

organizations.<br />

However, a strong identity and strong identification with the values and interests of<br />

the organization sometimes endangered the development of collaboration based on a<br />

diversity of perspectives. It also resulted in exclusion of other voices.<br />

In the river valley case the conveners strongly identified with ecological and environmental<br />

values and with their professional role (defend public interests). They seemed stuck in their<br />

position. Their vision of the future and their belief in an ‘ideal’ solution <strong>for</strong> the valley hindered<br />

the acceptance of the multiple interests and values. Initially, they gave a unilateral definition of<br />

the nature of the problem and the potential solutions <strong>for</strong> the valley. This perspective prevented<br />

them from accepting the legitimacy of the interests and claims of the stakeholders in the valley.<br />

Since they were an interest party, they primarily focused on defending ‘their’ study. It was hard<br />

<strong>for</strong> them to take up the role of convener and to bring the different perspectives around the table.<br />

It is essential to work with the differences relevant to the task, represented in the<br />

collaborative, by building relationships (Thomas, 1995). Responses such as denial,<br />

exclusion or suppression of diversity decrease complexity and endanger the benefit<br />

of collaboration. The challenge is to develop a sense of common ground that<br />

represents the diversity in the system, without reducing it to a common<br />

284


denominator. Talking about ‘values’ and hiding behind an organizational identity<br />

does not foster trust or respect. It is important that participants show who they are,<br />

what they do, and what they stand <strong>for</strong>. This may avoid positional bargaining w<strong>here</strong><br />

parties are locked up in a self-chosen identity.<br />

4.2. Mutual dependence and interdependence<br />

A critical challenge of collaborative work is to change our independent and<br />

competitive attitude into an attitude of collaboration and to develop a sense of lived<br />

interdependence (Trist, 1983; Ackoff, 1997; Bouwen & Taillieu, 2004). This implies<br />

that parties mutually negotiate, recognize and accept each other’s perspective,<br />

interest, contribution, and identity. When they acknowledge their mutual<br />

dependence to develop sustainable and optimal solutions <strong>for</strong> the domain the parties<br />

develop interdependence. The multiparty paradigm moves away from a power<br />

based approach to solving problems. It reflects the awareness that one organization<br />

or group cannot act or decide alone. This confronts participants with a paradox:<br />

interdependence gives each party the ability to damage the other. Forced<br />

interdependence often results in a battle between the rational and emotional (Carlisle<br />

& Leary, 1981). In a culture w<strong>here</strong> autonomy and independence are idealized or<br />

necessary <strong>for</strong> survival, imposed interdependence may elicit resistance. Moreover, in<br />

an institutional context w<strong>here</strong> rivalry <strong>for</strong> resources is necessary (e.g. foster care), this<br />

state of mutual dependence can stir up anxiety. Participants need to work through<br />

the anxieties provoked by being mutually dependent <strong>for</strong> success and the anxiety of<br />

not being in control (Long et al., 2000; Gould et al., 1999; Carr, 2001). The cases<br />

demonstrated different levels of interdependence.<br />

A first level of interdependence was at the level of the project group. This research<br />

mainly focused on the interdependence in the project group. The members of the<br />

project group usually managed to accept their mutual dependence. The main reason<br />

was that in most cases they knew each other and that they met on a regular basis. In<br />

the cases, this core group was often at the origin of the collaborative endeavor and<br />

285


t<strong>here</strong><strong>for</strong>e was one step ahead and more motivated than the other players in the<br />

domain.<br />

In foster care the managers had worked together <strong>for</strong> 10 years. They had personal relationships<br />

and trusted each other. They had had positive experiences in working together. They realized<br />

that collaboration meant either all going ‘up’ or all going ‘down’. They talked about ‘differences<br />

in speed’, meaning that (most members of) the project group was further in their thinking and<br />

more willing to collaborate than the employees and members of the boards.<br />

This level of interdependence refers to mature interpersonal relations and the process<br />

of group development (Bennis & Shepard, 1956). However, in most cases, contact in<br />

the project group was quite superficial. The members did not address or explore<br />

critical issues, such as the consequences of being dependent upon each other, or the<br />

diversity of interests.<br />

A second level was interdependence between the constituent organizations. The<br />

constituencies were often more reluctant to accept their interdependence. The<br />

members of the constituencies did not know each other, they had few opportunities<br />

<strong>for</strong> interaction, and were involved at a later moment in the process. This level of<br />

interdependence refers to inter-group phenomena (Schruijer, 1990; Gemmill & Elmes,<br />

1993; Zagier Roberts, 1994; Vanbeselaere, 2000). Inter-organizational interdependence<br />

was poorly handled. For instance, dynamics of exclusion of organizations or groups<br />

occurred, as a defense against the tension of being dependent on other organizations<br />

<strong>for</strong> success. The dynamics at this organizational level require further research.<br />

A third level refers to the development of interdependence on the domain level,<br />

among organizations, social groups, or stakeholders in the domain. The challenge of<br />

collaborative work is to deal with the task by building relationships with all relevant<br />

parties who have a stake in the inter-organizational domain (Trist, 1983). The cases<br />

have demonstrated that this interdependence was often complex and experienced as<br />

threatening. Dealing with interdependence in the domain was blocked by the way in<br />

which the process was organized. Formal structures or premature <strong>for</strong>malizing often<br />

left few opportunities <strong>for</strong> direct interaction and <strong>for</strong> experiencing interdependence in<br />

286


the domain. The ‘participative’ plat<strong>for</strong>ms or structures were used in a procedural<br />

manner and not as a space to jointly take decisions <strong>for</strong> the future of the domain.<br />

In the cases, ‘leadership’ was ambivalent. On the one hand, the participants needed<br />

to move the process ahead, mobilize ‘leadership’, and take up their authority. On the<br />

other hand, they were aware of the fact that no one was in ‘in charge’ or had the<br />

authority to take decisions <strong>for</strong> the domain. The actors had few role models <strong>for</strong><br />

interdependent decision-making. Moreover, they often realized that players in the<br />

context were taking the final decision. In some instances, this confronted the<br />

participants with an authority vacuum or ‘task authority gap’ (Mackenzie, 1986) and<br />

resulted in inertia or a dependency on those in a <strong>for</strong>mal ‘leading role’ (e.g. project<br />

leader, coordinator, or facilitator). The ambiguity of interdependent decision-making<br />

and shared leadership may provoke regression, withdrawal, and a defensive group<br />

culture (Diamond & Allcorn, 1987).<br />

In the erosion project the members of the project group expected explicit and directive<br />

leadership from the person in the role of ‘project leader’, even though this person had no <strong>for</strong>mal<br />

authority to take decisions <strong>for</strong> the collaborative. The project resulted in inertia, partly because<br />

t<strong>here</strong> no one took the lead and because the project group was not able to take joint decisions.<br />

The (third) <strong>for</strong>mal project leader did not take up his leading role. He did not publicly authorize<br />

his colleague to take the lead. The organizational psychologists were not authorized to facilitate<br />

the process. The in<strong>for</strong>mal leader only showed up at critical moments. The municipalities who<br />

could have taken up a leading role also abdicated. This confusion and ambiguity resulted in an<br />

authority vacuum.<br />

In the foster care case the managers demonstrated dependent behavior towards the consultant<br />

team. They projected expectations of competence and leadership on the consultants and hoped<br />

they would ‘know’ what to do and provide them with a blue print scenario.<br />

In the cases, several aspects hindered the development of interdependent<br />

relationships. A first obstacle was the task definition that often did not include the<br />

interests of a wide range of stakeholders. Thus, a unilateral task definition set the<br />

direction of the process.<br />

In the foster care project the normative task was to develop structural collaboration among the<br />

services. This task definition shut out other players in the domain who were necessary to<br />

develop optimal solutions <strong>for</strong> the child (existential task).<br />

287


Secondly, the split between internal and external stakeholders reduced<br />

interdependent work. Internal stakeholders did not perceive the external<br />

stakeholders as critical partners in the process and thus denied the importance of<br />

interdependence. This seems to demonstrate the belief or hope that one party or a<br />

small coalition of parties can take decisions <strong>for</strong> the domain.<br />

In the river valley case the conveners believed they could work out an ‘optimal’ and ‘integrated’<br />

solution <strong>for</strong> the valley in collaboration with the external consultants. They did not believe that<br />

external stakeholders could contribute significantly to the solution of the problem domain.<br />

Thirdly, the asymmetries among the stakeholders also hindered the development of<br />

interdependent relationships (e.g. power, resources, in<strong>for</strong>mation, social network,<br />

available time). These asymmetries made it hard to establish ‘equal’ relationships<br />

and to accept all stakeholders as ‘legitimate’ parties in the process. For instance, <strong>for</strong><br />

powerful parties it was hard to accept their dependence on weaker parties.<br />

In the erosion case the soil experts wondered why it was necessary to involve the farmers. They<br />

were used to develop technical solutions in an independent way. They had a hard time<br />

accepting that the solutions needed to be jointly developed with the end users. The engineers<br />

did realize they needed the support and participation of the farmers to achieve success<br />

(implement experimental interventions). T<strong>here</strong><strong>for</strong>e, they put a huge ef<strong>for</strong>t in trying to involve<br />

farmers in the project (e.g. individual visits to the farmers).<br />

A final obstacle to the development of interdependence was the lack of opportunity<br />

and time <strong>for</strong> direct interaction. In some cases t<strong>here</strong> was a tension between the<br />

requirement to work on the task and the experienced need to invest time in the<br />

‘process’ of getting to know one another, and to develop trust and commitment to<br />

the process. Trust makes it safer <strong>for</strong> people to interact, it facilitates face-to-face<br />

interactions, and secures equity, fairness and respect (Vansina, 2002). In other cases,<br />

underestimating the importance of establishing interdependent relationships was<br />

detrimental <strong>for</strong> the task.<br />

In foster care the managers strongly emphasized the importance of the ‘process’. They argued<br />

that developing collaborative relationships takes time. On the other hand, t<strong>here</strong> was little time<br />

<strong>for</strong> direct interaction, <strong>for</strong> the project group and <strong>for</strong> other participants in the process. Towards<br />

the end of the project the emphasis on the ‘process’ was used as a defense against taking task<br />

related decisions.<br />

In the erosion case the project group met on a regular basis. This helped to feel committed to the<br />

project and to the other participants. However, the third project manager stated that meetings<br />

of the project group were no longer necessary. From that moment the members of the project<br />

group did not feel committed anymore, they worked in isolation or stopped contributing to the<br />

288


work. It seemed as if the focus on the task (‘results’, ‘visible output’) was used as a defense<br />

against potential conflicting relationships in the collaborative.<br />

A condition to develop interdependent relationships is the opportunity to engage in<br />

direct interaction. ‘Relational practices’ are activities, actions and interactions among<br />

stakeholders engaged in a collaborative process. They either occur spontaneously<br />

and in<strong>for</strong>mally (e.g. a drink), or can be organized (e.g. a field visit). The interactions<br />

take place in a particular historical and social context. Through 'content' or work, the<br />

parties engage in a 'relation' (Bouwen, 2001; Wenger, 1998). The awareness of<br />

interdependence can result in a ‘multifaceted’ identity of a change process, w<strong>here</strong> all<br />

stakeholders are connected in the process of constructing solutions <strong>for</strong> the inter-<br />

organizational domain.<br />

4.3. The paradoxical nature of ‘collaboration’: collusive behavior<br />

The notion ‘collaboration’ has a positive connotation in itself. At the outset of the<br />

projects, most participants were optimistic. They hoped that collaboration would<br />

solve the problems they were facing or create new opportunities. In most cases, the<br />

notion ‘collaboration’ represented different expectations and meanings. The meaning<br />

of collaboration was usually not explored in the process. This represents a risk in<br />

multiparty collaboration. T<strong>here</strong> may be a gap between the ideal and rhetoric of<br />

multi-stakeholder collaboration and what actually happens in practice.<br />

In some cases, the conveners used the notion ‘collaboration’ as a cover to obtain<br />

funding. Huxham and Vangen (2005) refer to ‘pseudo-aims’ that are invented to<br />

legitimize the existence of the collaborative or to pursue personal involvement in the<br />

collaboration. The strategic use of collaborative ‘jargon’ was intentional.<br />

In the erosion case the convener had used collaborative jargon in the project proposal as it was<br />

used in European policy documents (‘bottom-up approach’, multi-stakeholder strategy’). He<br />

admitted he had made strategic use of the language in order to obtain funding. T<strong>here</strong> was a<br />

difference between the proposal text and what actually happened. It soon became apparent that<br />

European money was the drive to set up the collaboration. The project was a ‘cover’ to work on<br />

the personal agenda of the engineers (e.g. carry out large construction works) and the<br />

politicians (e.g. realize visible results in the community in order to win votes). All members of<br />

the project group colluded around this issue: everybody could see what was happening and<br />

talked about it in private conversations, but no one raised it in public.<br />

289


Often the participants got frustrated about the slowness of the process, the lack of<br />

results, the complexity of the endeavor and the difficulty to make progress. In the<br />

three cases, t<strong>here</strong> was a tension between the rationality, social desirability and<br />

rhetoric of collaboration and the ambivalent emotional responses to the practice or<br />

prospect of collaboration. The case analyses demonstrate that entering a collaborative<br />

often provokes anxiety in the participants. In all cases, some <strong>for</strong>m of collusion<br />

emerged. The participants tacitly agreed to cover up unwanted or unacceptable<br />

aspects that emerged in the process. In doing so, they seemed to protect the group<br />

from confrontation with reality and the anxiety this may have provoked (e.g.<br />

embarrassment, unethical behavior, failure).<br />

In foster care the participants tried to develop structural collaboration, while at the same time<br />

the subsidizing policy - identified as the main obstacle to collaboration - was maintained. They<br />

claimed to work on new ways of organizing in the benefit of the children, but self-interests were<br />

predominant. The managers in the project group argued they wanted to ‘sit on their chair’ to<br />

defend the interests of their organization and thus engaged in positional bargaining. T<strong>here</strong> was<br />

no plat<strong>for</strong>m w<strong>here</strong> the interests of the domain were represented. This issue was mentioned in<br />

individual conversations, but nobody raised it in public. The underlying aim seemed to be the<br />

survival of the individual organizations in the prospect of a potential imposed merger of the<br />

services.<br />

In the cases, two different organizational logics were present. On the one hand, the<br />

multiparty strategy, w<strong>here</strong> all parties with a stake in the domain are considered as<br />

legitimate stakeholders. On the other hand, a participation logic, w<strong>here</strong> a small<br />

group of key actors decides on how ‘collaboration’ is organized and implemented.<br />

This reflects a top-down vision on participation. As Miller (1993, xvi) argues, “(…) the<br />

notion of giving power is in<strong>here</strong>ntly patronizing – it implies dependency – and hence is of<br />

itself disempowering”.<br />

However, the final power of decision-making was with players in the context: policy<br />

makers, sponsoring organizations or politicians. They were the ones deciding on<br />

funding, approval or disapproval of plans, and implementation. The existing power<br />

relations in the domain were maintained. This made it hard <strong>for</strong> the collaborative to<br />

work from a shared power base (Himmelman, 1996; Vansina, 2002). It jeopardized<br />

290


the credibility of the collaborative endeavor and the cautious attempts to involve<br />

stakeholders in the process.<br />

In all cases, the participants found themselves in a paradoxical situation. The contract<br />

with the sponsoring organization was at the origin of this situation. What in essence<br />

was intended as an emergent, open and t<strong>here</strong><strong>for</strong>e unpredictable process was caught<br />

in procedural language and pre-established structures and procedures. A condition<br />

to obtain funding is to speak the procedural language of sponsors and ‘play the<br />

game’. However, this language cannot grasp the essence of an emergent process. One<br />

of the consultants used the following powerful image to describe this phenomenon:<br />

‘You cannot broadcast a video through the radio’. Financing organizations look <strong>for</strong><br />

certainty in structures, w<strong>here</strong>as participants in the collaborative seemed to be looking<br />

<strong>for</strong> certainty in their relationships (e.g. trust, commitment). Thus, those making the<br />

collaboration possible, dictated the opportunities, norms and restrictions <strong>for</strong> the<br />

projects. In some sense, the funding organizations were part of the problem.<br />

Participants found themselves in a double bind: external authorities established the<br />

terms <strong>for</strong> collaboration and at the same time expected the participants to act by<br />

themselves (Quaghebeur, Masschelein & Huong Nguyen, 2004). The contract was<br />

bounded and limited the freedom of the participants to be critical. It was hard to<br />

question or criticize the authorities, as they were the ones enabling the collaborative<br />

process. Nobody tried to re-negotiate the terms of the contract.<br />

The following model (figure 2) is a visual representation of the issues that influence<br />

direction setting in collaborative work.<br />

291


Antecendents<br />

Collaborative<br />

relationships<br />

Figure 2: A systems psychodynamic process model <strong>for</strong> direction setting in<br />

multiparty collaboration.<br />

Context<br />

Manifest dynamics of direction setting<br />

Latent dynamics of direction setting<br />

Formalizing of<br />

the process<br />

292<br />

Task


NEW PERSPECTIVES ON DESIGNING AND FACILITATING EMERGENT<br />

ORGANIZATIONAL PROCESSES<br />

In this final paragraph, I discuss some challenges <strong>for</strong> organizational development<br />

posed by the turbulent organizational context of today. I briefly discuss a few<br />

perspectives on designing and facilitating new processes of organizing and change.<br />

Then I present some critical competencies <strong>for</strong> those leading and facilitating<br />

collaborative processes based on this research. The intention is not to present them as<br />

a prescription or as a recipe, but they can be used as general guidelines or<br />

recommendations.<br />

Organizational development (French & Bell, 1990) is based on assumptions that are<br />

no longer valid in new <strong>for</strong>ms of organizing characterized by horizontal relationships,<br />

complexity, high levels of interdependence, and unpredictability. Cummings and<br />

Worley (2001) introduced the notion of ‘Trans-organizational Design’. Their<br />

approach supports organizations to develop collaborative strategies with other<br />

organizations. They present a strategy of planned change with ‘application stages’ to<br />

create trans-organizational systems: identification stage, convention stage,<br />

organization stage, and evaluation stage. Although this approach may be helpful to<br />

structure the process, important aspects are missing. Stacey (2003) presents a<br />

perspective on change based on complexity theory. He stresses the need to<br />

understand processes of human relating in a context of increased interdependency.<br />

Participation means direct interaction between people in a self-organizing process in<br />

which patterns emerge. His theory is an attempt to understand the insights from<br />

psychoanalysis on human behavior in terms of a process theory. Homan (2005)<br />

emphasizes that change in turbulent contexts is not predictable and controllable and<br />

that such processes are hard to plan and manage. His contribution is a combination<br />

of insights from social constructionism and complexity theory in an attempt to<br />

increase understanding of the natural dynamics of change. Bouwen and Taillieu<br />

(2004) emphasize the need to focus on the social dynamics that lead to sharing<br />

293


esponsibility: in<strong>for</strong>mation exchange, shared construction of reality, empowerment,<br />

and internalization.<br />

The transitional approach to change (Amado & Ambrose, 2001; Amado & Vansina,<br />

2005) emphasizes that change is not a linear process moving towards a clear and<br />

predefined ‘vision’ of the future. Change reflects a state of temporary confusion and<br />

uncertainty that can be overwhelming and result in defensive responses to contain<br />

the anxiety. Under favorable conditions, however, the participants can use such a<br />

state <strong>for</strong> experimentation, innovation, and <strong>for</strong> creatively designing a new future <strong>for</strong><br />

the domain or a reinvention of the organizations involved. Change is viewed as a<br />

psychosocial process and not just as an organizational process. This implies that<br />

changing structures and procedures is not sufficient. The convener or leader needs to<br />

take the emotional responses, the underlying dynamics, and the complex nature of<br />

people and groups into account (Amado, Faucheux & Laurent, 1990; Amado &<br />

Amato, 2001a; 2001b; Huffington, James & Armstrong, 2004). They cannot come up<br />

with a plan or promise a ‘solution’. The contribution of those taking up a leading role<br />

is to facilitate the search process. Change can be more or less planned when the<br />

objective is clearly defined and when all noses point in the same direction. However,<br />

in collaborative processes t<strong>here</strong> are many different ‘noses’ that point in different<br />

directions and often the direction to take is unclear.<br />

In this research, I was interested in the way in which anxieties stirred up by the<br />

organizational context influence processes of organizing. This research argues that<br />

change in multi-actor contexts is unpredictable and open-ended and that planning of<br />

the process is difficult. Although change ef<strong>for</strong>ts, such as multiparty collaboration, are<br />

often described in procedural terms, such processes are essentially iterative, heuristic<br />

and ongoing. I view change as an opportunity <strong>for</strong> people to increase their<br />

understanding of the realities around them, to become aware of the part they play in<br />

the whole, to develop a shared vision of the future, and to increase awareness of how<br />

they need to change to realize their vision. I assume that it is impossible to make<br />

people change. It is critical, however, to create conditions to increase chances that<br />

294


people will make the changes themselves (Amado & Ambrose, 2001). In the<br />

following paragraph, I discuss some important competencies and interventions to<br />

facilitate emergent processes w<strong>here</strong> participants can share responsibility <strong>for</strong> direction<br />

setting.<br />

Critical competencies <strong>for</strong> designing and leading emergent<br />

processes<br />

Containment<br />

A critical task of ‘leadership’ is containment of the negative emotions, conflicting<br />

feelings and anxieties provoked by the change process. Containment (Bion, 1970) is a<br />

psychic task w<strong>here</strong> those in a leading role temporarily carry the stress of the<br />

participants in order to protect them from 'destruction' or from being overwhelmed<br />

by the demands and complexity of the situation. It refers to the capacity of those<br />

facilitating the change to deal with the messiness, uncertainty and unknown outcome<br />

of the process. The facilitator cannot rely on blueprints or checklists and needs to<br />

resist the temptation of prematurely structuring and organizing the process. This<br />

means that those in a leading role need to manage their personal anxieties and<br />

contain feelings of uncertainty and inadequacy.<br />

The process leader is confronted with the insecurities, anxieties and aspirations of the<br />

participants. Good leadership, according to Al<strong>for</strong>d (2001), is about interpreting the<br />

hopes and fears of the parties and helping them to face the anxiety and work it<br />

through without projecting it 'out t<strong>here</strong>'. The ‘leader’ should be capable to stay in<br />

touch with the <strong>here</strong>-and-now, with the underlying anxieties of the participants, and<br />

to contain the messiness sufficiently long to enable alternative solutions to emerge<br />

(Vansina, 2002). This requires the capacity to sense and understand underlying<br />

dynamics and to cope with the emotions stirred up by the change. It is also important<br />

to resist the regressive pull of groups to reduce the diversity, interdependence and<br />

complexity of the process. Potentially destructive dynamics need to be contained,<br />

because they may harm the process and the participants.<br />

295


In <strong>for</strong>ms of organizing w<strong>here</strong> distributed leadership is promoted, containment needs<br />

to be provided at the group level. The participants need to foster a culture of<br />

collective reflection, share and process experiences, suspend judgment, engage with<br />

conflicts, challenge and explore differences of perspective both overt and convert.<br />

The challenge is to mobilize or develop processes, structures and interventions to<br />

contain the organizational anxiety of emergent processes when hierarchical channels<br />

are not available (Huffington, et al., 2004).<br />

Transitional space: sense making<br />

Those leading the process can support the participants to work through the<br />

inevitable tensions of collaborative work by providing time and space <strong>for</strong> sense<br />

making. A facilitating environment is a setting that itself can be trusted to provide<br />

physical and psychological safety. A holding environment gives people the feeling<br />

that their feelings of anxiety and insecurity are acceptable (Overlaet & Barrett, 2000).<br />

Leadership can establish such a holding environment by “(...) serving as a safe<br />

container who can accept and survive the anxieties and sometimes hostile projections coming<br />

from the client system.” (Miller, 1997, 191) The facilitator uses interventions to enable a<br />

double adaptation process. He helps the participants to adapt their inner and outer<br />

world, as well as their rational knowing and emotional feeling to the new, emergent<br />

situation (Vansina, 2004). In such conditions, the participants can use the space as a<br />

'potential space' (Winnicott, 1971): they engage in an open relationship with the other<br />

parties and share 'valid in<strong>for</strong>mation' (Argyris, 1999). They explore issues that might<br />

normally be anxiety provoking, politically subversive or counter-cultural. They learn<br />

to live with the paradoxes and dilemmas that are in<strong>here</strong>nt in collaborative work.<br />

Participants work through the feelings that emerge during the work, which<br />

otherwise become suppressed or operate in an underground manner. When such<br />

feeling are contained, and the participants can make sense of them and learn from<br />

them, they can be integrated <strong>for</strong> work rather than counter-work purposes (Long, et<br />

al., 2000).<br />

296


In the positive sense, the participants can also use a transitional space to share their<br />

dreams, hope, and fantasies; they can 'play' with ideas, try out potential scenarios <strong>for</strong><br />

the future without binding consequences. This facilitates creativity and innovation<br />

and enables the transition to something ‘new’. Relating to one another in this way<br />

may foster commitment to the task, to the other stakeholders and enables the group<br />

to develop. It allows parties to feel responsible <strong>for</strong> the collective output and to be<br />

emotionally invested (Krantz, 1998). A transitional space is a meaningful space <strong>for</strong><br />

acknowledging different understandings, and a social space <strong>for</strong> acknowledging each<br />

other’s presence and identity (Bouwen & Taillieu, 2004).<br />

A transitional space support participants in the changes they are going through.<br />

Bridger observed that people engage in three different but closely related types of<br />

transitional experiences. (1) Relinquishing earlier roles, ideas and practices; (2)<br />

creating, finding, or discovering new, more adaptive and feasible ideas and ways of<br />

thinking and acting; (3) coping with the instability of changing conditions and with<br />

the insecurity, this change provokes (Ambrose, 2001). Some <strong>for</strong>m of ‘cover’,<br />

‘com<strong>for</strong>ter’, or transitional object (Winnicott, 1971) can facilitate the change.<br />

According to Bridger the function of com<strong>for</strong>ter “(…) permits some expression of<br />

relationship with an uncertain external world while using fantasy exploration/working-<br />

through phases of the transitional process to be developed and carried out” (Amado<br />

&Ambrose, 2001, xii). Transitional experiences can be facilitated in different ways.<br />

Interventions do not have to be restricted to verbal reflections. Relational practices,<br />

different <strong>for</strong>ms of engaging, or visual representations can help to make the transition.<br />

In an African hospital, <strong>for</strong> instance, action researchers radically changed their<br />

approach when a classic OD intervention had failed. They started using visual<br />

images (photos and video), recorded by the people working in the hospital, as an<br />

intervention. The aim was to make them aware of the risks of their hygienic practices<br />

(contamination of HIV and tuberculosis) and to generate creative solutions <strong>for</strong><br />

increasing safety in the hospital (Lhuillier & Rolland, 2005). However, facilitators<br />

cannot choose a transitional object <strong>for</strong> a group. The participants choose an ‘object’,<br />

297


which in essence is neutral. When they invest their emotional energy in the object<br />

(e.g. a ‘plan’, a visual image, a slogan), it can function as a transitional object <strong>for</strong> the<br />

group and help them cope with the change.<br />

Reviewing: reflection-in-action<br />

Groups are usually action oriented and focused on the task. Leadership can<br />

encourage and support the group to engage in ‘reflective action’ (Schön, 1983) and<br />

reviewing as an opportunity <strong>for</strong> learning from the experience. Reviewing is an<br />

attempt of a human system to increase awareness of how it is functioning at both the<br />

manifest and the latent level. The aim of reviewing is to achieve the task and purpose<br />

<strong>for</strong> which the system exists. “The purpose of review is to make sense of the system’s inner<br />

life and to optimize its ongoing capability in a conscious way while remaining in tune and in<br />

touch with the wider system of which it is part.” (Amado & Sharpe, 2001). This process is<br />

at the root of learning from experience, creativity and innovation. It helps the group<br />

to evaluate if the goals it is pursuing are still valid. The participants reflect on past<br />

activities and collaboration with the intention to commit to future actions (Vansina,<br />

2005). A secure atmosp<strong>here</strong> w<strong>here</strong> the ‘search <strong>for</strong> sense’ is central and w<strong>here</strong><br />

uncom<strong>for</strong>table feelings that could disrupt constructive work are contained, provides<br />

a facilitating condition <strong>for</strong> reviewing. Unconscious obstacles (e.g. dependency) often<br />

hinder the participants in their capacity <strong>for</strong> self-analysis. Power issues (e.g. presence<br />

of a manager) may inhibit open expression (Amado & Sharpe, 2001). Those<br />

facilitating collaborative work can encourage exploration, sharing, comparing and<br />

finding out (Harrisson, 1970; Vansina, 2005). In doing so, they have to take the<br />

readiness and maturity of the participants and the level of trust among them into<br />

account.<br />

Reviewing focuses on how individual and group ef<strong>for</strong>ts affect the direction of the<br />

process how the organization emerges in the interactions. Those engaged in<br />

emergent processes can benefit from reviewing. It increases their system awareness<br />

and helps them understand the manifest and latent dynamics that influence the<br />

298


process. The participants can discover, <strong>for</strong> instance, what the system is doing to them<br />

or how defensive inter-group dynamics obstruct task-oriented work. Reviewing can<br />

help them to keep in mind that the collaborative is part of an overall system of<br />

organizations (Huffington et al., 2004). It is not about ‘managing’ change, but about<br />

how the participants themselves become aware of how they are changing (Homan,<br />

2005).<br />

Conveners, leaders and participants cannot establish the system features of a<br />

collaborative process in advance. The collaborative process is ‘emergent’ and<br />

t<strong>here</strong><strong>for</strong>e the focus shifts towards the process itself. A reviewing process emphasizes<br />

sense making of the dynamics in the <strong>here</strong>-and-now. Reflection on the process helps<br />

the participants to establish the optimal way to organize and structure the process in<br />

a conscious manner, based on valid in<strong>for</strong>mation. As the process unfolds, the<br />

participants negotiate the psychological boundaries in order to facilitate work on the<br />

task. They are stimulated to take up ownership and to set the direction of the process<br />

in shared responsibility. In the process, they engage in social learning (Schusler,<br />

Decker & Pfeffer, 2003; Bouwen & Taillieu, 2004; HarmoniCop, 2005).<br />

As Cooper and Dartington (2004) point out, participants often experience a focus on<br />

reflection and process issues as ‘touchy-feely’. Moreover, reflection is always under<br />

pressure of more ‘urgent and important matters’. This research has demonstrated<br />

the importance of the ‘process’ and relational aspects of organizing in complex<br />

settings. Containment, the creation of a transitional space and reviewing are<br />

interventions and processes that help to cope with the tensions of collaborative work.<br />

They support all those involved in the process to deal with the issues that influence<br />

direction setting in a balanced way. A task that is sufficiently clear and shared, while<br />

at the same time open enough to stimulate creativity and innovation. A <strong>for</strong>malization<br />

of the process in order to foster containment, but not too structured to obstruct the<br />

benefits of collaboration. Relationships characterized by trust, openness and respect,<br />

but with sufficient tension to foster constructive conflict and creativity. Finally, a<br />

system with a boundary that is adequately firm to provide an identity <strong>for</strong> the group,<br />

299


and sufficiently fluid in order to respond to the opportunities and threats in the<br />

environment.<br />

To conclude<br />

During the research, I often wondered if multiparty collaboration is an ideal or<br />

ideology, mainly fostered and defended by researchers, or if it is a realistic and<br />

effective organizational strategy to develop solutions <strong>for</strong> inter-organizational<br />

problem domains. This research made me understand t<strong>here</strong> is no ideal model to<br />

design or facilitate collaborative processes aimed at solving complex societal and<br />

environmental problems. Conveners, stakeholders, coordinators, policy makers,<br />

consultants, experts and other players engaged in collaborative work find themselves<br />

in a complex, turbulent field of <strong>for</strong>ces. They need to let go of the illusion t<strong>here</strong> is an<br />

‘ideal approach’, a ‘blueprint’ or ‘best way’. T<strong>here</strong><strong>for</strong>e, it is not sufficient to develop<br />

‘handbooks’ or ‘checklists’ to deal with the messiness and complexity of the process.<br />

It is hard <strong>for</strong> all players to have an impact on the direction of the process and to<br />

structure to work or predict its outcome. The only way is to improve the<br />

‘collaborative capability’ (Huxham, 1993) of all parties involved.<br />

A better awareness of the specific nature of collaborative processes, the critical issues<br />

and dilemmas that influence the process and the underlying dynamics that either<br />

facilitate or obstruct change may help to facilitate each collaborative endeavor in its<br />

own, optimal way. The aim of this research was to increase psychological<br />

understanding of the ‘mechanisms that make things work’, and to assess how<br />

participants establish and enact ‘group locomotion’. T<strong>here</strong><strong>for</strong>e, I have analyzed and<br />

discussed different aspects that influence direction setting. In practice, however,<br />

these issues are all part of an ongoing stream of activities. The challenge is to<br />

facilitate the process as a whole and to work with all the issues simultaneously. I<br />

sincerely hope this research has contributed to a deeper understanding of the nature<br />

of collaborative processes.<br />

300


REFERENCES<br />

Ackoff, R. (1997). Systems, Messes and Interactive Planning. In Trist, E., Emery, F. &<br />

Murray, H. (Eds.) The Social Engagement of Social Science. A Tavistock Anthology.<br />

Volume III: The Socio-Ecological Perspective. Philadelphia: PENN, pp. 417-438.<br />

Al<strong>for</strong>d, C.F. (2001). Leadership by interpretation and holding. Organisational and Social<br />

Dynamics, 2, 153-173.<br />

Amado, G. & Ambrose, A. (Eds.) (2001). The transitional approach to change. London:<br />

Karnac.<br />

Amado, G. & Amato, R. (2001a). Organizational change theories and practices: a critical<br />

review. In Amado, G. & Ambrose, A. (Eds.) The transitional approach to change.<br />

London: Karnac, pp.29-85.<br />

Amado, G. & Amato, R. (2001b). Some distinctive characteristics of transitional change.<br />

In Amado, G. & Ambrose, A. (Eds.) The transitional approach to change. London:<br />

Karnac, 87-117.<br />

Amado, G., Faucheux, C. & Laurent, A. (1990). Changement organisationnel et réalités<br />

culturelles. Contrastes franco-américains. In Chanlat, J.F. (Ed.) L’individu dans<br />

l’organisation. Les dimensions oubliées. Les Presses de l’Université de Lavel, éditions<br />

Eska.<br />

Amado, G. & Sharpe, J. (2001). Review as a necessary ingredient in transitional change.<br />

In Amado, G. & Ambrose, A. (Eds.) The transitional approach to change. London:<br />

Karnac, pp. 119-136.<br />

Argyris, C. (1999). On organizational learning. Second edition. Ox<strong>for</strong>d: Blackwell<br />

Publishers.<br />

Bennis, W.G. & Shepard, H.A. (1956). A theory of group development. Human Relation,<br />

9 (4), 415-457.<br />

Bion, W.R. (1970). Attention and Interpretation. London: Karnac Books.<br />

Bouwen, R. (2001). Developing Relational Practices <strong>for</strong> Knowledge Intensive<br />

Organizational Contexts. Career Development, 6/7, 361-369.<br />

Bouwen, R. & Taillieu, T. (2004). Multiparty collaboration as social learning <strong>for</strong><br />

interdependence: Developing relational knowing <strong>for</strong> sustainable natural resource<br />

management. Journal of Community and Applied Social Psychology, 14, 137-153.<br />

Carlisle, J. & Leary, M. (1981). Negotiating groups. In Hackman, J. (Ed.) Groups at work<br />

(and those that don’t): creating conditions <strong>for</strong> effective teamwork. San Francisco: Jossey-<br />

Bass, pp. 165-188.<br />

301


Carr, W. (2001). The Exercise of Authority in a Dependent Context. In Gould, L.G.,<br />

Stapley, L.F. & Stein, M. (Eds.) The Systems Psychodynamics of Organizations.<br />

Integrating the Group Relations Approach, Psychoanalytic, and Open Systems<br />

Perspectives. London: Karnac, 45-66.<br />

Cartwright, D. & Zander, A., (Eds.), (1960) Group Dynamics. Research and Theory. Second<br />

Edition. New York: Harper & Row.<br />

Cooper, A. & Dartington, T. (2004). The vanishing organization: Organizational<br />

containment in a networked world. In Huffington, C., Armstrong, D., Halton, W.,<br />

Hoyle, L. & Pooley, J. (Eds.), Working below the surface. The emotional life of<br />

contemporary organizations. London: Karnac, pp. 127-150.<br />

Cummings, T.G. & Worley, C.G. (2001). Essentials of Organization Development and<br />

Change. South-Western College Publishing, Cincinnati, Ohio.<br />

Dewulf, A., Craps, M., Bouwen, R., Taillieu, T., and Pahl-Wostl, C. (2005). Integrated<br />

management of natural resources: dealing with ambiguous issues, multiple actors<br />

and diverging frames. Water Science & Technology, 52(6), 115-124.<br />

Diamond, M.A. & Allcorn, S. (1987). The Psychodynamics of Regression in Work<br />

Groups, Human Relations, 40 (8), 525-543.<br />

Eden, C. (1996). The stakeholder/collaborator strategy workshop. In Huxham, C. (Ed.)<br />

Creating collaborative advantage. London: Sage, pp. 44-56.<br />

Feyerherm, A. (1994). Multiple paths <strong>for</strong> inter-organizational journeys. Paper presented at<br />

the Workshop on Multi-Organisational Partnerships: Working together across<br />

organisational boundaries. Brussels, September.<br />

Finn, C.B. (1996). Utilizing stakeholder strategies <strong>for</strong> positive collaborative outcomes.<br />

In Huxham, C. (Ed.) Creating collaborative advantage. London: Sage Publications, pp.<br />

152-164.<br />

French, W. & Bell, C.H. (1990). Organization development. Englewood Cliffs, NJ: Prentice<br />

Hall.<br />

Gemmill, G. & Elmes, M. (1993). Mirror, Mask, and Shadow. Psychodynamic Aspects<br />

of Inter-group Relations. Journal of Management Inquiry, 2 (1), 43-51.<br />

Gould, L.J., Ebers, R. & McVicker Clinchy, R. (1999). The Systems Psychodynamics of a<br />

Joint Venture: Anxiety, Social Defenses and the Management of Mutual<br />

Dependence. Human Relations, 52 (6), 697-722.<br />

Gray, B. (1989). Collaborating: Finding Common Ground <strong>for</strong> Multiparty Problems. San<br />

Francisco: Jossey Bass.<br />

Gray, B. (1996). Cross-sectoral partners: collaborative alliances among business,<br />

government and communities. In Huxham, C. (Ed.) Creating collaborative advantage.<br />

London: Sage Publications, pp. 57-79.<br />

302


HarmoniCop (2005). Learning together to manage together. Improving participation in water<br />

management. Output of the project ‘Harmonising Collaborative Planning’, funded<br />

by the European Commission.<br />

Harrison, R. (1970). Choosing the depth of organizational intervention. The Journal of<br />

Applied Behavioral Sciences, 6 (2), 181-202.<br />

Harrison, M.I. (2005). Diagnosing organizations: Methods, models and processes. Third<br />

Edition. London: Sage.<br />

Himmelman, A.T. (1996). On the Theory and Practice of Trans<strong>for</strong>mational<br />

Collaboration: From Social Service to Social Justice. In Huxham, C. (Ed.) Creating<br />

collaborative advantage. London: Sage Publications, pp. 19-43.<br />

Hirschhorn, L. (1988). The Workplace Within. Psychodynamics of Organizational Life.<br />

Cambridge: MIT Press.<br />

Hirschhorn, L. & T. Gilmore (1992). The New Boundaries of the “Boundaryless”<br />

Company. Harvard Business Review, May/June, v70, n3, 104-115.<br />

Homan, T. (2005). Organisatiedynamica. Theorie en praktijk van organisatieverandering. Den<br />

Haag: Academic Service.<br />

Hoyle, L. (2004). From sycophant to saboteur – responses to organizational change. In<br />

Huffington, C., Armstrong, D., Halton, W., Hoyle, L. & Pooley, J. (Eds.) Working<br />

below the surface. The emotional life of contemporary organizations. London: Karnac, pp.<br />

87-106.<br />

Huffington, C., James, K. & Armstsrong, D. (2004). What is the emotional cost of<br />

distributed leadership? In Huffington, C., Armstrong, D., Halton, W., Hoyle, L. &<br />

Pooley, J. (Eds.) Working below the surface. The emotional life of contemporary<br />

organizations. London: Karnac, pp. 67-82.<br />

Huxham, C. (1993). Collaborative capability: an intra-organizational perspective on<br />

collaborative advantage. Public Money and Management, 12 (July-September), 21-28.<br />

Huxham, C. (Ed.) (1996). Creating collaborative advantage. London: Sage Publications.<br />

Huxham, C. & Vangen, S. (2003). Enacting leadership <strong>for</strong> collaborative advantage:<br />

dilemmas of ideology and pragmatism in the activities of partnership managers.<br />

British Journal of Management, 14, 61-76.<br />

Huxham, C. & Vangen, S. (1996). Working together: key themes in the management of<br />

relationships between public and not <strong>for</strong> profit organizations. International Journal of<br />

Public Sector Management, 9 (7), 5-17.<br />

Huxham, C. & Vangen, S., (2000) Leadership in the Shaping and Implementation of<br />

Collaboration Agendas: how Things happen in a (not quite) Joined-up World.<br />

Academy of Management Journal, 43 (6), 1159-1175.<br />

303


Huxham, C. & Vangen, S. (2005). Managing to collaborate. The theory and practice of<br />

collaborative advantage. London: Routledge.<br />

Koppenjan, J. & Klijn, E.H. (Eds.) (2004). Managing uncertainties in networks. London:<br />

Routledge.<br />

Krantz, J. (1998). Anxiety & the New Order. In Klein, E.B. & Gabelnick, F. & Herr, P.<br />

(Eds.) The Psychodynamics of Leadership, Madison: Psychosocial Press, pp. 77-107.<br />

Lawrence, W.G. & Robinson, P. (1975). An innovation and its implementation: issues of<br />

evaluation, document no. CASR 1069, Tavistock Institute of Human Relations<br />

(unpublished). (cf. Miller, E. (1993). From dependency to autonomy. Studies in<br />

organization and change. London: Free Association Books).<br />

Levinson, H. (2002). Organizational Assessment. A step-by-step guide to effective consulting.<br />

Washington: American Psychological Association.<br />

Lhuillier, D. & Rolland, D. (2005). Action research and transitional processes: Risk<br />

prevention in a hospital in Burundi. In Amado, G. & Vansina, L. (Eds.), The<br />

transitional approach in action. London: Karnac, pp. 175-194.<br />

Long, S., Newton, J. & Dalgleish, J. (2000). In the presence of the other: developing<br />

working relations <strong>for</strong> organizational learning. In Klein, E.B., Gabelnick, F. & Herr,<br />

P. (Eds.) Dynamic consultation in a changing workplace. Madison: Psychosocial Press,<br />

pp.161-192.<br />

MacKenzie, K.D. (1986). Organizational Design: the organizational audit and analysis<br />

technology. New Jersey: Ablex Publishing Corporation.<br />

Maier, N.R.F. (1963). Problem-solving discussions and conferences. New York: McGraw<br />

Hill.<br />

Menzies Lyth, I. (1988). Containing Anxiety in Institutions. Selected essays. Volume 1.<br />

London: Free Association Books.<br />

Miller, E.J. (1993). From Dependency to Autonomy: Studies in Organization and Change.<br />

London: Free Associations Books.<br />

Miller, E. (1997). Effecting organisational change in large complex systems: a<br />

collaborative consultancy approach. In Neumann, J.E., Kellner, K. & Dawson-<br />

Sheperd, A. (Eds.) Developing Organisational Consultancy, London: Routledge, pp.<br />

187-212.<br />

Mills, T. (1967). The sociology of small groups. NJ: Prentice Hall.<br />

Overlaet, B. & F. Barrett (2000). The Dynamics of Transitional Space, Paper submitted to<br />

the ODC Division of the Academy of Management Meeting, Toronto.<br />

304


Quaghebeur, K., Masschelein, J. & Huong Nguyen, H. (2004). Paradox of participation:<br />

giving or taking part? Journal of Community & Applied Social Psychology, 14, 154-165.<br />

Rice, A.K. (1958). Productivity and social organization: the Ahmedabad experiment.<br />

Tavistock. Reprinted, New York and London: Garland Publishing, 1987.<br />

Ring, P.S. & Van de Ven, A.H. (1994). Developmental processes of cooperative<br />

interorganizational relationships. Academy of Management Review, 19 (1), 90-118.<br />

Schön, D. A. (1983). The reflective practitioner. How professionals think in action. Basic<br />

Books.<br />

Schruijer, S. (1990). Norm violation, attribution theory and attitudes in intergroup relations.<br />

Tilburg: Tilburg University Press.<br />

Schuman, S.P. (1996). The role of facilitation in collaborative groups. In Huxham, C.<br />

(Ed.) Creating collaborative advantage, London: Sage Publications, pp. 126-140.<br />

Schusler, T.M., Decker, D.J. & Pfeffer, M.J. (2003). Social learning <strong>for</strong> collaborative<br />

natural resource management. Society and Natural Resources, 15, 309-326.<br />

Stacey, R.D. (2003). Complexity and group processes. A radically social understanding of<br />

individuals. Hove: Brunner-Routledge.<br />

Taillieu, T., Schruijer, S. & Vansina, L. (2000). Dynamiek van samenwerking tussen<br />

organisaties. In Bouwen, R., De Witte, K., De Witte, H. & Taillieu, T. (Eds.) Van<br />

groep naar gemeenschap. Liber Amoricum Prof. Dr. Leo Lagrou, Leuven: Garant, pp.<br />

147-164.<br />

Thomas, R.Jr. (1995). A diversity framework. In Chemers, M., Oskamp, S. & Constanzo,<br />

M. (Eds.) Diversity in organizations: New perspectives <strong>for</strong> a changing workplace. London:<br />

Sage.<br />

Triest, J. (1999). The Inner Drama of Role Taking in an Organization. In French, R. &<br />

Vince, R. (Eds.) Group Relations, Management and Organization, Ox<strong>for</strong>d University<br />

Press, 209-223.<br />

Trist, E. (1983). Referent Organizations and the Development of Inter-Organizational<br />

Domains, Human Relations, 36 (3), 269-284.<br />

Turcotte, M.F. & Pasquero, J. (2001). The paradox of multi-stakeholder collaborative<br />

roundtables. The Journal of Applied Behavioral Science, 37 (4), December, 447-464.<br />

Vanbeselaere, N. (2000). De social-psychologische benadering van intergroepsrelaties.<br />

In Bouwen, R., De Witte, K., De Witte, H. & Taillieu, T. (Eds.) Van groep naar<br />

gemeenschap. Liber amicorum Prof. Dr. Leo Lagrou. Leuven: Garant, pp. 165-184.<br />

Vansina, L. (2002). Making the best out of diversity: working towards collaboration between<br />

different interest groups. Paper presented at the annual symposium of the Society <strong>for</strong><br />

the Psychoanalytic Study of Organizations, Melbourne, June.<br />

305


Vansina, L. (2004). Over zin en onzin van psychodynamiek voor organisatieadviseurs.<br />

In Varwijk, W.G.J.M. & van Zijl, R.M.H.J. (Eds.) Strategie moet je samen doen. Visies<br />

op strategisch management uit theorie en praktijk. Liber amicorum Prof.Dr. Michel<br />

Vandenput. Ubbergen: Tandem Felix Uitgevers, pp. 159-177.<br />

Vansina, L. (2005). The art of reviewing: a cornerstone in organizational learning. In<br />

Amado, G. & Vansina, L. (Eds.) The transitional approach in action. London: Karnac,<br />

pp. 227-254.<br />

Vansina, L. (2007). Groups as tip of the iceberg: Locating issues in context. In: Vansina,<br />

L. et al. (Eds.) Sense and nonsense of psychodynamics <strong>for</strong> consultants and managers. (to<br />

be published in 2007).<br />

Vansina, L., Taillieu, T. & Schruijer, S. (1998). “Managing” Multiparty Issues: Learning<br />

from Experience. In W. Pasmore & R. Woodman (Eds.) Research in Organizational<br />

Change and Development (vol. 11), JAI Press Inc., pp. 159-181.<br />

Wenger, E. (1998). Communities of Practice. Learning, Meaning, and Identity. Cambridge<br />

University Press.<br />

Winnicott, D.W. (1971). Playing and Reality. London: Routledge.<br />

Zagier Roberts, V. (1994). Conflict and collaboration. Managing inter-group relations.<br />

In Obholzer, A. & Zagier Roberts, V. (Eds.) The unconscious at work, London:<br />

Routledge, pp. 187-196.<br />

306


307


ATTACHMENT 1: COPP MEMBERS INVOLVED IN THE DIFFERENT PROJECTS<br />

For the sake of anonymity I have used the following abbreviations to refer to my<br />

colleagues of the COPP who were in some way involved in the different projects.<br />

Erosion project<br />

COPP members Role and involvement Referred to as<br />

CO1 Senior researcher: design, facilitation “Facilitator”<br />

CO2 Senior researcher: design, facilitation “Facilitator”<br />

CO3 Researcher: documentation of the process,<br />

River valley project<br />

interviewing, feedback, design, some<br />

facilitation<br />

“Researcher”, “I”<br />

COPP members Role and involvement Referred to as<br />

CO1 Senior researcher: interviewing, feedback,<br />

facilitation of workshop, reporting <strong>for</strong><br />

HarmoniCOP<br />

CO2 Junior researcher: interviewing, feedback;<br />

involved during the first 6 months<br />

CO3 Researcher: documentation of the process,<br />

interviewing, feedback<br />

“we”<br />

“we”<br />

“we”<br />

Attachments


Foster care<br />

COPP members Role and involvement Referred to as<br />

CO1 Senior researcher only involved during the<br />

preparatory phase<br />

CO2 Senior researcher, consultant to the project:<br />

facilitation and scientific coordination<br />

CO3 Senior researcher, consultant to the project:<br />

mainly facilitation of stakeholder<br />

conferences and work groups<br />

CO4 Coordinator, scientific collaborator at the<br />

center: daily management, research,<br />

reporting, facilitation<br />

CO5 Researcher: documentation of the project,<br />

some facilitation<br />

CO6 Senior researcher: only marginally involved<br />

“Senior researcher”<br />

“Facilitator”<br />

“Coordinator”<br />

“Researcher”<br />

Attachments


ATTACHMENT 2: OVERVIEW OF THE STAKEHOLDERS INTERVIEWED IN<br />

FOSTER CARE<br />

Stakeholder cluster Organization/social<br />

group<br />

Authorities – Subsidizing<br />

organization 1<br />

– Subsidizing<br />

organization 1<br />

– Subsidizing<br />

organization 2<br />

– Subsidizing<br />

organization 3<br />

– Province<br />

Umbrella organizations – Federation foster care<br />

– Organization <strong>for</strong><br />

employers (catholic)<br />

– Organization <strong>for</strong><br />

employers (pluralistic,<br />

handicapped)<br />

– Organization <strong>for</strong><br />

employers (pluralistic,<br />

youth care)<br />

Relegating parties – Juvenile court 1<br />

Other institutions or<br />

centers<br />

– Juvenile court 2<br />

– Social committee<br />

– institution <strong>for</strong> youth<br />

care 1<br />

– institution <strong>for</strong> youth<br />

care 2<br />

– institution <strong>for</strong> youth<br />

care 3<br />

Interviewees<br />

– Staff member of<br />

headquarters<br />

– Provincial<br />

representative<br />

– Coordinator + 2 staff<br />

members<br />

– Director<br />

– Provincial depute<br />

welfare<br />

– Head<br />

– Director<br />

–<br />

– Coordinator<br />

–<br />

– Coordinator<br />

– Judge<br />

– Judge + head social<br />

service<br />

– Regional coordinator +<br />

6 team members<br />

– Director<br />

– Director<br />

– Director + social<br />

assistant<br />

– Coordinator<br />

– Coordinator<br />

Attachments


– day center 1<br />

– day center 2<br />

Target groups Foster parents Group interview with 4<br />

Experts Project ‘integrated care <strong>for</strong><br />

Foster care services (FC):<br />

employees<br />

Foster care services: board<br />

members<br />

Foster care services:<br />

managers<br />

youth’<br />

FC 1<br />

FC 2<br />

FC 3<br />

FC 4<br />

FC 5<br />

FC 1<br />

FC 2<br />

FC 3<br />

FC 4<br />

FC 5<br />

FC 1<br />

FC 2<br />

FC 2<br />

FC 3<br />

FC 4<br />

FC 5<br />

foster parents<br />

3 coordinators<br />

6 employees<br />

2 employees<br />

1 employee (+ Director)<br />

3 employees<br />

8 employees<br />

President<br />

President<br />

President<br />

President<br />

President + Director<br />

Director<br />

Coordinator<br />

Director<br />

Director (+ employee)<br />

Director<br />

Coordinator<br />

Total: 34 interviews Total: 66 persons<br />

Attachments


ATTACHMENT 3: PRESENTATION OF ANALYSIS STAKEHOLDER INTERVIEWS<br />

(Slide presentation of the analysis per stakeholder cluster, presented to the project<br />

group on 24 March 2004 and 22 April 2004.)<br />

Gebruikte afkortingen:<br />

PGZD = pleeggezinnendienst<br />

SW = samenwerking<br />

IJH = Integrale Jeugdhulp<br />

PZ = Pleegzorg<br />

RvB = Raad van Bestuur<br />

BJB = Bijzondere Jeugdbijstand<br />

Q = kwaliteit<br />

⌦ : geeft een spanningsveld aan (‘versus’)<br />

� = ‘leidt tot’<br />

COPP<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

Terugrapportering: introductie<br />

• Tijd: Februari – maart<br />

• Lijst stakeholders opgesteld op vorige<br />

projectvergaderingen<br />

• Verlaten begrip ‘loketfunctie’: te vaag,<br />

oplossingsgericht<br />

• 4 basisvragen: huidig, toekomstige,<br />

hinderpalen/hefbomen, betrokken actoren<br />

– Vrij open vragen � mogelijkheid tot verhaal<br />

– Minimale basisstructuur � analyse<br />

Attachments


COPP<br />

COPP<br />

COPP<br />

Doelgroepen:<br />

Kind, ouder,<br />

Pleegouder, VVP<br />

Doorverwijzer:<br />

JRB, Soc. Dienst,<br />

Comité, PEC<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

Overzicht stakeholders<br />

Overheid:<br />

Administratie &<br />

provincie<br />

Pleeggezinnen-<br />

Diensten:<br />

Personeel, RvB,<br />

directie<br />

Experten<br />

IJH, UGent,<br />

K.U.Leuven<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

Analyse gegevens<br />

• Interviewgegevens: uitgeschreven<br />

interviews<br />

• Rijke bron aan in<strong>for</strong>matie<br />

• Analyse met twee onderzoekers<br />

• Per stakeholder oplijsting antwoorden op<br />

basisvragen � gelijkenissen en verschillen<br />

duiden<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

Resultaten<br />

• Nog niet alle stakeholders bevraagd<br />

• Perspectief ‘perceptie van dienstverlening’<br />

en ‘perceptie van samenwerking’<br />

• Algemene lijnen<br />

Aanwezige<br />

Hefbomen<br />

Huidig Toekomst<br />

Hinderpalen<br />

Conditionele<br />

Hefbomen<br />

Vertegenwoordiging:<br />

WG-koepels &<br />

federatie<br />

Andere voorziening:<br />

OOOC, CKG, OBC,<br />

Thuisbegeleidingsdienst<br />

Attachments


COPP<br />

• Relatie CKG/OOOC en<br />

PGZD: oriëntatie, selectie gezin,<br />

overgang � geen continuïteit,<br />

weinig wederzijdse bevruchting<br />

• Positionering/ profilering van<br />

PGZD niet duidelijk<br />

• Plaats natuurlijke ouders?<br />

• SW = persoonlijk gegroeide<br />

contacten<br />

• PGZD: voorlopers in SW,<br />

deskundig, individueel naar<br />

buiten<br />

• Verschil tussen PGZD:<br />

theoretisch, procedures, relatie<br />

doorverwijzer<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

Andere voorzieningen<br />

• IJH<br />

• locatie<br />

• contextueel<br />

• visie en<br />

engagement<br />

• beleid: lijnen en<br />

opvolging<br />

• PZ profileren<br />

• Ideologie<br />

• Overleg, enkel op directieniveau<br />

• Tijdsdruk<br />

• Regelgeving<br />

• PZ als ‘zaligmakend<br />

• Comité als drempel<br />

• Op maat van het kind:<br />

vraaggestuurd<br />

• Overgang: continuïteit,<br />

duidelijke regels, overdracht<br />

dossier, traject volgen,<br />

complementariteit<br />

• Regelmatige in<strong>for</strong>matie:<br />

in<strong>for</strong>meren en vraagbaak<br />

• Verruimen van aanbod<br />

• Geen eenheidsworst:<br />

accentverschillen zijn goed<br />

• Duidelijker profileren: PZ op<br />

sociale kaart zetten,<br />

verduidelijken aanbod<br />

Attachments


COPP<br />

• LOP: goed aanspreekpunt, basis<br />

samenwerking<br />

COPP<br />

• Versnippering over 3 sectoren<br />

• Aanbodgestuurd<br />

• PZ imago van BJB<br />

• Onduidelijkheid voor kandidaat<br />

pleegouders<br />

• niet professioneel in<br />

vertegenwoordiging<br />

• te weinig specialisme<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

• goed fundament<br />

• potentieel<br />

• intersectoraal<br />

denken<br />

• Ideologie<br />

Experts<br />

• Regelgeving<br />

• duidelijke opdracht: visie?<br />

• keuzes: specialisatie,<br />

gemeenschappelijkheid<br />

•Mandaat LOP?<br />

•Afstemmen IJH & PZ<br />

•2 andere sectoren ook<br />

betrekken<br />

•Overheid:<br />

randvoorwaarden<br />

• Beslissingsstructuur: niveau PGZD<br />

en inbedding in sectoren<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

Overheid<br />

•Integratiegedachte<br />

aanwezig in PZ<br />

• Rijp klimaat<br />

• Bestaande SWdynamiek<br />

• IJH<br />

• Regelgeving – subsidies –<br />

pleegouders (statuut?)<br />

• concurrentie<br />

• ideologie: vnl RvB<br />

• Organisatie één toegang:<br />

positief, efficiënt<br />

• vraaggericht<br />

• zo groot mogelijke<br />

hulpgarantie<br />

• Cultuurverandering<br />

• harmonisering en aanpassing<br />

regelgeving<br />

• intersectorale SW: continuüm<br />

• Werken in tussenstappen<br />

• vraaggestuurd<br />

• Engagement besturen<br />

• preventie en<br />

• Bereid zijn iets in te leveren<br />

responsabilisering eerste lijn<br />

• Historische vergroeiing: eigenheid<br />

als drogreden, behoud posities?<br />

• Intentie SW: écht samenwerken?<br />

• Verschil in visie directie en RvB<br />

• Verschil in mandaat vanuit de<br />

organisatie<br />

• Kleine diensten<br />

• Beleid: stimuleren, sturen<br />

en/of opleggen?<br />

• Kerncompetenties: duidelijk<br />

profiel en mandaat,<br />

inhoudelijk, sluitende<br />

afspraken.<br />

• Privacy opgeven,<br />

doorstroming in<strong>for</strong>matie<br />

• imago: moderniseren en<br />

verduidelijken<br />

• centraal aanspreekpunt voor<br />

cliënt en verwijzers<br />

• schaalvergroting,<br />

standaardisering, kostenbesparend<br />

Attachments


COPP<br />

•Verkaveling: tussen sectoren,<br />

territoriaal, tussen diensten<br />

(eigenheid), geschiedenis PGZD<br />

• Diversiteit als rijkdom<br />

• Iedereen doet alles<br />

• strikte regels<br />

• Wat willen ze écht?<br />

• geen programmatie aanwezig<br />

in BJB<br />

• grote druk verwijzers + geen<br />

normen voor doorverwijzing<br />

• ideologische verschillen<br />

• underdog-gevoel<br />

• geen open cultuur<br />

• Overheid: visie op PZ?<br />

• Leden spelen koepels tegen<br />

elkaar uit.<br />

COPP<br />

• concurrentie<br />

• niet kiezen van begeleiding<br />

• verschillen in selectie &<br />

vorming, ouders gaan shoppen<br />

• kwaliteitseisen naar beneden<br />

• beeld pleegouders<br />

• rechten pleegouders<br />

• kind staat niet centraal<br />

• waarom 5 diensten?<br />

• Wat willen ze met SW?<br />

• werkdruk PGZD<br />

• SW op papier<br />

• pervers en ziek systeem<br />

• relatie PGZD – doorverwijzers<br />

• beeldvorming pleegkind,<br />

slachtoffer<br />

• bemiddelingscommisie?!<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

Vertegenwoordigers<br />

• historiek<br />

• zelfde problemen<br />

• basismethode =<br />

• IJH<br />

• overheid: interesse<br />

• project = accident<br />

de parcours<br />

• kwaliteitsnormen<br />

• loonharmonisering<br />

• nieuwe denken<br />

• goede positionering<br />

vanuit persoon met<br />

een handicap-sector<br />

• stichters diensten<br />

verdwenen<br />

• Duidelijkheid<br />

• Actie, bv. Pilootproject,<br />

bottom-up<br />

• Andere financieringsmech.:<br />

sectorale regelgeving en<br />

sponsoring<br />

• Specialisatie<br />

• Goedkeuren nota<br />

• Management en<br />

procesbegeleiding<br />

• Bewust eigen identiteit<br />

• RvB: vorming voorzitters,<br />

zitjes voor collegadiensten<br />

• Overheid: sturing, politiek<br />

draagvlak<br />

• geschiedenis<br />

• politieke constellatie: andere minister en te eng<br />

aangesproken<br />

• schrik privatisering/ verzakelijking/ opleggen SW<br />

• weinig creativiteit<br />

• verschil in managementstijl<br />

• verborgen agenda’s<br />

• keuze dit project sluit andere keuzes uit<br />

• Toekomstige ontwikkelingen: druk vanuit andere<br />

zorgvormen<br />

• Sterke lobby<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

Pleegouders<br />

• Maatschappelijke<br />

veranderingen naar<br />

nieuw<br />

samengestelde<br />

gezinnen<br />

• wanneer SW: wat willen<br />

we?<br />

• slordig geworden in selectie, te<br />

weinig kandidaten<br />

• SW bestaat in verschillende<br />

gradaties, loskomen van<br />

hokjes<br />

• Pleegouders teveel rechten geven<br />

leidt tot meer gedwongen plaatsing<br />

• Netwerk: rond cliënt, tussen<br />

diensten<br />

• Pragmatische SW<br />

• specialisatie en<br />

accentverschillen<br />

• centraal aanspreekpunt<br />

• schaalvergroting<br />

• vraaggestuurd<br />

• aanbodverduidelijking<br />

• nieuwe vormen PZ<br />

• Afspraken: gedragen door<br />

iedereen, deontologische code<br />

• mandaat PZ – overheid<br />

• inhoudelijk beleid werkvloer<br />

• Eén dienst, zelfde criteria:<br />

externe dienst (neutraliteit)<br />

• degelijke selectie, erkenning<br />

deskundigheid pleegouders<br />

• vorming leerkrachten<br />

• PZ bekend maken<br />

• kind centraal<br />

• fijn profiel in pool, geen<br />

supergezinnen<br />

• zwarte lijst voor gezinnen die<br />

geweigerd zijn<br />

• Zeker met 5 samenwerken<br />

• Flexibiliteit om van begeleider<br />

te veranderen<br />

• kan het comité geen 2 jaar<br />

garantie geven?<br />

• Moeten PGZD niet meer tamtam<br />

maken over wat er misloopt<br />

• Meer rechten voor<br />

pleegouders<br />

Attachments


COPP<br />

• Is er nood aan SW? Kan dit<br />

gebrek aan pleeggezinnen<br />

oplossen?<br />

• Achter de rug om; wat verwijten<br />

ze ons?<br />

• Verschillen diensten:<br />

individueel engagement, cultuur,<br />

geen verbinding<br />

•geen aanspreekpunt, <strong>for</strong>um,<br />

weinig overleg<br />

•Gestandaardiseerde verslagen, te<br />

oppervlakkig; soms in<strong>for</strong>matie<br />

afgeschermd; weinig<br />

transparantie over waarom er geen<br />

gezin voor handen is<br />

• PZ geschikt voor kortdurende<br />

opvang?<br />

• Juridisch onduidelijk<br />

• Niet tegelijk willen zoeken �<br />

tijdverlies, geen keuze<br />

•Ken aanbod niet; wat willen ze?<br />

•PGD komen soms teveel op voor<br />

pleeggezinnen; wij waken over<br />

kansen natuurlijk milieu<br />

COPP<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

Doorverwijzers<br />

• LPJ<br />

• bestaande relaties,<br />

vertrouwen<br />

• beroepsgeheim<br />

• schrik dat instellingen ‘modern’<br />

willen doen<br />

• schrik dat verscheidenheid verloren<br />

gaat<br />

•verschillen in werking<br />

•allemaal afhaken als ze samengaan<br />

•dubbele erkenning van sommige<br />

PGD<br />

• kandidaat ouders laten<br />

• Criteria voor ideale pleeggezin,<br />

praten met pleegouders: het zou hetzelfde moeten zijn<br />

echte verhaal laten horen<br />

•Gericht op zoek gaan naar<br />

•<strong>for</strong>um PZ om met gezag te gezinnen, anticiperen<br />

kunnen spreken<br />

•contacten en<br />

doorverwijzingen over<br />

sectoren heen<br />

•traditie: vanuit individuele casuïstiek<br />

werken<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

Pleeggezinnendiensten<br />

•Gezamenlijke pool, betere<br />

matching; 1 aanspreekpunt<br />

• Verruiming en versoepeling<br />

aanbod, vb. onthaalgezin<br />

• Begeleiding pleeggezin tijdens<br />

spitsmomenten<br />

• Goede voorbereiding<br />

pleegouders, vb. incest<br />

• Specialiseren in familiale<br />

plaatsingen<br />

• Bestuur: Raden van Bestuur, directieleden<br />

• LOP-leden<br />

• Medewerkers pleeggezinnendiensten<br />

Attachments


COPP<br />

COPP<br />

Huidig beeld<br />

• imago PZ: langdurig, weinig bekend,<br />

verwarring adoptie, versnippering, slecht<br />

imago, moeilijk ‘product’, weinig waardering<br />

bij bevolking<br />

• verschillen:ver uiteen, verschillen in hoofden<br />

vs praktijk, naast elkaar,concurrentie,<br />

vooroordelen tov elkaar<br />

• SW: drijfveer? Erbij willen zijn? Nog niet<br />

veel goede SW gezien; bereidheid?<br />

Praktische SW maar eigenheid behouden,<br />

personeel en RvB voelen wenselijkheid aan<br />

• kritische vragen mogen niet in de sector<br />

• systeemvisie dominant<br />

• grote organisaties: specialiseren<br />

• verwijzers: shoppen<br />

• relatie consulenten belangrijk,<br />

spanningsveld, willen gewoon oplossing<br />

• leden RvB kennen elkaar niet<br />

Aanwezige hefbomen<br />

• Integrale<br />

• SW tussen 2 diensten<br />

• we verstaan mekaar goed<br />

• overleg: gemeenschappelijke nood<br />

• vaak in<strong>for</strong>mele initiatieven<br />

• personeel vragende partij<br />

Conditionele hefbomen<br />

• gezamenlijke visie, doel, draagvlak besturen<br />

• vertrekken van concreet werk, vergelijken<br />

• inspraak gebruikers<br />

• open keuken, eigenheid appreciëren<br />

• overheid: onderzoek, SW aanmoedingen, Q<br />

criterium<br />

• vertrekken vanuit gelijkwaardigheid<br />

• <strong>for</strong>um voor gesprek & procesbegeleiding<br />

• SW: pragmatisch<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

Bestuur<br />

Toekomstbeeld<br />

• brede waaier hulpverlenings-vormen: PZ<br />

niet apart<br />

• eigenheid behouden ⌦ doel is niet<br />

organisaties in stand houden<br />

• kwaliteit verhogen & besparen<br />

• SW rond: vorming, werving,<br />

belangenverdediging<br />

• eventueel nieuwe constellatie<br />

• 1 dienst, moreel verplicht tot SW, betere<br />

kansen voor kind ⌦ geen verdere SW, er<br />

moet uitweg zijn als er conflict is, structureel<br />

SW is personeel verliezen,willen er wel bij<br />

zijn, voordelen meepikken maar rest hoeft<br />

niet<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

Bestuur<br />

Hinderpalen<br />

• geen wil tot veranderen, geen<br />

zelfreflectie<br />

• te grote cultuurverschillen<br />

• vasthangen in kader<br />

• wantrouwen, ambivalentie,<br />

concurrentie, protectionisme, verborgen<br />

agenda’s<br />

• kleine diensten: bekommernis personeel<br />

• onvoldoende ontzuild,<br />

‘stichterssyndroom’<br />

• SW als doel, waarom project?<br />

• nog ingewikkelder<br />

• mensen aan tafel soms geen mandaat<br />

• RvB: engagement, kandidaten<br />

• personeel: positie, inspraak,<br />

betrokkenheid<br />

• overheid: geen incentives<br />

Attachments


COPP<br />

COPP<br />

Huidig beeld<br />

• PZ zwakke broertje, lichtgewicht, pleegouders<br />

tellen niet mee, verandert!<br />

• regelgeving: perverse systemen, concurrentie,<br />

‘ideologische verschillen’drogreden<br />

• risico: Q eisen omlaag<br />

• Gelijkenissen groter dan verschillen ⌦diensten<br />

werken inhoudelijk verschillend<br />

• SW: beperkt, extern gericht, ‘veilige’ domeinen,<br />

‘tactisch’, regionaal of zorgoverschrijdend,<br />

vooral kleinere diensten vragende partij, niet<br />

rond gemeenschappelijke opdrachten<br />

• 5 diensten is raar; iedereen doet alles; niet<br />

afgesproken specialismen<br />

• (pleeg)ouders & consulenten spelen diensten<br />

tegen elkaar uit<br />

• Soms onevenwicht inbreng diensten<br />

• grote werklast, middelen en omkadering niet<br />

meegeëvolueerd<br />

• communicerende vaten<br />

• verschillen in mandaat vanuit de organisatie<br />

Aanwezige hefbomen<br />

• SW is gegroeid<br />

• overzichtelijk<br />

• vraag vanuit medewerkers<br />

• openheid, vertrouwen in LOP, kwetsbaar<br />

• externen<br />

• in<strong>for</strong>mele contacten<br />

• we gebruiken mandaat, ruimte<br />

• besef: kunnen leren van elkaar<br />

• nieuwe directie Opvang<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

LOP<br />

Conditionele hefbomen<br />

• open communicatie, vertrouwen, belangen op<br />

tafel, goodwill, gelijkwaardigheid, evenredige<br />

participatie<br />

• SW RvB, medewerkers, gedragen door<br />

dienst(en)<br />

• stapsgewijs<br />

• overheid: ondersteunen, krijtlijnen<br />

• sterktes in kaart brengen, terreinafbakening<br />

• iemand leiding durven laten nemen<br />

• begeleiding<br />

Toekomstbeeld<br />

• SW: inhoudelijke werking, werving, pool<br />

pleegouders, profilering naar verwijzers,<br />

regionaal met andere hulpverleningsvormen, beter<br />

met middelen omgaan, specialiseren, eerst PZ<br />

optimaliseren, dubbel loket, moet functioneel zijn,<br />

meer dan een intentie<br />

• project: naar kern, weten waar je voor kiest<br />

• subsidiesysteem veranderen<br />

• 1 contactpunt: goede afspraken over verdeling<br />

achteraf<br />

• geen monopolie<br />

• eigen identiteit behouden, geen eenheidsworst<br />

• winst medewerkers: bijscholen, iets<br />

ontwikkelen,…<br />

• opvolging kinderen uitwerken<br />

• minimale eisen familieleden netwerkplaatsingen<br />

• overheid: Q bewaken<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

LOP<br />

Hinderpalen<br />

• overheid: geen incentives, te weinig<br />

middelen, enveloppefinanciering<br />

• verschil in overtuigingen, autonomie,<br />

ideologie promoten<br />

• verschil visie RvB ⌦ directie, RvB<br />

niet vooruitstrevend<br />

• ‘instroom’ is gevoelig domein,<br />

weerstand<br />

• persoonlijk spelen als je systemen niet<br />

ziet<br />

• verschil mandaat<br />

• zijn alle leden wel geïnteresseerd?<br />

• sommige dingen niet op tafel<br />

(financieel, personeel,..)<br />

• basisdemocratie ⌦ managers<br />

• hangt af van goodwill<br />

• verlies drive medewerkers in groot<br />

geheel<br />

Attachments


COPP<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

Medewerkers<br />

Huidig beeld<br />

• Wat is reden voor project?<br />

• Rijkdom PZ = diversiteit en maatwerk<br />

• absurd dat er 5 diensten bestaan<br />

• in<strong>for</strong>matie over kind versnipperd<br />

• consulenten: shoppen, persoonlijke contacten,<br />

verkeerd beeld PZ, weten waar we voor staan, mogen<br />

werking niet toelichten<br />

• hard werken � meer plaatsingen<br />

• grote verschillen ⌦ onvoldoende zicht op wat<br />

anderen doen, visie: zijn we uniek?<br />

• Beeld PZ verwarrend, niet doorzichtig, PZ<br />

buitenbeentje, weinig onderzoek<br />

• slagkracht Federatie?<br />

• veel extra werk, weinig middelen, externe begeleiding<br />

kan niet<br />

• SW op papier, geen opvolging<br />

• PZ zit overal in: keuzes maken<br />

• werkgroep vorming: weinig autonomie en<br />

vertrouwen van LOP<br />

• grotere diensten: meer geld, meer tijd en ruimte om<br />

visie te ontwikkelen � druk, invloed, positioneren<br />

COPP<br />

Toekomstbeeld<br />

• uitwisselen, intervisie selectie<br />

• wat is eigenheid? � SW en eigenheid<br />

behouden, geen eenheidsworst<br />

• SW: werving, meer professionaliteit rond<br />

tafel; vorming; jongerenweekends; specifieke<br />

functies (bv. in<strong>for</strong>maticus)<br />

• 1 centraal punt doorverwijzers, willen<br />

keuzevrijheid<br />

• 1 pool: los van visie, is winst/service voor<br />

consulenten en kind; matching door neutrale<br />

persoon<br />

• ‘Paal PZ’ sterker uitbouwen<br />

• drive = verschil maken, je onderscheiden<br />

• specialiseren qua doelgroep<br />

• gaan we niet verliezen?<br />

• Vrees invoering NL model<br />

Center <strong>for</strong> Organizational and Personnel Psychology<br />

Medewerkers<br />

Aanwezige hefbomen<br />

• LOP: doorgeven welke gezinnen geweigerd<br />

• vanuit bestaanszekerheid gaat SW vlotter<br />

• de dingen die we doen zijn zinvol<br />

• concrete realisaties (bv.week PZ)<br />

• Limburg heeft stapje voor qua SW<br />

• we stappen al spontaan naar andere PGD<br />

Conditionele hefbomen<br />

• opdracht geven, autonomie en krediet geven, jaarlijks<br />

evalueren<br />

• 1 affiche en slogan, 1 pool en toebedeling afspreken<br />

• externe onderzoekers<br />

• RvB: neuzen in zelfde richting<br />

• samen iets groots en duurs doen<br />

• SW opleggen; ligt te gevoelig bij diensten<br />

• mensen van diensten samenzetten<br />

• tussenstappen (bv. centrale lijst)<br />

• Basisvisietekst: wat is PZ?<br />

• Knopen doorhakken: bottom-up ofwel sturen van<br />

boven; duidelijk kader<br />

• subsidiesysteem veranderen<br />

Hinderpalen<br />

• dubbel: geen aanmelding = geen personeel<br />

• LOP: werkgroep gebruiken voor eigen<br />

agenda; zitten niet op 1 lijn<br />

• grootschalig: verlies dynamiek<br />

• nog onoverzichtelijker, verdeelsleutel?<br />

• Verzuiling nog steeds<br />

• consequenties voor ouders<br />

• 1 selectieteam = job kwijt<br />

• verschil in visie � thema’s vermijden<br />

• geen doel, probleem, knelpunt<br />

• privacy<br />

• gemeenschappelijk probleem ≠<br />

gemeenschappelijke oplossing<br />

• meer SW � minder creativiteit, soepelheid,<br />

motivatie, betrokken; anoniemer<br />

• mensen zijn werkgroepen kotsbeu; geen<br />

beloning<br />

• onvoldoende geld<br />

Attachments


ATTACHMENT 4: STAKEHOLDER ANALYSIS OF THE DOMAIN OF FOSTER<br />

CARE<br />

Structure of the collaborative system and stakeholders in foster care (based on Eden,<br />

1996).<br />

Schools<br />

Mental health<br />

services<br />

Physicians<br />

Province<br />

Foster care adults<br />

Umbrella<br />

organiza-<br />

tions<br />

Residential<br />

child care<br />

The public<br />

Mediation<br />

commission<br />

Subsidizing institutions<br />

Services FC<br />

Relegating parties<br />

Minister of welfare<br />

Experts<br />

Foster care services in Flanders<br />

Foster<br />

parents<br />

Center <strong>for</strong><br />

welfare<br />

Federation<br />

Natural<br />

parents<br />

Children<br />

Regional<br />

plat<strong>for</strong>m<br />

youth<br />

care<br />

Attachments


ATTACHMENT 5: ISSUES, QUESTIONS AND DILEMMAS BASED ON THE<br />

STAKEHOLDER INTERVIEWS<br />

Issue<br />

Questions, dilemmas<br />

Identity of foster care – vocation vs. professionalism<br />

– strong identification with services<br />

– diversity as richness vs. obstacle to<br />

collaboration<br />

– perceived as protecting the foster<br />

families<br />

Perception of assistance – driven by supply vs. by demand<br />

– child not at the core<br />

– positioning and profile unclear<br />

– idealization of foster care as best<br />

solution makes collaboration with<br />

others hard<br />

Motive <strong>for</strong> collaboration – ambivalence: collaboration in<br />

competitive environment?<br />

– Is collaboration a solution <strong>for</strong> the<br />

shortage of families?<br />

– Reception function is a solution <strong>for</strong> a<br />

problem that is not well defined<br />

Desired type of collaboration – Collaboration means losing personnel<br />

vs. purpose should not be to maintain<br />

the services<br />

– Collaboration among services <strong>for</strong><br />

foster care or across sectors?<br />

Perceived obstacles – History of splits and conflicts among<br />

services<br />

– ‘Pillarization’ of sector<br />

– Subsidizing mechanism<br />

– Time pressure<br />

– Board members are volunteers and<br />

should be the driving <strong>for</strong>ce (no time)<br />

– Fear to lose identity, jobs, fear <strong>for</strong><br />

Attachments


Perceived enablers and facilitating<br />

conditions<br />

merger<br />

– Interest and commitment of services<br />

to the change?<br />

– Only direct contact among<br />

management of the services<br />

– Employees are tired of work groups<br />

– Resistance to change in sensitive<br />

domains<br />

– Goodwill and no ‘<strong>for</strong>mal’<br />

commitment of participating services<br />

– Existing collaboration is safe domains<br />

(in<strong>for</strong>mal, concrete actions, charter<br />

with minimal agreements)<br />

– Institutional situation in region is not<br />

too complex<br />

– Same basic approach in work<br />

– Founders of the services are<br />

gradually disappearing<br />

– The managers use their mandate to<br />

make changes<br />

Required conditions – Commitment of services<br />

– Be prepared to give in<br />

– Be conscious of own identity<br />

– Be open to exchange in<strong>for</strong>mation<br />

– Process consultation<br />

– Decide if change is top-down or<br />

bottom-up<br />

– Provide clear framework<br />

– Clarify mandate of project group<br />

– Let go of feeling of being in underdog<br />

position<br />

– Keep commitment and energy high<br />

and introduce some management<br />

principles<br />

Perceived relationships between the<br />

services<br />

– United because faced with similar<br />

problems vs. rivalry <strong>for</strong> resources<br />

– Strong sense of autonomy of the<br />

services; loyalty<br />

– Open, trustful relationships among<br />

managers vs. distrust, hidden<br />

agendas, protectionism<br />

– Not knowing the other services;<br />

Attachments


Relationship between foster care and<br />

wider domain of welfare<br />

assumptions and prejudice<br />

– Growing awareness that services can<br />

learn from each other<br />

– Differences in vision within services<br />

– One service identified as<br />

‘troublesome’ from the start<br />

– Reporting to relegating parties not<br />

adequate<br />

– Loss of time, no choice, because<br />

services do not want to look <strong>for</strong> a<br />

family in parallel<br />

– Relegating parties play services off<br />

against each other<br />

– Nourishing personal contacts with<br />

relegating parties is critical<br />

– Foster care is not strong in relation to<br />

magistrates<br />

– Little cross-fertilization or<br />

complementarities between foster<br />

care and other services/institutions<br />

– Little continuity in care when child is<br />

transferred<br />

– Social map of welfare in region is not<br />

transparent<br />

Attachments


ATTACHMENT 6: CATEGORIES AND SUBCATEGORIES OF PROVISIONAL<br />

DATA ANALYSIS<br />

Categories developed as a provisional analysis of the field notes, using Atlas-ti.<br />

Antecedents of the project<br />

– Positive and negative experiences with collaboration<br />

– Culture of foster care (well meaning people, amateurism, little inflow of new<br />

people and ideas, consensus model of decision making, everybody knows<br />

everybody)<br />

– Position of foster care in the domain of welfare (small sector, foster children less<br />

visible)<br />

– Self perception of foster care services (‘underdog’, is last solution because of a<br />

high threshold)<br />

– History of conflicts and splits in foster care (ideological differences)<br />

– The regional consultation plat<strong>for</strong>m<br />

– Perception of foster care by external stakeholders (defend the foster parents,<br />

supply driven, lack of clarity about diversity, no understanding why t<strong>here</strong> are<br />

five services)<br />

– Policy in foster care (availability of funding by ‘coincidence’)<br />

– Strong wish of services in the selected region to participate in the project<br />

Enabling conditions already present<br />

Socio-political context<br />

– Changes in the domain of welfare<br />

– Interest of policy makers in foster care<br />

– Pressure on policy makers to put foster care on the agenda<br />

– Strategic use of the project<br />

– Professionalization of the sector<br />

– Right moment<br />

– Societal pressure to collaborate<br />

Attachments


Regional consultation plat<strong>for</strong>m<br />

– Existing concrete initiatives<br />

– Ground rules established in regional consultation plat<strong>for</strong>m (‘charter’)<br />

– Existing collaboration between two services (model function)<br />

– Trust among managers<br />

– Personalized contacts among managers<br />

– Personalities of the managers<br />

– Willingness of the managers<br />

– Managers use mandate to act<br />

– Driving <strong>for</strong>ce of convening organization<br />

– Links with other collaboratives<br />

The services<br />

– Interest and demand <strong>for</strong> collaboration of employees<br />

– Changes in management of services<br />

– Confronted with similar problems<br />

– Small number of organizations in the region<br />

– Felt necessity to collaborate<br />

Conditions <strong>for</strong> collaboration that need to be developed or strengthened<br />

Basic conditions<br />

– Be aware of necessity to collaborate<br />

– Broad support from the basis<br />

– Be committed to the change<br />

– Goodwill of participants<br />

– Mutual appreciation and recognition<br />

– Sufficient tangent planes between organizations<br />

– Trust each other<br />

– Openness<br />

– Relationship of equality<br />

– Move beyond individual organizational interests<br />

– Be prepared to let go of part of identity<br />

Attachments


– Sense of belonging (employees)<br />

Facilitating interventions<br />

– Stress similarities and what we have in common<br />

– Balance between giving and taking (fairness)<br />

– Have the courage to take the lead<br />

– Take ownership<br />

– External facilitation of the process<br />

– Let go of central control<br />

– Maintain domain of expertise<br />

– Maintain ideology and values (identity)<br />

Required guarantees<br />

– No job losses<br />

– Respect agreements<br />

External conditions<br />

– Clear framework by policy makers<br />

– Incentive <strong>for</strong> collaboration by policy makers<br />

Existing obstacles to collaboration<br />

External obstacles<br />

– Subsidizing policy<br />

– Sudden and unexpected start of the project<br />

– Differences in policy between the umbrella organizations<br />

– Fear <strong>for</strong> liberalization of sector<br />

– Playing off the services against each other (relegating parties, foster families)<br />

– Limited resources<br />

Internal obstacles<br />

– Asymmetry in size (foster care services)<br />

– Differences in ideology (services)<br />

– Differences in management style (services)<br />

– Differences in mandate (members of project group)<br />

– Different interests of services<br />

Attachments


– Not knowing each other<br />

– Existing power relations<br />

– Autonomy of the services<br />

– Collaboration as a goal in itself<br />

– Influence of founding fathers of the services<br />

– Inefficiency and lack of effective use of resources<br />

– Little experience with collaboration<br />

– No differentiation or specialization in assistance<br />

– No one takes up nurturing role<br />

– No open discussion<br />

– Lack of creativity<br />

– No strategic thinking<br />

Fears<br />

– Fear <strong>for</strong> employment<br />

– Fear <strong>for</strong> loss of identity<br />

– Fear of becoming nothing more than a face in the crowd<br />

– Tension between competition/loyalty to service and collaboration<br />

Potential obstacles that could hinder the development of collaborative<br />

relationships<br />

– Failure in other related projects<br />

– Unfair distribution of placements (‘distribution key’)<br />

– Fear <strong>for</strong> tensions and conflict<br />

– Personal conflicts<br />

– Differences in ideology<br />

– Differences within the services<br />

– Voluntary nature of participation in the project<br />

– Number of services too large<br />

– Rivalry<br />

– Lack of time<br />

Attachments


Desired approach to the change ef<strong>for</strong>t<br />

External interventions or change<br />

– Change subsidizing policy<br />

Task and procedural level<br />

– Clarify collective task<br />

– Start with collaboration in safe territories<br />

– Clarify mandate of participants<br />

– Develop shared frame of reference<br />

– Clarify issues<br />

– Involve constituency<br />

– Develop collaboration between boards of the services<br />

– Develop collaboration between employees of the services<br />

– Establish clear profile of foster care<br />

– Look at facts and numbers<br />

– Focus on results<br />

– Watch over quality<br />

– Make clear agreements<br />

– Translate reservations into conditions <strong>for</strong> collaboration<br />

– Optimize organization<br />

– Develop a strategy towards policy makers<br />

Relational level<br />

– Get acquainted<br />

– Direct interaction among participants<br />

– Explore differences and similarities<br />

– Foster commitment<br />

– Include diversity<br />

– Put issues on the table<br />

– Keep options open<br />

– Learn from each other<br />

– Learn from bench marking visits<br />

– Make progress visible <strong>for</strong> all<br />

Attachments


– Develop specialization of services<br />

– Take the necessary time <strong>for</strong> this process<br />

Desired results and output of the project (potential benefits)<br />

Expressed by internal stakeholders<br />

Effects on the product (assistance)<br />

– Joint organization of activities (e.g. fair, education)<br />

– Uni<strong>for</strong>mity in procedures<br />

– Optimizing procedures (e.g. selection, intake)<br />

– Higher transparency of available foster families (‘pool’) <strong>for</strong> relegating parties<br />

– A regional foster care house<br />

– Increased chances of finding an optimal family <strong>for</strong> the child (better ‘matching’)<br />

– Have a larger capacity<br />

Effects in the environment<br />

– A clear and consistent image and profile of foster care (clear overview of<br />

assistance)<br />

– Improve the image of foster care<br />

– Speak with one voice to relegating parties (e.g. judges) in order to have more<br />

influence<br />

– Have more impact on policy<br />

– Better positioning of foster care in the region<br />

– Reduce shopping behavior of relegating parties<br />

– Have a wider representation of foster care in different projects, workgroups, etc.<br />

Effects on the organization of the services<br />

– Clear inventory of differences between the services<br />

– Identification of strengths of each service<br />

– Develop strengths of each service<br />

– Cross organizational team <strong>for</strong> selection and intake<br />

– Specialization of the services<br />

– A joint ‘pool’ of candidate foster parents<br />

– Joint marketing ef<strong>for</strong>ts to promote foster care in society<br />

Attachments


– Share work in order to save time and energy (e.g. write procedures together;<br />

quality handbook)<br />

– Share costs of marketing<br />

– More effective use of resources<br />

Effects on the employees<br />

– Learning from each other<br />

– Develop expertise<br />

– Be recognized as experts<br />

– Share know-how<br />

– Exchange experiences between employees (e.g. selection)<br />

– Increased career opportunities <strong>for</strong> employees<br />

– Be able to rely on a team in order to increase quality and to feel supported<br />

– Provide opportunities <strong>for</strong> training and specialization <strong>for</strong> employees<br />

Expressed by external stakeholders<br />

– Merger of the services on regional level<br />

– Collaborate across the boundaries of foster care as a separate sector<br />

– Provide a broader range of assistance<br />

Potential drawbacks of collaboration in a large scale organization (internal<br />

stakeholders)<br />

– Rigidity and slowness of assistance<br />

– Bureaucracy (‘paper matching’)<br />

– Loss of motivation of employees in a larger structure<br />

– Fear of becoming nothing more than a face in the crowd<br />

– Lower quality of assistance<br />

– Less personal<br />

– Individual services lose their influence<br />

– Relegating parties can no longer choose with which service they collaborate<br />

– Risk of monopoly <strong>for</strong> candidate foster care families: no second chance if they are<br />

rejected<br />

Attachments


– Risk of monopoly <strong>for</strong> employees: no alternative if you lose your job or have<br />

problems with management<br />

– Loss of diversity<br />

– Imposed collaboration does not work<br />

Issues in the process<br />

Experienced differences<br />

– Ambition (disillusion, impatience)<br />

– Commitment<br />

– Objectives and task definition of the project<br />

Experienced ambiguities<br />

– Around differences and similarities<br />

– About the value or threat of differences and similarities<br />

– In motivation <strong>for</strong> collaboration<br />

– Around authority: who takes decisions?<br />

– Around inclusion and exclusion of stakeholders<br />

– Around interdependence<br />

– Around role and contribution of facilitators<br />

– Around concept of ‘reception function’<br />

– Around the fuzziness in the project<br />

Fields of tension between<br />

– The wish <strong>for</strong> collaboration and the fear to lose one’s identity and autonomy<br />

– The rhetoric of open communication and suspicion of hidden agendas<br />

– Expressed need to move on and the low sense of urgency<br />

– Complexity of the process and reduction of complexity<br />

– Solution mindedness (reception function) and exploration of the problem<br />

– Openness of the process and control over the process<br />

– Management and field workers<br />

– The need to trust each other and the existing distrust<br />

– The intended stakeholder approach and the choice <strong>for</strong> an internal focus<br />

– Being a representative of a constituency and being facilitator<br />

Attachments


ATTACHMENT 7: PROCESS RECONSTRUCTION FOSTER CARE CASE<br />

The original process reconstruction was 66 pages. In this overview I have deleted the column with in<strong>for</strong>mation on the available<br />

documentation, because I did not think this in<strong>for</strong>mation would be critical <strong>for</strong> the reader. I also deleted some minor, insignificant<br />

events or interactions from the overview. I have copied the issues from the stakeholder conferences in a separate attachment (5). I<br />

made the overview anonymous consistent with the names and number of the foster care services used in the introduction of the<br />

foster care case. I have also used abbreviations <strong>for</strong> the consultants (see attachment 1). Finally, I have translated the document into<br />

English, to make it consistent with the rest of the text in this book.<br />

Date Event/<br />

Convening<br />

phase<br />

interaction<br />

2002-10-28 Letter to<br />

Federation<br />

Participants Content Issues<br />

Two<br />

convening<br />

organization<br />

s<br />

Proposal <strong>for</strong> structural<br />

collaboration in foster<br />

care<br />

Definition of qualitative<br />

foster care<br />

Identified stakeholders:<br />

users (parents and children)<br />

voluntary collaborators (foster families)<br />

professional collaborators (personnel)<br />

Attachments


Date Event/<br />

interaction<br />

2002-11-27 Mail +<br />

letter<br />

(28/10/02)<br />

2002-12-11 Explorative<br />

conversation<br />

2002-12-19 Mail & 1st<br />

proposal<br />

Participants Content Issues<br />

Convener to<br />

CO1<br />

Convener,<br />

CO1, two<br />

external<br />

experts in<br />

multiparty<br />

collaboration<br />

CO1 to<br />

convener<br />

Identification of<br />

stakeholders<br />

Assumptions<br />

Request <strong>for</strong> coaching and<br />

research <strong>for</strong> network<br />

development in foster<br />

care<br />

(no field notes or report)<br />

Design of intervention by<br />

COPP <strong>for</strong> project<br />

proposal<br />

Objectives:<br />

protect foster care as<br />

relegating parties<br />

policy makers<br />

They do not want a merger<br />

Objective: unite <strong>for</strong>ces and preserve the identities aimed at a<br />

qualitative foster care (less time, energy and financial losses)<br />

Approach:<br />

involvement of wide stakeholder group<br />

emergent process<br />

action research<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

educational practice<br />

more effective<br />

management of scarce<br />

foster families<br />

professionalisation of<br />

foster care and<br />

knowledge sharing in<br />

foster care<br />

more effective<br />

representation of foster<br />

care with legal and<br />

authorities and policy<br />

makers<br />

Steps:<br />

contact stakeholders and<br />

getting acquainted<br />

preparation future search<br />

conference<br />

research activities<br />

meetings: design,<br />

problem setting, agenda,<br />

planning of action steps,<br />

design sustainable<br />

Attachments


Date Event/<br />

interaction<br />

2002-12-19 Letter Convening<br />

organization<br />

s to Minister<br />

of Welfare<br />

and Special<br />

Youth Care<br />

2003-01-27 2nd<br />

proposal<br />

Participants Content Issues<br />

CO1 to<br />

convener<br />

2003-10-16 Mail CO1 to<br />

COPP<br />

members<br />

structuring<br />

concluding meeting<br />

follow-up<br />

Submission of project<br />

proposal ‘Project<br />

network organization<br />

development in foster<br />

care’<br />

Second proposal with<br />

lower budget: less<br />

budget <strong>for</strong> search<br />

conference and final<br />

meeting<br />

Project has not been<br />

approved because<br />

Minister has abdicated.<br />

Cabinet asks if convener<br />

is still interested.<br />

Convener checks with<br />

Timing: three years<br />

Area: Flanders<br />

Budget was too high<br />

Minister of welfare (ecological party): priority was on a higher<br />

capacity in Special Youth Care<br />

Proposal is not approved<br />

New Minister of welfare<br />

New conditions <strong>for</strong> the project:<br />

One instead of three years<br />

One region instead of Flanders<br />

Attachments


Date Event/<br />

interaction<br />

2003-10-22 Internal<br />

meeting<br />

COPP 1<br />

2003-10-22 3rd<br />

proposal<br />

Participants Content Issues<br />

CO1, CO2,<br />

CO6, CO5<br />

CO1 to<br />

convener<br />

2003-10-23 Interview CO5 with<br />

convener<br />

COPP if they are still<br />

interested.<br />

Chances that sponsoring<br />

of the project will be<br />

approved. Conditions:<br />

Pilot project<br />

Not only consulting<br />

Stress the positive and<br />

negative aspects of such<br />

processes<br />

If it is successful, it may<br />

be transferred to other<br />

regions<br />

Budget consulting<br />

reduced to 50%<br />

Exploratory interview<br />

with convener<br />

50% of the original budget<br />

Criteria <strong>for</strong> choice pilot area? 1 or 2 regions?<br />

Lower ambition of project<br />

How much budgetary space is t<strong>here</strong>?<br />

Dilemma: rivalry vs. collaboration<br />

Foster parents have no voice<br />

5 levels of stakeholders<br />

xxx<br />

Attachments


Date Event/<br />

interaction<br />

2003-10-24 Meeting<br />

Federation<br />

2003-10-24 In<strong>for</strong>mal<br />

meeting<br />

after the<br />

meeting of<br />

the<br />

Federation<br />

Participants Content Issues<br />

Members<br />

Federation<br />

foster care,<br />

CO1, CO5<br />

4<br />

representativ<br />

es of the<br />

services<br />

present in<br />

the region +<br />

CO1 + CO5<br />

Presentation of project<br />

during monthly meeting<br />

Convener introduces<br />

project<br />

Senior researchers<br />

stresses multiparty<br />

approach. Main message:<br />

Part of the system will be<br />

chosen, but the whole<br />

system is involved<br />

It is important to design<br />

your own system<br />

Aim is to keep<br />

responsibility shared<br />

around the table<br />

The group adapts the<br />

proposal <strong>for</strong> the Minister<br />

and adapts it to the new<br />

conditions: 1 year, 1<br />

region, 50% of the<br />

budget.<br />

Proposal is sent to the<br />

Cabinet on 25 October<br />

Criteria:<br />

Region with experience in collaboration<br />

The 3 sectors must be represented<br />

Result of the meeting:<br />

Choice <strong>for</strong> region X<br />

No representative of the liberal service present at the meeting<br />

The decision is taken very quickly<br />

A service, part of the convening organization, is involved in the<br />

project<br />

Lot of enthusiasm<br />

Inclusion and exclusion: who is in and who is out? They do not<br />

want an organization (mental health) located outside the region.<br />

Who is at the core of the project: the services <strong>for</strong> foster care of the<br />

parents and children?<br />

Attachments


Date Event/<br />

interaction<br />

2003-11-04 Mail Convener to<br />

CO5<br />

2003-11-14 Mail Convener to<br />

CO5<br />

2003-12-03 Mail Convener to<br />

CO5<br />

Start-up<br />

phase<br />

Participants Content Issues<br />

2003.<br />

The project is approved.<br />

Financial aspects still<br />

have to be approved by<br />

board of convening<br />

organization.<br />

The liberal service has<br />

agreed to participate in<br />

the project. No news<br />

from Brussels.<br />

Ministry of finance has<br />

approved the project<br />

She sends the contract to<br />

COPP<br />

Liberal service has received a request to participate in the project<br />

Internal problems with management of liberal service.<br />

The president of the board is temporarily Director<br />

More complex organization to collaborate with, but in the field it<br />

works out.<br />

Liberal service involved in project in a later phase of the process<br />

and in a different way<br />

COPP is subcontracted by the convening organization<br />

Attachments


Date Event/<br />

interaction<br />

2003-12-09 Internal<br />

meeting<br />

COPP 2<br />

2003-12-11 Internal<br />

meeting<br />

COPP 3<br />

2003-12-12 Meeting<br />

project<br />

group 1<br />

Participants Content Issues<br />

CO1, CO2,<br />

CO5<br />

Practical arrangements<br />

(contract, budget<br />

allocation)<br />

Preparation meeting 12<br />

December: set dates,<br />

action plan, who are<br />

stakeholders<br />

CO4 & CO5 Preparation of questions<br />

<strong>for</strong> the first meeting on 12<br />

December<br />

Members<br />

project<br />

group &<br />

CO2<br />

Aim: start-up project<br />

CO2 presents proposition<br />

of planning <strong>for</strong> the<br />

project<br />

Next meeting: 6 January<br />

2004<br />

Create sense of belonging: organize start up meeting?<br />

Involve a broader group than just the participating<br />

organizations: all directly involved actors<br />

We raise questions about:<br />

Content: e.g. is Federation only about placements in families? To<br />

what extent are the organizations alike or different?<br />

Procedure: e.g. which logic <strong>for</strong> collaboration now? Legal status of<br />

personnel? Structure of foster care? How about the quality<br />

policy? Financial structure?<br />

Planning as presented by COPP is approved without further<br />

questions<br />

First important step is identification of the stakeholders (next<br />

meeting)<br />

Attachments


Date Event/<br />

interaction<br />

2004-01-06 Meeting<br />

project<br />

group 2<br />

Participants Content Issues<br />

Managers FC<br />

1-5, CO4,<br />

CO5<br />

Preparation : frame<br />

stakeholder analysis<br />

(Eden)<br />

Getting acquainted<br />

Discussion around<br />

perceptions of what<br />

collaboration could look<br />

like: similarities and<br />

differences<br />

Stakeholder analysis<br />

following the structure of<br />

the 3 subsidizing<br />

organizations<br />

The system is not transparent and complex<br />

Differences in mandate (‘who speaks <strong>for</strong> whom ?’) : size and<br />

geographical presence of service<br />

New member : CD of the Federation<br />

Basis <strong>for</strong> collaboration : document with agreements (regional<br />

consultation plat<strong>for</strong>m)<br />

Context : lack of foster families<br />

Want to collaborate but watch over fair distribution<br />

Context : subsidizing system provokes competition ; regulation<br />

as obstacle<br />

Tensions<br />

individual organization vs. big organization/network<br />

autonomy/collaboration<br />

drive and identification of employees vs. loss of energy<br />

individualism vs. loss of energy<br />

generalization vs. specialization<br />

drive <strong>for</strong> foster care vs. concern <strong>for</strong> own organization<br />

from underdog to impact on policy<br />

Attachments


Date Event/<br />

interaction<br />

2004-01-07 Internal<br />

meeting<br />

Participants Content Issues<br />

CO4, CO3,<br />

CO2, CO1,<br />

collaboration means wonderful offer and bigger capacity<br />

result on foster care adults ? (wider system)<br />

collaboration as an intention (ideas) vs. something concrete<br />

process facilitation enables defending the interests of service<br />

what after the project? Not link future to the availability of<br />

funding (sustainability)<br />

develop a concept, but this is not transferable to other regions<br />

OPZ Geel not included because no presence in Limburg<br />

How broad do we identify the stakeholders? Who can contribute<br />

to this project?<br />

Group of ‘suppliers’ (e.g. schools, CLB) but that goes too far<br />

Involvement of stakeholders: organizing a stakeholders<br />

conference of two days is difficult; spread two days over time;<br />

many different projects going on<br />

To what extent are stakeholders interested and willing to<br />

participate and how do they want to participate? (check during<br />

interviews)<br />

Decision to also interview the LOP members because they don’t<br />

seem to say what is really on their minds…<br />

Budget COPP (CO5) proposed a project plan and the project group<br />

Attachments


Date Event/<br />

interaction<br />

COPP 4<br />

2004-01-23 Internal<br />

meeting<br />

COPP 5<br />

Participants Content Issues<br />

CO5<br />

Role distribution COPP<br />

Reflect back on meeting<br />

of yesterday<br />

CO4 & CO5 Planning interviews<br />

Questions <strong>for</strong><br />

stakeholder interviews<br />

accepts it without further expectations<br />

Budget cut in half and consequences <strong>for</strong> our roles<br />

Common ground is output project: ‘double reception function’<br />

Diversity: internal personnel management also perceived as<br />

output of project<br />

Tension common services/assistance vs. identity of the<br />

organizations<br />

The notion of ‘reception function’ (terminology in the proposal)<br />

is already a solution.<br />

Developing a concept <strong>for</strong> this region and the risk of simply<br />

taking over and copying it to another region<br />

Encourage participants to take action themselves to make sure<br />

the project will be successful afterwards (ownership)<br />

CO4 becomes central person after the manager of FC3 sends<br />

letter and puts him in Cc.; he is submerged with mails<br />

Stakeholder list: almost complete; only missing names of foster<br />

parents, foster children, employees<br />

CO4 wants the project group to assign a contact person; this way<br />

of working is not efficient<br />

Attachments


Date Event/<br />

interaction<br />

2004-02-03 Meeting<br />

project<br />

group 3<br />

Inventory<br />

phase<br />

2004-02-05<br />

until 2004-<br />

03-01<br />

Stakeholder<br />

interviews 1<br />

- 16<br />

Participants Content Issues<br />

FC 1-5, head<br />

of<br />

Federation,<br />

CO4, CO5<br />

+<br />

coordinator<br />

of FC 5<br />

Stakeholder<br />

representativ<br />

es<br />

Follow-up of agreements Head of Federation present <strong>for</strong> first time<br />

Perception of:<br />

Present situation in foster<br />

care<br />

Desired future situation<br />

Obstacles to collaboration<br />

Enabling factors<br />

In what way does<br />

stakeholder wish to be<br />

They will ask whether foster parents are willing to be<br />

interviewed<br />

Agreement to ask older foster children to look back on their<br />

experiences<br />

Don’t think contact person among the group of managers is<br />

necessary; CO4 can be central person<br />

CO4 struggles with his position: is he supposed to keep them ontask?<br />

T<strong>here</strong> is a lot of chatting and wandering off from agenda<br />

See attachment 2<br />

Attachments


Date Event/<br />

interaction<br />

2004-03-01 Meeting<br />

researchers<br />

2004-03-01 Internal<br />

meeting<br />

COPP 6<br />

Participants Content Issues<br />

involved? Is he/she<br />

prepared to come to the<br />

stakeholder conference?<br />

Who is a critical partner<br />

in this process?<br />

CO4, CO5 Preparation COPP<br />

meeting:<br />

CO4, CO2,<br />

CO1, CO3,<br />

CO5<br />

What have been surprises<br />

so far?<br />

Issues that emerge from<br />

the stakeholder<br />

interviews<br />

The Federation is in favor of reception function<br />

FC 5 is/was obstructing<br />

One stakeholder received a phone call be<strong>for</strong>e interview to warn<br />

him: did he know what he was getting himself into?<br />

Reception function mandated by policy makers<br />

Managers foster care and project integrated youth assistance<br />

seem far apart: surprising<br />

Would be helpful to make a clear picture with the proportions:<br />

Special Youth Care, Flemish Fund <strong>for</strong> Handicapped, Child &<br />

Family (subsidizing organizations)<br />

Important influence of politics: subsidizing and approving<br />

projects; also concerning a change of mentality: paternalism vs<br />

emancipation of the client<br />

Emergent issues in the 16 interviews so far:<br />

Big vs. small organizations: can small organizations survive?<br />

Tension holding on to identity, holding on to what has been<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

developed vs. efficiency<br />

External image: unclear; related to differences and similarities<br />

Everybody is doing the same vs. own identity; related to<br />

ideology and other differences<br />

Different perspectives within the services: <strong>for</strong> boards, employees,<br />

etc<br />

Integrate foster care in the broader field or separate profiling?<br />

Tension: merger or stay separate organizations?<br />

Underdog position foster care vs. stakeholders who are willing<br />

to collaborate<br />

Antecedent: initial question of the convener was: big<br />

organizations only think about themselves and only afterwards<br />

about the children; policy makers do not talk with the small<br />

players in the field<br />

What is the alternative if they do not want to collaborate?<br />

Inclusion/exclusion: Do we have to invite only the services<br />

(boards, employees, management) <strong>for</strong> the first day?<br />

Role researchers: if we interview the members of the project<br />

group, can we use the in<strong>for</strong>mation afterwards? What can come<br />

on the table? If you do so, don’t you put yourselves in an<br />

impossible position?<br />

Attachments


Date Event/<br />

2004-03-03<br />

until 2004-<br />

03-23<br />

interaction<br />

2004-03-24 Meeting<br />

project<br />

group 4<br />

SI 17 - 32 Stakeholder<br />

representativ<br />

es<br />

Participants Content Issues<br />

FC 1-5, head<br />

Federation,<br />

CO2, CO3,<br />

CO4, CO5<br />

Feedback:<br />

List of quotes stakeholder<br />

interviews, organized per<br />

stakeholder cluster and<br />

Multiparty is about similar AND different interests; the different<br />

interests will come <strong>for</strong>ward in the interviews; necessary to<br />

explore both similarities and differences; fake similarity cannot<br />

be maintained towards the outside world<br />

Intervention: clustering the stakeholders in different ‘stakeholder<br />

clusters’<br />

Output: tension between the objectives in the project proposal<br />

and what happens in the collaboration<br />

Issue: set up a steering group with the function of correcting the<br />

project, give critical perspective, give their vision, carry the<br />

project as a ‘sponsor’; if the question changes, does the sponsor<br />

change accordingly? (idea CO2 based on experience in other<br />

projects)<br />

Stakeholder conference on a ‘neutral’ terrain<br />

Some responses to the feedback:<br />

Perception of being supply driven vs. demand driven<br />

Hidden agendas don’t need to be negative!<br />

Attachments


Date Event/<br />

2004-03-30<br />

until 2004-<br />

04-06<br />

interaction<br />

2004-04-19 Internal<br />

meeting<br />

COPP 7<br />

SI 32 - 33 Stakeholder<br />

representativ<br />

es<br />

Participants Content Issues<br />

CO4, CO3,<br />

CO2, CO5<br />

per question<br />

General issues per cluster<br />

on slide: present, future,<br />

obstacles, enablers that<br />

are present and enablers<br />

that need to be<br />

strengthened or<br />

developed<br />

Preparation stakeholder<br />

conference<br />

Agenda <strong>for</strong> next project<br />

group<br />

COPP sends report with<br />

feedback interviews to<br />

stakeholders; foster care<br />

services invite<br />

stakeholders to<br />

conference<br />

Objective day 1: what do<br />

“not professional”: in relation to what criteria? Who says so?<br />

We still did not receive any names of parents or foster children<br />

from the project group!!!<br />

Who to invite <strong>for</strong> stakeholder conference? (inclusion)<br />

Discuss what issues?<br />

How to feed back the results of the stakeholder interviews?<br />

Also include those who have not been interviewed (different<br />

levels of stakeholders)<br />

Legitimacy of foster parents as representatives is questioned: are<br />

not organized, representative, emotionally involved, may take<br />

Attachments


Date Event/<br />

interaction<br />

2004-04-22 Meeting<br />

project<br />

group 5<br />

Participants Content Issues<br />

FC 1-5, head<br />

Federation,<br />

CO3, CO4,<br />

CO5<br />

we want to do<br />

together/separately in<br />

the future? What is t<strong>here</strong><br />

already today? What<br />

needs to be developed?<br />

What are fields of<br />

tension, helping and<br />

hindering factors?<br />

Organization of the<br />

issues from the<br />

interviews<br />

Preparation stakeholder<br />

conference:<br />

We do not have much<br />

concrete in<strong>for</strong>mation on<br />

the basis of the analysis<br />

<strong>for</strong> the conference<br />

Proposal of a list with<br />

names of 29 ‘internal’<br />

stakeholders<br />

Prepare <strong>for</strong> next meeting<br />

advantage of this process to express their frustrations<br />

Who is at the core of the system: the services, foster child and<br />

foster parents?<br />

Purpose: w<strong>here</strong> do they want to go?<br />

Function work groups: give concrete shape to the collaboration<br />

Distinction between types of stakeholders emerges: action<br />

stakeholders (key actors) sounding board stakeholders<br />

Role researchers: structure the themes that emerge from the<br />

interviews<br />

Clarify (during stakeholder conference): what do they want?<br />

What do they not want? W<strong>here</strong> is still doubt?<br />

Who defends which stakeholder in the process of<br />

mediation/placement in foster care? (Relegating parties vs.<br />

services foster care)<br />

Neutral position of foster care<br />

What is the motivation <strong>for</strong> collaboration? Is a means or an end in<br />

itself?<br />

Project as vehicle to get to something concrete<br />

Stakeholder involvement: cautious approach with only internals<br />

or involve the externals from the beginning?<br />

Boundary of identity: who is ‘internal’?? Whose voice can be<br />

Attachments


Date Event/<br />

Explora-<br />

tion phase<br />

interaction<br />

Participants Content Issues<br />

(5 May) a list with names<br />

of people who can join in<br />

the reflection<br />

heard?<br />

How safe does if feel to open up the discussion?<br />

Effect of including externals: makes it easier to think <strong>for</strong> the<br />

system; make abstraction from your ‘chair’; conceptual thinking<br />

enabled; more neutral<br />

Only internals: reflex is “my service!!”; protective and defensive<br />

reactions; How safe is it to openly talk with ‘internals’?; this is<br />

also a group of ‘strangers’<br />

Enabler: make sure the boards get acquainted to start off a<br />

collaborative process<br />

The list of stakeholders <strong>for</strong> day 2 is too internal vs. philosophy<br />

multiparty collaboration ‘involve all stakeholders’<br />

Do internal work first be<strong>for</strong>e you can interact with externals:<br />

how far do we want to go?<br />

Risk of getting stuck in intentions, theorizing<br />

Talking about system vision vs. the system cannot be present<br />

Use the external stakeholder as an adviser<br />

2004-04-26 Internal CO2, CO4, Reflecting back on Stakeholder conference: internal vs. external stakeholders<br />

Attachments


Date Event/<br />

interaction<br />

meeting<br />

COPP 8<br />

Participants Content Issues<br />

CO3, CO1,<br />

CO5<br />

previous project group<br />

meeting<br />

Clarification of mandate<br />

CO2 & CO5 <strong>for</strong> next<br />

meeting project group<br />

Considerations about the<br />

stakeholder conference<br />

‘Internal’ stakeholders:<br />

What does ‘internal’ mean <strong>for</strong> them?<br />

Are almost strangers to each other; almost as unsafe as with the<br />

external stakeholders present!!<br />

Potential role <strong>for</strong> external stakeholders:<br />

Panel of experts<br />

Observers<br />

Give feedback and input<br />

Fears and worries:<br />

Fear <strong>for</strong> conflicting expectations of the stakeholders<br />

They think about foster care as system, but <strong>for</strong>get to invite the<br />

system!<br />

Design issues:<br />

Ideal: externals constantly present<br />

Find ways to let internal and external interact: variety, intensity,<br />

interaction, dialogue?<br />

Integrate external perspective while respecting the fears of the<br />

services<br />

Build on insight expressed by MS: ‘when the externals are<br />

present we come <strong>for</strong>ward as foster care, if not as separate<br />

services’<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

Our concern: include sufficient external perspective<br />

The concern of the services: keep things in control and not show<br />

the public what their struggle and questions are (external image)<br />

Design of conference:<br />

Tensions open vs. structured:<br />

Start in an open way or provide some input?<br />

Give input vs. their ownership and initiative<br />

If you give some input, they have something to relate to<br />

Openness/safety vs. letting the external stakeholders directly<br />

confront them; risk = issues are avoided, abstract level of<br />

discussion, lots of talking, statements of intention<br />

Potential input:<br />

Interview material: quotes to show ‘life’: it is about children,<br />

parents and foster parents<br />

Extract some general principles <strong>for</strong> collaboration from interviews<br />

What to do with the stakeholder perspective??!!<br />

Tension: getting to know each other vs. getting some work done<br />

in 1,5 days<br />

Design: changing constellations; give them seats; active<br />

facilitation<br />

Attachments


Date Event/<br />

interaction<br />

2004-04-30 Meeting of<br />

Federation<br />

2004-05-05 Meeting<br />

project<br />

group 6<br />

Participants Content Issues<br />

20 members<br />

of the<br />

Federation,<br />

head of<br />

Federation,<br />

FC1, FC2,<br />

FC4, CO4,<br />

CO5<br />

FC1, FC2,<br />

FC4, FC5,<br />

CO2, CO5<br />

Current status of the<br />

project<br />

Start-up<br />

Objectives<br />

Interviews stakeholders<br />

Results<br />

Next step: stakeholder<br />

conference<br />

Aim:<br />

A list of stakeholders<br />

who will be invited to the<br />

stakeholder conference<br />

Look <strong>for</strong> a realistic design<br />

Invite those from whom the project group expect obstruction<br />

(e.g. someone from other region)<br />

Physical limitation: maximum 40 persons in the conference room<br />

Choice to restrict project to children and not to expand it to<br />

adults (this has been an issue in December 2003)<br />

How broad do we define ‘external’ stakeholder? Who do we<br />

invite?<br />

External stakeholders can give input<br />

Discussion among internal stakeholders afterwards<br />

Who to invite among the ‘internals’? Work with representatives?<br />

Output after 2 days stakeholder conference: agreement on<br />

principles around what we want to do together<br />

Attachments


Date Event/<br />

interaction<br />

2004-05-14 Internal<br />

meeting<br />

COPP 9<br />

Participants Content Issues<br />

CO4, CO3,<br />

CO5<br />

Aim:<br />

Prepare next meeting<br />

project group<br />

Role stakeholders?<br />

First design scenario<br />

stakeholder conference<br />

Idea of workgroups to concretely work out ideas<br />

Design stakeholder conference<br />

How to include external stakeholders: external panel, statements<br />

on flip chart with external stakeholder, how to group them?<br />

What input do we expect from external stakeholders?<br />

What has to be discussed with ‘internals’ only, what while the<br />

‘externals’ are present?<br />

We should bring in statements from the interviews to clearly<br />

convey the message of the external stakeholder on how the<br />

services should collaborate (reality testing)<br />

Importance of getting to know one another<br />

Use the energy present in the group at that moment<br />

Negative dynamics/feelings:<br />

They keep out the external stakeholders; they are afraid of them<br />

People feel exposed and vulnerable; both among ‘externals’ but<br />

also with the ‘internals’ only<br />

They are in a logic: ‘t<strong>here</strong> will be shooting’, ‘let’s be careful’<br />

(defensive, underdog)<br />

Us and them logic: this is both true among internals as well as<br />

Attachments


Date Event/<br />

interaction<br />

2004-05-14 Meeting<br />

project<br />

group 7<br />

Participants Content Issues<br />

FC 1-3, head<br />

Federation,<br />

CO4, CO3,<br />

CO2, CO5<br />

(students<br />

briefly join<br />

to get<br />

acquainted<br />

with<br />

managers)<br />

Aim:<br />

Design stakeholder<br />

conference 1<br />

between internals and externals<br />

Internal dynamics<br />

Decision about external-internal stakeholders taken in last LOP-<br />

COPP when CO3 was not present: moves process away from<br />

multiparty collaboration<br />

Externals will not be present 2nd day; give them feedback<br />

afterwards; otherwise it gets too complex; first neatly work out<br />

the ideas (1,5 day with internal group) (reduction of complexity<br />

and diversity; split internal-external)<br />

Set framework and principles <strong>for</strong> collaboration<br />

Clarify domains of collaboration more clearly<br />

Direct interaction with external stakeholders:<br />

Added value?<br />

Input interviews<br />

Risk of repetition with interviews<br />

Added value is sitting together<br />

In what domain can they contribute?<br />

Objective is still vague: “optimizing foster care in the region”…<br />

Focus on ‘inflow’ not on foster care in general; two domains:<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

inflow of children and candidate parents<br />

Split up group or discuss in large group? Split up on basis of<br />

what criteria? Diversity of stakeholder representatives<br />

Feedback of subgroups in presence of external stakeholders or<br />

when they have left?<br />

Fear that external stakeholders will not show up<br />

Afternoon sh conference 1: only internals; does it feel like ‘us’?<br />

Need to consult constituency around the agreement in principle<br />

Risk: end of the end feeling like ‘we will see’…; then nothing<br />

changes<br />

Risk that employees don’t speak up if boards or management are<br />

present<br />

‘collaboration’ has different meaning <strong>for</strong> different groups (board,<br />

employees, management): different ‘levels of speed ‘; how to get<br />

these different dynamics together?<br />

First step: getting to know each other<br />

Reach common ground around the problem first<br />

Result of the day? Something concrete?<br />

Design of afternoon is emergent: depends on w<strong>here</strong> the group<br />

will be at the end of the morning<br />

Attachments


Date Event/<br />

interaction<br />

2004-05-28 First<br />

stakeholder<br />

s<br />

conference<br />

2004-06-07 Phone call<br />

2004-06-09 Internal<br />

meeting<br />

COPP 10<br />

Participants Content Issues<br />

38<br />

participants<br />

in morning<br />

(incl. CO2,<br />

CO3, CO4,<br />

CO5 and<br />

thesis<br />

students)<br />

convener &<br />

CO5<br />

CO2, CO3,<br />

CO4, CO5<br />

Aim: arrive at agreement<br />

in principle around<br />

collaboration<br />

Questions: what are your<br />

impressions of the<br />

stakeholder conference?<br />

Aim:<br />

Preparation meeting<br />

project group 11 June<br />

Preparation stakeholder<br />

conference 2<br />

See attachment 3<br />

Convener is disappointed:<br />

No clarity<br />

Resistances not on the table<br />

COPP should provide more leadership on the content<br />

Worries and questions:<br />

Are the values really so different?<br />

Will FC5 step out?<br />

Stakeholder conference: day 1<br />

FC5: ideological concern seems to be upfront<br />

‘reservations’: some manage to translate these into ‘conditions’;<br />

FC5 is not able to make that translation and they only see the<br />

impossibilities<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

Different levels of resistance: gap between boards (talking about)<br />

and work field (concrete action)<br />

Condition requested by employees: they want a clear mandate<br />

Level of group development: new group, focusing on being<br />

‘similar’<br />

Assignment between stakeholder conferences: managers give<br />

feedback to their constituency and collect the reactions to feed<br />

them back on the second stakeholder conference day<br />

Upcoming stakeholder conference: day 2 in 17th June<br />

Functions and levels of reporting of internal stakeholders is not<br />

transparent<br />

Who to invite?<br />

3 levels of hierarchy present; advantage is push from underneath<br />

(ideas)<br />

3 levels: drawback is that employees will not speak up<br />

Multiparty perspective: it is not about 3 levels of hierarchy, but<br />

different levels of commitment<br />

Involvement of two perspectives necessary:<br />

Boards: give green light<br />

Employees: involve them to know their concerns and to make<br />

sure it is more than a policy process with the risk that nothing<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

concrete happens on the work floor<br />

Dilemma: invite three levels of internal stakeholders or only<br />

boards and management?<br />

Preparation: individual questioning of members project group<br />

(telephone) to ask about their concerns? Expected resistance?<br />

How to use in<strong>for</strong>mation? Design second stakeholder conference?<br />

What do they want and not want together?<br />

Feedback from COPP:<br />

Not capable of looking at the potential, things they do want to do<br />

together<br />

No sense of urgency<br />

Not <strong>for</strong>mulating reservations in terms of conditions (e.g.<br />

distribution code)<br />

Example of collaborative experiences that have worked so far<br />

Concern: the feeling of getting now<strong>here</strong> at the end of the day<br />

General critical issues<br />

What are the consequences of not joining the project? Exclusion<br />

from regional consultation plat<strong>for</strong>m? Bad image at Ministry?<br />

The children and foster parents should be more central in the<br />

project<br />

Attachments


Date Event/<br />

interaction<br />

2004-06-11 Meeting<br />

project<br />

group 8<br />

Participants Content Issues<br />

FC 1-5, CO4,<br />

CO5<br />

Reflections on stakeholder conference 1:<br />

Presence of external stakeholders constructive<br />

Not used their input in afternoon<br />

External stakeholders could not contradict false in<strong>for</strong>mation of<br />

my director<br />

We withdrew upon ourselves in afternoon<br />

We have held up a façade in the morning<br />

It is up to us to develop initiatives, not the external stakeholders<br />

Afternoon: missed input of employees and boards: differences in<br />

speed<br />

Afternoon: brainstorm did not follow what had happened that<br />

morning<br />

Lack of clarity on mandates<br />

Support needed (facilitation)<br />

Employees surprised by amount of resistance<br />

We have to go back to the initial assumptions of the project: it<br />

does not fit anymore<br />

Assumption t<strong>here</strong> was an agreement, but that was not so: step<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

backwards<br />

FC5 does not meet the requirements<br />

COPP should be more directive (also on content)<br />

Resistances should come on table<br />

Make distinction between participation in project and in LOP:<br />

explore possibilities to step out<br />

Flexibility: degrees of participation must be possible<br />

Preparation SH day 2: critical issues<br />

First step is: are the services prepared? Only then you can start<br />

working<br />

Focus on translation reservations into conditions + work on ideas<br />

from brainstorm<br />

More reservation in management than with employees<br />

Work in separate groups: risk parallel process<br />

Take everybody’s feelings into account<br />

Stay concrete; talking about values is bullshit<br />

Go back to original objectives of project<br />

Objective is NOT to arrive at better communication; we have that<br />

in LOP<br />

Attachments


Date Event/<br />

interaction<br />

2004-06-14 Phone calls CO4 with the<br />

5 managers<br />

Participants Content Issues<br />

Preparation of the second<br />

stakeholder conference:<br />

Reservations and<br />

conditions <strong>for</strong> further<br />

collaboration?<br />

What do you need to<br />

move <strong>for</strong>ward in this<br />

process?<br />

What if we get stuck?<br />

COPP: point out this is a normal phase, otherwise people take it<br />

personally<br />

Big drawback of collaboration is the time <strong>for</strong> meetings!!<br />

COPP will call each LOP member separately to discuss concerns<br />

as input <strong>for</strong> design (bilateral contacts)<br />

FC1:<br />

Wants to go far in collaboration; develop foster care<br />

Conditions: agreements, clear framework, guarantees, fair<br />

distribution code<br />

Core of resistance is competition <strong>for</strong> placements<br />

Employees’ concerns are secondary now<br />

Condition: everybody should put agenda on the table<br />

Concerned about using foster care to disseminate liberal values<br />

and power<br />

Wants to change dependency relationship with relegating parties<br />

and subsidizing parties<br />

FC2:<br />

Made ef<strong>for</strong>t to find support in own organization<br />

Believes in specialization, but afraid it is a unilateral ef<strong>for</strong>t that<br />

might lead to loss<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

Work with differences in speed<br />

Long term benefit should be gaining time<br />

Prefer to optimize existing collaboration, than to loose it all<br />

As concrete as possible<br />

Go back to input external stakeholders<br />

Hope my employees will come<br />

FC3:<br />

Wants all 5 to commit equally to project<br />

Openness is difficult<br />

New director FC5 has cleaning work in own organization<br />

Surprised that resistance is located in 1 service; evenly divided<br />

would have been easier<br />

If resistance leads to blocking, I have a problem with it; don’t<br />

want them to set the pace<br />

Feels judgment and no openness in way FC5 talks; liberal values<br />

play a role<br />

We need clear framework<br />

Needs to be clarified on management level first<br />

FC4:<br />

Want same investment and same objective <strong>for</strong> all<br />

Attachments


Date Event/<br />

interaction<br />

2004-06-16 Internal<br />

meeting<br />

COPP 11<br />

Participants Content Issues<br />

CO4, CO3,<br />

CO5<br />

Aim: preparation second<br />

stakeholder conference<br />

We want to go a step further<br />

Condition: say what we think, open process<br />

Collaboration means loosing at first; you don’t know what you<br />

will eventually gain<br />

Importance of internal support (board)<br />

Transcend ideological differences<br />

Have space <strong>for</strong> open discussion<br />

Concrete!<br />

FC5:<br />

Too much focus on final objective (one reception function)<br />

This is solution <strong>for</strong> part of external stakeholders, not <strong>for</strong> all;<br />

seems more based on our perceptions than their input<br />

Explore resistance and obstacles; e.g. organizational structure<br />

that can be an obstacle to collaboration<br />

Disappointment that after one day you start lobbying over the<br />

phone: put it on the table and talk about it<br />

Obstacle: having to clean up own organization first be<strong>for</strong>e being<br />

able to collaborate (FC5)<br />

Convener: expects COPP to set the direction more than we have<br />

so far (content steering): role clarification at start of 2nd<br />

Attachments


Date Event/<br />

interaction<br />

2004-06-17 Second<br />

stakeholder<br />

conference<br />

Participants Content Issues<br />

Approx. 5<br />

representativ<br />

es of each<br />

service (only<br />

internal<br />

stakeholders<br />

)<br />

+ CO2, CO3,<br />

CO4, CO5<br />

Aim: discuss items from<br />

brainstorm of the first<br />

day and make it more<br />

concrete brainstorm<br />

stakeholder conference<br />

Antecedent: FC5 has once been excluded from the regional<br />

consultation plat<strong>for</strong>m, because they did not follow the<br />

agreements (under previous director)<br />

Surprise that t<strong>here</strong> is resistance with FC5 and Director of FC2<br />

COPP: do we have to make sure things come ‘on the table’ and<br />

are we supposed to motivate them?!<br />

COPP: regret that we gave in to letting the external stakeholders<br />

leave so early vs. they have an internal problem<br />

The board of FC5 is blocking<br />

See attachment 3<br />

Attachments


Date Event/<br />

interaction<br />

2004-07-01 Mail Director FC5<br />

to CO4<br />

2004-07-02 Meeting<br />

project<br />

group 9<br />

Participants Content Issues<br />

FC 1-5, head<br />

Federation,<br />

CO3, CO4,<br />

CO2, CO5<br />

Announcement that<br />

board has agreed to<br />

engage in the next step in<br />

the project<br />

Reflecting back on<br />

stakeholder conference 2<br />

Agreements on next steps<br />

Formal commitment to continue of all 5 services<br />

Reflections around stakeholder conference 2<br />

Need to check action plans with external stakeholders<br />

People speak in terms of ‘their’ service (strong ownership)<br />

Output was not in line with project objectives<br />

Ambiguity about objectives and approach<br />

Contrast between far reaching <strong>for</strong>ms of collaboration vs. step 1<br />

‘getting to know one another’!<br />

Ambivalence: move <strong>for</strong>ward vs. feeling uncertainties<br />

Workgroups: ready to go <strong>for</strong> it vs. reluctance because of unclear<br />

mandate<br />

Employee: we want to invest but we also want results<br />

Focus on the process vs. t<strong>here</strong> must be a clear objective<br />

Not all services have same ideas in mind<br />

Wish to include all parties, to do an ef<strong>for</strong>t to bridge the gap, to be<br />

patient vs. need to move on<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

Need to do internal work vs. producing results<br />

Tension between top-down decisions and strong ownership of<br />

employees<br />

Group seems to question the objective each time<br />

Differences in speed vs. differences in direction<br />

Need <strong>for</strong> a period to get to know each other vs. we must have<br />

concrete results <strong>for</strong> sponsor<br />

Speed of some as obstacle <strong>for</strong> collaboration<br />

Difference between the decision to start a project and the way<br />

this decision was taken at the start<br />

Question is not if we do it, but how?<br />

What are ‘results’?<br />

Getting to know one another is also a result<br />

Present what we have done as a ‘result’ of project<br />

Need to go back to project proposal: reception FUNCTION<br />

When things become concrete, some parties may step out<br />

Develop a critical mass; not everybody has to be convinced<br />

Position FC5<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

Agree on objective of collaboration around inflow<br />

Will be different when it becomes concrete<br />

Do not share history of 10 years in regional consultation plat<strong>for</strong>m<br />

(kicked out once)<br />

FC5 was contacted after the decision was taken; only 2/3 days to<br />

decide (involved later, not intentional)<br />

FC5 could not disagree with proposal, very sensible<br />

Other services were already further in the process than FC5<br />

Concerns<br />

Not reach objectives as they were <strong>for</strong>mulated<br />

Seize opportunity given by policy makers vs. not go too fast<br />

Fear to loose face as an organization (convener) if failure<br />

Policy<br />

T<strong>here</strong> is interest and willingness<br />

New funding depends on color of new Minister<br />

Need something concrete in order to obtain new funding<br />

Pressure to come with concrete results<br />

Attachments


Date Event/<br />

interaction<br />

2004-07/08 Summer:<br />

Participants Content Issues<br />

Letter to invite members<br />

of work groups (CO4)<br />

Mail (FC1) to external<br />

stakeholders who were<br />

present at first<br />

stakeholder conference to<br />

in<strong>for</strong>m them of current<br />

state of project<br />

No meetings<br />

Next steps<br />

Share vision texts<br />

COPP makes summary of visions<br />

Develop different scenarios <strong>for</strong> collaboration<br />

Operationalize<br />

Workgroups give feedback<br />

Management decides<br />

Meeting with management + boards<br />

Process facilitation required<br />

How to keep external stakeholders in<strong>for</strong>med: ??<br />

Inertia: part of culture?<br />

Frustration with CO4: feeling he has to pull; as if it is not ‘their’<br />

project (ownership)<br />

Sense of urgency???<br />

Attachments


Date Event/<br />

interaction<br />

2004-09-14 Meeting<br />

work group<br />

‘inflow<br />

foster<br />

children’<br />

2004-09-24 Internal<br />

meeting<br />

COPP 12<br />

Participants Content Issues<br />

CO4 + 4<br />

employees<br />

representing<br />

FC 1-4<br />

(FC5 absent)<br />

CO2, CO4,<br />

CO5<br />

Work group CO3<br />

postponed to October<br />

First meeting:<br />

Getting acquainted<br />

Clarify objectives<br />

Aim:<br />

Preparation meeting of<br />

project group with board<br />

members (work group<br />

‘management’)<br />

Preparatory document:<br />

matrix with differences<br />

and similarities among<br />

the services, based on<br />

their mission statements<br />

(by CO4)<br />

Discuss: what after the<br />

project? Alternative ways<br />

Convener is ambiguous position:<br />

She is our employer<br />

She is afraid to loose face with policy makers<br />

Frustration in COPP over summer period:<br />

I do not want to push the car while they are pulling!! (CO2)<br />

What is the most appropriate channel to express frustrations?<br />

(CO4)<br />

Work groups inflow: one member not present (FC5) and some<br />

completely new representatives<br />

Work group ‘management’ on 28 September:<br />

Objective: compare visions (= intentions) and decide if<br />

operational collaboration is possible<br />

Attachments


Date Event/<br />

interaction<br />

2004-09-28 Meeting<br />

project<br />

group with<br />

board<br />

members 10<br />

Participants Content Issues<br />

Managers<br />

and board<br />

members of<br />

FC 1-5, CO2,<br />

CO4, CO5<br />

to support this process?<br />

President of board of FC4<br />

is not present, because<br />

the meeting was not<br />

organized in the region<br />

of the project (matter of<br />

principle)<br />

Central theme: are the visions really so different that<br />

collaboration is not possible, or do other –unspoken- things get<br />

in the way?<br />

Concern: what if a service discovers they are not so unique<br />

(identity)? Why would you then not collaborate?? What to do<br />

when your carefully constructed identity falls apart?<br />

Head of board of FC2 is not coming to meeting of work group<br />

‘management’ because it is organized in Leuven and not in the<br />

region of the project (matter of principle)<br />

What are potential scenario’s <strong>for</strong> collaboration?<br />

What results do we deliver on 30 November? What if results are<br />

poor and if we don’t meet the stated objectives?<br />

How to continue this process if t<strong>here</strong> is no funding <strong>for</strong> a new<br />

project?<br />

Ambiguity around differences and similarities:<br />

Explicit promotion of ideology vs. implicit use, not mentioning,<br />

not important in practice of ideological inspiration<br />

Organizational functioning: hierarchical vs. consultation of<br />

employees<br />

Position of the board and way they work<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

Big organization: more structured<br />

Differences in organizational culture; as part of the richness of<br />

the Flemish landscape<br />

Differences between services bigger than differences between<br />

people<br />

Distrust vs. not being able to empathize with another vision<br />

Striking resemblances between services; a lot in common<br />

FC5 being ‘different’: hard to understand what it means <strong>for</strong><br />

foster care; not concrete<br />

Differences in expertise or domain of intervention (e.g. child<br />

diagnosis)<br />

Clear differences makes it easier to collaborate; work in<br />

complementary way<br />

It is similar on paper but the stories around it differ<br />

Conditions:<br />

T<strong>here</strong> must be a red thread <strong>for</strong> the important things<br />

Being able to imagine the consequences of being different<br />

Think from perspective of foster parents and what they expect<br />

from us<br />

If process is well facilitated we are in<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

Rising tension:<br />

Irritation:<br />

FC5: it’s a slow and careful process<br />

Others: impression that FC5 is slowing down process; ‘yes, but’<br />

Difference between intensive collaboration and progressing<br />

towards reception function<br />

Fear that concrete joint action will lead to conflict and that it will<br />

blow up existing collaboration (FC5)<br />

Tension:<br />

FC5: joint positioning towards juvenile court ok; joint activities to<br />

make foster care known ok; risky & too early to go further<br />

FC1/FC4: reception function; move beyond the ‘safe’ domains<br />

What is domain of Federation (e.g. develop vision?) and what of<br />

project (e.g. clarity around time frame and procedure)?<br />

Different interpretations of ‘pool’, output of project, ‘reception<br />

function’, ‘joint system to keep track of families’<br />

Turning point:<br />

Time to take a decision; pressure two board members<br />

Attachments


Date Event/<br />

interaction<br />

2004-10-08 Meeting<br />

project<br />

group 11<br />

Participants Content Issues<br />

FC 1-4, head<br />

Federation,<br />

CO4, CO2,<br />

CO5<br />

New composition of<br />

project group: FC5 no<br />

longer member<br />

Membership of regional<br />

consultation remains the<br />

same (representatives of<br />

FC 1-5)<br />

Clear commitment of one service (FC2)<br />

Tension: remain with 5 and 1 hesitant partner vs constructive<br />

collaboration with only 4<br />

Take decision tonight; we have waited long enough; should have<br />

been clear be<strong>for</strong>e the start<br />

Relief when decision is taken<br />

Conditions <strong>for</strong> stepping out<br />

Structure of regional consultation plat<strong>for</strong>m is not same as project<br />

FC5 can step back in at later date<br />

They will be kept in<strong>for</strong>med of project; are now external<br />

stakeholder<br />

Respect <strong>for</strong> their choice<br />

Reflections about last meeting:<br />

Perceived reasons <strong>for</strong> stepping out:<br />

FC5 has different structure<br />

Project came too soon<br />

Director FC5 has to clean up own organization first<br />

Director FC5 has to win his position<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

Strategic: they want to grow<br />

Go own way as liberals<br />

No trust<br />

FC5 feels like a stranger in regional consultation plat<strong>for</strong>m<br />

T<strong>here</strong> is a difference between head of board and director of FC5<br />

Hard to collaborate if you cannot empathize with the values of<br />

others<br />

President of board FC5 could not make difference between<br />

merger and ‘reception function’<br />

They do not want to collaborate<br />

They are stuck in their own specificity<br />

President of board FC5 is the problem; it will change once he has<br />

left<br />

Benefit of long process: our organization (FC2) now also full<br />

heartedly says ‘yes’<br />

Consequences:<br />

two contact points in the region<br />

lost one <strong>for</strong>m of assistance (Child & Family)<br />

Now convener has sufficient trust to send all documents around<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

vision!<br />

Confidentiality of documents that have been exchanged<br />

Lack of clarity in representation of FC5; different structure<br />

Voluntary collaboration based on trust vs. <strong>for</strong>ced based on<br />

distrust and conflict<br />

Next steps: scenarios<br />

Role of workgroups: concrete elaboration<br />

Role of management: draw framework, make sure the work<br />

groups are committed<br />

Scenario FC2/FC3 as model: relational organizing based on good<br />

will, trust, openness, fair distribution<br />

Requires lot of communication; alignment; clarify what must be<br />

common and what can be different<br />

Resistance employees: concerns about quality of work; they all<br />

think they are more competent; proud of their work; motivation<br />

Differences between services in terms of organizational<br />

development: big with tradition vs. young and employees have<br />

developed own way of working<br />

Meaning of ‘pool’: one number; one team of intakers; service<br />

only engages in coaching; distribution code<br />

Worries of the managers themselves? Started talking about it and<br />

Attachments


Date Event/<br />

interaction<br />

2004-10-11 Meeting<br />

work group<br />

‘inflow<br />

foster<br />

children’<br />

2004-10-11 Meeting<br />

work group<br />

‘inflow<br />

foster<br />

Participants Content Issues<br />

CO4 + 4<br />

employees of<br />

FC 1-4<br />

CO3 + 6<br />

employees of<br />

FC 1-4<br />

Second meeting:<br />

objectives<br />

Assessment of<br />

differences and<br />

similarities<br />

Learn from each other’s<br />

know how<br />

consistent with policy<br />

and projects in the<br />

environment<br />

check feasibility of<br />

potential scenarios <strong>for</strong><br />

collaboration proposed<br />

by management<br />

First meeting: objectives<br />

(similar to other work<br />

group)<br />

then meeting was over (did not explicitly come back to it in later<br />

meetings)<br />

Procedures similar, the concrete approach is different,<br />

differences are nuances<br />

Curiosity about how the approach of FC5 is similar/different<br />

Appreciate each other’s commitment to do this on a voluntary<br />

basis<br />

Added value of the services is in the coaching of families<br />

Some ideas <strong>for</strong> future collaboration (e.g. shared list of criteria to<br />

exclude candidate foster parents)<br />

Some fields that require further attention and discussion<br />

Attachments


Date Event/<br />

interaction<br />

parents’<br />

2004-10-14 Meeting<br />

work group<br />

‘inflow<br />

foster<br />

children’<br />

2004-10-22 Meeting<br />

work group<br />

‘inflow<br />

foster<br />

parents’<br />

Participants Content Issues<br />

CO4 + 6<br />

employees of<br />

FC 1-4<br />

CO3 + 7<br />

employees of<br />

FC 1-4<br />

Second meeting:<br />

Further discussion of<br />

question: what services<br />

do we offer and what are<br />

our strengths?<br />

Discussion of continuum<br />

<strong>for</strong>ms of foster care (per<br />

service)<br />

What does this mean <strong>for</strong><br />

collaboration?<br />

Second meeting:<br />

Discussion and<br />

evaluation of scenario<br />

proposed by managers<br />

Focus on similarities gives energy<br />

Interest to learn from each other (idea: establish peer group)<br />

Assumption of equality: intention is not to arrive at one method<br />

The more you do, the more subsidies you seem to get; everybody<br />

does everything Loose discussion of potential ways of<br />

collaborating: share in<strong>for</strong>mation, work in complementary way,<br />

joint folder, internal search instead of letting relegating<br />

consultants do it, create independent matching team,<br />

Obstacles: time and energy; big team is more distant and you<br />

loose a lot<br />

Benefits: if you bring everything together more chances of<br />

finding a good solution;<br />

Next steps: getting to know one another better; work on the<br />

perception of foster care (relegating parties)<br />

Feeling that management wants to go very far in collaboration<br />

(e.g. FC1 postpones the move to new building because things<br />

might change in the near future)<br />

Reactions to scenario: fear <strong>for</strong> merger, loss of job and colleagues;<br />

imposed merger is easier but also interesting to contribute and<br />

design; developing a shared vision is essential; you cannot<br />

Attachments


Date Event/<br />

Final phase<br />

interaction<br />

2004-11-05 Internal<br />

meeting<br />

COPP 13<br />

Participants Content Issues<br />

CO2, CO3,<br />

CO4, CO5<br />

Aim:<br />

Current state of work<br />

groups: reporting<br />

Program stakeholder<br />

conference<br />

copy/paste<br />

Next steps: peer group; work in small steps because scenario is<br />

too overwhelming<br />

Work out concrete list of criteria <strong>for</strong> exclusion of candidate foster<br />

parents<br />

Output project: development of scenario or concept <strong>for</strong><br />

collaboration with conditions and processes<br />

Work groups:<br />

CO3: discussed small aspects; small successes; question <strong>for</strong><br />

management: what is our mandate?<br />

CO4: intensive interaction; need decisions from management; in<br />

favor of joint intake team<br />

They go <strong>for</strong> it! Difference with energy level in management<br />

T<strong>here</strong> are big differences in ‘speed’ between services<br />

Make sure t<strong>here</strong> is continuity in the project:<br />

Go back to list of brainstorm stakeholder conference 1<br />

Respond to concerns expressed in the interviews<br />

Attachments


Date Event/<br />

interaction<br />

2004-11-09 Meeting<br />

project<br />

group 12<br />

Participants Content Issues<br />

FC1, FC3,<br />

FC4, head<br />

Federation,<br />

CO4, CO3,<br />

CO5 (FC2<br />

Preparation stakeholder<br />

conference 3<br />

Concerns of management: what about those?<br />

Idea that it is a 5 year plan is com<strong>for</strong>ting<br />

Importance of setting intermediate goals<br />

Discuss the hot issues (e.g. job loss, distribution code,<br />

specialization)<br />

So far a relational way of organizing/collaborating (FC2/FC3):<br />

what if someone from management leaves? Vulnerable way of<br />

organizing<br />

Resistance by FC5:<br />

This gave the managers time to take a closer internal look at<br />

support <strong>for</strong> the project<br />

FC3 frustrated<br />

FC2 positive: it gave her board time to fully approve the project<br />

Concern: big difference between expectations of external<br />

stakeholders and the results of the project; frame and explain it<br />

Reflections on work groups:<br />

W<strong>here</strong> do we want to go and w<strong>here</strong> can they go?<br />

No big differences, only nuances<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

could not be<br />

t<strong>here</strong>)<br />

Not clear w<strong>here</strong> they are heading<br />

Results: interesting topics to work on, result oriented; no clarity<br />

on time they can spend on it; prefer to work on one topic that is<br />

not too big; ideas <strong>for</strong> peer groups<br />

Process: interested, curious, but also scared (job loss); need to<br />

develop safety and to grow towards each other; no clear<br />

mandate; not of laughing<br />

Issues of working conditions come up (‘union issues’)<br />

Image of flirting vs. big love<br />

Parallel processes in two workgroups and management group<br />

and in future with the group of coaches (broadening<br />

participation)<br />

Preparation stakeholder conference 3:<br />

Strategic choice of participants stakeholder conference;<br />

possibilities <strong>for</strong> funding (loose ideas)<br />

Invite people and give them flavor of what is happening<br />

Listen to concerns of work groups<br />

Justify why the objectives were not met: is role COPP; managers<br />

feel they cannot judge whether process was good or bad<br />

Not give FC5 too much time & space during the meeting<br />

Take sensitivities into account; hostess is catholic politician<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

(Province)<br />

Align with expectations of external stakeholders<br />

Stress the process oriented approach, dynamic vs. administrative<br />

approach<br />

What after project?<br />

Project stops but process continues<br />

You need something concrete to obtain funding<br />

Process facilitation is must, especially <strong>for</strong> management because<br />

they take decisions and have to handle frictions<br />

Be more selective in what ‘process facilitation’ means<br />

Map out things but also start moving things; objectives and time<br />

frame; flexibility<br />

Observations:<br />

No discussion about how the managers experience the process,<br />

their resistance<br />

Chaotic meeting; need <strong>for</strong> clear agenda<br />

Frustration of facilitators (CO3 & CO4): they feel they work<br />

harder <strong>for</strong> the project than the managers<br />

Issues related to first phases of group development: who are the<br />

Attachments


Date Event/<br />

interaction<br />

2004-11-19 Meeting<br />

project<br />

group 13<br />

Participants Content Issues<br />

FC 1-4, head<br />

Federation,<br />

CO2, CO3,<br />

CO4, CO5<br />

Aim: preparation<br />

stakeholder conference 3<br />

(Name of the group is<br />

now ‘steering group’.<br />

The group was also<br />

called ‘work group<br />

management’ and<br />

‘project group’)<br />

other members? Am I accepted in the group? Are t<strong>here</strong><br />

differences? How big can they be? Can t<strong>here</strong> be differences?<br />

How do we deal with differences?<br />

Preparation of stakeholder conference 3:<br />

Some important stakeholders ‘<strong>for</strong>gotten’ to invite: how to<br />

respond to that?<br />

Role of managers in project group:<br />

present framework and time frame<br />

give clear mandate: domain, time, authority<br />

talk about their individual and shared ‘dream’<br />

their reflections on withdrawal of FC5<br />

clarify double role: promote project & go through process<br />

themselves<br />

talk about their worries, anxieties, questions to demonstrate it is<br />

not a self evident process<br />

why is this project important <strong>for</strong> the region?<br />

bring the hidden topics on table (e.g. job loss)<br />

clarify positions of boards<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

clarify objective of project (concept)<br />

talk about broadening of project (coaches)<br />

option <strong>for</strong> process approach: what does this mean?<br />

now: no merger, no job loss<br />

process will clarify what will happen; no 100% guarantees<br />

importance of open communication // foster care<br />

employees need to know when they have done good job: need<br />

<strong>for</strong> criteria <strong>for</strong> success<br />

important to create common vision<br />

issue: who takes the decisions?<br />

managers and employees bring story: ownership (no central role<br />

<strong>for</strong> consultants)<br />

Communicate enthusiasm of project members<br />

Should be interactive meeting<br />

Talk about expectations and role of external stakeholders<br />

Fear that FC5 will take up time & space; COPP will block off<br />

Some loose thoughts about funding of next project:<br />

Ask <strong>for</strong> how much?<br />

Who makes proposal?<br />

What is meaning of process facilitation <strong>for</strong> LOP?<br />

Attachments


Date Event/<br />

interaction<br />

2004-11-22 Third<br />

stakeholder<br />

conference<br />

Participants Content Issues<br />

Internal<br />

stakeholders<br />

from 4<br />

services,<br />

including<br />

representativ<br />

es of work<br />

groups<br />

External<br />

stakeholders:<br />

FC5, some<br />

additional<br />

foster<br />

parents,<br />

representativ<br />

Morning: internal<br />

stakeholders<br />

Feedback of 3 work<br />

groups<br />

Preparation of<br />

presentation <strong>for</strong> the<br />

afternoon<br />

Afternoon:<br />

Feedback and current<br />

state of project to external<br />

stakeholders<br />

Presentations by COPP:<br />

What are chances of funding?<br />

Important to be able to guarantee employees a continuation of<br />

process<br />

Other sources of funding (e.g. budget ‘training’)<br />

Confusion about name of project: ‘project regional consultation<br />

plat<strong>for</strong>m-COPP’; project ‘reception function’; ‘project COPP’;<br />

project ‘foster care’<br />

See attachment 3<br />

Attachments


Date Event/<br />

interaction<br />

Participants Content Issues<br />

es invited at<br />

first<br />

conference<br />

CO2, CO3,<br />

CO4, CO5<br />

(1) looking back at issues<br />

from stakeholder<br />

interviews and what<br />

happened with the<br />

issues; (2) the experiences<br />

in this project linked to<br />

the model of multiparty<br />

collaboration<br />

Questions and discussion<br />

Attachments


ATTACHMENT 8: ISSUES THAT EMERGED DURING THE STAKEHOLDER<br />

CONFERENCES<br />

First stakeholder conference (28 May 2004)<br />

Perception of foster care and its position in the system<br />

– Perceived as speaking up <strong>for</strong> foster parents, w<strong>here</strong> the relegating parties speak up<br />

<strong>for</strong> the parents<br />

– An ‘unclear mess’ as a profile is daunting<br />

– Perceived as doing only long term placements; network placements not widely<br />

known<br />

– Foster care as a three-unit: child, parents and foster parents<br />

– Threatening <strong>for</strong> certain groups (e.g. teenage mothers: fear that child will be taken<br />

away)<br />

– What to do about profiling?<br />

o Better profiling is necessary, both internal and external<br />

o Communicate clear profiles <strong>for</strong> the services<br />

o Communicate which assistance is available<br />

o Clearly communicate what foster care is<br />

o Present ourselves as experts: think and collaborate with others<br />

– Profiling can lead to competition and a smaller ‘back pack’<br />

Differences and diversity<br />

– High degree of variety, within and outside the services<br />

– Big diversity, but it is not known<br />

– Diversity in <strong>for</strong>ms of foster care, target groups, vision on coaching, methods<br />

– Is difference as <strong>for</strong>ce or a weakness?<br />

– It is mainly about differences between people!<br />

– Diversity is not consciously organized; it has just emerged<br />

Attachments


– Foster parents perceive the differences<br />

– Differences are less visible from the inside than from the outside<br />

– T<strong>here</strong> is not yet a shared identity<br />

– What to do with the differences?<br />

o Maintain differences between services<br />

o Important issue is clarity about differences<br />

o Each service should hold onto identity<br />

o Better management of diversity is needed<br />

– In brainstorm: no suggestion (action step) to clarify the differences between<br />

services<br />

Provided services & assistance<br />

– Very individual <strong>for</strong>m of assistance<br />

– We want to do everything and answer each call <strong>for</strong> assistance<br />

– Expectation: develop <strong>for</strong>ms of foster care that are directly and indirectly<br />

accessible<br />

– Desired services and assistance in the future:<br />

o Provide continuity in assistance <strong>for</strong> the child<br />

o Support the natural environment (parents and foster parents) because it<br />

is a painful moment<br />

o Not all or nothing in terms of foster care: Combination of assistance<br />

should be possible (e.g. BJB & assistance at home)<br />

o Develop shared criteria <strong>for</strong> foster parents<br />

o Specialize<br />

o Offer ‘intake’ as a module<br />

o Be specialists in recruitment and selection<br />

o Develop screening and investigation <strong>for</strong> family and network<br />

placements<br />

Present way of organizing (procedure)<br />

– Depends highly on persons<br />

Attachments


– Vulnerable when person leaves<br />

Foster parents<br />

– No ‘superfamilies’ required<br />

– Are important party; listen to them<br />

– What is their status and what are their rights and duties?<br />

– Recognize their expertise<br />

Natural parents<br />

– Not underestimate the pressure of parents against foster care as a solution<br />

– Condition: take care of foster parents because they are the potential<br />

Relegating parties<br />

– In case of short term solution it is necessary to ask several services <strong>for</strong> help<br />

(juvenile court)<br />

– Important to consult the advisers (social service) in the preparation<br />

– Pool of parents would give relegating parties a view on the available candidate<br />

foster parents<br />

Other institutions and services<br />

– Do not have clear vision on how services work and cannot in<strong>for</strong>m parents; wrong<br />

expectations?<br />

– Wish: institutions not only refer to residential assistance but also automatically<br />

consider foster care<br />

The context<br />

– Align with developments in IJH and BJB<br />

– Trend personal budgets will profoundly change the dynamics in the field (sector<br />

handicapped)<br />

Attachments


Perceptions of collaboration<br />

Aim of collaboration<br />

– Aim: relegating parties and foster parents experience as little hinder as possible<br />

from the way foster care is organized<br />

– Do we want to attune our practices with each other or in parallel?<br />

Benefits of collaboration<br />

– Better matching<br />

– Increase our expertise<br />

– Higher efficiency and better use of resources, e.g. central selection<br />

– One pool benefits the child<br />

Enabling conditions<br />

– Agreements regional consultation plat<strong>for</strong>m<br />

– Experience with collaboration, e.g. jointly invest money in activities or actions<br />

– T<strong>here</strong> are a lot of similarities already, lots of goodwill; good chances <strong>for</strong> success<br />

Conditions <strong>for</strong> collaboration<br />

– Recognition of quality orientation of each other<br />

– Services give clear mandates to those participating<br />

– Open discussion, e.g. about organizational interests<br />

– Readiness to learn from each other<br />

– Moments of consultation and interaction are important but they have to lead to a<br />

focus on specific domains/issues and to results<br />

– Clarify aim, <strong>for</strong>ms, conditions and time frame<br />

– Collaboration should transcend the services: also with residential institutions,<br />

regulation, mentality<br />

‘Reservations’ and questions<br />

– T<strong>here</strong> are safe and unsafe domains of collaboration; selection of candidate parents<br />

easier than children<br />

Attachments


– Will one selection team lead to a loss of jobs or loss of tasks?<br />

– Decide after step 1 if we are ready <strong>for</strong> step 2<br />

– Pool is not interesting; will not lead to more potential parents than now<br />

– How are differences in values expressed in daily practice? Are t<strong>here</strong> really<br />

differences?<br />

– No paper or bureaucratic procedure, that takes the spirit out of it<br />

– Collaboration giving up one’s identity vs. holding on to identities and differences;<br />

is the aim to achieve uni<strong>for</strong>mity?<br />

– Little time <strong>for</strong> consultations and meetings<br />

How to organize or approach the collaborative ef<strong>for</strong>t? Concrete steps:<br />

– Getting to know each other<br />

– Discover what we have in common<br />

– Compare practices and concrete problems in services<br />

– Clarify differences in criteria, jargon, procedures, effects of differences in ideology<br />

– Observe each other’s practices<br />

– Find out what we can do together and we want to do separately<br />

– Start up a reflection process around optimizing the procedures<br />

Emergent dynamics:<br />

– Presence of external stakeholders generated a drive; experienced as healthy;<br />

clarifies why we do this work<br />

– Presence of external stakeholders experienced as a recognition <strong>for</strong> foster care:<br />

they feel we are important<br />

– After external stakeholders left the controversies re-emerge: being different or<br />

thinking you are different<br />

– FC5 emerges as service with most resistance and questions<br />

– Need to trust the coaches of other services after the process of selection by a cross-<br />

organizational team<br />

– Talk about ‘open communication’ but hardly doing it<br />

– The discussions in the subgroups in the afternoon are very carefully<br />

Attachments


– No agreement in subgroup (afternoon) experienced as resistance<br />

– 3 hierarchical groups present in one room experienced as inhibiting<br />

– Different origins <strong>for</strong> resistance in the 3 hierarchical groups (employees,<br />

management, boards)<br />

– Risk that middle group (managers) are squeezed between the other two groups<br />

– Facilitators opted <strong>for</strong> maximum diversity: 3 hierarchical groups together to avoid<br />

a superficial agreement<br />

– Convener: impatience<br />

– The foster children and parents are missing in the stakeholder group<br />

– Little sense of urgency<br />

– Some feel resistance and are disappointed about the day<br />

Attachments


Second stakeholder conference (17 June 2004)<br />

Reflections on stakeholder conference 1<br />

– Input of external stakeholders clearly indicated the need <strong>for</strong> collaboration<br />

– After external stakeholders left, no further processing of what they said in the<br />

morning<br />

– We stick together when the outside world is present, but we are separate when<br />

we are among ourselves<br />

– Disillusion: what happened t<strong>here</strong> should have happened be<strong>for</strong>e the project<br />

started<br />

– Resistance with FC5 and the director of FC2; that is ok and is part of processes<br />

(protection); FC5 perceived as obstacle<br />

– Collaboration around selection of child seems harder than selection of parents<br />

(see: stakeholder conference 1)<br />

– These processes take time: getting to know each other, talking, expressing<br />

differences and similarities, agreeing on the desired <strong>for</strong>m of collaboration<br />

– We went too fast: go back and clarify the objectives<br />

– Lack of sense of urgency: we must do something!<br />

– It was hard to translate reservations into conditions <strong>for</strong> collaboration<br />

– Afternoon focus on solutions, no attention <strong>for</strong> differences, resistance, obstacles, as<br />

if they could not be t<strong>here</strong><br />

Starting conditions of the project<br />

– Uncertainty if all parties subscribe objectives; ranges from commitment to<br />

develop a reception function (change legal structure of the organizations) to the<br />

readiness to research and assess the possibility of a reception function<br />

– Services have had different internal discussion about the project<br />

– SH day 1 started from the assumption that the project was supported in the same<br />

way by all<br />

Attachments


Existing facilitating conditions and events<br />

– Enabling conditions: domains on which we already collaborate<br />

– Being able to sit around a table and talk; t<strong>here</strong> is space to communicate directly<br />

– T<strong>here</strong> is readiness and curiosity to collaborate<br />

Necessary conditions<br />

– Support of initiative by whole organization<br />

– Talk about the differences<br />

– Clarity around resistances, tensions<br />

– Turn reservations and questions into ‘conditions’<br />

– Distribution code<br />

– Clear objective and a long perspective<br />

– Clear time frame, but also flexible<br />

– Process facilitation, neutral<br />

– Share work load<br />

– Transcend our own interests<br />

– See our own blindness<br />

– Learn from each other<br />

– Clear mandate <strong>for</strong> work groups<br />

– Clarify meaning of ‘pool’ in relation to the issue of diversity<br />

– Condition: letting go of a part of your identity in order to arrive at something new<br />

that is now still unclear<br />

– No job losses<br />

(Potential) obstacles and challenges to collaboration<br />

– Questions around the need and motivation <strong>for</strong> this project<br />

– Uncertainty about having or not having the mandate to make decisions <strong>here</strong><br />

today<br />

– Organizational structure of the services<br />

– High work load; presence in different consultation structures and projects<br />

Attachments


– Bad experiences with collaboration, scepsis, resistance vs. loyalty to services in<br />

the project (FC5)<br />

– Different perception of notion ‘reception function’: diplomatic (funding),<br />

structural, ‘function’<br />

– Differences in ambition in the objectives of project<br />

– Differences in terms of when the organization was involved and how the project<br />

entered the organization<br />

– Lack of trust (FC5) that employees who do not share humanist values will<br />

understand what the consequences <strong>for</strong> foster care really are (sensitivity to the<br />

values)<br />

– Challenge: make the theoretical concept of ‘reception function’ concrete<br />

– Risk: because t<strong>here</strong> are less families, the criteria <strong>for</strong> foster families are lowered<br />

– Dilemma of representative: speak in terms of foster care in general or speak <strong>for</strong><br />

your own organization (survival)<br />

Perceived benefits of collaboration<br />

– Less work (long term…)<br />

– Training <strong>for</strong> employees<br />

Role of COPP<br />

– Expected role (firm steering, set direction also on content of collaboration towards<br />

the objectives) and negotiated role (process facilitation) of the external consultants<br />

– Doing ‘research’ (scientists) vs facilitation (consultants)<br />

– Provide neutral and objective summary of the visions and missions: facilitate<br />

difficult discussion about differences and similarities (values, identity)<br />

Emergent differences in commitment and interpretation of the objectives<br />

– Question: should it be possible to participate only in different aspects or<br />

participate with different levels of commitment?<br />

– What to do if not all services commit to the goals of the project?<br />

Attachments


– Differences in commitment and ‘speed’ between different layers of the<br />

organizations: managers have been involved in this much longer than the board<br />

members and the employees<br />

– Differences in the way the starting point of this project is perceived<br />

– Differences in the way the ‘reception function’ is seen as a certain outcome<br />

– Four services committed, while one still hesitates; too early to fully commit to<br />

project<br />

Tension around differences and diversity<br />

– Differences in pedagogical project must remain, in order to offer a choice to the<br />

relegating parties<br />

– Tension around domains w<strong>here</strong> we have little experience of collaboration, e.g.<br />

selection of children<br />

– Exploration of what the ‘difference in pedagogical project’, claimed by FC5, really<br />

means in practice: it remains unclear and ambiguous<br />

Outcome: critical next steps and commitments<br />

– Work group ‘management’ convinces FC5 to engage in step 1 be<strong>for</strong>e deciding on<br />

further participation<br />

– Agreement that stepping out will mean that membership of other groups remains<br />

unchanged and that t<strong>here</strong> are agreements in other domains<br />

– Commitment to ask <strong>for</strong> a mandate in the home organization (FC5); no<br />

commitment possible <strong>here</strong> and now<br />

– Exchange texts on vision and mission; COPP makes summary; meeting with<br />

managers and board members<br />

– Make sure members of boards get to know one another be<strong>for</strong>e they are<br />

confronted with difficult decision<br />

Attachments


Final stakeholder conference (22 November 2004)<br />

Reflection on the project<br />

How and why project started:<br />

– Dream: start from what unites us instead of what divides us in the interest of the<br />

child.<br />

– Project was unexpectedly approved: start was rushed<br />

Aims:<br />

– Discover from each other what we each do in practice and what our qualities are<br />

– Positive image in the outside world, recognition by residential services<br />

– Raise quality of foster care<br />

– Better positioning of foster care<br />

– Reach more children<br />

– Collaboration of system around the child: improve efficiency<br />

– Try to do things together within the boundaries of the existing regulations<br />

– Aim of policy (cut back) is not our aim<br />

– Very ambitious project<br />

Fears and concerns:<br />

– Paper reorganization; keep it alive; commitment with head and heart<br />

– Not being able to sell the project to constituency<br />

– One, impersonal, big organization; no interest as an individual employee<br />

– Maintain specialization and identity of services<br />

– Consequences (job loss, tradition of consultation in the services)<br />

– Condition: fair distribution code<br />

– More time consuming: more consultation required<br />

Attachments


Approach to the project:<br />

– Anticipate what policy makers find important<br />

– It is an evolution, not a revolution<br />

– Collaboration is about holding onto autonomy and putting different ‘functions’<br />

together<br />

– Tension: give impression on paper t<strong>here</strong> are results vs. option <strong>here</strong> to grow in an<br />

organic way and to nurture the developmental process<br />

– Stress on emergent nature of the process (‘process approach’)<br />

– Boundary of task: matching is included in project, but not placement of child<br />

Results of the project:<br />

– Euphoric feeling in workgroup: we deal with same things and think the same<br />

– Work groups made good start: open communication, trust, lot of ideas, some<br />

concrete results, plans <strong>for</strong> future meetings<br />

– Ability to take colourful decisions and not end up with colourless compromises<br />

(work groups)<br />

– Hard to communicate energy and enthusiasm to external stakeholders<br />

– The steps we have taken seem small from the outside (convener)<br />

– Joint decision that FC5 would not continue<br />

– Formal end of project is not the end<br />

Long term expected benefits of and hopes <strong>for</strong> the project:<br />

– Uni<strong>for</strong>m output but internal diversity as added value<br />

– Everybody can pursue his ambitions<br />

– Time to read, study<br />

– Employees enjoy their work and stay in foster care<br />

– More effective, although need <strong>for</strong> more consultation and meetings<br />

– Well being of child at centre<br />

– Intake team more chances <strong>for</strong> good matching<br />

– Avoid shopping behavior of consultants (only choice between FC or the reception<br />

function)<br />

Attachments


The future process: what after the project?<br />

Fears and concerns:<br />

– What if no more funding to continue?<br />

– Conflicts, splits, or ending in inertia<br />

– ‘Shopping’ will still be possible<br />

– Will we manage to align everything?<br />

– Fear <strong>for</strong> grey compromises vs. looking <strong>for</strong> the best solution<br />

– Danger of work groups: endless discussions and talking<br />

– Concern: effect of this project <strong>for</strong> those organizations who are also present in<br />

other provinces; keep communication open and situate in larger context; takes<br />

more time and resources to align and communicate<br />

What gives them hope:<br />

– FC5 very cooperative in regional consultation plat<strong>for</strong>m<br />

– Relationship with FC5 is still good<br />

– Differences are usually not so big in practice<br />

Conditions <strong>for</strong> success:<br />

– Time investment is minimal condition but hard to organize<br />

– Get back to stakeholders to consult them<br />

– Need <strong>for</strong> minimal process facilitation; otherwise find other ways of funding<br />

– Include the coaches in this process too<br />

– Keep communication with FC5 open, because they were not sure they made right<br />

decision<br />

– Need <strong>for</strong> criteria to evaluate and regular follow-up (operationalization)<br />

– Sometimes you have to let go of what you thought you were good at<br />

– Clarify mandate of work groups<br />

– Work with representatives (transfer) of both teams to win time<br />

Attachments


– Need <strong>for</strong> optimal heterogeneity in terms of history, structure, values: reason why<br />

it did not work out with FC5 (differences too big, collaboration not possible)<br />

Feedback of and relationship with external stakeholders:<br />

– Align themes of Integrated Youth Assistance and project<br />

– Timing and result orientation do not have to contradict with the process approach<br />

– In each phase ask the question: who can we involve now in a meaningful way?<br />

– Clarity around timing: when which results?<br />

– Clarity around one service or autonomy of services?<br />

– Announce they will come back <strong>for</strong> funding of follow-up project<br />

– External stakeholders:<br />

o in<strong>for</strong>m them of new decisions/procedure/etc<br />

o so far some have been kept out of discussions<br />

o also ask what their expectations are<br />

o involve in work groups?<br />

o more than only the relegating parties<br />

o foster parents not sufficiently included so far (work groups?)<br />

Expected consequences:<br />

– Consequences on labor conditions<br />

– Consequences <strong>for</strong> the coaches of services<br />

Emergent dynamics<br />

– Claim on facilitators to stress the need <strong>for</strong> process facilitation when policy makers<br />

are present<br />

– Enthusiasm and energy of work groups (morning)<br />

– The external stakeholders are in<strong>for</strong>med via slides of the progress; the energy of<br />

the morning fades away<br />

Attachments


– FC5 seems to look <strong>for</strong> rapprochement: state they agree with the<br />

principles/domains of collaboration as presented; are still ready to collaborate in<br />

certain domains; only condition is clarity (‘reception function’)<br />

Attachments


ATTACHMENT 9: OVERVIEW OF ‘CRITICAL INCIDENTS’<br />

The following overview is a summary of the reported critical incidents based on the<br />

critical incident interviews. These interviews were conducted after the project with<br />

the members of the project group in order to assess retrospective sense making of the<br />

process by the key actors. The detailed analysis of the nine interviews was 27,5 pages<br />

long. The analysis was structured as follows: what happened? What sense did the<br />

interviewee make of the incident? Effects and consequences <strong>for</strong> the direction of the<br />

process? In the summary I only mention the headings of the issues. For reasons of<br />

confidentiality I have simply numbered the interviewees without making a<br />

distinction between managers or consultants.<br />

Inter-<br />

viewee<br />

Reported critical incidents<br />

1 – Unprepared start of the project<br />

– Differences between the services<br />

– Role and interventions of the consultants did not meet expectations<br />

– Difficult process of trying to continue with 5 services<br />

– The objective was not clear and not central<br />

– Tension interests organizations – interests child<br />

2<br />

3<br />

– FC5 leaves the project but are still member of the regional<br />

consultation plat<strong>for</strong>m<br />

– ‘Pillarization’ in the sector of foster care hinders collaboration<br />

– Two fundamentally different visions among the services: strategic,<br />

large scale structural collaboration also outside foster care, vs.<br />

gradual, process oriented evolution towards collaboration within<br />

foster care<br />

– Consultants focus too much on similarities and consensus; no room<br />

<strong>for</strong> disagreement and doubts<br />

– Large influence of convening organization and convener<br />

– The regional scope of the project<br />

– Added value of process facilitation offered in the project<br />

– FC5 stepping out<br />

– Late emergence of the differences because boards were involved in a<br />

late phase<br />

– The difficulty of our internal process within the organization<br />

Attachments


4 – The differences in vision with the liberal service<br />

– Developing the objectives among the four services<br />

– Low involvement of external stakeholders<br />

– Differences in commitment of services to the process<br />

– Tension between managers and boards<br />

– Emergent nature of the process<br />

5 – Internal situation of the liberal organization<br />

– Attitude of the organization towards the project<br />

– Ambivalence around collaboration<br />

– Strategic concerns in relation to policy makers<br />

– Lack of in<strong>for</strong>mation in the discussions<br />

– The liberal organization steps out<br />

6<br />

– Failure to involve FC5<br />

– Late involvement of the boards<br />

– Ongoing competitive relationships due to funding system<br />

– Coordination not sufficiently intensive<br />

– Low involvement of stakeholders<br />

– The concrete added value of collaboration was not specified<br />

– Lack of capacity <strong>for</strong> strategic thinking<br />

– Project not build on concrete facts and figures<br />

7 – Decision of liberal service to step out<br />

– Stakeholders conference with external parties<br />

– Concrete work and small steps of work groups<br />

– Asymmetries in organizational structures of participating foster care<br />

services<br />

– Lack of time<br />

– Tension between interests organizations – interests child<br />

8 – Change of logic from stakeholder approach to internal focus and<br />

classic OD approach<br />

– The shift from five to four organizations<br />

9 – The participating foster care services have different expectations<br />

– Intervention: stakeholder interviews by consultants<br />

– First stakeholder conference: difference between discussions with and<br />

without the external stakeholders<br />

– Liberal organization steps out<br />

– Dependency on the external consultants<br />

– Role of coordinator as driving <strong>for</strong>ce of project<br />

Attachments


– Influence from workgroups on project group<br />

– Paradox between strong personalities of managers and weak in<br />

confrontation with external parties<br />

– Influence of head of the Federation<br />

– Little time investment in project<br />

– Poor involvement of foster parents, children and parents<br />

– Not fulfilling the requirements of the contract<br />

– Little to transfer to the next coordinator<br />

Attachments


ATTACHMENT 10: OUTPUT OF THE RESEARCH<br />

Output of the literature study (part 1)<br />

The literature review resulted in a proposal <strong>for</strong> my Ph.D. committee, which I<br />

defended on 15 October 2002:<br />

Prins, S. (2002). Distributed leadership in Inter-organizational Collaboration: a Systems<br />

Psychodynamics Perspective. Unpublished Ph.D. proposal, Faculty of Psychology,<br />

Katholieke Universiteit Leuven, September.<br />

I contributed to some theoretical publications on collaborative work:<br />

Prins, S., T. Taillieu & R. Bouwen (2004). Gedistribueerd proces leiderschap in<br />

multipartij samenwerking. In Varwijk, W.G.J.M. & van Zijl, R.M.H.J. (Eds.) Strategie<br />

moet je samen doen. Visies op strategisch management uit theorie en praktijk. Liber<br />

Amicorum Professor dr. Michel A.E. Vandenput. Ubbergen: Tandem Felix Uitgevers,<br />

pp. 71-87<br />

Craps, M., Van Rossen, E., Prins, S., Taillieu, T., Bouwen, R. & Dewulf, A. (2005).<br />

Relational Practices to make Social Learning happen: A Case Study in Water and<br />

Nature Management. In: Wildemeersch, D., Stroobants, V. & Bron, M. (Eds.) Active<br />

Citizenship and Multiple Identities. A Learning Outlook. Frankfurt am Main: Peter<br />

Lang, pp. 227-244.<br />

The following published and unpublished articles and papers relate to the system<br />

psychodynamic perspective on working and organizing. Some are directly related to<br />

my research, w<strong>here</strong>as others are of a more general nature. In the first phase of my<br />

research I made a thorough review of the psychodynamic literature. In order to<br />

process the amount of in<strong>for</strong>mation I made an extensive literature overview in Dutch<br />

(194 pages). On 6 March 2001 I presented this overview to researchers from the<br />

faculty of Economics and the Center <strong>for</strong> Organizational and Personnel Psychology in<br />

a literature seminar. The overview is available on the internet. I gave a presentation<br />

based on this document to students in organizational psychology in Rotterdam:<br />

Prins, S. (2001). Het psychodynamisch perspectief op organisaties: modetrend of zinvolle<br />

aanvulling op het denken over organisaties? Unpublished literature review, February.<br />

Available on: http://ppw.kuleuven.be/copp/silvia_prins.htm.<br />

Attachments


Prins, S. (2004): Het psychodynamisch perspectief op organiseren en adviseren: de<br />

nieuwste ‘hype’ in het managementlandschap? Guest lecture, 2 March, Rotterdam<br />

University.<br />

I presented my theoretical insights in several presentations at conferences and<br />

seminars:<br />

Prins, S. (2001). Emerging coordination processes in multiparty collaboration: a<br />

psychodynamic perspective. Paper presented at the EIASM seminar, May, Brussels.<br />

Prins, S. (2001). Relationele processen in multiparty samenwerking: een<br />

psychodynamisch perspectief. Een onderzoek naar leiderschapsprocessen in een<br />

complexe organisatiecontext. Paper presented at a colloquium organized by the<br />

Center <strong>for</strong> Organizational and Personnel Psychology (K.U. Leuven), 'Relational<br />

organizing: the process that works, October, Haasrode.<br />

Prins, S. (2002). Researching with Curiosity: the Interpretive Stance in Psychodynamic<br />

Research. Presentation at the OPUS conference 'Organizational and Social<br />

Dynamics: International Perspectives from Group Relations, Psychoanalysis and<br />

Systems Theory', 22 & 23 November, London.<br />

In addition, I gave some lectures in different settings:<br />

Prins, S. (2002). Social Defense theory: containing anxiety in organizational life. The<br />

perspectives of Isabel Menzies and Chris Argyris. Paper presented at the International<br />

Professional Development Programme: Leading Meaningful Change, February,<br />

Bévercé.<br />

Prins, S. (2002). Leiderschap in woelige tijden: welke inzichten kan de psychodynamica<br />

ons bijbrengen? Unpublished lecture, VOCAP, 30 April.<br />

To conclude, I also wrote a number of book reviews, a conference report and a book<br />

chapter in the domain of system psychodynamics:<br />

Prins, S. (2003). Book Review: R.D. Hinshelwood & Marco Chiesa (Eds.), Organisations,<br />

Anxieties & Defences. Towards a Psychoanalytic Social Psychology. (2002),<br />

London: Whurr Publishers, 2002, Human Relations, vol.56, no.3, 359-364<br />

Prins, S. (2003). Book Review: G. Amado & A. Ambrose (Eds.) (2001) The Transitional<br />

Approach to Change. London: Karnac, Socio-Analysis. The Journal of the Australian<br />

Institute of Socio-Analysis.<br />

Prins, S. (2005). Verandering en ontwikkeling: inzichten uit de ontwikkelingspsychologie van<br />

Winnicott voor organisaties. Book review of Amado, G. & Vansina, L. (Eds.) (2005)<br />

The transitional approach in action. London: Karnac. 285 p., Tijdschrift voor<br />

Psychoanalyse, 4, 290-291.<br />

Attachments


Prins, S. (2001). Een psychodynamische kijk op destructiviteit en creativiteit in<br />

organisaties. Nieuwsbrief NVOA, nummer 4, 11-13. (report of the ISPSO conference<br />

in Paris, June 2001)<br />

Prins, S. (2004). Delen en helen. Verandering en ontwikkeling bij Melanie Klein. In:<br />

Wirtz, F. & Idenburg-Van Iperen, A. (Eds.) Hestia's Haardvuur. Schiedam: Scriptum,<br />

pp. 89-100.<br />

Output of the erosion case (part 2)<br />

I presented the case at two seminars in our Faculty and discussed it with fellow<br />

researchers:<br />

- General doctoral seminar: ‘The ‘collaboration-in-the-mind’: a psychodynamic<br />

perspective on leadership processes in multiparty collaboration’, 14 November<br />

2001.<br />

- Methodological seminar: ‘Distributed leadership in trans-organizational<br />

collaboration: a psychodynamic action research’, 5 March 2002<br />

I discussed my findings with colleagues outside the Faculty in order to have an<br />

external perspective (‘peer debriefing’).<br />

- paper and poster presentation at MOPAN conference Bristol (June 2001)<br />

- presentation and discussion of the findings with colleagues at the International<br />

Professional Development Program, Bévercé (October 2001)<br />

- paper and presentation at ISPSO conference Melbourne (June 2002)<br />

- paper and presentation at Inter-logics conference Holland (May 2003)<br />

- paper and presentation at EAWOP conference Lisbon (May 2003).<br />

This case study resulted in several papers:<br />

Prins, S. (2002). Helping and Hindering Dynamics in Multiparty Collaboration: Designing<br />

Psychodynamic Action Research. In: Purdue, D. & M. Stewart (Eds.) Understanding<br />

Collaboration. Bristol: Faculty of the Built Environment, University of the West of<br />

England, 163-165.<br />

Attachments


Prins, S. (2002). “Who’s in charge <strong>here</strong>?!” Leadership Dynamics in Multiparty Collaboration. Paper<br />

presented at the Symposium of the International Society <strong>for</strong> the Psychoanalytic Study of<br />

Organizations, June 20 – 22, Melbourne, Australia.<br />

Prins, S. & Bouwen, R. (2003). Distributed leadership in multiparty collaboration:<br />

opportunities and challenges <strong>for</strong> leadership in the space-in-between organizations. Paper<br />

presented at the Inter-logics Conference, Holland, May.<br />

Prins, S. (2003). “Who’s in charge <strong>here</strong>?!” The Erosion of Leadership Dynamics in a Multiparty<br />

Collaboration. A Case Study. Paper presented at the 11th European Congress of Work and<br />

Organizational Psychology: 'Identity and Diversity in Organizations: Building Bridging<br />

in Europe', Symposium: 'Bridging Diversity through Multiparty Collaboration', Lisbon,<br />

14-17 May.<br />

These papers provided the basis <strong>for</strong> an article which I submitted <strong>for</strong> participation in a<br />

‘Professional development workshop’ on writing and publishing, organized by<br />

INSEAD and the Academy of Management (Paris, October 2004). I received thorough<br />

feedback from a reviewer of the Academy of Management (Prof. Susan Schneider,<br />

HEC, University of Geneva, INSEAD). I also received feedback from three<br />

participants in the workshop. I adapted the article and sent it back to professor<br />

Schneider <strong>for</strong> a pre-review. Finally I submitted the paper <strong>for</strong> publication to Human<br />

Relations in May 2005. My co-authors also provided valuable feedback on the paper.<br />

Prins, S., Taillieu, T. & Bouwen, R. "Who's in charge <strong>here</strong>?!" Emotional challenges and<br />

emergent dynamics in interdependent work. Paper submitted to Human Relations, May<br />

2005.<br />

On 24 November 2005 the reviewers decided that I could submit a major revision of<br />

the paper. Their main observations were: a lack of clarity in the methodology,<br />

insufficient development of the theoretical part, few implications <strong>for</strong> practitioners,<br />

and finally not enough theorizing from the empirical data. Because these aspects are<br />

developed either in the introduction of this case, or in the rest of this book, I have not<br />

thoroughly rewritten the article. On the basis of the feedback by the three reviewers I<br />

did make some small adaptations to the article. I will submit a full revision of the<br />

paper <strong>for</strong> March 2006.<br />

Attachments


Output of the river valley case (part 2)<br />

I presented the case study at conferences and wrote some papers and articles. For<br />

my research I wrote two papers on boundary dynamics in the case study. I discussed<br />

those papers at two conferences. Both papers were published. I wrote a first paper<br />

halfway the process. I presented this paper together with a poster at the MOPAN<br />

conference, Sub stream ‘The Knowledge Space: An Enacted Context <strong>for</strong> Knowledge-<br />

Based Coalitions and Collisions’:<br />

Prins, S., Craps, M. & Van Rossen, E., Managing 'psychological' boundaries in a collaborative<br />

ef<strong>for</strong>t: the dynamics of inclusion and exclusion in an ‘integrated’ study of a river valley.<br />

Paper presented at the 11th International Conference on Multi-Organizational<br />

Partnerships, Alliances and Networks, Tilburg University 23-26 June 2004.<br />

A revision of this paper was published:<br />

Prins, S., Craps, M. & Van Rossen, E. (2005). Managing ‘psychological’ boundaries in a<br />

collaborative ef<strong>for</strong>t: the dynamics of inclusion and exclusion in an integrated study of a<br />

river valley. In Gössling, T., Jansen, R.J.G. & Oerlemans, L.A.G. (Eds.) Coalitions and<br />

Collisions. Nijmegen: Wolf Publishers, pp. 255-264.<br />

I wrote a second paper after our research period in the project had ended. I presented<br />

this paper at the EGOS 2005 colloquium:<br />

Prins, S. & Craps, M. (2005). Unlocking boundaries between public authorities and actors in civil<br />

society in natural resources management. Paper presented at the 21st EGOS colloquium<br />

‘Unlocking Organizations’, Sub-theme 32: The Symbolic Construction of Organization:<br />

Boundary Setting, Identities, and the Process of Organizing, 30 June - 2 July 2005, Berlin.<br />

On request of the reviewer of this conference paper, I submitted a revision of the<br />

paper <strong>for</strong> publication. It was published in the issue of January 2006:<br />

Prins, S., Craps, M. & Taillieu, T. (2006). Boundary dynamics in natural resource<br />

management: the ambiguity of stakeholder inclusion. Revue Gouvernance, 2 (2),<br />

January, 2-11.<br />

During the research I involved a thesis student. I was co-promoter of her thesis<br />

which focused on the critical issues in the river valley case from the perspective of<br />

Attachments


multiparty collaboration. She based her research on data which I collected<br />

(interviews, field notes of meetings):<br />

Deman, S. (2005). Een empirisch onderzoek naar de kritische drempelvoorwaarden van een<br />

multipartijsamenwerking. Case: X (anonymous). Verhandeling aangeboden tot het<br />

verkrijgen van de graad van licentiaat in de psychologie, juni, onder leiding van Taillieu,<br />

T. & Prins, S.<br />

The case study was embedded in the HarmoniCOP project. In that context we<br />

published several reports and presented the case at a conference organized in the<br />

context of the project. In a first phase of the project (work package 2) the Center <strong>for</strong><br />

Organizational and Personnel Psychology (COPP) produced a report w<strong>here</strong> the<br />

concept of ‘social learning’ was presented. This <strong>for</strong>med the basis <strong>for</strong> further work in<br />

the HarmoniCOP project and provided the structure <strong>for</strong> the case analyses (work<br />

package 5).<br />

Craps, M. (Ed.) (2003). Social learning in river basin management. HarmoniCOP, work package<br />

2, Reference document. K.U. Leuven, Centre <strong>for</strong> Organizational and Personnel<br />

Psychology. Prepared under contract from the European Commission, contract No.<br />

EVK1-CT-2002-00120, deliverable no. 3a.<br />

Craps, M., R. Bouwen, A. Dewulf, S. Prins, T. Taillieu & E. Van Rossen (2003). Constructing<br />

a social learning concept <strong>for</strong> river basin management. In: Mostert, E. (Ed.), Public<br />

Participation and the European Water Framework Directive. A Framework <strong>for</strong> Analysis.<br />

Inception report <strong>for</strong> the HarmoniCOP project, prepared under contract <strong>for</strong> the EC, pp. 16-20.<br />

Prins, S. & Craps, M. (2004). Poster presentation at the 5 th HarmoniCOP meeting, Leuven, 28<br />

September – 1 October.<br />

My colleagues presented the concept of ‘social learning’ at the MOPAN conference<br />

in June 2003 in Glasgow:<br />

Taillieu, T., R. Bouwen, M. Craps, A. Dewulf & S. Prins (2003). Multiorganizational<br />

collaboration in River Basin Management and the social learning concept. Presented at the 10th<br />

International Conference on Multi-Organizational Partnerships, Alliances and Networks,<br />

Co-creating Emergent Insight, 25-28 June 2003, University of Strathclyde, Glasgow,<br />

Scotland.<br />

Attachments


We discussed our findings with the actors in the river valley case in <strong>for</strong>mal and<br />

in<strong>for</strong>mal settings. On 15 September 2004 we organized a one-day workshop: ‘Public<br />

participation and social learning in water management’. Organization of a workshop<br />

was a requirement of the HarmoniCOP project (work package 5). Representatives of<br />

the following organizations were present: department Water, department Nature, a<br />

local authority, a non-governmental organization in the domain of environment, an<br />

external consulting firm, and members of the Center <strong>for</strong> Organizational and<br />

Personnel Psychology (12 participants). Eight persons could not be present. We made<br />

a report of the workshop <strong>for</strong> the HarmoniCOP project. A Dutch translation was sent<br />

to the participants.<br />

Craps, M. & Prins, S. (2004). HarmoniCOP WP5 “Case Studies”, K.U.Leuven, Centre <strong>for</strong><br />

Organizational and Personnel Psychology, The River Valley Development Plan: Report of<br />

the Stakeholder Workshop, September.<br />

The workshop helped us to validate our findings and to finalize the case study<br />

report:<br />

Craps, M. & Prins, S. (2004). Participation and Social Learning in the Development Planning of a<br />

Flemish River Valley. Case study report produced under Work Package 5, HarmoniCOP<br />

Project Prepared under contract from the European Commission, Contract No. EVK1-CT-<br />

2002-00120, Deliverable nr. 7, November.<br />

My colleagues also presented and discussed the case at the ‘<strong>Connection</strong>s conference’,<br />

organized in Leuven in September 2003. Two different versions of the paper were<br />

published:<br />

Craps, M., E. Van Rossen, S. Prins, T. Taillieu, R. Bouwen & A. Dewulf (2003). Social<br />

learning and water management: Lessons from a case study on the Dijle catchment.<br />

Proceedings of the <strong>Connection</strong>s Conference on “Active Citizenship and Multiple Identities”,<br />

Leuven, September, pp. 418-429.<br />

Craps, M., Van Rossen, E., Prins, S., Taillieu, T., Bouwen, R. & Dewulf, A. (2005). Relational<br />

Practices to make Social Learning happen: A Case Study in Water and Nature<br />

Management. In: Wildemeersch, D., Stroobants, V. & Bron, M. (Eds.) Active Citizenship<br />

and Multiple Identities. A Learning Outlook. Frankfurt am Main: Peter Lang, pp. 227-244.<br />

Attachments


After the HarmoniCOP project (October 2005) the coordinator of the project took the<br />

initiative to bring together a number of papers <strong>for</strong> a special issue of ‘Ecology and<br />

Society’, based on the HarmoniCOP project. We submitted a paper in January 2006:<br />

Prins, S., Craps, M. & Taillieu, T. Social learning and boundary dynamics in collaborative<br />

work: a case study in river valley planning.<br />

Output of the foster care case (part 3)<br />

The project resulted in three research reports describing the approach, the<br />

interventions and the research results. They were written <strong>for</strong> the funding<br />

organizations of the project (policy makers).<br />

Andriessen, M., Prins, S., De Witte, K., Hovelynck, J., & Taillieu, T. (2004).<br />

Samenwerking tussen diensten voor pleegzorg in Limburg: Eerste tussentijds rapport.<br />

Rapport pleegzorg in opdracht van vzw Jeugdzorg in Gezin. Leuven: Katholieke<br />

Universiteit Leuven, Departement Psychologie, Centrum voor Organisatie- en<br />

Personeelspsychologie, Mei.<br />

Andriessen, M., Prins, S., De Witte, K., Hovelynck, J., & Taillieu, T. (2004).<br />

Samenwerking tussen diensten voor pleegzorg in Limburg: Tweede tussentijds rapport.<br />

Rapport pleegzorg in opdracht van vzw Jeugdzorg in Gezin. Leuven: Katholieke<br />

Universiteit Leuven, Departement Psychologie, Centrum voor Organisatie- en<br />

Personeelspsychologie, Oktober.<br />

Andriessen, M., Prins, S., De Witte, K., Hovelynck, J., & Taillieu, T. (2004).<br />

Samenwerking tussen diensten voor pleegzorg in Limburg: Eindrapport. Rapport<br />

pleegzorg in opdracht van vzw Jeugdzorg in Gezin. Leuven: Katholieke<br />

Universiteit Leuven, Departement Psychologie, Centrum voor Organisatie- en<br />

Personeelspsychologie, December.<br />

In response to a call <strong>for</strong> papers I wrote a first article with a focus on the research<br />

methodology I used in this case. The call was <strong>for</strong> a special section of the Journal <strong>for</strong><br />

Occupational and Organizational Psychology entitled: ‘Beyond Positivism and<br />

Statistics: Neglected Approaches to Understanding the Experience of Work’. My aim<br />

with this paper was to demonstrate the relevance of doing organizational research<br />

from the psychodynamic perspective and to show that it generates complementary<br />

insights that can help to understand why so many collaborative ef<strong>for</strong>ts fail or end up<br />

Attachments


in inertia. The basis <strong>for</strong> the article was a methodological paper I had presented in<br />

November 2001 in London.<br />

Prins, S. (2002). Researching with Curiosity: the Interpretive Stance in Psychodynamic<br />

Research. Presentation at the OPUS conference 'Organizational and Social<br />

Dynamics: International Perspectives from Group Relations, Psychoanalysis and<br />

Systems Theory', 22 & 23 November, London.<br />

I presented a first draft version of the paper to the Research group <strong>for</strong> psychotherapy<br />

and depth psychology, chaired by Prof. J. Corveleyn in March 2005. I submitted the<br />

paper to the journal on 30 April 2005. On the basis of feedback by three reviewers I<br />

sent a thorough revision of the article on 25 October 2005. In December the paper<br />

was accepted <strong>for</strong> publication and will be published in September 2006.<br />

Prins, S. The psychodynamic perspective in organizational research: making sense of<br />

the dynamics and emotional challenges of collaborative work. Journal of<br />

Occupational and Organizational Psychology, Special Section ‘Beyond Positivism and<br />

Statistics: Neglected Approaches to Understanding the Experience of Work’.<br />

I could not discuss all the findings within the boundaries of one article. T<strong>here</strong><strong>for</strong>e I<br />

decided to split up the issues and write two papers. The first paper discusses issues<br />

related to the influence of the consultants on direction setting. The second paper<br />

discusses more general issues that typically emerge in collaborative work (e.g.<br />

dealing with diversity). Because the two articles are based on the same data, t<strong>here</strong> is<br />

overlap in the introduction of the case (e.g. conceptual framework, context and<br />

narrative of the case). Since the issues are interconnected and need to be described in<br />

their context t<strong>here</strong> is also some overlap in the discussion of the issues.<br />

The basis <strong>for</strong> the second article was a paper presented at the Symposium of the<br />

International Society <strong>for</strong> the Psychoanalytic Study of Organizations in Baltimore,<br />

June 2005. The paper fitted with the conference theme: ‘New Psychoanalytic<br />

Responses in our work with Organizations and Society’. It was published on the<br />

website of ISPSO. Later I thoroughly rewrote the paper to align it with the focus of<br />

my research. I organized a research seminar at our center to discuss the paper on 4<br />

Attachments


November 2005. I submitted the article to the Journal of Applied Behavioral Science<br />

on 17 December 2005.<br />

Prins, S. (2005). The emotional and relational challenges of working in collaborative systems:<br />

the bumpy road from competition to collaboration. Paper presented at the 2005<br />

Symposium of the International Society <strong>for</strong> the Psychoanalytic Study of<br />

Organizations, ‘New Psychoanalytic Responses in our work with Organizations<br />

and Society’, 17-19 June, Baltimore:<br />

http://www.ispso.org/Symposia/Baltimore/2005%20papers/2005Prins.htm<br />

Prins, S. & Taillieu, T. From competition to collaboration: dynamics of direction setting in<br />

collaborative work. (submitted to the Journal of Applied Behavioral Science, on 17<br />

December 2005)<br />

Two students were at some point engaged in the foster care project. I was co-<br />

promoter of their master’s thesis on the critical conditions <strong>for</strong> collaboration in the<br />

foster care project. They observed two stakeholder conferences and used data I had<br />

collected (stakeholder interviews, field notes of stakeholder days). The students also<br />

organized a survey among the large group of stakeholders, but the response rate was<br />

relatively low. We had many conversations and discussed our observations. The<br />

findings of the two students substantiate most of my findings.<br />

Bos, L. & De Vos, G. (2005). Onderzoek naar de kritische succesfactoren in multipartij<br />

samenwerking, project pleegzorg Limburg. Verhandeling aangeboden tot het verkrijgen<br />

van de graad van Licentiaat in de Psychologie, K.U. Leuven, Centrum voor<br />

Organisatie- en Personeelspsychologie (unpublished masters thesis).<br />

Attachments

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!