evidence EV-HANDOFF-2026-2A10
Unavailable coworkers block software-task information needs
Evidence Record
Evidence summary
Observation of 17 developers identified 21 information types. Design rationale, intended behavior, and causes of program state were often deferred; tasks stalled when the only source was an unavailable coworker.
Interpretation
A handoff artifact should expose rationale, intended behavior, current state, and unresolved causes rather than merely list files changed.
Limitations
One collocated organization and older tooling; the study does not test a handoff intervention.