Case Study — Jatango, LLC

From Alpha to Beta: Building a Live-Streaming Marketplace

How I established design operations from the ground up at an early-stage startup and led the product from its first wireframes to a market-ready beta launch.

18 mos Alpha → Beta
12+ Features Shipped
1st Design System
2 roles Design + PM Lead
Alpha screenshot Before
Beta screenshot After

Jatango

Signup

Next project showcase

Overview

The Challenge, My Role & the Impact

Jatango is a live-streaming marketplace that merges social commerce with multi-platform live selling: imagine Etsy meets TikTok, built around live streams. I joined as the company's first designer.

The Challenge

Early-stage startup. Zero design ops.

Jatango had no design system, a departing project manager, growing technical debt, and an ambitious beta deadline. The product needed structure without sacrificing velocity.

My Role

Lead Product Designer → Design + PM Hybrid

I was a solo designer building the design foundation from scratch, working with leadership to define product strategy, and serving as a cross-functional team lead bridging design, development, and business goals.

Impact

Key success metrics

  • Achieved month of month growth for 8 straight months following beta launch
  • Shipped 12 major features at launch
  • Reduced design-to-dev handoff time & dev-reworking by 20%

Foundations

Building Systems in Chaos

When I joined Jatango, the product had basic functionality: user registration, store creation, product uploads, and checkout. However, there was no design system, no component library, and live streaming was still handled externally through Facebook Live.

Design System Genesis

Before — Inconsistent UI
After — Unified Component Library

We were building the plane while flying it. I needed to create structure without slowing velocity.

In my first two months, I created Jatango's first comprehensive design system, establishing visual consistency and interaction patterns that became the foundation for all future development. This system enabled the dev team to build a component library that accelerated feature delivery by an estimated 20%. The system included a complete UI component library with interaction states, brand guidelines and visual language, accessibility standards and inclusive design principles, and documentation and usage guidelines for developers.

Guiding Framework

Design Principles

These principles guided every design decision and helped the team move quickly while maintaining quality.

01

Mobile-First in a Desktop World

Jatango's audience lives on their phones, so, even though the business decided to start with a web app, every feature was designed for mobile-first interaction, then adapted for larger screens. This was critical for a platform rooted in live streaming culture.

02

Consistency Over Novelty

In a fast-moving startup, a predictable and familiar interface builds user trust faster than flashy innovation. The design system ensured every interaction felt cohesive, intuitive, and easy to use.

03

Build for Scale

By relying on atomic design, every component and pattern was designed to be flexible enough to accommodate future growth from new features, new user types, and new platforms without requiring a redesign of the foundation.

Flagship Feature

Leading Through Complexity

A closer look at one of the flagship features I designed — from problem space to shipped solution.

Scheduling Chat: a chat-based, live show scheduling UI

Feature Deep Dive

User Pain Point

A main differentiator for Jatango is that an influencer and a store owner can go live together from two different locations on a dual live: the influencer brings the audience, the store brings the products. However, the main challenge was providing an easy way for the influencer and store owner to coordinate a time to go live and discuss what will be sold and the sales commission.

Business Constraint

We had to figure out a way to accommodate this coordination within Jatango so users didn’t have to rely on off-platform communication via text, phone, email, etc. Additionally, our CEO wanted to allow either party to initiate the scheduling flow.

Technical Limitation

Prior to this feature, Jatango lacked a pre-existing scheduling architecture and a means of in-app communication, leaving us with a blank slate but requiring us to start from scratch. On top of this, our dev team was stretched pretty thin, so we only had one frontend engineer available, with support from one backend engineer.

Exploration & Iteration

The Solution

Chat-based scheduling UI screenshot with annotations callouts pointing to key features and design decisions.
1

Redesigned the Shows page to make it easy to access and monitor new show requests

2

Allowed users to seemlessly create the show from within the chat once two to users settle on a date, time, and commission

3

Leading up to the show, both users can continue to chat, access show details, and see past shows, ensuring everything they need is all in one place

Outcomes

  • 100% of intra-user communication could now be handled in-app
  • I got to see patience pay off. I was confident from the outset that this chat-based UI was the best approach from both a user and a business perspective, and I just had to be patient and persistent in helping my boss reconsider his initial call.
  • I would have presented the chat design differently the first time around. I can’t help but think if I had done a better job with the initial presentation, we could have saved a lot of time from not having to go in a big circle.

Dual Roles

When the PM Left: Absorbing Dual Responsibilities

When our project manager departed mid-project, I stepped into the gap and began managing both design and project delivery, thus becoming both the product designer and product manager. This dual role gave me a 360° view of the product and allowed me to help save Jatango time by making more informed decisions for both the user and the business.

