01
Category & Format
Define the product category and the most relevant format for the project.
RESEARCH & DEVELOPMENT
A structured pathfrom brief to prototype.
R&D connects product direction with technical decisions. The journey begins by understanding what the project needs, then moves through concept development, ingredient and technology review, sampling, evaluation and refinement.
CONCEPTREVIEWSAMPLEOPTIMIZE
OVERVIEW
R&D starts by defining the right questions.
Before development begins, the project needs a clear technical context. Product purpose, market direction, desired experience and development constraints all influence the pathway that follows.
OBJECTIVE
Product Objective
Clarify what the product is intended to become and the role it should serve.
MARKET
Market Direction
Understand the intended audience, positioning and commercial context.
TARGET
Development Target
Translate the project brief into practical technical priorities.
CONCEPT DEVELOPMENT
Give the product idea a clear technical direction.
Concept development organizes the commercial idea before detailed formulation work begins. It helps align the product category, intended user experience and development priorities.
02
Target Market
Consider where the product is intended to compete and who it is designed for.
03
Product Experience
Identify the intended texture, application experience and overall product character.
04
Business Direction
Keep the technical pathway connected to the wider commercial objective.
INGREDIENT / TECHNOLOGY REVIEW
Review what belongs in the development pathway.
Ingredient and technology review is not simply about creating a long list. It is about identifying what is relevant to the product direction and what information is needed before moving further.
FACTORREVIEW
Function
What technical role should the material or technology support?
Compatibility
How does it fit within the wider formulation and product direction?
Development Fit
Is it relevant to the project objective and intended product experience?
Technical Information
What supporting information is available or required for review?
SAMPLING
Make the direction tangible.
Sampling turns the development direction into something that can be evaluated. Feedback from each sample helps identify what should remain, what should change and what requires further technical attention.
S01Direction
Initial Sample
Establish the first practical interpretation of the development direction.
S02Evaluation
Reviewed Sample
Apply structured feedback and review the resulting changes.
S03Refinement
Refined Sample
Move the development closer to the intended product target.
TESTING & OPTIMIZATION
Evaluate the product against the project direction.
Testing and optimization create a feedback loop between the intended product and the development sample. The purpose is to identify gaps, review relevant characteristics and guide the next technical decision.
DEVELOPMENT REVIEW
Qualitative review against project targets
01
Appearance
Review visible characteristics against the intended direction.
02
Texture
Assess how the sample behaves and feels during application.
03
Sensory Experience
Consider the overall interaction between the product and the user.
04
Project Fit
Review whether the sample is moving toward the defined project objectives.
WORKFLOW
One development journey. Connected stages.
The specific scope can vary between projects, but the R&D journey follows a logical progression from understanding the brief to refining the resulting development.
01Brief
02Concept
03Review
04Develop
05Sample
06Optimize
START AN R&D PROJECT
Have a product concept to develop?
Share the essentials about your company and project. We'll start from your current stage and understand what development support the project needs.