Topics — What a work is about. Nucleation holds whatever reading the owner files here, whether or not an Anthology of the SOTA topic could also hold it; instruction for ML practice belongs to the anthology (ADR-048). The words are seeded from the clusters the reading-time triage of 2026-09-25 found, and grow by decision.
Design rationale — recording the reasoning behind a design or decision as it is made — issues, positions and arguments, options and criteria (IBIS, gIBIS, QOC and their successors) — and why such capture systems are or are not used: who bears the cost of capture and who gets the benefit, premature formalization, cognitive overhead, and the groupware adoption problems behind them (ADR-030).
1 of 1352 THEORY documents. Back to the full index.
| # | Title | Summary | Status |
|---|---|---|---|
| THEORY-311 v2 | Groupware that requires extra work from members who do not perceive a direct benefit from it, where that work is not made part of their job, is resisted or goes unused, and the applications that succeed in groups without a mandate give each user who does the work a benefit of their own | Grudin (1994), LIT-757, read in NOTE-835. The first of his eight challenges for groupware, argued from cases (meeting schedulers, voice annotation, project management) and from email’s success, where the sender does a little more work and also wants the message read. An argued review, not a measurement, and Grudin himself says that removing the disparity does not guarantee use. | Proposed |