Scaling supply in collaboration with customers at Newsflare

Product architecture • Experience design • User research

Overview

I led the end-to-end redesign of Newsflare’s video ingestion systems, unifying manual and automated contributor journeys. From identifying partner friction to defining a new ingestion model, I launched a fully automated MRSS pipeline for content partners, a first for the company, alongside a redesigned, mobile-first upload experience for on-the-ground contributors.

Involvement

  • What: Project and design lead

  • When: ~3 month duration

  • With: Sketch, Trello, Google Analytics

Impact

+50%

Increase in median monthly uploads from professional contributors (Chasers)

+200%

Increase in uploads from Content Partners after adopting the newly built pipeline.

0 → 1

Conceived from a blank slate, validated with partners, scoped across engineering and product, and delivered as a new cornerstone of Newsflare’s content platform.

The Challenge

Newsflare is a video marketplace connecting public filmers to media buyers across news, entertainment, and advertising. But while demand was strong, the upload experience couldn’t scale, especially for high-value contributors like Content Partners and professional filmers (Chasers).

Uploads were slow, fragmented, and manual. As both Design Lead and Product Manager, I was tasked with reimagining this journey from the ground up to scale contribution, retain high-value users, and future-proof the upload experience.

To summarise:

  1. Fragmented architecture: Multiple upload flows with duplicated tech debt made iteration nearly impossible.

  2. Mobile-first audience, desktop-first design: 90% of uploads came from mobile, yet the experience was not optimised.

  3. Zero feedback loops: Filmers described uploading as “throwing videos into a black hole.”

  4. Lack of product-market fit clarity: Newsflare had never defined core filmer segments or how their needs differed.

Flowchart diagram showing a website content structure with pages labeled Guest Homepage and Mobile App Upload at the top, followed by sub-pages for Main Upload, Video Brief, Consent Form, Upload (Legacy/China), and Upload Widget Instances.

Practically speaking there were five upload processes when the work began. These generated an incredible amount of inconsistency and tech-debt.

The Approach

Early on their were a few crucial opportunities that I wanted to make the most of:

  1. Scale video ingestion from both manual and automated sources

  2. Prioritise high-value filmer types

  3. Consolidate and modernise the upload journey

  4. Build a flexible architecture that could adapt across verticals and ingestion points

We began by speaking directly with our users—through interviews, focus groups, surveys, and buttressing the insights that came out of these through a review our platform analytics informed by the feedback we got from our qualitative research.

A line graph showing data trends from January 25 to May 4, with fluctuations in values over time.

I started recording sentiments of users regularly uploading video to the platform in addition to a review of platform analytics.

Interior room with a woman standing next to a wall covered in colorful sticky notes and printed papers, some arranged in a grid pattern. She is smiling and making a hand gesture. There are kitchen items on a counter and a staircase visible in the background.

As part of this I gathered perspectives on customer attitudes towards submitting video to Newsflare, both in group settings and one-on-one interviews.

Doing this we identified four filmer archetypes:

  • Primary need: Opportunistic earnings

    Upload volume: Low

  • Primary need: Reliable income

    Upload volume: High

  • Primary need: Audience and platform growth

    Upload volume: Moderate

  • Primary need: Sales and syndication

    Upload volume: Very high

I then ran a product-market fit survey across each segment to seek out if any segment had a >40% PMF threshold. When I did this, we realised that not only were Chasers and Content Partners disproportionately valuable, but they were also really sold on the value of Newsflare. It turned out chasers in particular were key to Newsflare securing a defensible supply base.

A stacked bar chart showing the percentage distribution of member types, content types, and saleables among users, grouped into categories: Member Types, Count Videos, and Saleables, with percentages for Creator, Chaser, and Chancer.

We then summarised comments from key customer segments who responded positively to the PMF surveys we sent out to the user base.

A survey titled 'Would be very disappointed if Newsflare disappeared' with multiple sections and questions about the benefits, improvements, and feedback regarding Newsflare.

“I like to shoot proper footage, interviews with good audio, etc, sometimes A & B roll, etc. The effort that goes into that can feel wasted when, for the same price, someone’s wonky phone footage that’s carelessly shot gets sold simply because it’s first past the post.”

Newsflare Chaser

Solution

I then oversaw the end-to-end redesign of the upload experience for both Chasers (manual) and Content Partners (automated), two tracks running in parallel, but each requiring a fundamentally different strategy.

Solution 1: MRSS Uploads for Content Partners

Challenge

Partners wanted to upload thousands of videos but lacked the time or UI to do so.

Iteration

Initial UI prototypes for scale upload failed. We went back to user interviews, and discovered many partners already used MRSS feeds internally. This was the breakthrough.

A very early prototype design, not finalised.

Screenshot of a video upload webpage with a list of video files, a map of London, and options for video details, categorization, and publishing.

Implementation

I designed and launched a new ingestion architecture that scraped MRSS feeds and imported video libraries directly into Newsflare. I prototyped it alongside a single partner, then scaled it across our supply pipeline.

