Home
About
contact

PlugWorld is a leading print-on-demand provider with minimal digital presence. This case study highlights my ability to work within tight project restraints and limited direction.

SaaS Solutions
Product Mapping

PlugWorld

2023
Project brief
PlugWorld is unique in that our client had little-to-no digital presence before onboarding and a very open-minded approach to the solutions we could offer. The only clear goal was to create a SaaS product that could maximize efficiency internally, and eventually boost revenue through white-labeling. My responsibility was spearheading user requirements, UX design, and plans for product development.
timeframe
3 months
industry
Ecommerce + SaaS
case study

the problem

The initial goal for PlugWorld was to solve business inefficiencies with digital tools. Through an initial discovery phase, we uncovered that clients were ordering through email and the entire process from order to payment was taking as long as 2 weeks. Our goal was to reduce this to 2-3 business days with the initial MVP. The first phase would be an online product order and quote system for custom print products. We would also road map for the following phases. My responsibility was designing the screens for the MVP and building out user requirements and a road map for features in the following phases in line with project constraints such as timeline, budget, and fundraising.

design

Building the MVP was broken up into a few phases:

‍

  • Category definition
  • Wireframing
  • Validation
  • Component system
  • Interface design
  • More validation

‍

Category definition was the most intensive piece for the UX strategy. I had to work with the client to understand the print-on-demand industry better so that our order form would surface the logic behind possible printing combinations in an easily digestible format to users. In creating our quote system I had to balance user needs of simplicity and customizability and our stakeholder's desire to save time spent on manual business operations. Making sure categories were clearly defined helped create a funnel system for getting to the core of what a user was trying to order. For example, instead of giving users an overwhelming catalog of 800+ T-shirt brands, I broke down T-shirts into conditions including:

‍

  • Neckline
  • Material
  • Sleeve length, and
  • Hem

‍

In terms of interface design, I found a way to make pre-existing brand colors work in an accessible way despite limited accessible color combinations across neon green, white, black.

approach

I mapped the product journey from user requirements for the MVP to feature roll outs for the following phases. When mapping out the product journey I considered the complexity of each feature as well as sequence. I wanted to ensure that we built foundational features first. I also sorted feature builds into three phases with three levels of priority based on value it would bring to the user. I did this for each phase to set us up for an Agile approach to building. Upon completing the roadmap, I met with our client to explain the reasoning for selecting each feature and how it translates to the bottom line.

‍

Key phases:

‍

  • Minimum Viable Product (MVP): Basic order form - Account creation - Vendor interest collection
  • Integrated Quote: Vendor storefronts - More seamless process
  • Automated Process: Inventory and quote management - Logic-based matching

key iterations + design choices

I used design principles and feedback to improve the user journey while designing the MVP screens. Some of the key choices I made include:

‍

  • Utilizing a "pizza tracker" or "stepper" at the top to allow the user to know how far along they are in the order process. This keeps users focused and motivated to complete the process.
  • Providing "info bubbles" on print methods that may be unfamiliar for the user. This keeps the user in the order form so that they do not need to go Google info that we could instead provide for them.
  • Highlighting the area of focus and hiding elements that do not apply to the selections they've made. This eliminates confusion and guides the user's attention to where it needs to go.
  • Building in logic based on conditions to contain and limit any potential user error. For example: only providing enough "file upload" slots for the number of print areas selected; not listing "print on sleeve" for tank tops, etc.

‍

VIEW IN FIGMA
NExt
project
contact
Let's
Talk      
Sitemap
homeaboutcontact
social
BehancelinkedindribbbleMedium
©
2023