Volume 05, Chapter 2
When Should a New Pattern Be Created?
Definition
Imagine a customer asks for a distinctive collar style once, and the tailor cuts it straight onto the fabric from a quick sketch, no pattern made. Eighteen months later the same customer wants it again. Nobody who worked on it the first time is even sure exactly how it was built. It takes three expensive attempts to recreate what a single pattern, made at the time, would have preserved for free.
A new pattern should be created whenever a design has value beyond a single order, the moment there's a real chance it will be needed again, in roughly the same form.
The rule of thumb: if you think you'll ever sew it again, make a proper pattern. Not every order deserves one, a genuinely unique, never-to-be-repeated request doesn't need the overhead of a full pattern. But erring toward "just this once" is how businesses end up remaking the same design from a sketch, or from memory, over and over, quietly paying Chapter 1's whole cost every single time.
The Decision, as a Simple Test
| Ask | If Yes → Make a Pattern | If No → A Sketch or Note May Be Enough |
|---|---|---|
| Could this exact design be ordered again by this customer? | ||
| Could this design suit other customers with similar bodies or tastes? | ||
| Did this design take significant time or skill to get right? | ||
| Is this design part of a standard collection or catalogue? | ||
| Is this truly a one-time, never-repeated request (e.g., a costume for a single performance)? |
If even one of the first four is true, the time invested in a proper pattern will very likely be repaid. This is really a small, physical version of Volume 07's capital-vs-profit lesson: the time spent making a pattern is an investment, recovered, with interest, every time it's reused.
When in doubt, make the pattern. The cost of an unnecessary pattern is small. The cost of remaking a needed one from scratch, repeatedly, adds up silently for years.
What Triggers a New Pattern (Not Just a Variation)
A closely related question: is this a new pattern, or a variation of an existing one? Getting this wrong clutters the pattern library with near-duplicates, or, worse, quietly overwrites a master pattern that other orders still depend on.
| Situation | New Pattern, or Variation? |
|---|---|
| A genuinely different garment style (e.g., a new jacket cut) | New pattern |
| The same jacket, different customer body measurements | Variation via grading (resizing the pattern) and alterations, not a new pattern |
| The same jacket, a structurally different sleeve or collar style | New version of the existing pattern (Chapter 5) |
| An entirely different garment category (e.g., first-ever trouser design) | New pattern |
Example Story: The Sketch That Should Have Been a Pattern
A regular MANIAC MINDZ customer requested a distinctive collar style for a special event, sewn once from a quick sketch and cut directly on the fabric. Eighteen months later, the same customer wanted it again, and a completely different tailor had to reconstruct the collar from a fading photograph and the customer's imperfect memory of "what it felt like."
It took three attempts to get right the second time, at real cost in fabric and labour, costs that a ₦0 pattern-making step, taken the first time, would have avoided entirely. The lesson became a standing rule: any request from a repeat customer defaults to becoming a real pattern, unless there's a specific reason to believe it truly is one-of-a-kind.
Across Industries
| Business | A Design Worth Patterning | A Genuine One-Off |
|---|---|---|
| Golden Crust Bakery | A new standard bread recipe added to the daily lineup | A single custom cake for one wedding, unlikely to be requested identically again |
| Precision Print & Press | A repeat client's standard letterhead layout | A one-time commemorative flyer for an event that won't recur |
| Nimbus Labs | A reusable login/authentication module | A one-off data migration script used only once |
Common Mistakes
The exact failure in the example story. Popularity is precisely the signal that a pattern is worth making, not a reason to skip it.
A structural change to a design used elsewhere should create a new version (Chapter 5), never silently replace the original, other orders may still depend on it exactly as it was.
The opposite failure: over-formalizing a genuinely unrepeatable request wastes time the business could spend elsewhere. The test in Section 2 exists to prevent both mistakes.
Quiz Yourself
Practice Exercise
- Look back at your last ten custom orders. Run each through Section 2's test.
- For any that should have become a pattern but didn't, note what it would take to reconstruct that design today.
- Set a standing rule for your team: what's the default answer when a tailor isn't sure whether to pattern a new design?
Quick Summary
Quick Summary
- Create a new pattern whenever a design has value beyond a single order, the rule of thumb: if you'll likely sew it again, pattern it.
- Distinguish a new pattern (different design) from a variation (same pattern, different body, see Chapter 3) from a new version (structural change to an existing design, see Chapter 5).
- The time spent making a pattern is an investment, repaid every time it's reused, the cost of skipping it compounds silently.
- Over-patterning genuine one-offs is the opposite, smaller mistake, the test in Section 2 guards against both.