The factory already has the record

The first three notes were written from the house's chair: how to read a vendor's evidence, what record the technology has to run on, who is allowed to say no. This one is written from the other side of the table, because I have sat there. [One or two sentences: the family factory, what it made, for whom, over what period, and the years you ran it. Name the category and the kind of client, not the client.]

Luxury houses buy technology for their product in the belief that it stops at their own walls. It does not. A product lifecycle system, a digital-sampling mandate, a supplier portal, a specification drafted by a model: each one arrives at the factory as a new way of being asked for the same things, and a new place to type them.

What a rollout looks like from the receiving end

[The core of the note. Choose one technology decision a client house made that landed on your factory. Describe it as a sequence: what the house announced; what arrived at the factory and when; what your team had to do differently; what it cost in hours, software, re-keying or delay; and what the house measured, if anything. Three or four short paragraphs. Keep the house unnamed and the category true.]

[If you have a second, shorter instance of a different kind, give it in one paragraph here: for example a supplier portal that duplicated the email thread rather than replacing it, or a 3D sample that still needed a physical one for hand and drape.]

The pattern I saw, more than once, was that the house's project finished at go-live and the factory's project started there. The vendor's case study reached "delivered". Our side of it never reached a rung, because nobody was counting.

Rung five lives at the factory

The ladder in the first note ends at "worth the cost". A house computes that against its own licence, its own staff time and its own returns. The costs it does not see are the ones it has pushed down the chain.

[List the costs that landed on your factory and never appeared on any house's business case. Be concrete: double entry between the house's system and your own; sample rounds added because the digital version was approved and the physical one was not; translation of a house's data fields into what a knitting technician actually needs; software your factory had to buy or subscribe to in order to supply one client; time spent reconciling two versions of a tech pack. Give at least one number: hours per season, extra sample rounds, a subscription cost, a lead-time effect.]

Those costs do not disappear. They come back as price, as lead time, as a factory quietly favouring the client whose systems are easier to work with, or as a supplier who stops bidding. A business case that leaves them out is not cautious; it is incomplete, and incomplete in the direction that flatters the purchase.

The record was already there

The second note argued for one versioned product record beneath every function. Here is what houses tend not to know: for a knitted product, most of that record already exists, and it exists at the factory.

[What your factory held for every style, and in what form: yarn supplier and lot, count and composition, gauge and machine, stitch density, the knitting programme, lab dip and shade approval, wash and finishing recipe, the care result from testing, measurement charts by size, the reason a particular seam or panel failed in wear. Say where it lived, who maintained it, and which of it any client ever asked for.]

The house's product record, when it had one, was a thinner copy of ours, re-typed by someone who had not seen the yarn. When a system was introduced to hold the record, it was introduced on the house's side, and we were asked to fill it. Nobody asked what we already had, or whether it would be cheaper to connect to it than to replace it.

The practical implication is awkward for anyone buying software. Before paying for a product record, ask your suppliers what they already keep, in what form, and what it would take to get a clean copy. [If you ever gave a client that copy, or were refused when you offered, say so in a sentence.]

The ladder, applied to my own decision

I have asked houses to read their technology on the evidence. It is fair to ask the same of me.

[One technology decision you made in your own factory, read on the five rungs. What you bought or built, and why. Whether it was delivered as sold. Whether your team was still using it six months later, without being told to. What improved, against what comparison. What it cost after the time it took, and whether it was worth it. End with the number that decided it. If the honest answer is that it was not worth it, say so; that is the most credible paragraph in the series.]

What a house should do with this

Three things, none of which requires buying anything.

Count the supplier's cost in the business case. Ask the factory what the change will cost them per season, and add it to yours. If they cannot say, the rollout is not ready.

Ask for the record before you buy one. For your top styles, ask your suppliers what they already hold and in what form. The gap between that and what you need is the real scope of any system.

Put the factory in the pilot. A pilot that measures the house's screens and not the factory's hours has measured half the change. The stop rule should include a supplier signal: [name the one you would use, from your own experience].

The series began with a question for the house: before you buy the technology, what does it have to prove? From the factory's side the question is the same with one word added: what does it have to prove, and to whom?

---

---

Sources