You have probably had the conversation already. One of you floats a name you love, and the other makes a face. Or worse - one of you has a family tradition in mind, a name that has been passed down through generations, and the other feels nothing for it at all. No warmth, no pull. Just a polite but definite no.
This is one of the most common places couples get stuck. And it is not really about the names.
It is about what names mean.
When one partner wants to name a baby after a father, a grandfather, a whole line of men who carried the same name, they are not just choosing syllables. They are choosing continuity. They are saying: this child belongs to something. When the other partner resists, they are not being difficult. They are saying: this child is also their own person. Both of those feelings are completely valid. Neither of them is wrong. But they pull in opposite directions, and a list of names on a baby name website is not going to resolve that.
A thread on r/BabyBumps this week captured this exactly. A woman posted about her husband wanting to name their son a III - a third-generation name, following grandfather and father. She did not want it. Not because she disliked the name itself, but because she wanted their son to have something of his own. The comments were full of people who had been in the same conversation: one partner weighted toward tradition, the other toward individuality, both unable to move because the disagreement was never really about the name on the list.
This is the kind of naming conflict that cannot be solved by scrolling.
Why couples get stuck
Most naming tools assume that you and your partner have roughly similar taste and just need a broad enough database to find the overlap. Filter by letter, filter by origin, scroll until something feels right. But that model only works when the gap between you is stylistic - when one of you likes classic names and the other likes modern ones, and somewhere between Oliver and Ezra is a name you both smile at.
It breaks down when the gap is about values. About what naming a child actually means to each of you.
Generational names are the clearest example, but they are not the only one. Some partners feel strongly that a name should honour a culture or heritage. Others feel just as strongly that it should not carry expectations. Some want a name nobody else has. Others want a name that has been loved for centuries. These are not matters of taste. They are matters of identity.
And when you are both sitting with a list of names, neither of you can see the other's reasoning. You just see the nos.
What changes when you start with questions instead
The thing that breaks a naming deadlock is not finding the right name. It is understanding what each of you actually needs from a name - and realising that those needs, once named, are often more compatible than they seemed.
The couple in that r/BabyBumps thread were not fundamentally incompatible. He needed the name to carry family meaning. She needed the name to feel like their child's own. A name that honours a grandfather without directly repeating his name - a name that shares an origin, a sound, a first letter - can hold both of those things. But you only find that name once you have understood what you are each looking for.
That is the logic behind findaname.app's partner quiz. Rather than presenting a database to filter together, it asks each of you ten questions separately. Questions about feeling, not style. What matters to you in a name. What you want it to carry. What you want your child to feel when they grow into it. You each answer independently, and then your responses are brought together.
What comes out is not a compromise list. It is a set of names generated specifically from where you overlap - built from the values and instincts you share, even when you did not know you shared them.
For a couple navigating a generational naming conflict, that process can surface something neither of them would have found alone. A name with genuine family resonance that does not come with the weight of a suffix. A name with a shared root or a similar sound that honours the tradition without repeating it. Something that is theirs.
The conversation is different when you arrive at a name that was made for both of you
There is a particular kind of tiredness that comes from arguing about names. You stop suggesting things you actually love because you already know they will be knocked back. You start holding your real favourites back, not wanting them to become casualties of another disagreement. The list gets smaller and more cautious, and neither of you is fully in it anymore.
Starting with questions instead of names changes that. You are not negotiating from entrenched positions. You are discovering what you have in common before a name is even on the table. That shared discovery is a genuinely different conversation.
It does not guarantee you will agree on everything. Naming is intimate and personal, and sometimes one partner simply needs more time with a name before it becomes real. But it gives you something to work from together, rather than two separate wishlists pulling against each other.
If you are in the middle of a naming disagreement right now - whether it is about tradition, individuality, heritage, or just completely different taste - it is worth trying a different kind of process. Not a longer list. A better set of questions.
The quiz at findaname.app takes about three minutes each. You both do it separately, then share your results. The names it generates come from where you meet, not from where you differ. That is a better place to start.