Case Study: OPSGEAR Vest Builder
2011
TL;DR
Impact
Context and Problem Analysis
OPSGEAR was a small Utah-based retail company that served the military, law enforcement, and military-simulation ("milsim") recreation communities. Across all of these diverse groups, one essential piece of gear is a modular duty vest: a heavy-duty vest worn over the uniform that is customized to each wearer with pouches and carriers to hold a variety of gear, from medical kits to weapon or ammunition pouches to radio, command, or navigation devices.
Although OPSGEAR stocked thousands of pouches for every conceivable purpose and in every conceivable duty color, sales in this area lagged somewhat when compared to our many competitors. It was clear we needed a big way to differentiate our offering.
The idea for the Vest Builder started off as the answer: an interactive website that would allow the user to select a vest, add pouches manually and customize their color and position, then add the entire package to the retail store site with a single click of an "Add to Cart" button.

Research and Insights
Working with the Marketing team, we discovered that the target user bases for the Vest Builder aligned neatly with the three major market segments for OPSGEAR as a whole. Understanding each market required an understanding of their core goals and needs, and so we started by documenting the main needs of the three personas:
Personas
Military
Law Enforcement
MilSim
Development and "Guerilla Testing"
Being in such a small company where everyone wore many hats, I was responsible for the entire implementation of the app (including product photography) with the exception of the initial UI concepts. The app was built in Adobe Flash using a simple XML file as the data store, and a separate admin console to make it so anyone could add or remove pouches.
Much of the testing for the Vest Builder happened at unexpected times during development. The CEO of OPSGEAR was himself ex-military, and the retail store attracted many friends of his across military and law enforcement. He would often grab whoever was in the store at the time (maybe a Salt Lake City police officer, or a buddy of his from the Air Force Security Forces) and haul them up to the media office to have them check out this new application we were working on.
The at-first unprompted feedback gave us some unexpected and extremely valuable insight into the needs of our target audience. After the first couple of surprise drop-ins, I insisted that anyone else in the store with a military or police background come up immediately to sit and try to configure a vest.
Insights and Iteration
Some of the most insightful feedback included off-the-cuff comments that made us rethink large parts of the interface. They all started out with "this is cool, but…"
"My department regulations say we can only wear black."
– Salt Lake City SWAT Officer
"I'm a field medic, how do I find the first aid and trauma kit pouches?"
– Utah National Guard Member
Which led directly to the addition of new features including:
Filtering vests and pouches by color
Filtering pouches by type
Creating pre-configured options when called for by organization
Emailing yourself a shopping list with purchase links
To further drive sales and meet business needs, we then worked closely with our e-commerce provider to develop a custom process to allow us to add an add-to-cart button, linking directly to the online store's shopping cart, with the user's chosen vest and pouches already added and ready for purchase, reducing friction even further.
Lessons Learned
As one of my first experiences designing and iterating on a user-focused product, some of my hardest won career lessons happened here. Among the most important are:
1.
"I am not my target audience"
— UX axiom
Given my complete lack of military or law enforcement experience, I relied heavily on those early testers who gave candid, and sometimes blunt but necessary feedback that helped make a better product.
2a.
"No plan survives first contact with the enemy"
— Prussian Field Marshal Helmuth von Moltke the Elder
See also:
2b.
