Skip to content

Retail interface | Shipped product

Eddie Bauer: Confident Outdoor Shopping

I designed the path from storefront and product listing through product details, the shopping bag and checkout.

Retail interfaceStorefront · Listing filters · Product details
Eddie Bauer outdoor shopping experience

PROJECT AT A GLANCE

The essentials.

Design scope
Retail interface
Available views
Shopping bag · Checkout
Screen focus
Shipped interface
Design intent
A clear path from product choice to checkout
Skip to project details

KEY DESIGN DECISIONS

Product selection and checkout entry.

How I structured the journey from browsing to checkout.

01

Discovery to checkout

The retail flow runs from product discovery through to checkout entry.

02

Checkout groups

I split checkout into shipping fields, payment fields and the order summary, so each group reads on its own.

03

Product selection

Product detail brings imagery, variant choice and the purchase action into one view.

Each of these decisions shipped in Eddie Bauer.

Design
Question

How does product information carry from selection into the bag and checkout?

Project
Design Scope

I designed these areas of the product:

  • Storefront
  • Listing filters
  • Product details
  • Shopping bag

Shopping
Flow

How the shipped screens connect.

StorefrontListing filtersProduct detailsShopping bagCheckout

Retail Shopping Flows

Eddie Bauer seasonal shopping homepage
Storefront — Eddie Bauer screen
Product listing — Eddie Bauer screen
Product details — Eddie Bauer screen
Shopping bag — Eddie Bauer screen
Checkout — Eddie Bauer screen

Seasonal homepage

Discover outdoor products and seasonal collections.

01 / 06

FROM THE PROJECT FILES

Inside the shipped product

Screens from the shipped product. Values shown are sample data.

Product listing

Product listing — Eddie Bauer screen
The listing places filters beside product cards, so options and product attributes stay in view while shoppers browse. View full-size screen

Product details

Product details — Eddie Bauer screen
The detail view brings the product image, variant selection and purchase action together. View full-size screen

Checkout

Checkout — Eddie Bauer screen
Checkout separates shipping and payment entry from the order summary. View full-size screen

What I’d Change
Next

Looking back, I’d carry the selected variant more visibly from product detail into the bag and checkout, so size and colour never have to be re-checked along the way.

LEADERSHIP APPROACH · EXAMPLE SCENARIO

A deadline is fixed.
The scope needs judgment.

This is the approach I take when a release deadline is fixed. The situation below is an example scenario, not an account of this project; the decision record and critique structure show the method.

The situation

A commerce team is preparing a seasonal release. The commercial priority is to improve checkout; engineering capacity is constrained. Design sees a broader opportunity to improve product, sizing and pricing clarity. My job is to help the team choose a defensible first release.

COMMERCIAL LENS

Protect the release.

Focus investment where it can support purchase decisions before the seasonal window.

ENGINEERING LENS

Control delivery risk.

Prefer changes that fit existing components and can be tested and rolled back.

DESIGN LENS

Resolve uncertainty earlier.

Examine product information and sizing as well as the final checkout steps.

EXAMPLE DECISION RECORD

Agree on the question before the answer.

My part is to make the choice legible, preserve dissent and agree up front on what evidence would change the decision.

Decision to make
What customer-confidence problem can the first release responsibly address?
Option A · Narrow
Checkout copy and disclosure improvements. Smaller scope; upstream uncertainty remains.
Option B · Broad
Redesign discovery through checkout. Wider coverage; larger implementation and validation risk.
Proposed first slice
Review sizing and promotional disclosure in existing product-detail and checkout patterns. Confirm feasibility before committing scope.
Revisit when
Research points to a different source of uncertainty, implementation exceeds capacity, or a release guardrail deteriorates.

OWNERSHIP MODEL

Alignment needs a decision owner.

Product

Own release scope and the business decision. Record the accepted trade-off.

Design

Recommend the experience direction, explain alternatives and define interaction quality.

Engineering

Assess feasibility, dependencies and rollback. Identify delivery constraints early.

Research & analytics

Challenge assumptions, define measurement and distinguish findings from hypotheses.

DESIGNER DEVELOPMENT / CRITIQUE TEMPLATE

Build judgment,
not approval dependency.

This critique structure lets the designer own the recommendation while the reasoning stays open to challenge.

  1. Describe the decision.

    What must the customer understand or do here?

  2. Bring an alternative.

    What else could work, and which constraint changes the choice?

  3. Separate fact from assumption.

    What does the artifact show, and what still needs research?

  4. Own the next step.

    Make a recommendation, name the risk and propose the smallest useful test.

What I look for

A written decision record the whole team can point to, dissent captured rather than lost, and designers who arrive at critique with their own recommendation and an alternative.