From sketching to scaling: How wearable soft goods actually get built

Turning an idea into a functional wearable product takes far more than a sewing machine, a hope, and a prayer. Believe me, I’ve tried.  Between the first sketch and a real-world-ready prototype lies a complex web of decisions about materials, geometry, usability, and manufacturing — all of which can make or break a product before it ever reaches a user. 

From the outside, soft goods development looks simple: there’s fabric, thread, maybe a sensor or two if you’re feeling spicy. But the reality is far more complex. Every seam changes stretch, every layer changes breathability, and every closure changes usability. A design that feels perfect on paper can fall apart once it meets skin, motion, and sweat.

That’s why it’s important to treat the translation between idea and implementation as a structured process, not a guessing game. Each phase, from discovery and early benchtop mockups to material validation and preproduction builds, exists to reduce uncertainty before it becomes expensive. 

Here we’ll walk through that process and how to translate user needs into testable, manufacturable systems. The objective isn’t to innovate as fast as possible — it’s to make sure that by the time your prototype leaves the bench, it’s ready for the real world, not just the photo.

Phase 1: Discovery and requirements generation

Let’s start at the very beginning, a very good place to start. The discovery phase is where ideas meet reality. Assumptions about the user, environment, and product constraints are tested before a single material is cut. 

The mission is simple: Understand the user and define the problem that must be solved. That means learning how the product will actually be used, by whom, and under what conditions. Market research identifies gaps in existing solutions, while user interviews and workflow mapping reveal pain points and environmental constraints that don’t show up in a spec sheet. These insights turn vague aspirations into measurable requirements.

The purpose of this phase is to define what success looks like in practical terms: Does the end-user care more about a low profile battery or having to charge the device less frequently?  How many different environments does it need to be worn in? Will each end user get their own or will one device be shared among colleagues? How frequently is your product going to be used and for how long? Each of these choices echoes through materials, patterning, and integration later in development. 

The outcome of this phase isn’t a prototype — it’s a roadmap. A clear purpose behind every decision keeps teams aligned and turns creativity into direction instead of chaos.

Phase 2: Ideation and early benchtop prototyping

Once the goals are clear, it’s time to start building, but not beautifully. The second phase is all about messy creativity: sketching, experimenting, and quick-and-dirty testing of ideas before investing in refinement. This is where concepts take shape and reality starts to argue back.

The objective is to explore and rule out possibilities quickly and cheaply. That means sketching alternative layouts, mocking up form factors from scrap materials, or taping things together in ways no mere mortal was ever meant to witness. It’s not about making something pretty — it’s about learning fast. 

Each rough prototype exists to answer two main questions:

• Does this product concept have any real potential?
• What are the broad categories for the most viable solutions?
  

Rapid prototyping using muslin, an inexpensive fabric often used for mockups.

Benchtop testing at this stage helps surface issues that no amount of whiteboarding could predict. These insights are used to update product requirements and start mapping out iteration paths. Don’t aim for a pristine prototype at this stage — instead, aim for clarity and direction. 

The best outcomes are rarely the ones that worked perfectly on the first try, but the ones that failed in useful ways. Each test reduces uncertainty before it becomes expensive, setting the foundation for informed iteration.

Phase 3: Patterning, user testing, and refinement

After the strongest concepts emerge, the work shifts from exploration to precision. This is where ideas are translated into geometry, fit, and function that can truly interact with the human body. The goal of this phase is to move from proof of concept to something usable. 

At this stage, it’s useful to build mid-fidelity prototypes that mimic how the final device will move, stretch, and breathe. These aren’t final builds yet, but they’re refined enough to test fit, comfort, and performance with real users.

User testing at this stage goes deeper, focusing on measurable feedback: Does this resist load and distribute it comfortably? Does it allow the end user the full range of motion required for their day-to-day tasks? Can the wearer don and doff it without assistance? These answers guide fit adjustments, material selection, and usability refinements.

This is also the phase where assumptions meet reality. The fabric that looked perfect in theory may trap heat or shift under motion. The closure that worked on the bench may frustrate users in practice. These small but critical discoveries shape each iteration, bringing the design closer to something that feels intuitive, durable, and trustworthy.  

By the end of this phase, the design begins to act like a real product. Each iteration narrows the gap between prototype and clinical readiness, ensuring that refinements build on data rather than guesswork.

Phase 4: Functional prototypes and material sourcing

With form and fit validated, the focus shifts to real-world performance. This phase moves prototypes from “works for now” to something that can survive actual use. Production-intent materials are selected based on durability, comfort, and compatibility with the product’s functional requirements. The challenge isn’t finding materials — it’s finding ones that behave consistently under real conditions.

