How it happens today
The launch lives in a spreadsheet and many email threads. Each team updates its part when it remembers, and dependencies, such as notifications needing final INCI lists, are tracked in someone's head.
Systems and information
- · Project or task management tool
- · Shared document storage
- · Email and calendar
- · Product information or PIM system (where it offers an API or export)
How it could flow
- 1 Launch milestones and dependencies are set out once, for example final formula, stability results, artwork approval, notifications, retailer data and content.
- 2 Owners receive reminders ahead of each due date.
- 3 When a document such as a test report or approved artwork arrives, the related task is updated and the file stored in the right place.
- 4 Delays are highlighted alongside the tasks they affect downstream.
- 5 A weekly launch summary goes to the brand director, with access limited to the launch team and changes logged.
Human oversight
The brand director and regulatory lead decide when the product is ready to launch in each market. The system tracks status; it does not sign off safety or compliance.
What gets easier
Everyone can see where the launch stands, and delays become visible while there is still time to adjust.