The Technical Brief Behind a Strong Fashion Collaboration

Collaborations are announced on concept and delivered on process. The concept is usually fine. The process is usually improvised, and that is where the product gets worse.

A collaboration doubles the number of people who can say no, doubles the standards the product has to clear, and adds a set of brand questions — whose label, whose colour, whose fit — that a single-brand programme never has to answer.

None of that is difficult. All of it is difficult if it is decided while samples are already being made.

What a collaboration brief has to contain

Beyond the normal product brief, six things are specific to working with two names.

1. Named decision-makers, one per side

Not a committee, not a distribution list. One person per partner who can approve materials, colour, decoration and fit, and whose approval is final within their organisation.

This single item removes more delay than anything else on the list. Most collaboration slippage is not manufacturing time — it is the gap between a sample landing and a decision arriving.

2. A fixed comment window per gate

Each approval gate gets a deadline: samples arrive Monday, consolidated comments due Friday. One consolidated sheet per partner, not a thread of individual opinions.

If comments are late, the launch date moves. Stating that at the brief stage is uncomfortable and considerably less uncomfortable than discovering it in week nine.

3. A co-branding standard, agreed before sampling

Which mark goes where, at what size, in which technique, on which colourway, on which label. One page, both signatures, applied consistently.

The alternative — negotiating branding per style as samples arrive — produces a range where the balance shifts from garment to garment, which reads as indecision.

4. Whose fit block

A collaboration between a sports property and a fashion label involves two different fit philosophies. Someone has to own the block.

The usual right answer is whichever partner's customer is buying, but the answer matters less than making it explicit. Unstated, it gets resolved in fit comments, style by style, badly.

5. Whose quality standard applies

Both partners have expectations about construction, finishing, testing and acceptable defect rates. They are rarely identical, and they are almost never written down in the same document.

Agree the higher standard, in writing, before sampling. Discovering a difference in acceptable defect levels at final inspection is an expensive way to learn it.

6. A shared calendar with the long poles marked

Fully fashioned knitwear, garment dyeing, custom hardware and custom trims all have long lead times. Woven labels and packaging have their own, and they are the items most often forgotten until the goods are boxed.

One calendar, both partners, with the critical items visible. Everything else is built to meet them.

The product decisions that follow

With those six settled, the product brief itself becomes ordinary — and can be answered properly:

• Style count and price ladder. Set before design. A collaboration is usually better small and complete than broad and thin.
• One material story. The strongest collaborations share a fabric or finish idea across categories, which is what makes them read as one collection rather than two brands' products in the same box.
• Categories each partner is credible in. A sports property bringing a knit and a fashion label bringing outerwear is a better division than both trying to do everything.
• The one object that only exists because of this collaboration. Every good collaboration has one piece that makes no sense without both partners. It is usually the piece that gets photographed.

Where collaborations actually break

Three failure modes account for most of them.

Approval drift. Comments arrive from people who were not in the brief, late, contradicting earlier decisions. Prevented by decision rights and comment windows.

Late co-branding changes. A legal or brand review that lands after decoration is approved, forcing re-trials on every style. Prevented by getting the co-branding standard through review before sampling starts.

Calendar built backwards from a launch date. Someone picks a launch, works backwards, and arrives at a knitwear development window of three weeks. Prevented by building the calendar forwards from the longest lead item and being honest about where it lands.

Discretion and credit

Two administrative points worth settling at brief stage, because they are awkward later.

Credits. Who is named, in what order, in what contexts — retail, press, packaging, social. Written down.

Confidentiality. What each side may show, and when. Collaborations frequently involve a party who cannot be publicly associated with the work, including the execution partner. That should be a stated position rather than an assumption.

A workable sequence

1. Written creative direction from both partners, reconciled into one product brief.
2. Decision-makers, comment windows, co-branding standard, block owner and quality standard agreed.
3. Calendar built forwards from the longest lead item.
4. Material and colour approvals.
5. First prototypes, one consolidated comment round per partner.
6. Fit samples and decoration trials on production fabric.
7. Sealed samples, both partners.
8. Production, inline checks, final inspection to the agreed standard.

Eight steps, and the first two are where the collaboration is actually won.

The uncomfortable truth

Most collaborations that disappoint were not badly designed. They were well designed and then executed through a process that nobody owned, in which every decision took a week longer than it should have, and the final compromises were made by whoever was still awake.

The brief above is not a creative document. It is the thing that lets the creative document survive contact with a factory.