Wear Testing: Turning Real-World Feedback Into Better Product
- Suzy Wakefield
- 5 days ago
- 8 min read
Two weeks ago, we talked about why wear testing matters and why an approved sample isn't necessarily a proven product. Now comes the part that determines its value: how you execute it.
Buckle up. I have a lot to say about this one because, when it comes to wear testing, the value lives in the details. Read to the end for a valuable tool to use in your own wear test.
Because handing a few samples to friends and asking, "What do you think?" is not a wear test.
A good wear test is structured. You know who you're testing, what you're asking them to do, and what you need to learn. Most importantly, you have a plan for what happens when the feedback comes back.
The goal isn't simply to collect opinions. It's to uncover information you can act on before making the much larger investment in production.
Start With the Right Number of People
Ideally, I like to see between five and ten wear testers per size. Ten makes patterns easier to identify, but samples cost money, particularly when you're paying your factory for each one. Five committed testers per size can still give you very useful information.
And the word committed matters. Five people who follow the protocol, use the garment as intended, wash it correctly and document their experience are far more valuable than ten who put it on once and say they "liked it."
The more innovative or complex the product, the more important wear testing becomes. With a particularly complex product, I would also build one or two additional fitting rounds into the development calendar following the test. You may not need them, but it’s better to allow the time than discover that you need it late in development.
Which Sizes Should You Test?
Ideally, test as many sizes as you reasonably can without derailing the calendar or budget. Don't assume that because something works beautifully in your base sizes, it will perform exactly the same way throughout your range. Different sizes and bodies place different demands on a garment.
With bras, the band and cup combinations you test should reflect the niche you're designing for. If your brand is built around fuller busts, for example, your test group needs to adequately represent those bodies and sizes. The same principle applies to every category.
Test the customer you're actually designing for.
That doesn't mean testing every possible size at the expense of moving the product forward. It’s a balance between gathering enough information to make a good decision and keeping the process moving.
You Don't Have to Wear-Test Everything
You don't need to wear-test every garment. I recommend testing anything functional or anything you haven't developed and proven before.
A new sports bra with a different support construction? Yes. A swimsuit with a new fabric or performance attribute? Yes. An innovative closure, convertible feature, compression level, or other new functionality? Absolutely.
Fashion is different. If you're making a fashion update to a product with a proven block, construction, materials, and performance, there generally isn't a reason to test it again.
Wear testing should answer questions you can't adequately answer in a fitting. If you already know how it performs and are primarily changing its fashion expression, there may be little new information to uncover.
Remove the Bias You Can Control
Here's a small detail that can have an outsized effect on the quality of your feedback: color.
Whenever possible, I prefer wear-test garments in a light to mid color and nothing particularly fashion-forward. The fabric and components must also be mid-spec, since their quality and performance will influence the results. You want someone evaluating the product, not deciding how she feels about the color or print. Give a tester a color she loves and that enthusiasm can influence her assessment. Give her one she hates and the reverse can happen.
And I wouldn’t use black as your neutral. People tend to like things better in black, but there’s also a technical reason. Black generally requires the heaviest dye application, which can affect the hand and behavior of the material. If you’re trying to get the cleanest read possible on the product, black isn’t necessarily neutral at all.
You can’t remove subjectivity from a wear test, nor should you. Your customer is subjective too. But you can remove some of the variables that have nothing to do with what you’re trying to learn.
Give Them a Job, Not Just a Garment
A wear-test sample should never arrive by itself. Once you've confirmed her size, she should receive the garment with a structured protocol explaining what to do.
The protocol must reflect the product’s intended use. If you're testing swimwear, testers need to swim in it and spend meaningful time in the water. If you're developing running apparel, they need to run. If it's tennis apparel, someone needs to play tennis in it. A product designed to perform through activity can't be adequately evaluated by someone walking around her house in it for an hour.
For most wear tests, I recommend approximately one to two weeks, including at least two to three extended wears and two to three washes. The exact protocol will vary, but testers should understand precisely what you're asking of them.
"Try it a few times and let me know what you think" doesn't give you enough.
Capture the Experience as It Happens
The freshest feedback is generally the most useful. I don't want someone sitting down at the end of two weeks trying to remember how a bra felt on the first day or what she noticed when she first opened the package.
The questionnaire should follow the tester through the experience with micro-questions at each stage. Capture first impressions when they are truly first impressions and extended-wear feedback while the experience is still fresh. The same goes for activity, washing, and wearing the garment again.
Those micro-questions might include: What did you notice when you first picked up the garment? How did it feel when you put it on? Where did it naturally land on your body? Did anything move, roll, ride up, dig in, stretch out, or become irritating during wear? What changed after washing? Did you read and follow the care instructions? How did it feel when you put it back on?
Combine quick ratings, short fill-ins, and selected open-ended questions. That gives you enough structure to compare responses across testers without making the exercise feel like homework. It also gives testers room to tell you something you didn't think to ask.
Your questionnaire isn't only a way to find problems. Pay attention to the language testers use to describe what is working, too. The language they use around comfort, support, ease, performance or feel can inform product positioning and marketing.
The goal is to help people become better observers without leading them toward the answer you want. That's an important distinction.
You don't need every tester to try the garment on for the team before taking it away. You can provide an on-body reference image from the fitting if that's helpful, but part of the test is discovering where the product naturally wants to land on a real person's body. Don't force it into position and potentially remove one of the things you're there to learn.
Look for Patterns, Not Just Individual Comments
Once the questionnaires come back, design and technical design should take the first pass, consolidate the feedback, and begin identifying patterns. The product team can then review the findings and determine what needs action.
If one person tells you a band feels too tight and everyone else loves it, you don't automatically change the band. That may be personal preference. If six people in the same size tell you the band feels too tight, you have something very different. This is why more testers are valuable: patterns give individual comments context.
But personal preference shouldn't automatically be dismissed either. You're developing a product people must want as well as one that must function. A tester may tell you she would prefer a lower neckline. That's useful information. But on a sun-protective top, lowering the neckline may undermine the product’s purpose. Alternatively, I've seen a bra become a no-go because it peeked out of a V-neck tee.
You want to hear both. Then you evaluate each comment against the intended use, functionality, design intent, and the patterns you're seeing across the larger group.
Sometimes the Simplest Garments Teach You the Most
Underwear is a great example of how quickly preference, aesthetics, fit, and function can collide.
One issue surfaces repeatedly in underwear wear testing: back coverage. From a fashion perspective, too much coverage can quickly make a panty feel old-fashioned, so there's a natural inclination to take it away.
Functionally, though, you need enough coverage to anchor the garment. Remove too much and suddenly the panty becomes a little too friendly with places you definitely didn't design it to go.
Then add elastic tension, fabric stretch and recovery, and the tremendous variation in body shape. Suddenly, something that looks like a very simple hipkini becomes anything but simple.
This is where product development becomes equal parts art and science. Wear testing reveals whether you've found that balance across different bodies and sizes. It's also one of the reasons underwear is much harder to design well than people think.
So, What Does It Mean to Pass?
If you're anything like me, there’s something satisfying about getting the good grade. We like the check mark. We like the word "approved." We like knowing we passed.
Wear testing doesn't quite work that way.
Sometimes the strongest result from a wear test is finding something that needs to be fixed. That's not a failure. That's exactly what you spent the time and money to discover.
You're preparing to make a much larger investment, so what matters is identifying the issues and correcting them before production. Often, they're relatively easy solves. You make the changes, conduct another fitting, and move forward.
With a particularly complex or innovative product, you may want a second, more informal wear test on the corrected sample. It's rarely necessary, but sometimes that extra step gives you the assurance you need before committing to production.
And then you launch and learn.
You absolutely will learn more once your product reaches a larger group of customers. Wear testing isn't meant to eliminate that. The point is to get to launch. It’s to launch the strongest product you can reasonably build, with fewer avoidable problems and the best chance of success.
You could test forever. At some point, you have to put the product into the market and let the next stage of learning begin.
Make Your Wear Test Work Harder
Wear testers give you something enormously valuable: access to your product in circumstances your team can't fully replicate. Make that access count.
Choose testers who represent the customer you're designing for. Give them a clear protocol. Ask the right questions at the right moments. Make sure they actually use the product the way your customer will. Then listen carefully, look for patterns, and put what you've learned back into the product.
Because a wear test shouldn't simply tell you what people think.
It should help tell you what to do next.
Final Question
Are you asking your wear testers whether they like your product, or are you giving them the structure to show you how to make it better?
A Tool to Help You Get Started
Knowing what to ask is often the hardest part, so I've created a simple Wear Test Worksheet: From First Impression to Final Wear to help you structure the process.
It follows the product through first look, first wear, real-world use, washing, rewear, and final evaluation. It also includes a simple wear and wash diary so feedback is captured while the experience is still fresh.
The goal isn't to make your testers fill out pages and pages of forms. It's to ask the right questions at the right moments and get feedback you can use.
If you're building an apparel brand and want to make sure your development strategy is working for your brand, not against it, that's exactly the kind of clarity we work through together. Book a call here to talk through where you are and what your product actually needs.
Comments