Functional prototypes are built using construction methods that reflect real manufacturing, then pushed hard through repeated use, environmental exposure, and mechanical stress. Failures at this stage are expected, and useful. 

Materials that seemed ideal may degrade, shift, or behave unpredictably over time. Small usability issues often become more obvious with repeated wear. Iteration here is about convergence, not exploration. At the same time, sourcing and scalability come into focus. A prototype isn’t useful if its materials can’t be reliably produced or sourced at scale. 

Each revision reduces variability, improves reliability, and resolves edge cases uncovered during testing. This is where the design stops being something that works once and becomes something that works consistently. By the end of this phase, the product demonstrates repeatability. It performs consistently under real-world conditions, and is ready to be finalized and documented.

Prototyping different material configurations to achieve a controlled performance.

Phase 5: Design freeze and preproduction handoff

Design freeze is when the product stops evolving and starts being defined. By this point, the design has already been tested for fit, function, and durability under repeated use. What changes here isn’t the product itself, but the tolerance for change. Every pattern, material, and construction method is finalized with the expectation that it won’t be interpreted differently later. 

The focus shifts from improving performance to preserving it. That requires translating a working prototype into something that can be built consistently by people who weren’t involved in development. Patterns are finalized, seam allowances and construction steps are explicitly defined, and materials are specified in a way that removes ambiguity. If a step can be interpreted in more than one way, it will be.

Manufacturability is considered here, but only to the extent that it affects whether the defined process can actually be followed. Construction methods that rely on careful handling, tight alignment, or informal adjustments during prototyping need to be formalized or replaced. The goal isn’t to optimize production, but to ensure the product can be built as specified.

Quality expectations are also defined at this stage. Critical dimensions, functional features, and key construction points should be identifiable and measurable. This isn’t a full quality system, but it establishes what needs to be checked and what acceptable output looks like. 

The result of this phase is a complete and unambiguous definition of the product. Not just what it is, but how it’s built, and what conditions it must meet to be considered correct.

Phase 6: Scaling without surprises

Scaling is when a defined product is tested against the realities of production. At this point, the design and process have been specified. The challenge is whether that process can be executed consistently outside of the development environment. If a design depends on tight tolerances, specific material behavior, or precise handling, those requirements have to match the capabilities of the factory. If they don’t, the process will adapt in ways that weren’t intended, or units will fail inspection. In practice, both tend to happen.

Material consistency becomes a factor at scale. The same fabric may behave slightly differently across production lots, finishes, or suppliers. Adhesives and laminates can respond differently depending on processing conditions. These differences are usually small, but they matter when performance depends on them. 

Quality assurance (QA) is what connects the design to the outcome. QA needs to verify not just that a unit matches its specifications, but that it performs as expected. If performance isn’t tied to measurable criteria, it’s possible for a product to pass inspection and still fail in use.

Factory capability matters as well. Different manufacturers have different equipment, process controls, and experience with specific materials or constructions. A design that’s straightforward for one factory may be difficult or inconsistent for another. Selecting a factory that can actually execute the process is part of making a product scalable.

Pilot production is where these assumptions are tested. It reveals whether the process is clear, whether the materials behave as expected, and whether the product is more sensitive to variation than anticipated. Issues found here can still be corrected. Issues found after full production are much harder to unwind. 

When scaling is successful, the product behaves the same regardless of who builds it. When it isn’t, inconsistencies appear that are difficult to trace because they come from small mismatches between design, materials, and process rather than a single point of failure.

Industrial sewing machine being adjusted to sew through specialized materials.

Designing with intention

Bringing a wearable soft-goods product to life isn’t a linear process, but it’s a structured one. Each phase exists to reduce a specific type of uncertainty: 

• Discovery defines the problem. 
• Early prototyping explores possible solutions. 
• User testing offers real-world feedback for solution refinement. 
• Functional prototypes stress-test a product’s real-world performance. 
• Preproduction defines the product and how it’s built. 
• Scaling tests whether that definition holds in practice.

Skipping steps doesn’t remove complexity — it shifts it to a stage where it’s harder and more expensive to correct. The difference between a product that works once and a product that works consistently isn’t iteration count or speed — it’s whether the process accounted for how materials behave, how users interact with the product, and how manufacturing systems introduce constraints.

informal is a freelance collective for the most talented independent professionals in hardware and hardtech. Whether you’re looking for a single contractor, a full-time employee, or an entire team of professionals to work on everything from product development to go-to-market, informal has the perfect collection of people for the job.