Stickymade

2026

Stickymade UX Case Study

While preparing customer orders at Stickymade, I kept seeing the same problems: low-resolution logos, screenshots used as artwork, unfinished files, and designs customers believed were “print-ready” but still needed work. Instead of treating these as isolated mistakes, I looked into why they were happening. What I found led me to rethink the ordering experience around something customers understand much better: what they actually have to work with.

Role

UX Designer (Independent Project)

Timeline

August 2026

Team

Independent Project

Platform

E-commerce / Web

Role

UX Designer (Independent Project)

Timeline

August 2026

Team

Independent Project

Platform

E-commerce / Web

Overview

What looked like a file problem was really an experience problem

At first, the issue seemed straightforward: customers were uploading poor-quality artwork.

But the more orders I reviewed, the clearer it became that the problem started earlier. Stickymade expected customers to understand print-production requirements that many of them had no reason to know.

Rather than adding more instructions, I explored how the ordering experience could identify what customers needed earlier and provide guidance only when it was useful.

The Opportunity

The goal was to catch preventable artwork issues before they reached production without adding unnecessary steps for customers who were already prepared.

Because the concept was not implemented, I focused on building a research-backed solution and defining how I would validate it before development.

Problem

Customers could complete an order without being ready for production

The existing experience relied on customers understanding terms like “print-ready artwork” and "vector artwork" to know whether their files met production requirements.

In practice, that often wasn't the case.

Customers submitted low-resolution logos, screenshots, photos of existing stickers, watermarked proofs, and files that still needed design changes.

From the customer's perspective, the order was complete. From the production side, the work was just beginning.

Research

I tracked real orders to understand what was actually going wrong

Rather than redesigning from assumptions, I documented incoming orders during my normal production workflow.

For seven working days, I tracked the problems that prevented orders from moving directly into production and the time required to resolve them.

I wasn't looking to prove a specific solution. I wanted to see which issues repeated often enough to point to a larger problem.

Research snapshot

55 orders observed

22 documented issues or interventions

125+ minutes of direct resolution time

That number only reflects time I could directly measure. It doesn't fully account for delayed orders, waiting on customers, repeated emails, phone calls, or the cost of switching between production and customer support.

What I learned

Low resolution was only a symptom

The individual problems varied, but the same underlying issue kept showing up.

Customers were being asked to classify their artwork using terminology they didn't always understand.

Someone might consider a screenshot “print-ready” because the design itself was finished. Another customer might know their file wasn't ideal but simply have nothing better available.

Both could end up in the same workflow as a customer with professionally prepared artwork.

Key Insight

Stickymade and its customers did not share the same definition of “print-ready.”

That changed the problem I was trying to solve.

Instead of asking:

How do I stop customers from uploading bad artwork?

I started asking:

How can the ordering experience understand what customers have before asking them to make production decisions?

Exploration

Designing around what customers have, not what they know

I explored several ways to improve the experience.

Guided vs. Express Checkout

A separate guided flow could help inexperienced customers while keeping the process fast for experienced ones.

The problem was self-selection: someone who needed help could still choose “Express” simply because it sounded faster.

Automated Artwork Validation

Automatic checks could catch objective issues such as low resolution or unsupported file dimensions.

But automation alone wouldn't help customers who simply didn't have better artwork.

Artwork-Readiness Routing

The strongest direction was to stop asking customers whether their artwork was “print-ready” and instead ask what they currently had.

The experience could then adapt based on their answer.

I worked through the logic before polishing the UI

I moved into low-fidelity wireframes to pressure-test the flow before focusing on visual design.

I looked at whether each step had a clear purpose, whether the language made sense without print knowledge, and what would happen when someone chose the wrong option.

I also wanted to make sure additional guidance for first-time customers didn't create unnecessary friction for people who already knew what they needed.

Solution

A guided ordering experience that adapts to the customer

The final concept moves the most important decisions earlier in the ordering journey.

Rather than expecting customers to understand print terminology, the experience first learns what they're working with and adjusts the amount of guidance from there.

Customers who need help get it earlier. Customers who are already prepared can keep moving.

Once a sticker is selected the customer is prompted with a choice to make sure a new customer doesn't struggle while a returning customer isn't slowed down.

A faster path for repeat customers

Returning customers shouldn't have to rebuild an order they already placed successfully.

The reorder flow allows them to find a previous order using:

  • Order number

  • Email address

  • Phone number

After confirming the correct order, they can reorder it immediately, make changes, or search for a different one.

This creates a faster experience based on what the customer is trying to accomplish rather than asking them to choose between a “beginner” and “expert” mode.

Catching problems before production

If the system identifies a possible file-quality issue, it doesn't simply reject the artwork.

Instead, it explains what may be wrong in plain language and gives the customer useful ways forward.

  • Upload a different file

  • Continue with the best file they have

  • Get help preparing the artwork

The goal isn't to stop every imperfect file from being uploaded. It's to stop imperfect files from entering the wrong workflow.

A guided ordering experience that adapts to the customer

The final concept moves the most important decisions earlier in the ordering journey.

Rather than expecting customers to understand print terminology, the experience first learns what they're working with and adjusts the amount of guidance from there.

The simplified file-upload experience.

One meaningful decision at a time

Once the artwork is handled, the customer moves through the remaining configuration in focused steps:

Size → Quantity → Finish → Production → Review

A progress indicator shows where they are in the process, while a persistent order summary keeps previous choices visible.

This gives customers enough context without asking them to process every option at once.

Reflection

The answer wasn't teaching customers more. It was asking them less.

If I would have pitched this for implementation, the most likely pushback would have been scope. The artwork-readiness routing touches checkout, customer support, and production simultaneously. A real team would probably want to ship the file-validation piece first and phase in the rest. I would have needed to make the case for why the routing logic mattered more than a faster technical fix.

The biggest lesson was simple:

Reducing user error doesn't always mean adding more instructions. Sometimes the better solution is removing a decision the user was never equipped to make.

Kyle Paeth

Product designer with a visual design background, focused on turning real user problems into simple, thoughtful experiences.

Contact

paethmedia@gmail.com

Kyle Paeth

Product designer with a visual design background, focused on turning real user problems into simple, thoughtful experiences.

Contact

paethmedia@gmail.com

Kyle Paeth

Product designer with a visual design background, focused on turning real user problems into simple, thoughtful experiences.

Contact

paethmedia@gmail.com