Over the holidays, I asked myself:
What does “multilingual” actually mean when we build products, communities, or workplaces across Europe?
We often default to English and call it a day. I’ve done that myself for years. My own mental default, though, is still French - especially in moments of reflection.
Exploring multilingual experiences forced me to revisit my own path, in HR and as a founder. What happens when language is treated as part of the experience, not as an added layer?
To look at this properly, I’m running a 6-week sprint using Sunny Future’s principles - goal-oriented, focused, with a bias to shipping.
A few things are materially useful already:
- spoken content travels differently than written content
- language choice shapes who engages, and how
- small design decisions compound fast within clusters
I built my first concrete automation: turning written text PDFs into English, French and Spanish audio files, using my own voice. That changed how I think about reach and participation.
We’re now testing what comes next: more languages, new use cases, and live sprint support.
If this is something you’re thinking about too, I’ve written a short playbook on language design (using n8n, DeepL, ElevenLabs).
DM me if that’s useful.
A short sprint on multilingual experience design.
15 January 2026
