|

From Wiki Pedagogy to Platformed Collaboration: Revisiting Collaborative Digital Writing in Technical Communication Through a Decolonial Lens

by Shuvro Das | Xchanges 21.1, Fall 2026

Five Principles for a Revised Pedagogical Framework

What follows is not a prescriptive curriculum but a set of principles for instructors who want to teach collaborative digital writing in ways that take seriously both Scott’s insights and the scholarly conversation that has developed since her article appeared. These principles can apply to wiki assignments, Wikipedia-based projects, Google Docs collaborations, shared documentation spaces, or other platformed writing environments. Their purpose is not to tell instructors which tool to use. Their purpose is to make the tool, the labor, and the epistemology of collaboration visible.

Principle 1: Teach Platforms as Arguments, Not Tools

The most fundamental shift this framework requires is also the simplest to state: instructors should treat the platforms they assign as objects of rhetorical analysis rather than as neutral infrastructure. This does not mean abandoning proprietary platforms or romanticizing earlier wikis as pure alternatives. It means building into any assignment a critical examination of the platform’s design, ownership, data practices, and epistemological commitments. Selber’s three-part framework of functional, critical, and rhetorical digital literacy offers a useful scaffold. Selber is careful to note that functional skill is “necessary if not sufficient” (p. 33) on its own; it is a floor, not a ceiling. A functionally literate student knows how to edit a wiki page or comment in Google Docs. A critically literate student understands that the interface reflects institutional values and interests. A rhetorically literate student can decide how to use the platform strategically, when to resist its defaults, and when another medium would better serve the writing situation.

In practice, this might mean asking students to read a platform’s help documentation, community guidelines, or terms of service alongside their first collaborative writing assignment. In a Wikipedia assignment, students might examine the community portal, student training modules, or policies on verifiability and no original research as genre instruction rather than treating them as neutral rules. In a Google Docs assignment, students might compare owner, editor, commenter, and viewer roles and ask what model of authority those roles assume. In a Notion or Microsoft 365 assignment, they might analyze how templates, databases, and permission structures shape what becomes visible as work. Jones’s advocate orientation makes a lot of sense in this context because professionals who can read the politics of their tools are better equipped to serve clients and communities whose interests may not align with the interests of the platform’s designers.

Arola’s land-based digital design rhetoric strengthens this approach by reminding instructors that interface analysis should not stop at what a screen permits users to do. Digital design is also situated in material relations among people, places, histories, and cultural practices. A platform can, therefore, be analyzed not only for its permissions and affordances but also for the kinds of relationships it makes easier to imagine, sustain, or ignore.

Principle 2: Expand the Definition of Collaborative Contribution

Any assessment framework that measures contribution primarily through tracked text edits will undervalue the labor that makes collaborative writing possible. This is not a minor grading issue. It is a structural feature of many platforms, and it reinforces existing patterns of whose intellectual labor is counted and whose is not. Gruwell’s findings about Wikipedia are compatible here because the platform can count edits while failing to count the translation, negotiation, mentoring, and community maintenance that make those edits possible.

A revised assessment framework should include structured self-assessments that ask students to account for the full range of their contributions, peer evaluations that name specific forms of non-textual labor, and reflection assignments that ask groups to examine how the division of labor emerged. Instructors can explicitly value project management, meeting facilitation, multilingual mediation, accessibility checking, conflict resolution, source evaluation, and audience research as collaborative contributions. This approach connects naturally with labor-based grading scholarship, particularly Inoue’s (2019) argument that assessment can become more equitable when it values labor, process, and reflection rather than only proximity to a dominant standard. For technical communication, the point is also professional. Technical communicators often work in team environments where stakeholder coordination, cross-functional translation, accessibility advocacy, and project management are as important as sentence-level production. A classroom assessment model that cannot see this work prepares students for a narrower profession than the one many will enter.

Principle 3: Design for Linguistic and Epistemological Plurality

Most collaborative writing assignments in technical communication courses are implicitly designed for native English speakers working within Western professional communication conventions. This is not always intentional, but structural as it is built into platforms, rubrics, assignment prompts, and models of successful writing. Gonzales (2018) makes clear that multilingual communicators bring intellectual resources to collaborative writing that are not less sophisticated than those of monolingual English speakers. They are differently sophisticated, organized around translation, code-switching, and the negotiation of meaning across cultural contexts.

