What Is Your Customer Actually Telling You? How to Turn Feedback Into Better Product
You fit the product. You wear tested it. You made the changes. You approved production.
And then you launched. Cue the drum roll and a little teeth chattering at the same time.
Because now, if you're lucky, hundreds, or maybe thousands, of people are wearing your product on different bodies, for different lengths of time, in different environments and in ways you may never have anticipated. And they are going to tell you things. Some you will love hearing. Some you won't.
Coming off our recent conversations about wear testing before production, this is the natural next step. As important as wear testing is, it doesn't end the learning process. Once a product becomes customer-facing, you have access to an entirely new set of information.
This is different from a wear test. Your product is now out in the real environment of retail, on your site and on models, being purchased and evaluated by people you don't have direct contact with. They haven't been recruited as testers, they haven't been given instructions about what to evaluate and, importantly, they paid for the product. Their expectations are different.
This is why I say launch and learn ad nauseam. Because you will. And that's a good thing.
The challenge isn't simply listening to customer feedback. It's understanding what the customer actually means by what she is telling you. A customer can usually tell you exactly what she is experiencing. She may not be able to tell you why it is happening.
That's our job.
Your Customer Is Describing the Symptom
I've spent much of my career designing close-to-the-body products, where a seemingly simple fit comment can have a surprisingly complicated answer.
A customer tells you there isn't enough coverage in the front of a swim bottom. Your first instinct might be to add more fabric to the front. But what if the real problem is that the garment is imbalanced and rotating forward?
Or she tells you that the bottom keeps shifting around when she moves. Again, it sounds like one problem, but the actual issue may be somewhere else entirely. The back gusset may be too narrow to properly anchor the garment on the body, allowing the entire bottom to move.
Change the symptom without understanding the cause and you can create a second problem without ever solving the first. This is where customer feedback starts to look a lot like fitting.
Listen literally. Diagnose intelligently.
First, Is It Actually a Product Problem?
This is an important question, and sometimes a tricky one. There are parts of fit that are within the customer's autonomy.
If you're spilling significantly out of the cups of a bra, you may simply need a larger cup size. If a bottom is digging into your waist or stomach, you may need to size up. If the entire garment is visibly too large, sizing down may solve the problem.
That doesn't mean the feedback isn't useful. If multiple customers are choosing the wrong size, you may have uncovered a different issue. Your size guide could be inaccurate or difficult to understand. Your imagery may be creating the wrong expectation. Your product description may not be giving customers enough information to make the right choice.
The garment may be fine. The customer journey to that garment may not be.
Make Sure You're Selling the Product You're Showing
There are many opportunities to set a customer up for either the right or wrong expectation before she ever opens the package. Model imagery is a big one.
If a dress hits above the knee on a model who is 5'9", a customer who is 5'3" can reasonably expect it to look longer on her. But that only helps if you tell her the model's height. Garment size matters too. If a size 2 model is photographed in a size 6 garment, the style may appear to have significantly more coverage or ease than it will when the customer orders her actual size.
Good product pages give customers context: model height and size, the size the model is actually wearing, accurate fit guidance, and information about the fabric and how it behaves. They should also clearly describe coverage, support and intended function, and give useful direction such as "runs true to size" or "size up for more ease."
I think of these as spokes of the same wheel. Imagery, language, sizing, fabric information and the actual product all need to point in the same direction.
And yes, I know not everyone reads the size guide. Heck, I'm sometimes one of those people because I think I know better. That doesn't make the information less important. It means brands need to get more clever about putting the most important fit information where customers will actually see it.
Preference Is Different From a Product Problem
There's another layer to interpreting feedback: sometimes the customer simply isn't the customer for that particular product.
We account for this during wear testing. I wouldn't give a tanga to someone who exclusively wears full-coverage hip huggers and then ask whether she likes the coverage. I already know the answer. The same principle applies after launch.
If someone only feels comfortable in very full-coverage bras, a minimal bralette may never be right for her. That doesn't mean the bralette is poorly designed or poorly fit.
The opportunity is to listen for the cues in what she is telling you. Good customer service might respond, essentially, It sounds like what you're looking for is X rather than Y. Let me recommend our favorite version of X.
For a larger organization, customer service may be the first to hear these comments. For many of the emerging brands we work with, it's the founder herself. Either way, the information needs a path back to the people who understand the product.
Sometimes that means the design or product team helps customer service answer an individual question: try this size instead, adjust this strap, or perhaps this other style would suit you better. When similar questions keep coming, that's when an anecdote starts becoming data.
When Does Feedback Become a Pattern?
There isn't a magic number. For a smaller brand, three to five customers independently describing the same issue can be enough to make me pay attention.
The pattern might also reveal itself through returns. If returns begin concentrating in one particular size, for example, that deserves investigation even if the total number of returns isn't enormous.
You're looking for consistency. Are people describing the same experience? Is it happening in one size or across several? Does it happen after a particular amount of wear, during a specific activity or after washing?
Those details matter far more than one loud comment in isolation. But there is an important exception.
Some Feedback Doesn't Need to Become a Pattern
Severity matters too. If a clasp is popping open during wear, I don't need 20 customers to tell me before I investigate it. If seams are opening, straps are literally falling off, or a swimsuit becomes unintentionally transparent or exposes something it clearly shouldn't, those are concerns.
Rolling or slipping can be different. That may relate to size, body shape, fit preference or how the garment is being worn, so I want more information before assuming there is a systemic product issue.
The question isn't simply, How many people complained? It's also, What are they telling us happened?
Frequency and severity are two different signals, and good product teams pay attention to both.
Before You Change the Pattern, Check Production
This step is easy to skip. You approved a garment that fit correctly, but customers are now telling you something isn't right. Before changing the pattern or tech pack, make sure the garments they received are actually the garments you approved.
Did production come in to spec? Was the correct fabric used? Were the correct components used? Did something shift between approval and bulk production? Is the issue happening across every garment in a size, or are there individual garments that measure differently?
Sometimes the answer requires actual QC at the warehouse: opening packages, pulling garments and measuring them. No one loves this answer. You're paying people to go into inventory you've already paid to produce and inspect it.
But that cost can be significantly smaller than assuming you have a design problem, making the wrong correction or potentially being unable to use an entire production run.
Be a detective before you become a fixer.
Customer Feedback Is Information, Not Instruction
This may be the most important distinction. Listening to your customer does not mean making every change she asks for. It means taking what she tells you seriously enough to investigate it.
Sometimes the answer is a different size or a different style. Sometimes it's better product copy or imagery. Sometimes it's a production inconsistency. And sometimes she has identified a genuine product issue that needs to be fixed.
Your responsibility is to determine which one you're dealing with.
That's why I don't see customer feedback as the end of the development process. It's another phase of it. You fit, you wear test, you launch and you listen.
Then you diagnose.
Next week, we'll take the next step: what happens once you know the feedback is real and you decide to act on it.
Because in close-to-the-body product, changing one thing rarely changes only one thing. Strap placement, coverage, fabric, anchoring, pads and proportions are all connected. Every adjustment has a potential domino behind it.
And that is where launch and learn gets really interesting.
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