Your Customer Feedback Is In. What Should You Change, and When?
I recently read an analogy from EQ Applied that has stuck with me: criticism is like cutting and polishing a diamond. Without the friction, the cuts and the polishing, you don't get to that finished, beautiful stone.
It made me think about customer feedback.
After you've spent months, sometimes years, developing a product, criticism can sting. I know my first reaction most certainly isn't always, What a wonderful learning opportunity. Sometimes you need to take a beat first. That's human nature.
But the feedback that makes you uncomfortable may also be the feedback that helps you improve the product. The trick is knowing what to do with it. And when.
In the first part of this series, we talked about how to figure out what your customer is actually telling you. Is it fit? Sizing? Preference? Production? A disconnect between what you showed and what she received?
Now let's assume you've done the detective work and the feedback is legitimate.
What do you actually change, and when do you change it?
Not every problem requires the same response. Some need attention immediately. Some become small rolling improvements in the next production run. Others are signals you keep on the radar until you have enough information to act. And sometimes the feedback points to so many changes that you're no longer talking about a 2.0. You're designing another product.
That's where launch and learn becomes less of a philosophy and more of a product-development discipline.
Take a Beat Before You Change Anything
Once you've confirmed the feedback is real, go back to what you know and your process.
Is the issue happening across all sizes or only some? Does it involve material, fit, construction, or the design itself? Does it happen immediately, after several hours of wear, after washing, or only when the product is being used in a particular way?
Then get the actual production garments back on bodies.
Fit the affected sizes. And fit the ones no one is complaining about. What are the visual and performance differences? Compare them with your approved samples and specifications. Go back to the wear-test results, if you did one. What did testers say then? What are customers saying now? What changed, and what didn't?
Production introduces variables that development doesn't always uncover, and paying customers behave differently from wear testers. They wear the garment longer, wash it their way, and use it in environments you can't fully replicate.
Then look at sales.
If a style is selling well overall but one or two sizes are tanking, that tells you something very different from universally poor feedback. You may have a grading or fit issue isolated to those sizes rather than a problem with the style itself.
Sometimes pulling those sizes is the better decision. It's painful. You've already paid for that inventory. But continuing to sell something you know isn't working can lead to poor reviews and ultimately hurt a style that is otherwise successful.
On the other hand, if customers across sizes are consistently reporting the same problem with fit, fabric, wash, or wear, that deserves more immediate attention.
None of these decisions should happen in a vacuum. Bring together the core stakeholders, especially the people who will need to make the change and those who will have to communicate it to customers. The founder or brand president may ultimately make the call, but they should do so with the full picture in front of them.
The first question isn't How quickly can we fix this?
It's: What exactly needs fixing, and when does it need to happen?
Small Changes Can Make a Big Difference
Once you know what needs attention, don't assume the answer needs to be dramatic. Some of the most meaningful product improvements I've seen have been surprisingly small.
A bra strap may simply need a bit more length to comfortably accommodate being worn straight or crossed. A light-to-mid-color swim bottom may need a mesh layer to provide the opacity the customer expected. An active legging may need slightly more curve through the saddle in larger sizes so it sits into the body properly rather than simply scaling the proportions of a smaller size upward.
These aren't flashy innovations. They're thoughtful technical adjustments that can materially change how someone experiences a garment.
We recently had another example with a swim bottom. We fit and tested it, but once customers began wearing the production garment for extended time in and out of the water, we heard that the fabric was bagging and the bottom was moving around more than it should.
We didn't need to reinvent the style. We needed the fabric to work harder.
We removed a small amount of outer fabric through the mid-gusset, front and back, to better balance it with the inner lining and make it react more consistently in water. Then we added a little to the back gusset to give the bottom more anchoring on the body.
Small changes, meaningful payoff.
And not every improvement needs a big announcement. Some are simply rolling changes you incorporate into the next production run because you now know how to make the product a little better.
That's continuous improvement. Ideally, your customer simply experiences a better product.
Know the Domino Before You Make the Change
Small doesn't necessarily mean isolated.
In close-to-the-body products, almost everything is connected. Change one thing, and another often moves with it.
Let's say customers tell you the straps on a balconette are slipping off their shoulders. The obvious answer might be to move the straps inward.
Except wide-set straps are part of what makes a balconette a balconette. So before moving them, I want to look at where the straps connect in the back, how much adjustment they have, the cup shape, and the overall balance of the bra.
And if enough customers consistently want those straps significantly closer together, they may actually be telling you something bigger.
Maybe they don't want a balconette.
Maybe they want a demi.
That's where you have to protect the product's integrity while still listening to the customer. If you keep “improving” a style until you've removed the attributes that define it, you haven't created a better version of the original. You've created another product.
The domino can be even bigger with something like a padded bra. Change the coverage, and you may need to change the pad. Change the pad, and you may be back in pad development, fit, and testing. That costs time, which costs money.
If the improvement is worth it, make it. But sometimes the number of dominos tells you that the better decision is to redesign the product or eventually discontinue it rather than keep trying to turn it into something it isn't.
Before making even a seemingly logical correction, ask what else it touches.
Is the juice worth the squeeze?
Is It 2.0, Something New, or Not Yet?
This may be the hardest judgment call.
Sometimes feedback tells you exactly what to improve for the next production run. Sometimes there are enough issues across a style that I'd rather take what we've learned and design something new. And sometimes you don't have enough information yet, so the right decision is to keep watching.
There's a difference between we took the style you love and made it better and we changed half the garment.
There's also a difference between quietly making a rolling improvement and announcing that you've “fixed” something. Customers don't need a press release every time you refine a strap length or tweak a fit measurement.
I like to use new and improved messaging with an eyedropper. If every product needs a highly publicized 2.0, you may unintentionally tell customers that what you're launching the first time isn't quite ready. That's not the message we want to send.
Cost matters here too. Pure fit tweaks often don't materially change garment cost. Fabric changes can. New trims can. Innovation usually does.
If customers are asking for features that genuinely add value but substantially increase cost, perhaps that becomes a premium or luxe version rather than replacing the original. The same goes if you've found the next big innovation or design update. If your brand is built around staple essentials at a particular price, adding every possible innovation may technically make the product “better” and more modern, while making it less right for your customer.
And then there's the opposite kind of feedback: success. A bestseller needs watching too. If customers keep coming back to a style, that's information. At some point, you may want to evolve it before the customer tires of it. But be careful. Understand exactly what she loves before you start improving it.
Don't innovate the reason she bought it right out of the product.
Whether you're dealing with a problem child or a bestseller, the questions are similar: What should we preserve? What have we learned? And is now actually the right time to change it?
Change It. Then Prove It.
Once you've decided on the correction, validate it. That doesn't necessarily mean restarting the entire development process.
Put the revised garment back on a fit model. If the issue occurred in particular sizes, fit those sizes. Have team members in the appropriate size range do a quick-and-dirty internal wear test. Depending on the issue, a handful of targeted testers may give you exactly what you need.
You're not reopening every decision you made about the garment. You're trying to answer two very specific questions:
Did we solve the problem we intended to solve? And did our solution create another one?
That second question is why understanding the domino matters. And then stop.
One legitimate product issue can quickly shake your confidence in everything, particularly when it's your brand. If we missed this, what else did we miss? Should we refit that style? Reconsider the other fabric? Go back through the whole collection?
Usually, no.
This is where I come back to the diamond analogy. The cuts and friction are part of what gets you to something better. That doesn't mean you keep cutting until there's nothing left. Customer feedback works much the same way.
Sometimes what you learn calls for a tiny fit adjustment. Sometimes it means changing a material or pulling a size. Sometimes the right change waits for the next production run. Sometimes it leads to an entirely new product. And sometimes the smartest decision is to leave the product alone and keep listening.
That's launch and learn.
Listen to what came back. Understand what it means. Make the changes that matter, when they matter. Then keep learning. That's what we do.
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