For design managers

How do you turn trend intelligence into a seasonal design brief?

Short answerA seasonal design brief is built by extracting one decision from each stage of the trend analysis: the driver behind each story, where it sits on the adoption curve, the window it must ship in, the market it applies to, how many options it carries, and the product-level colour, material and detail evidence to start from. Everything that is context rather than decision stays out.
Last updated 7 min readBy F-Trend

The problem

The forecast we buy runs to sixty pages. The brief my team can actually work from is two. Deciding what survives that cut is the hardest thing I do each season, and I am fairly sure I get it wrong in both directions.

Design manager, multi-category lifestyle brand

A brief that is too thin sends designers back to research, which is how a team ends up doing trend work twice. A brief that is too thick gets skimmed, and a skimmed brief produces a range assembled from whichever pages happened to be memorable. Both failures look like a design problem later and are actually a briefing problem.

The method

The compression rule that works: a brief carries decisions and evidence, not analysis. Analysis is how you arrived at the decision, and it belongs in the appendix nobody reads — which is fine, because that is what an appendix is for. Each of the six stages yields exactly one line for the brief.

  1. What is the one-sentence reason this story exists?

    Every story in the brief needs its driver stated in one sentence. Not the mood, not the name — the reason it is happening now. This single line does more work than any other part of a brief, because it is what lets a designer make a judgement call you did not anticipate and still land in the right place.

    What to look at

    • Write it as a shift: from something, toward something.
    • If it takes more than a sentence, the story is two stories.
    • Avoid names that describe an aesthetic rather than a cause — they read as instruction and produce pastiche.
  2. How new does this need to feel?

    Adoption stage tells the designer how far to push. An early-adopter direction should feel unfamiliar in the range and should be executed with conviction. An early-majority direction should feel confident and legible, and pushing it hard makes it look like you arrived late and overcompensated.

    What to look at

    • State the stage explicitly per story — not for the season as a whole.
    • Translate it into an instruction: lead, match, or execute cleanly.
    • Say which existing option each story sits next to, so newness is calibrated against the actual range.
  3. What is the window?

    Timing belongs in the brief because it changes what a designer should attempt. A story with a long runway can carry new construction and development risk; a short-window story should be executed in an existing block with a new colour and fabric. Designers routinely get this wrong when nobody tells them, and it is not their error to make.

    What to look at

    • Give the window in weeks against your calendar, not as a season name.
    • Mark each story explicitly as new development or carry-over refresh.
    • Flag anything where the window is shorter than your cycle, so nobody starts it.
  4. Who is this range for, and where?

    One line naming the market, the consumer and the occasion structure. This is the line most briefs assume rather than state, and the assumption is where multi-market ranges quietly go wrong — a brief written from one market’s evidence gets executed for all of them.

    What to look at

    • Name the market and, where relevant, what is different about it — climate, calendar, occasion mix.
    • Where a story is regional rather than global, say so on the story, not in a footnote.
    • Note the price architecture, because it constrains every make decision downstream.
  5. How big is each story?

    Option counts per story, and the split between carry-over and new development. This is the line that turns a brief from inspiration into a plan, and it is the one most often left out because it feels like merchandising’s job. It is not — a designer who does not know whether a story is three options or twelve cannot size their thinking to it.

    What to look at

    • Give a count or a range per story, and the categories it spans.
    • Mark which options are already in the range and being refreshed.
    • Say what the story replaces, so the range does not simply grow.
  6. What can they start from on Monday morning?

    The concrete half: colour with references, materials and trims with a reason attached, prints, and the details, proportions and constructions the direction implies. This is the bulk of the two pages and should be specific enough to open a supplier conversation and loose enough to leave the design to the designer.

    What to look at

    • Colour with Pantone references, grouped by story rather than in one flat row.
    • Materials named with the driver behind them, so substitution decisions can be made intelligently.
    • Details and proportions as direction, not as drawings — a brief that draws the product has stopped being a brief.

How F-Predict answers this

ScopeSS27 · Womenswear · Dresses · India · emotion: joy, anticipation

A F-Trend Predict run maps onto the brief almost line for line, which is the practical argument for evidence-led forecasting: the output is already organised by decision rather than by chapter.

Consumer map
The driver sentence for each story — the shift, stated as from-and-toward rather than as a mood.
Street trends & narrative intelligence
Adoption stage and velocity per story, which become the "how new should this feel" and "what is the window" lines.
Regional scope
Evidence gathered in India specifically, including the festive and wedding calendar that drives dress demand — the market line, with something actually in it.
Range architecture
Stories, option counts and the carry-over versus new-development split, which is the size line for each story.
Colour direction
Themes with Pantone TPX references grouped per story, ready to become the brief’s colour page.
Design intelligence & design board
Silhouettes, details, trims and prints as product language, plus generated boards for the visual half of the brief.

The same decision from another desk

The six stages are the same across roles; what changes is what each stage means when you are the one making the call.

What to leave out

  • The reasoning. Keep the conclusion and the evidence; move the argument to the appendix.
  • Rejected directions. Useful in a review, actively harmful in a brief — designers will read them as options.
  • Macro-cultural framing that does not resolve into a product decision. If it cannot change a garment, it is context.
  • Competitor imagery. It sets a ceiling and produces recognisably derivative work.
  • Anything you would not defend if challenged. A brief is a set of commitments; padding it dilutes the parts that matter.

Frequently asked

How long should a seasonal design brief be?

Two pages per story is a workable ceiling, with an appendix of evidence behind it. Length is not the real measure — whether every line changes a decision is.

Should the brief include imagery?

Yes, as direction rather than as reference. Boards that show finished product from elsewhere get copied; boards that show material, colour, proportion and context get interpreted.

Who should write the brief?

Whoever will defend it. Briefs written by someone who will not be in the review tend to hedge, and a hedged brief is one a team cannot act on.