Long absences need a difference view on return
Aliases: catch-up view · return view · absence awareness
What it is
A return-to-work difference view shows someone returning from leave, shift change, or extended absence what changed in objects, decisions, ownership, and risk relative to their last known state. It is not simply “recent activity”: recent does not mean relevant to what that person last understood.
Why it happens
The longer an absence, the more notifications and events accumulate, and the less certain a person is about where their understanding stopped. A reverse-chronological feed requires comparing every new item to an old mental model and can hide a pivotal change overwritten later. A personal checkpoint turns history into a before–after comparison while retaining the change path, restoring common ground and next action.
Studying it
- Paradigms: simulate different absence durations and compare timelines, summaries, and baseline difference views on reorientation tasks.
- Variables: absence length, baseline accuracy, object count, comprehension time, erroneous action, and follow-up questions.
- Methodological caution: last login is not necessarily last understanding; let people adjust or confirm the baseline.
Where it stops holding
Very short absence needs only a light prompt; a complex return package can add burden. If permissions changed or objects were deleted, show the gap rather than fabricating continuity.
Applying it
- At return, show object-level differences since confirmation, key decisions, ownership changes, and open issues.
- Let people skip irrelevant objects, set a new baseline, and drill from summary into versions and discussion context.
- Ask the owner or handoff partner to add a reason for high-impact changes.
- Verification: ask returning people to restate current state and complete their next task; record remaining information they must seek from colleagues.