ShipStation

Design Process

Discovery

I started by building a shared understanding of where merchants were losing confidence on the path to first label. I aligned across multiple inputs:

• Funnel and core action analysis to identify where trial users slowed down or stopped — tracking Trial Signup → Store Connection → First Order → First Print → Credit Card Entry as the primary conversion spine
• Support and Customer Success themes to understand which setup moments were generating the most tickets and hand-holding
• Qualitative user interviews (14 sessions covering Signup → Progressive Disclosure → Homepage) to observe real-world confusion, hesitation, and unmet expectations
• Competitive benchmarking against Veeqo, Shippo, Pirate Ship, EasyShip, and ShipHero to map how competitors reduce steps to a first label purchase

What came back was consistent: merchants weren't confused about whether to use ShipStation, they were confused about where to start and what the product was designed to do. User quotes from research made it human:

"I had thought I'd have it up and running faster." "I finally got a customer support to come in and they got it done in ten minutes. That's what we should have done from the beginning."

The decision I led: stop trying to teach everything upfront. Align onboarding around the minimum required to ship, with deeper configuration handled progressively after first-label success.

Tradeoff I named: reducing early flexibility risked feeling restrictive, especially for experienced merchants. We accepted that tradeoff deliberately, with a plan to reintroduce flexibility after the activation milestone was reached.

‍

Defining the Structure

The most important inflection point in this project wasn't a design decision, it was a strategic one, and navigating it was where my leadership mattered most.

What changed: Midway through the initiative, executive leadership transitioned. Where the previous CPO had shaped a more self-directed onboarding model, multiple entry points, flexible configuration, user autonomy from the start, the new CPO reframed the direction: elevate Rate Shopper as a strategic differentiator, reduce steps, create teaching moments, and move merchants to first-label success faster.

The concept changed. The mental model changed. The entry point changed. Feature exposure timing changed.

How I led through it: I didn't restart the work. I used what research had already proven, merchants were overwhelmed, uncertain where to start, and needed clearer "next right step" guidance, and mapped those findings to the new strategic direction. The friction was the same. The solution now had a sharper frame.

I aligned the team around a single design principle:

Reduce early branching to lower cognitive load, then reintroduce flexibility once merchants have momentum.

That became the architecture for the new FTU system:

1. Homepage New merchants land on the homepage first. I structured the hierarchy and messaging to make the “next right step” obvious and reduce wandering.

2. Setup Wizard The Wizard became the primary path for gathering critical setup information through clear, sequential steps:

1. Add Ship From location
2. Connect store(s)
3. Add a payment method
4. Optional: Inventory setup
5. Optional: Returns setup

3. To-Do I helped shape a “do later” model where optional tasks aren’t forced into the core onboarding path. Deferred items are captured and surfaced as To-Do tasks, helping merchants continue configuration over time without blocking early success.

Tradeoff: guiding users step-by-step increases completion and clarity, but requires careful “skip/resume/do later” handling so experienced users don’t feel trapped.

‍

Wireframes

In low fidelity, I validated the connected system: Homepage → Wizard → To-Do — before committing to UI direction.

My focus in wireframes was on three structural questions:

• Wizard: what are the minimum required steps, and how do we handle skip, resume, and "do later" without creating confusion?
• Homepage: how do we establish hierarchy that prioritizes action over passive resources, especially on first login?
• To-Do: how do deferred tasks get surfaced, completed, and dismissed without creating guilt-driven checklists?

Solutions I considered and why I chose the Wizard approach:

A full-page linear onboarding flow was faster to build but required merchants to complete everything before reaching any value. A highly flexible self-directed model preserved autonomy but reproduced the same "where do I start?" confusion we were solving for. The Wizard approach, structured enough to guide, flexible enough to skip, was the right balance given the research and the strategic direction.

‍

UI Design

With structure validated, I moved into high-fidelity UI with three clear priorities:

1. Homepage: action-first, scannable from top I designed the hierarchy so that new merchants see their most important next step immediately, not a welcome banner, not a resource feed, not a list of features. The setup prompt is primary. Everything else is secondary.

2. Wizard: lightweight, not bureaucratic Teaching moments are short and contextual. Progress is visible. Each step has a clear purpose, a clear completion state, and a clear path forward. I reduced copy at every iteration, consistently advocating for less instruction and more confidence-building through the interface itself.

3. To-Do: optional but purposeful Tasks are framed around value ("Set up your label layout so every shipment looks professional") rather than completion anxiety. Merchants can remove or dismiss tasks. The model is designed to pull people forward, not nag them.

The tradeoff I held throughout: simplification vs. platform depth. ShipStation is a powerful tool. I consistently pushed to protect the first-time experience from that complexity without hiding it from users who were ready for it.

‍