The Questions You Don't Know to Ask Can Cost You the Most
The most expensive product development mistakes often begin with assumptions nobody questioned.
You have a great product idea. You know your customer, have a vision, and you're ready to move forward. But what about the questions you don't even know you should be asking?
After decades in apparel design and development, I've learned that expertise isn't simply about having answers. It's knowing which questions to ask, when to ask them, and how one decision affects everything that follows. Just as importantly, the questions need to go both ways.
The Questions That Change the Conversation
When we begin working with a founder, we ask a lot of questions. Some seem surprisingly basic. Where do you want to manufacture? What size range are you planning? What does inclusivity actually mean for your customer? How many styles and colors do you envision?
These aren't just boxes on an intake form. They help turn an idea into a strategy.
Take assortment planning. Every additional style, color, and size affects your SKU count, production quantities, and inventory investment. I often encourage founders to prioritize two of these three assortment variables, rather than trying to maximize everything at launch.
The better question isn't always Can we do this? It's What matters most to our customer, and what are we willing to compromise on to deliver it well?
Sometimes these conversations reveal opportunities nobody considered, from a complementary product to packaging that strengthens the brand's identity. Experience builds a muscle for recognizing both risks and possibilities. Founders develop that same muscle by participating in the process, not simply watching it happen.
Every Decision Has a Domino Effect
We recently worked with a founder developing swimwear who was excited about an innovative fabric. It had real potential, but it was still in development. Even the supplier couldn't confirm whether it would perform as needed at production scale.
We shared the enthusiasm, but what would waiting for that fabric mean for the project? Additional testing? A delayed development timeline? More investment? And what if the material ultimately didn't work?
Once we mapped out the implications, another option became clear: move forward with a proven fabric and potentially introduce the innovation in version 2.0.
Our job wasn't to make the decision for the founder. It was to make sure the decision was fully understood.
That's the domino effect of product development. A material decision can affect fit, construction, testing, sourcing, timing, and cost. The earlier you understand those connections, the more choices you have.
Small Garments. Not-So-Small Complexity.
One misconception I encounter regularly is that smaller garments must be easier to make. They're not.
Whether it's a bra, performance short, swimsuit, or birthing gown, close-to-the-body products require an especially thoughtful marriage of materials, construction, fit, and movement.
A garment can look beautiful on a model and fail when someone actually wears it. Does it move with the body? Does it provide the intended support? Will it perform across sizes? Have you wear tested it?
And does your manufacturer have genuine experience in the category? A great apparel factory isn't automatically a great bra factory.
This is where art and science meet. A product needs a compelling, distinctive design, but the technical execution must deliver on its promise. Aesthetic value gets the customer's attention. Functional value earns their trust.
Your Team Isn't Made Up of Mind Readers. Neither Are You.
Whether you're working with an internal team, outside specialists, or figuring out the early stages yourself, you need enough understanding to make informed decisions about your product and your investment. That doesn't mean becoming an expert in every discipline.
I still regularly ask experts in marketing, technology, and other fields to explain things I don't understand. Even after working in companies with enormous resources, I don't pretend to know every nuance of every discipline. Why should a founder be any different?
Your team may be discussing fabric performance, technical construction, or manufacturing terminology that feels second nature to them. But if everyone assumes the meaning is clear when it isn't, important details can get lost.
Ask for clarification. And if you're the expert in the room, make sure you're explaining things in a way that helps everyone make better decisions.
We often act as our clients' explainers, dictionary, encyclopedia, and occasionally their Google. But some of our most productive conversations start when someone shares a concern, a question, or an idea that hasn't quite taken shape yet. We can't read each other's minds. The earlier those conversations happen, the more useful they become.
Collaboration Doesn't Mean Giving Up Your Point of View
Many founders create products because of something they've experienced firsthand. A garment that didn't fit, a function that was missing, or a need the market wasn't addressing. That experience is often what makes the original idea so compelling, and it deserves a strong voice throughout development.
The strongest products come from combining that perspective with different areas of expertise. In our work, design and production are in conversation from the beginning. My role is to advocate for the product and the founder's vision, ideally making it even stronger. Production and sourcing bring another perspective. Technical design and manufacturing bring theirs.
No single person has every answer. The founder understands the experience that inspired the product, the customer, and the ambition behind it. The other disciplines bring the expertise needed to help execute it.
That doesn't mean every opinion carries equal weight on every decision. It means knowing when to lead, when to listen, and when to challenge an assumption.
A color change, redesign, or new vendor may be exactly what the product needs. It may also affect the schedule or investment. Understanding those trade-offs allows everyone to make better decisions together.
Good collaboration requires confidence in your vision, respect for other people's expertise, and enough humility to recognize when someone else knows more. Whether you're leading a team or building one, stay involved, stay curious, and be willing to learn.
Three Questions Worth Asking at Your Next Development Meeting
Whether you're just starting or already deep into development, try these:
1. What are we assuming that we haven't actually confirmed? Fabric performance, sizing, manufacturing capabilities, customer expectations, or even the timeline.
2. If we make this decision, what else does it affect? Consider the implications for design, fit, sourcing, testing, production, timing, and cost.
3. Is there something I should understand better before we move forward? And turn it around: Is there something I haven't explained clearly enough about what I'm trying to achieve?
The Product Is the Result of the Conversation
A great product idea is a starting point. Execution is everything.
I've learned, sometimes the hard way, that being confident in your point of view and being willing to say I don't know aren't opposites. The strongest teams make room for both.
Ask the question. Share the concern. Challenge an assumption. And give the people around you room to bring their expertise to the table.
Because the questions nobody asks can become expensive mistakes. But the questions you do ask can make your product better than you first imagined.
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