You love Arlo. They love Theodore. You both feel strongly. Neither of you is wrong. And yet here you are, weeks or months into this conversation, no closer to a name you both actually want.
If that sounds familiar, you are not dealing with a compatibility problem. You are dealing with a structural one. And that distinction matters, because it changes how you solve it.
Why couples get stuck - and it's not about taste
Most couples approach baby naming the same way: one person suggests a name, the other reacts to it. You fire names across the table, or send lists back and forth, and slowly a pile of vetoed options grows on both sides. After a while, the whole thing starts to feel personal. You liked Iris and they said no. They liked Jasper and you pulled a face. It stops being about the name and starts feeling like a referendum on your taste, your personality, your whole approach to parenting.
But here is the thing. When your partner says no to Iris, they are almost never reacting to the name in isolation. They are reacting to an association - a girl at school, a character from a film, a feeling they can't quite articulate. And when you say no to Jasper, you are doing the same thing. You're both responding to a web of meaning and feeling that has nothing to do with whether Iris or Jasper is objectively a good name.
The problem isn't that you have different taste. It's that you are each working from a completely different internal map - different associations, different instincts, different unspoken criteria - and you have never actually compared those maps.
The list approach doesn't fix this
Sending each other a list of twenty names feels productive. It rarely is. A list is just a queue of reactions waiting to happen. You're still in the same cycle: suggest, reject, feel slightly defeated, repeat.
What actually breaks the cycle is stepping back from individual names and getting to the level underneath them. What kind of name do you each actually want? Not "I want Arlo" - but what does Arlo represent to you? It's short, it feels warm, it travels well, it doesn't feel dated. And what does Theodore represent to them? It feels substantial, it has history behind it, it has a good nickname, it sounds like it belongs on someone who'll be taken seriously.
When you look at it that way, Arlo and Theodore aren't that far apart. You're both looking for something with warmth and weight. The disagreement was never as deep as it felt.
Getting to the real conversation
This is exactly the problem that findaname.app's partner sharing mechanic was built around. Rather than starting with a list of names to react to, both of you take a short quiz independently - questions about feel, sound, meaning, heritage, what matters most to you. The quiz surfaces what you actually care about, not just the names you happen to like. Then you share your results, and the tool generates names that sit in the overlap.
Instead of starting from opposing corners with lists, you start from a shared understanding of what you're both looking for. That is a genuinely different conversation.
It doesn't mean you'll agree on the first suggestion. But it means you'll be disagreeing productively - about real preferences, not accidental associations.
When one of you is more invested
Sometimes the stalemate isn't about having different values - it's that one partner is far more engaged in the naming process than the other. One of you has a shortlist of forty names and strong opinions. The other keeps saying "I don't know, what do you think?" and meaning it.
This creates a different kind of stuck. The more engaged partner starts to feel like they're carrying the decision alone. The less engaged one feels quietly guilty, or pressured into enthusiasm they don't quite feel.
If this is you, the quiz format helps here too - not because it forces enthusiasm, but because it gives the less engaged partner a structured way to input without having to generate opinions from scratch. Answering eight or ten specific questions is much more accessible than "just tell me what kind of names you like."
On names you both love for different reasons
Here is something worth knowing: it is completely fine to love the same name for completely different reasons. You might love Rosamund because it feels old and literary and unhurried. Your partner might love it because it sounds strong and can shorten to Ros. Those are different reasons. The name is still Rosamund.
You don't need to be in complete alignment about why a name is right. You just need to both feel, independently, that it is.
A note on the veto dynamic
If your naming conversations have started to feel like one person holds veto power and the other is always auditioning names for approval, it is worth naming that dynamic explicitly. The veto approach tends to favour the person with stronger negative reactions over the person with stronger positive ones. That's not fairness - it's just whoever says no loudest.
Try flipping it. Instead of reacting to each other's suggestions, each make a shortlist of the names you feel genuinely positive about, without seeing the other's list first. Then compare. You might find more overlap than you expected - because you're starting from what you want rather than what you're trying to avoid.
The goal isn't a compromise - it's a name you both love
A compromise name is one where both of you gave something up. You don't want that on someone's birth certificate for their whole life. You want a name that both of you feel, when you say it out loud, is the right one.
That name exists. You just haven't found the right way to look for it together yet.
If you want to find names that feel right to both of you, the quiz takes about three minutes each - and you can share your results directly with your partner.