Content Design & Product Design an essential duo for product excellence
summary
Mirakl claims a move from delivery-centric to product organization and rebuilds a new design system that includes templates, a responsibility matrix, and slot-based components so copy edits propagate across dozens of mockups. Teams store everything in Figma and use Figma branching for parallel work; content designers place translation keys for cleaner developer handoff. With ~300 marketplaces, 20+ languages, and $900M funding, the change reduces errors, shortens iterations, and makes content work happen earlier rather than later.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:32Product excellence at Mirakl?
- 4:14User experience is no longer a compromise
- 5:00Rebuilding the Design System
- 5:57From a delivery centric organization to a product organization
- 7:02“We are not seen as a blocker in the project”
- 8:48Content design + product design
- 10:48Storing all information + collaborating in Figma
- 14:42Developer handoff
- 15:32Key Takeaways
- 16:51Closing
related talks
14mEmpowering designers: AI, design systems, and quality
42mUnifying Your Product Design Org through DesignOps
18mDesign Systems in Practice
26mA Beautiful Mess: How We Build Products at Figma
22mDesign Systems at Deliveroo: Learnings and Frustrations
19mPlatform Design & Content Strategy
34mDesigners, Developers, Let’s Create the Difference!
28mLet's talk about design systems