Design Activities

End-to-end feature design from concept to handoff

Design system maintenance and expansion

High-fidelity interactive prototyping

Annotating developer handoff docs

Stakeholder design presentations

PM Activities

Sprint planning and backlog prioritization

Writing user stories and acceptance criteria

Cross-functional team coordination

Product roadmap and timeline management

C-suite strategy alignment sessions

Wearing both hats made me a better designer. When you own the backlog and the pixels, you make smarter tradeoffs, and you can ship with conviction.

I wrote so many user stories that I felt my brain was rewiring to think in a given-when-then format
To help facilitate a smooth handoff, I would create a clean and organized Figma design file that I would annotate with notes, callouts, and visual details about the design

My Progress

From Solo Designer to Design Leader

A timeline of how design operations at Jatango evolved from ad-hoc practices to a structured, repeatable system.

Early Days — Months 1–2

Laying the Groundwork

  • Solo designer navigating ambiguous requirements.
  • Established initial relationships with leadership and the dev team.
  • Built the design system from scratch.
  • Ad-hoc communication and handoff.

Mid-Stage — Months 3–8

Building Rhythm

  • Structured design reviews with leadership.
  • Created a Figma-to-dev handoff system with annotated files and phased implementation plans.
  • Introduced role-playing exercises that helped stakeholders understand user perspectives and significantly reduced late-stage design changes.

Current State — Months 9–18

Integrated Workflow

  • Mature design operations with user story frameworks, acceptance criteria documentation, and a multimodal handoff process
  • Team consistently met sprint goals in the final four months before beta launch which was a marked improvement from earlier missed deadlines.

Process Win

Created design review process that reduced feedback cycles by 1–2 weeks for some features.

Handoff System

Built Figma-to-dev handoff using annotated files with phased implementation plans and detailed feature requirements.

Stakeholder Alignment

Developed role-playing exercises for C-suite meetings that improved decision-making speed and reduced late-stage design changes.

My Growth

What I Learned Building at Startup Speed

01

Designing Without a User Research Budget

With no dedicated research budget, I developed creative workarounds: role-playing exercises with stakeholders to simulate user perspectives, competitive analysis to benchmark interactions, and leveraging my cognitive science background to apply evidence-based design heuristics. These methods weren't a replacement for formal research, but they grounded decisions in something stronger than assumptions, that we were then able to validate with our betac testers.

02

Balancing Speed vs. Quality

Leadership preferred seeing high-fidelity interactive prototypes rather than traditional wireframes. Instead of fighting this preference, I adapted — developing a rapid prototyping workflow that turned this constraint into a strength. By going straight to high-fi, I shortened the feedback loop and got alignment faster, while the design system ensured consistency even at speed.

03

Building for Unknown Users

As a pre-launch product, we were designing for users we hadn't yet acquired. I de-risked decisions through competitive analysis of adjacent platforms (Whatnot, Poshmark, TikTok Shop), persona development informed by market research, and an iterative phased-launch strategy that prioritized flexibility — allowing us to adapt features quickly based on real user behavior post-launch.

My Impact

Impact

A summary of measurable outcomes across product, process, and business dimensions.

Product

12+

Major features shipped

Product

28

Design system components

Process

~20%

Faster feature delivery via component library

Process

1–2 wk

Feedback cycle reduction

Process

4 mos

Consistent sprint goal completion before launch

Business

Alpha → Beta launched on schedule

Business

115%

Active user growth post-beta

Business

8 mo

Consistent revenue growth post-beta

My Takeaways

What This Role Taught Me

On Hybrid Roles

Wearing Both Hats Made Me a Better Designer

Owning both design and product management gave me a deeper understanding of the tradeoffs between user needs, technical constraints, and business goals. I stopped designing in a vacuum and started designing with full context — which led to solutions that were both more elegant and more shippable.

On Startup Life

Constraints Breed Creativity

Building with limited resources — no research budget, no design team, a departing PM — forced creative problem-solving at every turn. I learned to treat constraints as design parameters rather than blockers, and developed a rapid, systematic approach to prototyping that I'll carry into any future role.

On Leadership

Influence Without Authority

Leading a cross-functional team as a designer — not a manager — taught me that influence comes from clarity, consistency, and care. Clear documentation, predictable processes, and genuine collaboration earned the trust needed to move fast without creating friction.

This experience reinforced my passion for building cohesive user experiences on solid foundations. I'm energized by the opportunity to apply these skills in environments where design leadership can drive both user satisfaction and business growth — particularly in climate tech and mission-driven products where thoughtful design can create real-world impact.