AF
Back to work

Case study

Product Redesign Concept

A concept case study for improving activation, collaboration, and clarity.

Summary

This concept explores a mature-product redesign pattern for onboarding, activation, collaboration, empty states, error states, and measurable outcomes.

Product strategyOnboardingCollaborationUI systems

Role

Product designer, UI systems designer

Timeline

PLACEHOLDER: add concept exploration timeline

Type

Concept case study - no employment or affiliation claimed

Tools

Figma, Product heuristics, UX writing, Design systems

Users

  • New users trying to reach first value.
  • Collaborators joining an existing workspace.
  • Power users managing complex shared objects.

Goals

  • Reduce ambiguity during onboarding.
  • Make the first meaningful action more obvious.
  • Improve collaboration clarity and recovery from errors.
  • Define measurable product outcomes for each improvement.

Constraints

  • No affiliation with any existing company or product.
  • Concept work must not claim real business access or production impact.
  • UI changes should be plausible within a mature design system.

Context and problem

Mature products often accumulate friction in onboarding, empty states, collaboration flows, and error recovery.

A concept-only redesign inspired by patterns from productivity, video collaboration, creator tools, file sharing, and AI onboarding products.

Small UX improvements in activation and collaboration can improve comprehension, completion, and trust without redesigning an entire product.

Process

1

Friction audit

Identified high-leverage moments: onboarding, activation, empty states, collaboration handoff, and error recovery.

2

Outcome framing

Mapped each UX improvement to a measurable outcome such as activation, completion, or reduced support need.

3

System design

Created reusable states and microcopy patterns instead of one-off screens.

Key UX decisions

  • Turn empty states into guided next actions.
  • Make collaboration status visible before conflict happens.
  • Use error states that explain recovery, not blame.
  • Introduce AI onboarding only where it helps users understand the product.

UI direction

  • Mature SaaS-style interface with restrained hierarchy.
  • Reusable status chips, state panels, and action rows.
  • Microcopy focused on next action and expected outcome.

Interaction details

  • Onboarding checklist adapts to completed actions.
  • Collaboration state shows who owns the next step.
  • Error recovery offers one primary fix and one secondary path.

Accessibility considerations

  • Status and error states use text, icons, and ARIA-friendly structure.
  • Focus management is required for modal or guided flows.
  • Empty states include clear headings and native buttons.

Metrics to track

  • Hypothetical metric: activation rate from signup to first completed workflow.
  • Hypothetical metric: error recovery completion rate.
  • Hypothetical metric: collaboration invite acceptance and first action.

Outcome or expected impact

Expected impact: a clearer activation and collaboration experience. This is concept work and does not claim real production results.

Reflection

A redesign concept is strongest when it shows product judgment: what to change, what not to change, and how success would be measured.

Gallery placeholders

Placeholder product redesign concept showing activation flow.

Activation flow

Placeholder for onboarding and first-value flow.

Placeholder UI states for empty, error, and collaboration workflows.

State system

Placeholder for empty, error, and collaboration states.

Next project

Ergonomic Analytics Dashboard

A dashboard UX concept for translating XSens, Delsys, EMG, RULA, %MVC, and JASA data into clear ergonomic risk insight.

Continue reading