Posts ⁂ The Postmodern Terminal >_
Two ethical traditions the methods literature keeps apart, put in the same room: the risks of studying your own institution and the shift from consent to community authority over data.
Most practitioner-scholars never study strangers. They study their own congregation, their own school, the organization they founded or lead, and sometimes communities for whom "research" carries a documented history of extraction. Two ethical traditions speak to that situation and the methods literature keeps them apart. I will argue that they belong in the same room, and I will show it by running one ordinary study through both audits.
Teresa Brannick and David Coghlan's "In Defense of Being 'Native'" (2007) is genuinely a defense. Research by complete members of an organizational system is methodologically legitimate, and the insider brings what no outsider can buy. They call it preunderstanding: you know the history, the factions, the shorthand, why that committee never meets. An outsider spends eighteen months acquiring what you woke up with.
The advantage arrives with role duality, and four risks descend from it. The staff member sitting with you as researcher is also sitting with the person who writes her performance review. Then structural coercion, which has nothing to do with intent. Consent given to a pastor, founder, or principal travels upward through a power gradient, and a congregant who declines may reasonably fear it is noticed. No amount of warmth dissolves that. Then false anonymity: in a congregation of sixty, "an anonymous respondent who has served on the board and has adult children" identifies exactly one person. Then founder blindness: the critique nobody voices in front of you is invisible by definition, and it is often the finding that matters.
Each risk has a safeguard, and each is a design decision made before you collect anything. Build recruitment and opt-out channels that do not pass through you. Commission independent coding from a reader who does not depend on you, and take the divergences seriously. Add member checking, so participants contest your representation of them before publication. And stop promising anonymity you cannot deliver.
The second tradition lands in the same place. Linda Tuhiwai Smith opens Decolonizing Methodologies (1999) with a line that has organized a generation of work: "research" is probably one of the dirtiest words in the Indigenous world's vocabulary. She means it as description. Research came to Indigenous communities as an instrument of empire, classifying, collecting, extracting, publishing, and leaving. The response has not been to refuse research but to relocate authority over it, from research conducted on communities to research conducted with and by them. UNDRIP (2007) states in Article 31 that Indigenous peoples have the right to maintain, control, protect, and develop their traditional knowledge. Not to be consulted about it. To control it. Instruments operationalize that.
In Canada, the First Nations Principles of OCAP assert Ownership, Control, Access, and Possession. Communities collectively own information about themselves, govern the research, and hold the data, because possession is how ownership gets asserted. The CARE Principles for Indigenous Data Governance (Stephanie Russo Carroll and colleagues, 2020) give four words: Collective Benefit, Authority to Control, Responsibility, Ethics. CARE complements the FAIR principles for open data, which are data-centric where CARE is people-centric. Openness without authority is just extraction with better metadata.
Now run one study through both. You pastor a congregation of ninety and plan to survey it about a program you designed. Insider safeguards first: a lay coordinator sends the invitation and holds the declines; responses land where you cannot see them mid-collection; you report by theme rather than role; and an outside colleague codes a third of them. Then the CARE questions on that same study. Who collectively benefits, the congregation or your degree? Who holds authority over this data after your defense? Who stays responsible when the findings are unflattering and the people described are still in the pews on Sunday?
The governing question is not "may I study them?" That one has an easy answer and it is the wrong question. The better question, the one that changes a design, is what you owe the people who make your knowledge possible. So write the protocol: how permission gets renewed, what triggers a check-in, and how a community can withdraw its data after you are done with it. Theory that never reaches the protocol document has not done its work.
The Postmodern Terminal >_