Dsync (One workspace. Zero context Loss)

01 Discover

I began by mapping the current design team landscape understanding how teams operate, what tools they rely on, and where their daily friction surfaces.

Research Approach

Interviews: 12 participants across designer, lead, and manager roles. 20-25 min semi-structured sessions, recorded with consent.
Quantitative Survey: 94 designers via LinkedIn, Slack, and UX forums. Measured pain frequency, severity, and weekly time lost per lifecycle stage.

8 Core Problems Identified

02 Define

The Define phase synthesized my research findings into clear opportunity areas, design principles, and “How Might We” statements that guided all subsequent design decisions

Problem Statement

Design teams lose critical context across the full design lifecycle because research, decisions, feedback, files, and bugs live in disconnected tools with no single source of truth.

Core problem

A unified workspace built exclusively for design teams that connects files, decisions, feedback, bugs, and progress tracking in one context-aware environment, so teams spend less time managing work and more time doing it.

How Might We Statements

Lifecycle continuity — How might we keep research, decisions, and files connected across every stage of the design lifecycle?

Context preservation — How might we preserve design rationale so it never has to be reconstructed from memory?

Feedback unification — How might we bring all feedback into a single version-linked thread regardless of where it originated?

Manager visibility — How might we give managers real-time project visibility without adding reporting burden to designers?

Onboarding — How might we let a new team member understand the full project history on their first day?

Bug traceability — How might we link every bug report directly to the design file and version it was built from?