Treat user effort as high-value data.
Design systems to preserve time, thought, and intent embedded in user work.
Contents 4. System Behavior & Workflow Logic 6. Work Protection
How effort is preserved over time.
First, ask yourself
“Is user work protected in your system against interruption, failure, and error?”
Mission statement
Ensure users do not lose progress by safeguarding ongoing work.
Key heuristics Work Protection
- User time, thought, and intent must be treated as high-value data.
- Workflows must assume interruption and failure as normal conditions.
- Work must be saved automatically and continuously.
- Actions must preserve original work whenever possible.
- Permanent deletion must be unmistakable and intentional.
- Partial and intermediate states must be preserved throughout progression.
- Work must remain intact across sessions and devices.
- Users must perceive that their work is preserved.
- Preserved work must be restorable or reversible.
Executive brief
The system must protect user work under all reasonable conditions.
Core questions Work Protection
“Does the system protect user effort from loss?”
“Can work survive failures, interruptions, or mistakes?”
Focus areas
Continuity-first
“What happens to work if users leave, crash, or disconnect?”
“Can they safely stop and resume later?”
Scope-aware
“Which work is protected? Which is not?”
“When does protection start?”
Trust-aware
“Would users feel safe investing significant effort?”
“Does the system earn long-term trust?”
AI-aware
“Can automation destroy user work silently?”
“Is generated or inferred work equally protected?”
UX directives Work Protection
Design for interruption and failure by default.
Build resilience into workflows as a baseline condition.
Implement automatic and continuous saving.
Do not rely on manual save actions for data preservation.
Favor non-destructive workflows.
Design actions so original work remains recoverable.
Require explicit confirmation for destructive actions.
Make permanent deletion unmistakable and intentional.
Protect drafts and intermediate states.
Preserve partial work throughout task progression.
Ensure cross-session and cross-device continuity.
Maintain work integrity across time and environments.
Communicate protection status clearly.
Provide visible indicators that work is preserved.
Integrate recovery into protection systems.
Ensure preserved work can be restored or rolled back reliably.
Executive summary
- Work Protection treats user effort as high-value data, not disposable input.
- It preserves time and progress across interruption, failure, and transition.
- The system must default to automatic, continuous, and non-destructive preservation.
- Destructive actions must be explicit and recoverable wherever possible.
- Protection must extend across sessions, devices, and intermediate states.
- Work Protection succeeds when users trust that their effort is safe and their progress cannot be silently lost.
Success indicators
- User work is saved automatically and continuously.
- Drafts and partial work are preserved during tasks.
- Work remains intact across interruptions and session changes.
- Destructive actions require clear confirmation.
- Users can restore or recover previously saved work.
One-line summary
Before users invest effort, they must trust it will not be lost.