Frame.io V4

The Context

The challenge: Frame.io was rebuilding the entire platform from the ground up (V4). I led the only 2 teams shipping in V4 for the first few months:

• Video player infrastructure
• Commenting system
• Navigation
• Asset grid
• Vapor design system

The Constraints:

• Everything we built, everyone else would build on top of
• One year timeline to ship → Then Adobe acquired us for $1.2B and compressed the timeline
• Had to rebuild on V3 backend (slow) while maintaining 60fps performance
• Millions of existing V3 users with established workflows

The Constraint: Basecamp process - one cycle to ship anything, sometimes less

The Executive Dynamic

Weekly CEO Product Reviews:

• Every feature decision that changed V4 from V3 went through Emery (CEO)
• Emery wanted every detail thought through before presentation (pixel perfect)

Uncompromising Quality Bar:

• 60fps, zero dropped frames, zero millisecond load times
• If it didn't pass FluidUI principles, it came back
• No shortcuts, no "we'll fix it later"
• Believed in performance first, high-fi, no low-fi

The tension:

• Emery's vision: Modern, fluid, performant future
• Reality: Millions of V3 users with muscle memory
• Technical constraint: Rebuilding on V3 backend that was slow

Cross-Functional Complexity

I wasn't just managing my teams - I was the central coordination point:

Stakeholders:

VP Design VP Product Engineering leads Research Media Services team Mobile team All other product teams building on V4 foundation

Every decision had ripple effects:

• Example: Design wanted gradients on all cards for visual polish
• Challenge: Support thousands of cards loading with gradients without performance hits
• Solution: Had to architect frontend to handle visual richness at scale
• Result: Maintained 60fps while achieving design vision

My role: Translator between Emery's vision, team execution constraints, and V3 user workflows

How I Aligned Everyone

Weekly preparation with Emery:

• Came prepared with clear rationale for every proposal
• Learned intimately what he cared about - framed proposals around his priorities
• When we disagreed: brought V3 user behavior data, talked through perspectives until found alignment

Team coordination:

• Tight documentation so all teams had clarity on what we were building
• Clear process for my core teams
• Regular check-ins across all dependent teams

Key insight: Understanding what Emery valued deeply (performance, fluidity, user workflows) allowed me to propose solutions he'd accept instead of getting sent back

The Impact

Business outcomes:

• Shipped V4 on accelerated timeline during Adobe acquisition
• Won NAB Product of the Year 2024
• Set foundation and standards for entire V4 platform

Technical outcomes:

• Video player: Reduced time-to-first-frame from 200ms → 20ms (10x improvement)
• Commenting system: Complete rebuild shipped and adopted across all Adobe suite
• Navigation: New panel-based architecture enabling faster feature development
• Vapor design system: Foundation for consistent V4 experience - all components 60 fps/100ms

Team outcomes:

• Established quality bar that other teams followed
• Created reusable infrastructure that accelerated downstream development
• Proved platform work could ship fast without compromising quality