|

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

From Wikis to Proprietary Platforms: The Political Economy of Classroom Tools

The shift from wikis to proprietary collaborative platforms should not be treated as a simple software update. Wikis, Wikipedia assignments, Google Docs, Microsoft 365, and Notion all support collaborative writing, but they do so through different genres, architectures, ownership structures, and assumptions about work. A wiki is typically organized as a networked set of pages whose revision history records collective knowledge-building over time. A real-time collaborative word processor is typically organized around a document file that multiple people can edit synchronously, often within an institutional account system. A project management platform such as Notion organizes collaboration through databases, templates, permissions, and workspaces. These differences matter pedagogically because each platform teaches students, often quietly, what collaboration is supposed to look like.

In 2011, using a course wiki was often imagined as a choice to work outside the most familiar commercial systems. Wikis such as PBworks and Wikispaces offered educational accounts and made web publication seem more accessible than it had been before. Even when these tools were not fully open source, they were frequently framed through Web 2.0 ideals of participation, openness, and shared authorship. The situation now is different. Most collaborative writing in educational contexts happens through products owned by some of the largest technology companies in the world. Google Docs is convenient, powerful, and widely available, but it is also part of an ecosystem whose business model depends on data collection, account integration, and platform lock-in. Microsoft 365 and Notion operate through different models, but they too embed classroom writing within corporate infrastructures.

Gillespie’s analysis of platform governance is useful here. In “The Relevance of Algorithms” (2014), he argues that platforms often present themselves as neutral conduits while actively shaping communication through algorithmic systems, design affordances, data practices, and terms of service; even the most mundane classroom tool is, in his terms, “producing and certifying knowledge” (p. 167) rather than simply transmitting it. The apparent neutrality of a platform is itself an ideological achievement. When Google Docs presents itself simply as a tool for writing, it performs this kind of neutrality. The design choice to make comments threaded, to make suggestions accept-or-reject decisions, or to give some users ownership and others limited access, and to treat a resolved comment as a completed unit of work does not present itself as a theory of collaboration. It presents itself as the obvious way collaboration works. Gillespie’s point is that this naturalization is where the ideology resides.

Noble’s Algorithms of Oppression (2018) adds another layer. She demonstrates that the design choices of major technology platforms can encode racial and gender hierarchies even when those systems appear merely technical, a phenomenon she terms “technological redlining” (p. 1) to capture how systems that look neutral quietly sort and disadvantage users along familiar lines of race and gender. This insight matters for collaborative writing pedagogy because classroom platforms are not built from nowhere. They are designed in professional and corporate cultures with their own assumptions about productivity, documentation, ownership, and communication. When instructors assign tools built for those environments, they import some of those assumptions into the classroom. This does not mean instructors should refuse to use them. It means the use of these platforms should become part of the curriculum rather than an invisible condition of the curriculum.

Three concerns deserve particular emphasis in technical communication pedagogy. The first is surveillance asymmetry. Proprietary collaborative tools log activity in ways that are rarely disclosed to users in terms they can practically evaluate. A student using a cloud-based collaborative platform for a graded assignment has, in effect, been enrolled in a data environment whose terms they did not meaningfully negotiate. The Family Educational Rights and Privacy Act, or FERPA, offers some protections for student education records in the United States, but it was not designed for the current architecture of cloud-based educational technology. Its relevance to behavioral data, keystroke activity, revision patterns, and co-authorship networks remains difficult for ordinary users to evaluate. The ethical issue is not simply whether a tool is legally compliant. It is whether students can meaningfully consent to the data arrangements that participation requires.

The second concern is access, which looks different now than it did when course wikis were the dominant model of web-based collaboration. Many earlier wiki platforms ran adequately on slower connections and older hardware. Real-time collaborative editing does not always do so. Latency problems, synchronization failures, device limitations, and browser instability can make collaborative work uneven in ways that are easy for instructors to misread as lack of preparation or weak participation. What looks like a pedagogical level playing field may be tilted along familiar axes of class, geography, disability, language, and institutional access. This is not an argument against using contemporary platforms; it is an argument for designing assignments that acknowledge the unequal conditions under which students use them.

The third concern is epistemological. Proprietary collaborative platforms are organized around a particular model of how documents get made: individual contributions are tracked, attributed, commented on, accepted, rejected, and eventually accumulated into a unified text. Revision moves toward a settled version. Comments are discrete, addressable, and resolvable. This model is often useful, especially in professional documentation work, but it is not universal and not politically neutral. It reflects workplace cultures organized around accountability, productivity, ownership, and version control. Selber, to some extent, asks instructors to make such assumptions visible. Teaching students to use these platforms without teaching them to interrogate those values leaves them with functional literacy but not critical or rhetorical literacy.

The field’s relative silence around platform capitalism is itself worth noting. Technical communication has long studied tools, documentation systems, usability, and workplace writing, but it has often approached classroom platforms as practical supports rather than as political-economic actors. At the same time, decolonial and feminist technical communication scholarship has deeply examined power, access, positionality, and marginalization. Bringing platform studies into conversation with that scholarship does not import an unrelated concern into the field. It clarifies how tools participate in the very power relations that social justice-oriented technical communication has already taught us to analyze.