video management solution.

In June 2021, LumApps acquired Novastream, a B2B video management platform. As video became a strategic priority, a new feature team — Play — was created to integrate Novastream’s core offering into the LumApps ecosystem.

I volunteered to join this team as the Product Designer at the start of the project. I later worked with another designer and led the entire design stream of the feature.

Due to a customer commitment, we had only 4 months to deliver a production-ready version. We relied on Novastream’s 10 years of product knowledge, as we had no time for early-stage user research.

One of the initial challenges was to onboard the former Novastream team into LumApps’ design processes and tooling, including the use of Figma and internal design rituals.

We needed to provide a native, scalable video management experience for LumApps customers — primarily communication teams managing corporate intranets. The existing Novastream interface wasn’t integrated into LumApps’ design system and lacked the UX consistency and modernity expected from a SaaS platform.

At the same time, LumApps’ component library wasn’t built for rich media workflows, which made it difficult to assemble a usable interface for video-specific use cases.

• Design and ship a fully integrated video management feature within 4 months.
• Make the editing workflow intuitive and efficient for non-technical users.
• Lay the groundwork for broader video functionalities.
• Achieve $1M in ARR from this feature within 12 months.

designing mvp.

During these four months, I was the only LumApps “veteran” in the team. My role went beyond producing interfaces: I also onboarded the former Novastream team to LumApps’ mindset and product practices.

Because of tight deadlines, the MVP had to be scoped, designed, developed, QA-tested, and released in just four months. We reused existing LumApps components wherever possible, even if they weren’t optimized for video workflows. Despite this constraint, the MVP was ambitious and introduced:

• A new permission level: video manager
• Video management interfaces: manager & editor
• Video consumption interfaces: gallery & detail page

This first version allowed users to:

• Upload a video file
• Edit key metadata (title, description, thumbnail)
• Manage visibility and permissions

While functionally complete, the interface was not fully tailored to the specifics of video content (subtitles, chapters, etc.), and early internal feedback confirmed usability and consistency issues.

iterations to version b.

In parallel with MVP development, we started prototyping a more refined Version B. The aim was to correct the MVP’s limitations and provide a more scalable, user-friendly foundation. Key improvements included:

• Reducing the video player footprint to give priority to editing actions
• Moving permissions to a dedicated tab for better discoverability
• Revising the translation system, laying the foundation for a broader content translation initiative

Design critiques with the internal design team ensured alignment with LumApps standards and scalability across other product areas.

‍

usability testing in production.

Unlike most projects, we did not run usability tests on MVP prototypes. Instead, testing happened directly in production once the MVP was live. These sessions were partly used to validate the MVP, but also to evaluate Version B prototypes and collect further needs.

The outcome confirmed strong interest in Version B and highlighted new requirements such as playlist creation and video gallery customization.

‍

• 100% of testers preferred Version B over the production version.
• The new layout was perceived as cleaner, more structured, and more professional.
• The video preview column struck a good balance between visibility and space efficiency.
• Navigation was judged clearer and more intuitive.
• The new placement of the translation button improved understanding, although its label needed clarification.

The interface of Version B established a new visual and structural direction, which progressively influenced other parts of the product.

• The feature reached $1M in ARR within 7 months, ahead of the 12-month target.
• Customers expressed satisfaction with the interface, noting that it felt more mature and reliable than the MVP.
• The design patterns introduced in Version B were adopted elsewhere in the product, contributing to a broader UI refresh.
• The translation workflow, initially addressed in this feature, led to a dedicated, cross-functional project I later led.

• Delivering fast under pressure is possible by reusing and adapting components — but anticipating and designing better solutions in parallel is essential for long-term scalability.
• Even with limited testing opportunities, structured sessions with real users can surface clear, actionable insights.
• Layout clarity and content prioritization strongly impact the perceived quality of a product.
• Cross-cutting UX challenges (like translation management) often emerge from focused projects and deserve dedicated ownership and follow-up.