Designing for linguistic plurality means allowing multilingual drafting in the collaborative process before English-language revision when appropriate; naming translation and code-switching as rhetorical skills rather than deficits; and building rubrics that assess audience awareness, usability, ethical decision-making, and communicative effectiveness rather than conformity to a single standard of academic English. More ambitiously, it might mean designing projects whose final products can take forms other than unified English-language documents: multilingual guides, community-facing materials in languages other than English, or comparative analyses of how different rhetorical traditions approach a shared technical communication problem. Haas’s broader point is that technical communication pedagogy has something to learn, not merely something to offer, from knowledge traditions outside the Western canon. Designing assignments that create space for this learning is one way to act on that insight.

Principle 4: Center Consent, Credit, and Care

Collaborative writing assignments involve forms of consent that instructors rarely address explicitly. Students who contribute to shared documents share their intellectual labor, rhetorical choices, revision histories, and sometimes aspects of their personal experience or identity. When assignments are published publicly, as many wiki-based projects encourage, that sharing extends beyond the classroom with consequences that are difficult to anticipate. Students from marginalized communities may face risks when their writing becomes publicly visible; harassment, misrecognition, unwanted exposure, or pressure to represent a community to which others assign them.

Instructors should be explicit about what will happen with collaborative work: where it will be stored, who will be able to see it, how long it will remain available, and what rights students retain over their contributions. Where assignments involve personal narrative, community knowledge, or lived experience, instructors should create genuine alternatives rather than nominal opt-outs. They should not design their pedagogical goals in ways that require students from marginalized communities to perform their difference for an audience that may not share their stakes. Walton, Moore, and Jones describe reflexive attention to positionality as central to ethical practice in technical communication research and teaching. That principle extends naturally to classroom collaboration.

Race, Rhetoric, and Research Methods (Lockett et al., 2021) brings together antiracist and decolonial approaches to questions of embodiment, institutional critique, multimodality, materiality, and public digital literacies. Lockett’s chapter on Black Twitter, specifically, demonstrates how marginalized publics use digital platforms rhetorically while also negotiating the racialized structures that shape visibility, circulation, and participation. This chapter complicates the idea that making a platform available automatically creates an equitable collaborative space. Students do not enter digital writing environments with identical histories, relationships to technology, or levels of rhetorical power; they enter spaces already structured by racial, cultural, and institutional conditions.

Care also means attending to the relational labor that collaboration requires. Groups need time to establish trust, negotiate working styles, and address conflict before they can write together effectively. Assignments that treat collaboration as a technical matter of dividing tasks and assembling outputs miss this labor. They typically produce worse documents and worse learning. The care work of collaboration should be named, practiced, and assessed, not treated as the responsibility of whoever in the group happens to do it by default.

Principle 5: Situate Digital Tools in Their Histories

None of the tool’s instructors assign emerged from nowhere. They have organizational, cultural, and economic genealogies that shape what they can and cannot do. The open-source wiki tradition carries the intellectual inheritance of free software philosophy, with its commitments to transparency, meritocracy, and the belief that openness of code can support openness of knowledge. Wikipedia carries the history of encyclopedic writing, community moderation, volunteer labor, and formalized content policies. Google Docs carries the inheritance of enterprise software development, cloud computing, and data-driven platform ecosystems. Notion contains the logic of templates, databases, productivity culture, and workspace management. These histories matter because they continue to shape how collaboration feels, what it rewards, and what it hides.

Teaching students to situate tools historically is one of the most durable things a technical communication course can do. Trends in platforms change quickly; the capacity to ask about a tool’s history, values, and interests does not. Following Haas’s provocation in “Wampum as Hypertext,” this historical situating should include non-Western traditions of collaborative knowledge production: forms of collective authorship, knowledge maintenance, oral transmission, material memory, and community-based information management that exist outside the Western digital humanities tradition. Students who learn to see their tools’ histories are also students who can begin to imagine alternatives: different tools, different conventions, and different models of what collaborative writing might be for.

Lockett et al. similarly demonstrate why technological histories must be read alongside histories of race, embodiment, and public discourse. Their attention to public digital literacies shows that digital spaces are not simply containers into which users bring preexisting identities; they are sites where racialized identities, publics, and forms of knowledge are negotiated and contested. For students, then, situating a platform historically should include asking whose histories are represented in its design, whose forms of public participation it recognizes, and whose rhetorical practices have been treated as peripheral or illegible.