Resuming

Definition

Resuming is a continuity-driven mental mode where users return to a partially completed task, process, or draft with the intention of picking up exactly where they left off. This assumes prior work has been saved and the user values seamless reentry. It is part of the ‘Continuity’ Mode family. Synonyms include: Continue, Pick Up, Return, Revisit, Re-engage, Draft Completion.

Contextual Relevance by Role

• Workers: Resume submissions, tasks, time-off, or training.
• Managers: Resume approvals, planning, feedback.
• HR Partners: Resume organizational updates, compensation reviews.
• Developers: Resume config, build, or integration flows.
• Finance Specialists: Resume financial entries, audits, or close processes.

Mental Model

• “I already started this — I want to finish it.”
• Continuity, not restart
• Preservation of temporal and spatial context
• Expectation of saved state and memory
• Efficiency through reduced redundancy

Emotional Context

• Focused and intentional
• Frustrated by rework or reset
• Relief when context is intact
• Satisfaction from quick reentry and completion
• Anxious when unsure if progress was saved

Behaviors

• Reopening saved drafts
• Jumping back to the last touched tab, step, or scroll position
• Continuing in-progress tasks from a dashboard or homepage
• Navigating via “Recently viewed” or “Pick up where you left off” cards
• Re-engaging with an unfinished flow, checklist, or form

Journey Stage

When in the user journey this intent typically occurs:

• Mid-task, interrupted or deferred
• Between sessions
• After switching modes or roles
• When returning from home or overview surfaces

Measuring Resumption Success Rate

How easily and effectively users can return to and complete partially finished flows, tasks, or content.

Quantitative Metrics

• Resume completion rate (vs forced restart rate)
• Time-to-resume (seconds from reentry to productive state)
• Draft drop-off rate
• Step recall accuracy
• Resume feature engagement

Qualitative Indicators

• User trust in saved progress
• Perceived fluidity of resumption
• Satisfaction with continuity

UX Domains

• Task Management
• Draft Workflows
• Continuity
• Workflow Automation
• Productivity Surfaces

Related Intents

• Executing
• Monitoring
• Reviewing
• Deep Work

Design Implications

1. Persist and Autosave Progress Continuously

Users shouldn’t need to manually save — systems should remember progress automatically. → Implement silent autosave, and visibly reassure users their work is being saved.

2. Use Resume Entry Points With Clarity

Make return paths visible and easy to spot, especially for high-value workflows. → Display resume cards, pinned tasks, or notifications highlighting “in progress” items.

3. Deep Link to Exact Return Location

Jump users back to the field, tab, scroll position, or step they left. → Avoid generic re-entry pages; land the user where their memory expects them to be.

4. Indicate Resumption Status Visually

Help users orient by showing how much was completed and what’s left. → Use progress bars, draft banners, badges, or checkmarks to communicate status.

5. Avoid Unnecessary Resets or Forced Restarts

If context is preserved, never assume the user wants to start over. → Offer options to resume or reset, not automatic restarts.

6. Prompt Resumption When Helpful, Not Intrusive

Subtle nudges can help — but timing matters. → Use contextual prompts like “You have an unfinished task,” preferably inline, not modal.

7. Enable Filters and Surfacing of In-Progress Items

Help users find unfinished work by status or activity. → Use “In progress only” toggles, task sorting, and home screen visibility.

UX Context Examples

• Draft forms
• Unfinished tasks in a dashboard
• “Continue where you left off” cards
• Multi-tab or multi-step flows
• Saved-but-not-submitted goals or reviews

Components and Patterns

• Resume Card
• Progress Indicator
• Draft Banner
• Smart List (filtered by “in progress”)
• Activity Feed
• Contextual Reminder (inline or persistent)

Do’s and Don’ts

Treating Reentry as a Fresh Start

• Users don’t want to repeat effort.
• Restarting flows can lead to drop-off and frustration.

Assuming Users Remember Context

• Memory decays.
• Help users recall where they were with visual cues and brief recaps if time has passed.

Overengineering Draft Recovery

• Draft handling should feel seamless.
• Avoid unnecessary steps like “load draft” modals unless absolutely necessary for safety.