“We kept changing things — with no idea whether we were getting closer to a final product.”
Where the client started
Four months into sampling: photos to the factory over WhatsApp, size charts by email, wearing-feel notes by voice message. The waistband height confirmed in round two came back lower in round four — an old pattern file had been used. The jacket sleeve was corrected, then its cuff width reverted to version one. Both sides were convinced the other ignored their notes.
SEAMDANCE's diagnosis
The factory could sew. What no round ever stated was: what this round is validating, what is already locked, and which file is current. The client was also changing fabric, measurements and logo position in the same round — making it impossible to attribute improvement or regression to any single decision.
The new confirmation method
Everything got consolidated into one master version, line by line: confirmed, to modify, awaiting client decision, parked. Round six validated exactly two things — legging waist-hip fit and jacket sleeve length. No new colors, no packaging. Feedback came back through one movement set and one photo protocol; measurement comments carried positions and numbers, subjective feel stayed clearly labeled as such.
Round six settled the fit; round seven confirmed fabric color, logo and workmanship. When a pocket idea appeared at the last minute, we spelled out what it would do to the locked block and the timeline — the pocket moved to the next style instead of resetting this one.
Reference outcome
No magic one-round finish — but an endless loop became two rounds with stated purposes. The sealed file now says exactly which version bulk follows, and neither side reconstructs decisions from chat history.