Marketing Supply Chain Overhaul

Design, Research, Design Systems

Project Overview

The goal of this project was to understand the current user flow of the product they current have, their internal processes they go through, and then integrate those ideas into a singular product. This meaning that we'd be taking some items from their original product, but integrate new features into them, as well as give the overall product a facelift.

My Contributions

My role was to understand the current process that a user goes through, ideate, wireframe, then translate into high fidelity designs. This also included communicating with the client weekly, iterating designs, and developing a design system.

In the secondary phase of this project my role was to manage and organize the 2 other designers daily work, review it, and connect with the client to get feedback.

The Problem

At Marketing Supply Chain Company, they relied on multiple systems to process client mailing files, with our then-current process housed on a mainframe system, which was cumbersome and inefficient.

3 Month Discovery Phase

First we did a 3 month discovery phase trying to understand the constraints of the current processes. This included deep diving and iterating on through the processes below. process/user flow diagram to understand each step a user took. This also included creating a few personas based upon the users that we'd talked to. Lastly this consisted of attending many sessions with the client to understand their issues and what we could improve within the new product.
‍

User Interviews

Talking to some of the current and expected new users of the product we gained insights

Personas

After interviews we iterated and started finding out why users did the things they did

Flow Diagrams

Once personas and interviews were held, we were able to realize and understand how users did things and start making a flow diagram system to make sure the product worked for them in the future

Content - Elements Webflow Library - BRIX Templates

Some Images from the Discovery Process

_{A Continuation of 3 Months}

Wireframing Process

After getting a general understanding from the users of the system and processes, we began iterating and starting to get a general idea of the work needed to accomplish the clients ask. This involved a back and forth process with the key stakeholders of the design process including, C suite level individuals, Product Managers, Developers and other Designers on the team.

High Fidelity + Design System Curation

Once iterating and coming to a culmination we began producing high fidelity designs and creating a design system to pull from we we're really able to start to see things "come to life". Through writing requirements, and creating initial prototypes, this helped the client see our vision and theirs come together for their finalized product.

Example Components Created

Conclusions

This is a project that I was there from the beginning and then transitioned to be more of a managerial role assigning work to designers, and understanding the products next steps. This was my first longer interaction with a client, so I feel as though I was able to better integrate myself with the system and the product goals moving forward. It went through many changes, iterations, and growth, and I am so glad I got the opportunity to work on this. If I were to go back and change what I did differently, I would make sure the cadence for meetings would be set in a different manner, and make sure that as a team we were aligned with all items more cohesively.

This was also my first interaction with working with an offshore team, understanding and learning how to collaborate with different time zones although stressful proved to be very fruitful in my opinion. Understanding when is appropriate to meet vs being asynchronous in working, as well as different peoples type of how they work.

If I could go back and change anything, I'd love to re-evaluate our table structure and decisions around navigation as currently we don't have a ton of room for a lot of information going forward, and I'd like for the system to be flexible if that use case ever did come up.