2026

GoodSync for Business

A conceptual redesign of GoodSync's enterprise backup platform focused on scalable operations, multi-tenant management, and safer operational workflows.

Role

Senior Product Designer

Scope

Enterprise / B2B SaaS / Admin Tools / Infrastructure / Operational UX / Cross-platform

Key impact
  • Scalable backup operations for SMBs and MSPs
  • SMB + MSP Dual operational models
  • Cross-platform Windows, macOS, Linux, NAS
GoodSync for Business
SMB + MSPDual operational models
Cross-platformWindows, macOS, Linux, NAS
Interactive prototypeBuilt in React + TypeScript
Systems-first UXTemplates, rollback, reporting

GoodSync is a backup and synchronization platform used by both individual users and IT teams.

As the product expanded across SMB and MSP environments, operational complexity became increasingly difficult to manage at scale.

The project explored how backup operations, multi-tenant workflows, rollback systems, and reporting could evolve into a more scalable operational platform.

Designing for Scale

Traditional backup systems often become harder to manage as organizations grow.

The redesign introduced a layered operational model built around reusable templates, centralized propagation, and device collections.

Instead of configuring jobs individually, administrators could define reusable structures applied automatically across device fleets.

The platform architecture was reorganized into four connected layers:

Policies

Top-level intent — what should be backed up, where, and under what conditions.

Templates

Reusable configurations derived from policies, applied across device groups.

Device Collections

Groups of devices defined by rules, receiving templates automatically.

Jobs

Individual backup operations generated and managed through the layers above.

Operational Visibility

As the platform scaled, operational visibility became as important as configuration management.

The interface prioritized high-value signals over dashboard density: system health, blocked operations, failed jobs, and actions requiring attention.

Health states were simplified into clear operational categories: Healthy, Warning, and Critical.

Designing Safe Operational UX

Backup and synchronization systems operate on potentially destructive actions: overwriting files, deleting data, propagating changes, and restoring previous states.

The redesign introduced tiered confirmation patterns based on operational risk.

Rollback workflows became a central part of the exploration, supporting recovery, undo operations, and selective restoration flows.

The goal was reducing uncertainty during high-risk actions without slowing down experienced administrators.

Multi-tenant Operations

The platform supported two operational environments:

  • SMB teams managing a single organization
  • MSP operators managing multiple client organizations simultaneously

Instead of forcing both audiences into the same interface model, the redesign separated operational contexts while preserving a shared system architecture.

The MSP layer introduced client switching, fleet-wide monitoring, shared licensing, and cross-client reporting.

Storage & File Experience

The project also explored a browser-based file management experience with previews, drag-and-drop, keyboard navigation, responsive layouts, and multiple viewing modes.

Unlike static mockups, the prototype was implemented as a fully interactive React application with responsive behavior and real media previews.

The goal was making backup workflows feel more approachable without sacrificing power-user functionality.

Extending the Ecosystem

The work expanded into onboarding, positioning, deployment guidance, and public-facing information architecture.

The redesign introduced clearer separation between business and consumer audiences while maintaining a unified product identity.

Results

Outcome

Although conceptual, the project became a large-scale exploration of scalable backup operations for SMB and MSP environments.

The work clarified:

  • Platform architecture
  • Operational workflows
  • Rollback and recovery UX
  • Multi-tenant management patterns
  • Licensing visibility
  • Reporting structures
  • Product positioning

Takeaways

What I Took From This Project

1

Operational UX requires different priorities than consumer UX.

2

Visibility matters more than dashboard density.

3

Scaling systems means reducing operational surface area.

4

MSP workflows should not inherit SMB mental models directly.

5

Safety systems work best when they explain consequences clearly.

6

Product architecture and information architecture strongly influence each other.