Collaboo is a cloud-based media collaboration platform designed to streamline communication between producers, clients, and stakeholders during content review and editing.
Role
UX/UI Designer · End-to-End Design
Scope:
Full-cycle product design: discovery, UX strategy, system architecture, interface design, validation
Stage:
Early-stage startup under NDA - 0→1 product definition
Timeline:
2020
Problem Statement
A video producer collaborating with multiple stakeholders struggles to collect structured feedback, compare editing versions, and manage approvals in real time when using fragmented tools across devices. In distributed production environments, this leads to miscommunication, delayed approvals, redundant revisions, and increased production costs.
Strategic Product Vision
To create a seamless cross-platform collaboration layer that:
• enables structured feedback directly on media
• allows real-time version comparison
• reduces approval cycles
• centralizes communication
• supports remote-first production workflows
The mobile application was positioned not as a simplified viewer, but as a strategic extension of the desktop ecosystem.

My Role & Ownership
As a Senior UX/UI Designer, I owned the design strategy and execution end to end:
• benchmarking competitors and market trends to set the design direction
• presenting several design options and agreeing the direction with the manager, business analyst and stakeholders
• translating systemic problems into structured UX architecture
• designing information hierarchy and decision flows
• estimating how long each design task would take, so the manager could plan the work
• delivering cross-platform interface design
I took the project from competitor research to the final interface.

Research & Strategic Insights
The research phase included:
Key insights:
Feedback was scattered across emails, chats, and calls.We introduced in-context annotations directly on video frames.
Reviewers had to switch between files to compare versions.We designed side-by-side comparison and timeline-based switching.
Mobile users mainly needed to review content, not edit it.We prioritized clear playback and feedback tools over advanced editing features.
Approval delays increased production costs.We added clear status tracking and approval indicators.

Key Design Decisions & Trade-offs
Mobile-First Adaptation
Rather than replicating desktop complexity, the mobile app focused on high-frequency actions.
Trade-off: advanced editing features were excluded to maintain clarity and performance.
Structured Feedback System
Instead of free-form comments, feedback was attached to specific timestamps.
Trade-off: increased system logic complexity for higher workflow clarity.
Version Comparison Optimization
Designed for rapid switching with minimal cognitive load.
Trade-off: reduced customization options in favor of speed.
Constraints
• Fixed one-year timeline
• Dependency on existing desktop architecture
• Technical constraints of video streaming on mobile
• Limited quantitative analytics during early phase
Design decisions were made balancing technical feasibility and user workflow efficiency.
Outcome & Design Goals
I designed a cross-platform collaboration system for structured real-time feedback, mobile access and a simpler approval process.
Design goals:
• reduce feedback fragmentation
• shorten approval cycles
• reduce redundant video revisions
• increase collaboration transparency
• improve production efficiency
The aim was to make collaboration work on any device.
Delivered: a mobile review app: comments pinned to video frames, side-by-side version comparison, timeline-based switching and clear approval status.
Not tested: no usability tests were run and no data was collected, so I cannot say whether these goals were reached.
What I would track: time from first upload to final approval, and number of revision rounds per video.
Collaboration
Product Owner, Manager, and UX/UI Designer (me).
Key Learnings & Reflection
This project reinforced my ability to design within technical ecosystems and extend products strategically across platforms.
Key learnings:
• Platform consistency requires architectural thinking
• Mobile is not a smaller desktop — it requires behavioral prioritization
• Collaboration products succeed when workflow friction is reduced
• Enterprise workflows demand clarity over feature richness
This project strengthened my transition toward systems-level product design.




