MON2100 Chap.2 Collaboration and Constructive Conflict
Collaboration and Constructive Conflict
Collaboration and constructive conflict examines the communication, trust and coordination practices needed in a diverse fieldwork team. Difference can improve analysis when disagreement stays attached to evidence and assumptions.
This chapter turns broad intentions into observable team behaviours, distinguishes task conflict from relationship conflict, improves evidence handovers and shows how to reflect critically on a difficult group moment.
A shared mission gives the team a decision rule. When preferences differ, members can ask which choice makes the local challenge clearer, respects the evidence and supports the assessment purpose.
This reduces the chance that status or confidence determines the outcome. The mission should be specific enough to guide trade-offs and revisited when field evidence changes the problem frame.
Task conflict concerns the work: a source, definition, interpretation or proposed relationship. It can improve quality because weak assumptions are tested.
Relationship conflict shifts attention toward a person's character, motive or standing. A constructive response names the exact inference under review, asks what evidence would change the view and offers a clear next action. Curiosity comes before advocacy, but the group still needs a deadline and a decision process so openness does not become drift.
Coordination requires visible dependencies.
A field visit is not complete if contextual notes remain on one phone while another member builds slides from partial impressions. Use a common record that separates observation, stakeholder account, interpretation and uncertainty. Identify what another member is waiting for and record decisions with an owner, reason and review point.
Lightweight practices that survive a busy trip are better than elaborate templates nobody maintains.
Trust does not mean avoiding disagreement. It means members can raise uncertainty, acknowledge error and challenge a broad claim without expecting personal attack. Rotate facilitation and evidence-checking roles where suitable, notice invisible coordination labour and create a credible route for quieter concerns.
If evidence remains ambiguous, preserve the minority reading and state why the team made a provisional choice.
Critical reflection on collaboration should show a sequence: the specific tension, the behaviour used to address it, the effect on the analysis and what you would change next time. A difficult exchange is not automatically a team failure, and harmony is not automatically success.
The assessment value lies in showing how the process affected both relationships and the quality of the shared work.
What this chapter covers
- 01
Shared mission and team purpose
- 02
Task conflict and relationship conflict
- 03
Evidence handovers and dependencies
- 04
Curiosity before advocacy
- 05
Decision rules and minority concerns
- 06
Critical reflection on team process
- 07
Decision records with an owner, reason and review point
- 08
Rotating coordination labour and creating routes for quieter concerns
- 09
Separating productive discomfort from damage to working relationships
- 10
Authority for urgent field decisions agreed before time pressure makes the choice ambiguous
Worked example · free
Repair a claim that overstates one interview
- +1Identify the inference rather than the teammate as the problem.
- +1Narrow the current evidence to one stakeholder perspective.
- +1Ask what corroboration or contrary evidence is available.
- +1Agree who will revise the claim and when the team will check it.
Key terms
- Task conflict
- Disagreement about evidence, interpretation or the work itself.
- Relationship conflict
- Tension focused on people, status or motive rather than the analytical issue.
- Evidence handover
- A structured transfer of observation, context, interpretation and uncertainty.
Collaboration and Constructive Conflict FAQ
Can conflict be useful in a fieldwork team?
Yes, when it tests evidence or assumptions and members remain focused on the task. It becomes damaging when criticism shifts to personality, status or motive. Clear rules and a shared mission help keep disagreement productive.
What belongs in a team agreement?
Use observable behaviours: where evidence is stored, how quickly messages are acknowledged, how decisions are recorded, when disagreement is escalated and how broad claims are checked. Phrases such as communicate well are too vague to guide action.
How do I reflect on a team problem critically?
Describe the specific tension, the practice used to address it, the effect on the work and what you would change next time. Separate the discomfort of being challenged from evidence that collaboration failed.
Assessment move
Before travel, agree on one evidence format and a decision process. During group work, practise asking what evidence would change a view and record unresolved concerns. After each rehearsal, identify one overbroad claim and one dependency that could block another member. Use those observations in reflection. Convert broad team promises into observable behaviours.
Specify where notes live, when a field visit counts as complete, how decisions are recorded and which issues require host advice. Test the process on a small task and remove any step the group cannot sustain. Rotate facilitation, evidence checking and note keeping where appropriate so one member does not carry invisible coordination labour.
When disagreement appears, write the claim under review, the evidence for each reading, what could change the decision and the deadline. Keep critiques attached to the work. If uncertainty remains, record the minority concern rather than manufacturing agreement. After a decision, confirm what changed, who will update it and when the result will be reviewed.
For reflection, distinguish task conflict from relationship conflict and describe the effect on the analysis. A useful account names the tension, the repair, the outcome and the future practice. Harmony is not proof of good collaboration, and discomfort is not proof of failure.