Flowchart diagram depicting content partner MRSS upload workflow with steps, decision points, and actions.

The first, very basic, flow I sketched out for the MRSS Feed.

A stacked bar chart showing the number of news articles uploaded by different partners over time. The x-axis represents time, and the y-axis represents the count of articles, with various colored segments indicating different partners.

The jump in uploads reflects the impact the MRSS Feed release had on video intake from Content Partners.

Impact

  • Order-of-magnitude scale: Enabled bulk ingestion without human intervention.

  • Became the cornerstone of supply: Adopted as the primary supply strategy for the following year.

  • New partners onboarded: Lowered friction dramatically, opening doors to contributors previously deterred by manual uploads.

  • Industry edge: No other competitor offered this kind of automated syndication feed at the time.

Solution 2: Redesigning Video Upload for Chasers

Challenge

Chasers contributed ~35% of saleable video but were hampered by friction, repetition, and lack of feedback.

Tests & Experiments

I ran multiple iterative experiments to optimise the existing experience, reducing friction and increase clarity, including:

  • Strength indicators based on title quality

  • Auto-tagging based on metadata

  • Input presets for mobile

  • Reusable fields across uploads

  • Language simplification for EASL speakers

This multivariate test produced several variants that outperformed the control, revealing the levers that mattered most and shaping the next round of experiments.

A flowchart diagram with multiple steps and decision points, utilizing color-coded shapes and lines, with some text labels and instructions, related to a process or system overview.
Computer screen displaying code related to a YouTube video description of a snake rescue in Mysore, India, with details like video URL, title, description, keywords, and thumbnail.

The initial MRSS Feed from the Content Partner I worked with to prototype the initial upload feed.

Screenshot of a data analysis dashboard showing experiment data with conversion rates, probability to beat original, and modeled conversion rate over time, including a line graph of modeled conversion rates from February 19, 2022, to March 7, 2022.

We also redesigned the page mobile-first, chunking inputs, removing redundant features, and creating pre-upload and post-upload experiences to bookend the journey with clarity and encouragement.

A mobile app screen with a scenic coastal background, showing a call to action for uploading videos to a newsflare platform, with a yellow button labeled 'Upload a video now.'

Flow Mapping

I then mapped the multiple upload and post-processing journeys to consolidate all entry points and reduce duplication. Pushed toward a single injectable upload instance across the platform, modular, flexible, and maintainable.

This massively cut down technical debt and increased the operational effectiveness of the platform with a corresponding increase in median monthly uploads from key customer segments.

Revised default upload flow

Consolidated post-upload flow

Screen displaying a video upload progress at 64%, with a circular progress bar, file details, and a video link.
Flowchart illustrating the upload process for a contributor on a platform, including steps like navigating to the upload page, specifying file details, uploading video, and confirmation of approval.

Future Opportunities

During testing, we uncovered a critical barrier: Chasers filmed more than they uploaded due to repetitive metadata entry on mobile.

To solve this, I prototyped a one-to-many model: allowing multiple videos to share a single metadata set. This experiment led to a 7x increase in uploads during testing.

This unlocked multiple future growth avenues:

  1. Publishing spread across sessions, apps, and devices

  2. Automation and bots to handle content submissions on 3rd party apps popular with key filmer segments like Telegram.

  3. Varied metadata requirements based on category/location

  4. Abandoned upload recovery (similar to e-comm cart recovery)

  5. Timeline-style uploads for multiple videos depicting a single event.

Confirmation screen from a mobile app showing a message that a video has been uploaded successfully, with a rocket icon, and a yellow button labeled 'Upload video'.

Revised outboud/consent form flow

Flowchart diagram illustrating supply process steps, decision points, and actions for video review, tagging, and queue management in a content platform.

The Outcome

The changes led to sizeable quantitative, operational, and attitudinal gains for Newsflare. These included:

50% increase in monthly uploads from Chasers.
(Median. 2.4 → 3.6)

>200% Increase in monthly uploads from Content Partners.

This radically improved the upload experience for both the business and our suppliers. Dramatically increasing the amount of saleable video now available to be passed on to buyers.

We also had clear avenues to explore how to further scale video supply amongst our core, non-Partner, suppliers, thanks to earlier experiments.

Improving the supply of Chaser video was strategically crucial to scaling a defensible supply base. Whilst we relied disproportionately on Content Partners, the loss of even one was always a big blow. Continuing to invest in improving the Chaser experience, therefore, a clear natural next step.

What I learned

  • Product architecture reflects product strategy: How you structure ingestion shapes your entire value chain.

  • Scaling supply requires segmentation: Treating all uploaders the same was holding Newsflare back.

  • Automating value creation isn’t a nice-to-have; it’s essential when operating a media marketplace at scale.

Consistent 8+/10 CSAT scores in usability testing.

Collapsed 5 distinct user journeys, each with its own upload funnel, into a single experience, reducing technical overheads and increasing operational efficiency.