Designing the new cloud storage uploader
Background & context
Adjust clients use the cloud storage upload feature to automatically export their raw user data to their cloud storage provider of choice.
The problem
In the classic version (screenshots below), clients had to manually set this up by hand, using the help centre articles as a guide. See in the examples, there are no contextual help or prompts in the classic version to guide the user.
Users (especially from a non-technical background) felt a lack of confidence when attempting to create something so technical.
In addition, the original term was CSV upload. This is ambiguous and is unclear to the user what the feature is, what benefits the feature offers or why the user should use it.
Step 1 of the old version - note the lack of contextual help and general poor UX.
Step 2 of the old version - note the cognitive overload of technical information and lack of helpful copy.
My role
I was the sole UX writer in an agile team of developers, engineers, a QA engineer, a UX designer, a UX researcher and led by our product manager.
I was responsible for all copy in the user flow, testing copy. I used JIRA tickets and epics to keep a measure of my work.
Worked closely with the designer, giving and receiving feedback on copy and design decisions.
Led meetings with technical writers, product owners, product marketing and program managers to discuss terminology and potential changes to these terms.
Attended weekly planning sessions to provide updates on the copy.
Ensured all translations were requested, received and then pushed to production using Contentful, Smartling and liaising with the localisation team.
The solution
An entirely new UI and flow were created to replace the classic dashboard.
We designed a ‘guided setup’, whereby we walk the user through step-by-step and offer more contextual help such as tooltips.
In-line validation and error messages were incorporated.
Contextual help was incorporated to educate the user on why they require each part and where to find the necessary information.
Step 1 - notice the easily manageable chunks of information.
Step 2 - progressive reveal as the user moves through the flow.
Contextual help was added.
In-line validation was added.
Tool-tips were added.
How did we arrive at the solution?
Initially, I worked closely with the designer and researcher to identify user pain points.
Then the designer and I created some high-level wireframes in Miro.
After feedback and discussion with the researcher, engineering and the product manager, we designed more high-level wireframes in Figma.
We received design feedback from the VP of Product, and technical feedback from the developers and engineers. I also asked for feedback from the UX writing team in our weekly peer review sessions.
Once the Figma designs were ready, we then moved to user testing. We led moderated testing sessions with experienced Adjust clients. We gave them access to the prototypes and asked them to complete scenarios such as ‘add a Parameter’.
Some early prototypes are below:
An early version - note the change information hierarchy.
Another early version - this time with different terminology.
Another early version - note the change in copy in the sub-headers.
What challenges did I face?
The term CSV upload was outdated and didn’t reflect what the feature was.
I created the term Cloud storage upload instead. Because this was a feature name change, this had to go through the VP of Product as well as other stakeholders.
I had to make my case as to why I believed the name should be changed and why this new term is better. All stakeholders agreed with my choice.
What did I learn?
I learned to communicate and influence at an executive leadership level.