You love Iris. Your partner wrinkles their nose. Your partner suggests Rafferty. You can't quite say it with a straight face. You've been at this for three weeks and the list on your phone is longer than it was when you started.
This isn't stubbornness. It's not that one of you has bad taste. It's that you're both trying to solve the problem the same way - by scrolling through names and reacting to them - and that approach surfaces preferences without ever revealing what's underneath them.
The real problem isn't the names. It's that you don't yet know what you both actually want.
You're not disagreeing about names. You're disagreeing about instincts.
When your partner says no to a name you loved, they're rarely reacting to those four or five letters in isolation. They're reacting to a feeling. Too old-fashioned. Too common at nursery. Too tied to someone they knew at school. Too soft, too sharp, too everything.
And you're doing the same. You just can't see each other's reasoning because names-as-a-list doesn't show it.
This is the structural flaw in the way most couples approach naming. You start with names and try to find agreement. But agreement on a name is much harder to find when you haven't first found agreement on what you're looking for.
A couple who both want something grounded, slightly old-world, and easy to say in a northern English accent will find their overlap quickly once they know that about each other. A couple where one wants bold and unusual and the other wants familiar and timeless - that's a real tension, but it's a solvable one once it's named.
The conversation most couples need to have isn't 'what about this name?' It's 'what does a good name feel like to us?'
Why the shared shortlist doesn't work
The classic approach is a shared list. You both add names. You veto each other's suggestions. You circle the survivors. It feels productive because you're generating data. But it's a fairly brutal process, and it tends to surface conflict rather than common ground.
Every veto can feel like a small rejection. Every name you love that gets a flat 'no' leaves a trace. After a few rounds of this, the list stops feeling like a collaboration and starts feeling like a negotiation - and naming your child should not feel like a negotiation.
There's also a subtler problem: shared lists pool your preferences together before you've each had space to form them clearly. You influence each other from the start. If one of you mentions Nell early on, it colours the conversation. You're no longer arriving independently at what you want - you're reacting to each other's suggestions and losing the signal underneath.
What actually helps: taking the quiz separately
The approach that tends to work better is the one that gives you each space to think first, then finds where you converge.
This is what the partner-sharing feature at findaname.app is built on. Rather than presenting you with a shared database of names to swipe or veto together, it asks you each a series of questions independently - about sound, feeling, heritage, what matters to you in a name - and generates names from your individual answers. Then it shows you where your results overlap.
What comes back isn't a compromise. It's common ground you didn't know existed yet.
Some couples find their overlap is wider than they expected. Others find it's narrow but clear - there's one or two names that genuinely emerged from both of their instincts, and those names tend to stick immediately. A name that comes from that overlap doesn't need to be defended or negotiated. It just fits.
A name like Rowan, for instance, can emerge for two people with quite different instincts - one drawn to gender-neutral names with natural roots, one drawn to names that feel grounded and quiet without being dull. Neither of them had it on their list. But it comes from both of them, and that feels different.
When you're still stuck
Sometimes the quiz surfaces the disagreement more clearly rather than resolving it immediately - and that's useful too. If your generated names point in completely opposite directions, you at least know what you're working with. You're not stubbornly attached to different names. You have genuinely different naming instincts, and the next step is a conversation about what you're each actually looking for, not a longer list.
That conversation - 'I want something that feels timeless and you want something that feels distinctive' - is a much more productive starting point than 'I like Felix and you hate it.'
Most couples who have it find the path to agreement quite quickly afterwards. Not because one person gives in, but because you can see clearly what a name would need to do to satisfy both of you - and you can look for that, together.
A note on timelines
The pressure of a due date makes this harder. When you're 34 weeks in and still without a name, the emotional weight of every conversation increases. Both of you can feel the urgency, and urgency tends to make people dig in rather than open up.
If you're in that window, it helps to step back from the list entirely for a day or two and approach it fresh, separately, then bring your answers together. The quiz at findaname.app takes about three minutes each - it's a low-stakes way to start that conversation from a different angle.
The names that feel like yours tend to arrive that way: not from a list you've been negotiating for weeks, but from somewhere that already knew what you were looking for.
If you want names that come from both of you, not a list you're whittling down, the quiz takes about three minutes - and you can share it with your partner to take independently, then compare.