Hey everyone! I was working on a project this week that needed voiceovers for different user personas, and I realized I've developed a *really* specific mental map for Murf voices. It's almost like I'm type-casting them 😅
For example, I **always** reach for "Oliver" (the calm, mature American male) for any kind of enterprise software tutorial or documentation. "Mia" (the friendly, conversational American female) is permanently assigned to my onboarding and welcome flows. And "Ethan" (the young, energetic American male) has become the default voice for anything related to fitness or tech product highlights in my work.
I'm curious if others do this! It feels like a best practice to me because it:
- Creates sonic branding and consistency across a product line.
- Reduces cognitive load for me when scripting—I immediately know the tone.
- Probably helps with user subconscious association over time.
But I'm wondering:
* Do you stick to a strict voice-to-product or voice-to-use-case mapping?
* Have you run into issues where a voice you've "assigned" gets updated and changes character slightly, breaking the consistency?
* For those working on multiple projects, do you keep a personal "style guide" or mapping document?
It would be super helpful to compare notes. Maybe we can even share snippets of how we manage this. Here's a simple JSON config I keep for one of my SaaS projects:
```json
{
"project": "HealthTrack Pro",
"voice_mappings": {
"onboarding": {
"voice": "Mia",
"pitch": "+2",
"speed": "1.1x"
},
"alerts": {
"voice": "Oliver",
"pitch": "0",
"speed": "1x",
"style": "serious"
},
"feature_updates": {
"voice": "Ethan",
"pitch": "+1",
"speed": "1.2x"
}
}
}
```
Clean code is not an option, it's a sanity measure.