Product Design · Brand and Packaging · 2010 to 2016

Spiderz

He wrote the specification himself. It was better than anything I would have written.

Spiderz

At a glance

The problem
In January 2012 a competitor let you color a batting glove in before you bought it. My client sold gloves and didn’t have that.
My role
I designed the glove builder and built it by hand, as stacked images with no Flash, to a specification the client wrote himself. The packaging and the retail program around it were mine too, and I drew the logos for production.
What I did
Every view is a stack of images, so picking a color swaps one file and nothing’s redrawn. When checkout couldn’t carry the order, I replaced it with a quote request.
What changed
42 layers stacked live, 691 files drawn, and the builder still runs. A competitor shipped the same idea while I was still finishing the second generation.

On a Saturday evening in January 2012, a client pasted a competitor’s website into a chat window and asked me a question. He sold batting gloves. The competitor had a tool that let you color a glove in before you bought it, and he did not.

This is a custom glove modification tool, how much work to make something similar for both our batting gloves and a fielding glove? … figured, but just wanted you to know what the main goal would be….so if a team wanted to order custom colors, they could play around with a simulator on the website, and then find their combo and order

The client, January 28, 2012

That last sentence is the entire brief and it is better than anything I would have written. A team cannot picture their colors. Let them play until they find the combination, and then let them order it.

Thirty-four minutes later I sent him a link to a first attempt. He looked at it and told me I had the scope wrong: he did not need one image that changed color, he needed every area of the glove to change independently. That correction is the whole architecture, and it came from him in the first hour.

8colorable areas
18colors in each
42image layers stacked live
691layer files drawn
4 yrsone constraint took to solve

Counted from the surviving build and its correspondence

My role: I designed it and I built it. The client wrote the specification, and he wrote it well. The packaging and the retail program around it were mine too, and I drew the logos for production. That work had been running since 2010.

He wrote the spec himself

Five weeks after the first sketch, with another job of mine running late, he put it in writing that he was considering somebody else. I did not start coding faster. I asked him for a requirements document, because what I could not guess was which parts of a glove a glove person considers separate.

Four days later he sent one. Three views of the fielding glove, ten labeled areas, and a note that not every area is visible from every angle. He had gone through the photographs and lettered the regions himself. A second document followed for the batting glove: seven areas, two views, and restrictions on which colors were available where.

That is a client doing information architecture. My job after that was to make the tool behave the way his document already described.

No Flash, just stacked images, so it still runs

Every view is a stack of transparent images sitting exactly on top of one another. Choosing a color does not redraw anything: it swaps one image in the stack for the same image in a different color. The fielding builder stacks forty-two of them and carries 691 layer files, one per area per color per view.

There is no Flash in it and no canvas. In 2012 those were the two obvious ways to do this, and both would have been dead by now. Stacked images in a browser are a stupid, durable technique, and it is the reason the builder still runs.

No Flash, just stacked images, so it still runs. Every view is a stack of transparent images sitting exactly on top of one another. Choosing a color does not redraw anything: it swaps one image in the stack for the same image in a different color.

The client wanted teams to color every part of a glove, then order. I built it from stacked images, 691 layer files I colored by hand, so a color choice just swaps one image. No Flash, so it still runs. First-generation builder. The pulled-apart view is my annotation, and Buy Now is only pointed at.

He fixed a drawing problem with a few words

The first working preview went up on April 1, 2012, and he reviewed it while looking at it.

Looks good so far….Like you said the delay, could be quicker and I noticed Tobacco and Grey arnt working, but all the areas seem to be matching up … Not a major thing, but if you could, the areas I have the “Black/Red Spider Circle Patches”, could you make those as a graphic, with sharper colors, rather than the dull photo image that I used?

The client, April 1, 2012

Three defects in one paragraph: it is slow, two colorways are broken, and the patches look bad because they were photographs rather than drawings. All three are fair and all three got fixed.

Then he solved a problem I had been treating as a rendering problem, and he solved it with words. The preview could never show every combination, because glove type and web style and throwing hand all change the physical glove without changing its color. Rather than ask me to draw those permutations, he wrote the disclaimer himself and told me where to put it: above the buy button.

Some version of that paragraph is still sitting in the left rail of the build in the pictures above, three years after he wrote it. It is the cheapest fix in the whole project and it is the one that kept the returns down.

Six weeks after launch I asked him whether anyone was using it.

yeah…orders trickle through every now and then!

The client, May 22, 2012

That is the honest shape of a small brand launch and I would rather publish it than a number I cannot support.

Three years later the same loop was still running, and it is worth showing whole, because the interesting part is not the list. It is what happens after the list.

Four messages, three days
The client · August 29, 2015, 9:24pm

Things i noticed :

  • the Custom Text feature isn’t working on all 3 top hand views
  • please remove “Extra Padding” option
  • on the back hand view, there are (2) areas that are still white (the finger patch and the inside of the wrist area) please make both areas the same color as the “Outside Fingers”
  • also on the backhand view, is it possible to just remove the “spiderz” embroidery on the finger. My cutout looks bad.
