Sampling campaign request form

The problem
When our clients release new products, they want to find the right members from our 7.5M+ Influenster network to sample these new products, and then leave authentic reviews so that more people will be encouraged to purchase them. Previously, our clients were entering data for their Sampling campaigns into an Excel spreadsheet, and sending it to our admin team. This was slow and an archaic way of setting up the campaign, plus our admin team was struggling to keep track of all campaigns to be processed.
My role
I led this project, but had great support from the Product Manager. I carried out user research, designed the prototypes, and will be responsible for leading the user testing with selected clients.
Process
Due to a number of teams being involved in this project, there were various factors to consider. I collaborated on this project alongside the dedicated Product Manager.

User research

I spoke with different teams who are involved in the operations of Sampling, for example, those who process the campaigns, point of contact teams speaking directly with our customers, and those responsible for shipping clients' products if the client chooses not to do so themselves. These people were extremely knowledgeable in providing us with what should and should not be included in the form. There were a few logistical points we didn't consider.

I also spoke with several of our Sampling clients, who expressed what they would like in the Nomination Form. Having noted all of these points, I was able to better define what I needed to include.

Information architecture and user flows

Once all of the research was complete, I organised all of the data and feature suggestions into a logical flow. By doing this, it actually helped me to think of some capabilities we hadn't considered.
Outcome
Although there are different flows, here is the Retail Community flow for the Sampling Nomination form:

Campaign

Products: add products from catalog

Products: edit products in catalog

Audience

Fulfillment

Summary

Process

Internal research

Gathering feedback on the filters from Fullstory, Productboard, emails and relevant folders was important to do before beginning to re-design the filters.

I annotated all of the filters so that the feedback was collected in one place, and so that other relevant designers and engineers could better understand the design issues.

UX research

Fullstory

Users are rage clicking to get rid of pills instead of clicking 'clear all,' and that there is a lot of inconsistency with the copy across the filters (this has been influenced by individual teams making their own changes instead of using the Aperture Design System.)
Our enterprise clients are using many 'Saved filters': one is using 150 saved filters. This exemplified their importance
Users don't know if components are clickable or not, buttons aren't functioning properly, there are invisible overlays and there are broken elements

User interviews

I spoke with various product teams internally to gauge specific needs in relation to their product to ensure that we are incorporating all user needs into the filter as the Date and Product pickers are used across several products. I also carried our a number of user interviews with a mixture of enterprise and SMB clients.

Outcome

This project in still in flight, but I am working on high-fidelity prototypes that will be used for user testing.

I have been working with Client Success Managers to identify clients who would be keen to test the new filter design. I will ask clients to complete tasks in order to gauge if the filter is easy to use in order to complete complex tasks. I also plan to partner with a dedicated Aperture copywriter to ensure all copy is consistent and comprehensive across the filters.

Once user testing is complete and appropriate changes have been made, I will create design tokens and work with Engineering to build the filters.

Date picker

Product picker

Email or LinkedIn

Copyright © Emma Millar. All Rights Reserved.