DWIXEL

All posts
Approach

Measuring contribution without turning it into surveillance

Edit logs can show who did the work. They can also be misread, gamed, and abused. The design is the whole job.

The Dwixel team · June 2026 · 2 min read

If the work happens in a shared document, the document already knows a great deal about who did it. The temptation is to count edits and call it contribution. That is the wrong instrument, and the research on collaborative-writing analytics is unusually clear about why.

Counting is not measuring

Edit history can legitimately ground an assessment of who participated, but raw edit counts do not capture the value of what was contributed; the traces have to be interpreted against the task. 1 The sharpest version of this point comes from a study of Wikipedia: what reflects accepted contribution is the surviving content of an edit, not how many edits a person made. 2 A member who pastes a large block that is later cut has produced motion, not work.

This is why Dwixel does not score by volume. Large pasted bursts are detected and de-credited rather than rewarded, contribution is weighted toward authored text that survives revision, and editing and curation are counted as their own kind of work rather than mistaken for fresh writing. The aim is to measure the thing that matters, not the thing that is easy to count.

Showing the work, not reducing it to one number

Researchers who built tools to surface collaborative effort tended not to collapse it into a single figure. They reconstructed the full revision history so authors and instructors could see who contributed what over time. 3 We take the same stance. Contribution is presented as a profile a person can inspect, with attributed history behind it, not a verdict handed down without evidence.

The line between visibility and monitoring

Using students’ digital traces is not ethically free. A review of 77 studies groups the concerns into privacy and consent, the validity of the inferences drawn, ethical decision-making, and governance. 4 Those concerns are not a reason to avoid measurement. They are a specification for how to do it.

  • ·Instructors can review the group’s work and see who contributed what, but the measurement is of the work, not a covert profile of the person.
  • ·Students can see their own contribution data, so measurement is something done with them, not to them.
  • ·Scoring is deterministic and explainable. There is no opaque model deciding a person’s share; the rules can be read and checked.
  • ·Peer review is confidential, work is never exposed to other groups or the public, and access is enforced by row-level security.
  • ·Quality signals (surviving text, de-credited pastes) guard against the validity problem the research warns about.
The principle
Measure the work, not the person. Instructors get real oversight; the scoring stays explainable, students see their own data, and nothing is exposed beyond the group and its instructors.

Surveillance watches people covertly and judges them with hidden rules. A contribution record measures the work, shows each person their own data, and is deterministic and inspectable. That distinction is the entire design.

References

  1. 1.Trentin, G. (2009). Using a wiki to evaluate individual contribution to a collaborative learning project. Journal of Computer Assisted Learning, 25(1), 43–55. Link ↗
  2. 2.Viégas, F. B., Wattenberg, M., & Dave, K. (2004). Studying cooperation and conflict between authors with history flow visualizations. Proc. ACM CHI Conference on Human Factors in Computing Systems (CHI ’04), 575–582. Link ↗
  3. 3.Wang, D., Olson, J. S., Zhang, J., Nguyen, T., & Olson, G. M. (2015). DocuViz: Visualizing collaborative writing. Proc. ACM CHI Conference on Human Factors in Computing Systems (CHI ’15), 1865–1874. Link ↗
  4. 4.Hakimi, L., Eynon, R., & Murphy, V. A. (2021). The ethics of using digital trace data in education: A thematic review of the research landscape. Review of Educational Research, 91(5), 671–717. Link ↗