The client · August 30, 9:05pm

How is it going on those changes ?

Me · August 31, 9:17am
  • Textbox is now working
  • Textbox defaults to Spiderz Elite
  • Removed extra padding option
  • Removed spiderz embroidery
  • Changed Hweb top hand view spider logos
  • Red spider on palm changed to black (well almost black, so it is still visible on the black palm choice)

Still working on the back hand view, the two white areas. I’ll let you know when done.

The client · August 31, 9:59am

Can you take a peak at the Textbox, when you go to the Double H and T-Trap view, it doesnt line up. Thanks,

From the project correspondence

Forty minutes after I reported the text box fixed, he had it broken again on two of the three views. That is not a complaint about him. That is what a working review loop looks like, and it is the reason the tool got good: somebody was checking every claim I made, on the actual build, the same morning I made it.

A character limit became a phone call per order

The day after that first preview I told him the order line would have to be abbreviated, because the payment processor limited how many characters of custom options an order could carry. It read like a footnote at the time.

Two and a half years later it arrived as a business problem, and he had diagnosed it himself before he wrote to me.

I am still having problems with PayPal after the purchase. It shows ALL Available WEB selections and not what the customer selected. Then, because all the selections take up so much space character wise, there is not enough room for the rest of the glove area selections to report to PayPal, so the PALM color never makes it to the final report. Therefore we have to call each customer to ask what they ordered.

The client, January 4, 2015

Read that last sentence again. A character limit in somebody else’s checkout had turned into a phone call per order. The tool worked. The receipt did not, and the receipt is where the work actually lands.

The fix was not a fix. It was an admission that the ordering model was wrong for the product. Over the following year the option list was cut back to what the preview could truthfully draw, and then checkout was removed altogether and replaced with a quote request: the customer’s configuration goes out as an email with its own reference number, and a person answers it. The confirmation that goes back carries the specification for a custom logo, because that turned out to be the other thing people always got wrong.

The iPad hid five colors, and he caught it

In December 2015 the builder stopped being a website feature and became a sales instrument. He was flying to New York to close an exclusive with a sporting goods company, and told me plainly that the builder “is going to be the piece that makes the deal work”. A trade show in Nashville followed in the first week of January, where it would run on an iPad as a kiosk.

Days before that show, he found this:

when using Safari on my ipad (which is whats being used as a kiosk at the show this coming week inNashville) the scroll down bar doesnt appear, thus I dont have access to those 4 or 5 colors……….please take a look.

The client, January 3, 2016

Mobile Safari does not paint a scrollbar until you scroll. On a desktop the color list showed a scrollbar and everyone understood there was more below it. On the iPad the list simply appeared to end, and five colorways did not exist as far as any customer standing at that kiosk was concerned.

I did not find that. He found it, on the device, days before it mattered. It is the most useful piece of testing anybody did on this project and it is a good argument for putting the builder on the actual hardware in the actual room.

Five box sizes in thirteen minutes

The retail side ran on the same logic. In July 2011 a factory sent a dieline with another company’s artwork still on it and a fixed set of dimensions. The next day the client asked for it in every size.

The five size layouts carry creation stamps between 11:38am and 11:51am on July 4, 2011. Thirteen minutes, because the only thing that changes across them is the badge in the corner.

A size L batting glove header card with the Spiderz Sports logo and a feature list
One of the size run. The die shape came from the factory and could not move, so everything else was drawn to sit inside it.

That template kept earning. Five glove models eventually shared it, a second product line borrowed it for a different box, and years later four models were put on a single shared back panel to save a press run. The constraint that started as somebody else’s die became the reason the brand could add a product in an afternoon.

What is wrong with it

I was late. Not once, structurally. The second-generation builders were scoped in late 2015 and were still not finished the following spring, and the client told me exactly what that cost him: he missed the peak season for custom team orders.

Justin, I need this thing finished. Another competitor from the local area has krept up and built one since the time we announced ours was almost ready. His is operational now.

The client, March 28, 2016

A competitor shipped the same idea while I was still finishing. That is the outcome, and it is mine. There is no version of this case study where the design decisions were good enough to cover for that.

The tool has other faults I would fix now. The color lists are native selects, which is exactly why the iPad hid five of them; swatches would have failed visibly instead of silently. There is no empty or error state anywhere, so a missing layer file shows a broken image rather than a message. And the whole builder depends on a file naming convention with no validation behind it, which meant a single capital letter in a filename could remove a color from the product.

I know that last one for certain, because getting this build running again in 2026 took a small shim that matches filenames without caring about case. It was written for a web server that did not care either. Move it to one that does and a third of the glove disappears.

I’m looking for a full-time role as a lead product designer and design engineer, remote or hybrid.

Thirty years of it, since I was fourteen, usually as the only designer in the room. If this is the kind of work your team needs, I would like to hear from you.

Download resume

Or email [email protected].