MHST6902 Chap.6 Community Collaboration and Shared Authority
Community Collaboration and Shared Authority
Collaboration is a governance arrangement
Community engagement ranges from informing people about a finished decision to community control over purpose, resources and representation. Calling every interaction collaboration hides that difference. A project should state which decisions are open, who holds authority, how participants are selected and what the institution cannot promise.
Shared authority does not eliminate expertise; it makes the distribution of expertise and power explicit and negotiable.
Reciprocity requires resources
Communities contribute time, relationships, knowledge and reputational risk. A reciprocal project budgets payment, access support, intellectual credit, data care and benefits identified by collaborators.
It does not assume that public visibility is adequate compensation. Timelines must allow trust and disagreement, and institutional staff need enough authority to respond when community advice challenges the original concept.
Evidence should show influence
Counting meetings measures activity, not shared authority. A stronger record traces proposals, decisions, revisions and unresolved disagreements.
Evaluation asks whether participants could influence the project, whether processes were culturally and practically accessible and whether responsibilities continue after launch.
Where collaboration is limited, honest description is better than inflated language.
Map risk and benefit on both sides
Institutions may worry about schedule, brand or resources, while community partners may risk exposure, conflict, cultural harm or loss of control over knowledge. List these separately and ask who currently carries each risk.
Then connect safeguards to decision rights, payment, data governance and a review trigger. The same exercise should identify benefits defined by partners rather than assuming that visibility or participation is sufficient.
Keep institutional change in view
A project can create a positive participant experience while leaving collections, staffing and governance unchanged.
State what the institution will learn or do differently and assign a responsible role and date. A decision log should preserve where partners changed the concept, where agreement was not reached and what obligations continue. That record is stronger evidence of shared authority than a promotional list of meetings or contributor names.
What this chapter covers
- 01
Participation spectrum
- 02
Decision rights
- 03
Reciprocity and payment
- 04
Trust and time
- 05
Conflict and refusal
- 06
Change log
- 07
Post-launch accountability
Worked example · free
Move a local history project beyond consultation
- 2Reopen the theme and invite a representative community group to define desired outcomes, exclusions and criteria for selecting material.
- 2Agree payment, copyright or licence terms, attribution, storage, access restrictions, withdrawal and approval before collecting images.
- 2Maintain a decision log, provide accessible review points and establish who will handle corrections, returns and reuse after opening.
Key terms
- Shared Authority
- Meaningful distribution of interpretive and project decision making among institutions and community partners.
- Reciprocity
- An exchange in which benefits, resources and responsibilities respond to what collaborators contribute and value.
- Decision Right
- Explicit authority to propose, approve, revise, restrict or stop a defined part of a project.
- Change Log
- A record linking stakeholder input to decisions, revisions, reasons and unresolved issues.
Community Collaboration and Shared Authority FAQ
Is consultation always too limited?
No. Consultation can be appropriate when its scope is honest and participants know which decisions remain open. Problems arise when institutions ask for advice after core choices are fixed or describe feedback as co-creation. Match the engagement level to the decision and communicate its limits.
What should a collaboration budget include?
Include payment for expertise and time, access and transport, facilitation, translation where needed, production costs, permissions, care of supplied material and post-launch review. Budgeting only the public output transfers hidden costs to partners and weakens their practical ability to participate.
How can disagreement be handled without forcing consensus?
Agree decision procedures before conflict occurs, document competing positions and distinguish matters that require consent from those that allow several interpretations. A project can represent disagreement transparently. Consensus should not be manufactured by removing the perspective with less institutional power.
Assessment move
Rewrite every stakeholder list as a rights matrix. Across the top place propose, approve, edit, restrict, withdraw and review; down the side place each partner. Fill the cells and look for people who supply risk or knowledge without power. In case analysis, cite a concrete revision as evidence of influence. Add what each party contributes, receives and risks, then assign resources and safeguards.
Finish with one institutional change and a review date so collaboration is judged by continuing practice rather than the number of meetings held. Compare two cases by asking who initiated the work, who controlled money, who could refuse publication and what remained after launch. Where evidence is missing, write the document or participant account needed to establish it.
This prevents a visible community contribution from being mistaken for shared governance and keeps claims proportional to the available record.
