SESH FRAGRANCE ACADEMY | ADVANCED
How do you turn a consumer need into a testable fragrance-development project?
Citrus peel and flesh are different parts of the fruit. Use this as a sensory reference, not a way to infer a formula from a note name.
Translate a consumer need into a measurable, feasible design specification with documented uncertainties and go/no-go criteria.
1. Begin with a problem, not a marketing tagline
An advanced capstone begins with an observed consumer problem. Imagine someone who enjoys a fruity opening but finds the perfume overly sweet after an hour in a confined workplace. Write a problem statement covering user, context, measured complaint and uncertainty. Consider sensory balance, pump dose and application behavior as competing explanations. Do not jump into altering the formula without evidence of the root cause.
2. Develop competing scent concepts
Build competing hypothetical concepts: A, a fresh fruit to soft floral progression; B, restrained fruity gourmand; C, skin-clean musk with a subtle fruit top. Explain the user benefit and likely failure of each. These are sensory architectures, not material formulas. A qualified team may later convert a selected concept into a documented formula after screening risks and technical feasibility.
Linalool contains an OH alcohol group. One functional group is insufficient to predict every molecule’s odour or the performance of a mixture.
Open full-size image ↗3. Score fit, feasibility and uncertainty separately
Create a weighted decision matrix, for example 35% scent identity, 30% contextual comfort, 20% consistency and 15% technical feasibility as a teaching convention. Declare weights before scoring so they do not serve a preferred concept after the fact. Regulatory compliance and safety remain mandatory gates outside the tradeable preference score; excellent aesthetics never compensate for a failed safety requirement.
4. A temporal brief is a useful specification
Replace 'fruity perfume' with an illustrative sensory timeline: fruit 4/5 initially, floral 3/5 and sweetness ≤2/5 at thirty minutes, a soft residual identity at two hours. The numbers are project targets rather than validated consumer performance claims. Specify substrate, dose, sample age, and assessors. Define 'too sweet' operationally so team members do not score different concepts under the same vague label.
5. Scope protects the learning objective
The project ends with a technical development dossier and comparative recommendation, not commercial launch or advertising. Deliverables include a brief, sensory-accord map, traceable theoretical materials plan, testing protocol and compliance checklist. Exclude unsafe home blending, skin testing of neat ingredients, unsupported product safety declarations and invented performance claims. Scope makes the learning outcome auditable.
6. Make an assumptions and evidence log
Maintain a ledger distinguishing confirmed observations, user reports, assumptions and missing evidence. One person's sweetness complaint is evidence of that complaint, not proof that all consumers dislike vanilla. Ask for raw-material and intended-market information before physical development. Transparent uncertainties prevent a concept exercise from claiming to be a validated industrial specification.
7. Stage-gate 1: advance a concept for evaluation
After ranking concepts, select one for further controlled evaluation or revisit the brief. A defensible outcome may be to defer material selection pending supplier documentation rather than guessing. Preserve concept identifiers, date, matrix version and a decisive next test. This is a development handoff, not manufacturing authorization or safety approval.
Case: choose the concept that solves the real complaint
A scores fruit identity 4/5 but sweetness 4/5; B scores 4/5 fruit and 2/5 sweetness; C scores 2/5 fruit and 1/5 sweetness. Against targets fruit ≥3 and sweetness ≤2, only B passes both illustrative sensory conditions. No real stability or safety can be inferred.
Professional practice
Draft a consumer-problem brief with three competing sensory concepts, four weighted criteria and three non-negotiable gates. List uncertainties, reject any mismatched concept with rationale, and select one discriminating follow-up study.
Visual concept maps
From consumer problem to hypothesis
- Complaint and use context
- Three sensory concepts
- Acceptance rules and weights
- Risk and unknowns
- Decision for testing, not manufacture
Illustrative concept decision
- A: fruit4, sweet4
- B: fruit4, sweet2
- C: fruit2, sweet1
- Gates: fruit≥3, sweet≤2
Evidence classification
- Confirmed: verified observation
- Reported: consumer report
- Assumed: assumption
- Missing: absent document
Technical terms
- Stage gate
- Project review gate deciding further testing or revision by predeclared criteria.
- Concept matrix
- Comparison table weighing alternative sensory directions against objectives.
- Technical brief
- Structured statement of use, objectives, constraints and planned validation.
Primary references
Educational technical evaluation, not a safety approval or commercial release.
