Choosing a baby name together should be one of the good parts. In reality, it is often where the first real disagreement of parenthood lives.
One of you loves a name the other has already quietly vetoed. Someone has a family name they feel obligated to use. A name one partner adores sounds, to the other, like someone they went to school with and never liked. And underneath the practicalities is something harder to say out loud: a name carries identity. Suggesting a name is, in a small way, saying something about who you are, where you come from, what you want your child's life to feel like. When your partner rejects it, the rejection can land further in than it should.
This is why agreeing on a baby name is genuinely hard - not because couples are incompatible, but because naming is not a neutral act.
Why comparing lists does not work
The most common approach is the list method. Each partner notes down names they like, you compare, you look for overlap. It works, sometimes. But it has a structural problem: a list tells you which names you both like in isolation, not which names you both want for the same reasons.
You might both circle the name Rowan, but one of you loves it because it is nature-rooted and calm, and the other loves it because it sounds strong and modern. Those are compatible instincts, as it happens - but they might not always be. Two partners can converge on the same name from completely different places, and end up in an argument six months later about a different name that exposes the gap in their underlying values.
What couples actually need is not a shared list. It is a shared understanding of what they each care about in a name - and a process that builds from that shared understanding outward.
What makes naming conversations go wrong
A few patterns tend to derail the naming conversation between partners.
The veto spiral is the most common. One partner suggests names, the other rejects them, and eventually the person suggesting feels deflated and stops offering. The conversation stalls because one side has nothing left to propose and the other has only been in the position of saying no.
The obligation deadlock happens when one partner feels strongly that a family name - a grandparent's name, a name with cultural or generational significance - should be used, and the other feels equally strongly that it should not. This one is less about the name and more about what honouring the name means, and those conversations need to happen explicitly, not through the naming discussion itself.
The taste gap is subtler. You simply discover, mid-process, that you have fundamentally different instincts about what a name should feel like. One of you wants something classic and rooted; the other wants something distinctive and unexpected. Neither instinct is wrong - but without acknowledging the gap, you will keep talking past each other.
A better way to approach it together
The most useful reframe is to start with values before you start with names. Before either partner names a single name, talk about what matters to you in a name. Not which names you like - what kind of name feels right. Should it be easy to spell? Does heritage matter to you? How do you feel about names that are very well-known versus names that are genuinely unusual? Does the name need to work in a specific cultural context?
When you have mapped that first, you have something to compare that is more durable than a list. You might find your instincts are more aligned than you expected. You might find the gap, and be able to talk about it honestly before it becomes a source of friction.
How findaname.app approaches this
The partner-sharing feature in findaname.app was built specifically for this problem. When you take the quiz, you answer ten questions about your own naming instincts - sound, style, heritage, length, meaning, how the name needs to sit with your surname. Your partner takes the same quiz independently. The AI then generates names built around both sets of inputs, not just one.
The result is not a Venn diagram of two separate lists. It is a set of names that emerge from both of you - names that the process itself has already filtered against both partners' preferences, before you have to have a single negotiation. You are not comparing names in a vacuum. You are looking at names that already belong, in some sense, to both of you.
It also removes the veto spiral, because neither partner is proposing names for the other to accept or reject. The names arrive as a shared output. The conversation shifts from 'do you like this name?' to 'how do you feel about this name?' - which is a more open and less loaded question.
The part the tool cannot do
No quiz can resolve a genuine disagreement about family obligation, or help one partner process why a name carries difficult associations. Those conversations need to happen between the two of you, in whatever way works for your relationship.
What a shared, personalised process can do is remove the friction from the parts of naming that do not need to be hard - and give you a foundation of names that already fit both of you, so that when you do have to negotiate, you are negotiating from a smaller, better set.
Agreeing on a name is one of the first things you will do as parents together. It is worth doing thoughtfully.
If you want to find names that feel right for both of you, the quiz takes about three minutes each - and you can share your results directly with your partner.