AITA For backing out on an agreement my husband and I made years ago regarding potential kid names?

For over a decade, this couple thought they had their future neatly planned out, at least when it came to baby names. Married for 11 years and already parents to two daughters, they believed they had reached a fair compromise long ago. She would take the lead on naming their girls, and if they ever had a son, he would carry on his father’s name, continuing a family tradition that meant everything to her husband.

That agreement felt simple back then, almost theoretical. But once reality hit and an ultrasound confirmed their third child was a boy, everything changed. What followed was an emotional whiplash that drained the joy from a moment meant to be celebrated. When this story hit social media, reactions were swift, intense, and surprisingly unified, with many readers questioning trust, timing, and what it really means to keep your word in a marriage.

AITA For backing out on an agreement my husband and I made years ago regarding potential kid names?

What seemed like a settled plan resurfaced the moment a long-awaited ultrasound brought unexpected clarity

My husband (38M) and I (37F) have been married for 11-years and have 2 daughters (8 & 4). I am currently 12-weeks pregnant with our third child.

I just had an ultrasound and we were able to determine the s__ of the baby, a little boy. We have found out the s__ of all of our children...

Long before marriage, one tradition carried deep emotional weight for him

My husband is a "third." As in, John Smith III. Before we got married and were having discussions about kids, he did make it very clear that passing down his...

Over time, her feelings quietly shifted, even though the agreement stayed the same

At the time I thought it was really cute and adorable how much pride he took in it since most guys don't really care about that sort of sentimental stuff.

But as the years have gone by I've definitely cooled on the idea quite a bit and I don't think I want to have our son be named after my...

ADVERTISEMENT

The imbalance in naming choices only became obvious in hindsight

But when we were choosing names for our daughters, my husband was very much in the "you can take the lead on naming our daughter because I already have the...

It's not like he wasn't involved in naming our daughters, but he definitely deferred to my opinion. So, when we found out we were having a boy, my husband was...

ADVERTISEMENT

The excitement peaked, then vanished in a single conversation

On the car ride home after the ultrasound it was all he could talk about. He was giddy like a teenager talking about how proud he would be of sharing...

I don't know if it was the best time to bring this up, but I kind of had one of those "yeah, about that" moments.

ADVERTISEMENT

I told him how I know we had talked about this many times before with our other kids and that I technically agreed to it years ago, but I don't...

I don't think I've ever seen anyone's mood change so quickly and visibly as my husband's did in that moment. It was like all the joy went out of his...

Her hesitation landed harder than she expected…

ADVERTISEMENT

I told him that I just don't want our son to be a "forth." It seems tacky and has weird aristocratic vibes that just don't seem right to me.

I told him that I am not totally against the idea, but I don't want to just agree to it right now because I want time to think about other...

He took that as me basically saying that I am going back on our years-long agreement and that there is no way we are naming our son after him. He...

ADVERTISEMENT

The emotional fallout lingered well beyond that moment

This has taken all of his excitement about the baby away. He's been withdrawn and quiet with me ever since.

When I try to talk to him about it, he tells me he has nothing to say because he's been very clear about where he stands on this and he...

ADVERTISEMENT

I asked him if he would want to think of some other names together and he told me to give him a list and he'll look at it when he...

At its core, this conflict isn’t really about a name. It’s about expectations that were set early, reinforced over years, and then suddenly shaken. From the husband’s perspective, this wasn’t a casual idea; it was a deeply personal tradition tied to identity, pride, and continuity. Hearing hesitation after so much anticipation likely felt like the rug being pulled out from under him.

From the wife’s side, changing feelings during a long marriage isn’t unusual. People evolve, especially around emotional topics like children. Still, timing matters. Bringing up doubts only after confirming the baby’s sex turned a private concern into a public disappointment, at least within the relationship. That’s where much of the hurt seems to stem from.

ADVERTISEMENT

Relationship expert Dr. John Gottman has often emphasized the importance of trust in small, everyday promises. He notes, “Trust is built in very small moments, which I call sliding door moments.” When one partner feels those moments are mishandled, resentment can grow quickly if not addressed with empathy and repair.

A practical path forward would focus less on winning the argument and more on repairing the emotional damage. Openly acknowledging the hurt, apologizing for the timing, and genuinely exploring compromises could help. Options like keeping the traditional name legally while using a nickname socially might ease tensions. What matters most now is restoring a sense of partnership before the baby arrives.

Here’s the input from the Reddit crowd:

Many users strongly supported the husband, emphasizing fairness and keeping promises

ADVERTISEMENT

Active-Anteater1884 − Let me understand. You made an agreement with your husband. You got to name the girls, he would name a boy. You benefited from this agreement twice.

Now, when it's his turn to benefit, you have some moral objection to naming a kid IV. You don't like the weird, aristocratic vibes. (I don't necessarily disagree with you...

But surely, four years ago (when you had your second child), you felt those same vibes? But you nonetheless took the lead in naming your daughter, without, at that time,...

ADVERTISEMENT

"I feel weird about the IV thing, so why don't you take the lead on this, honey?" I mean, because people just MIGHT think you went along with naming a...

because it gave you the lead in naming your first child who you knew to be a daughter; and again four years ago, in naming your second child who you...

and have only now developed "weird vibes" when you husband gets to take the lead in naming a child. YTA. ETA: Cleaned up some typos.

ADVERTISEMENT

BelowAverage1986 − I am sorry to say but YTA. Your husband made it clear during the dating process how important this was to him. You made a commitment to him...

He married you and had a family with you on the pretense that you respected him and his family's tradition of naming their first male son "John Smith the Fourth".

You let him believe for the past ELEVEN years, while he graciously let you name your female children, which you gladly let him do, all on the pre-tense that should...

ADVERTISEMENT

As a married individual, nothing short of a baby onesie with said name printed on it accompanied by the biggest apology could even BEGIN to repair this rupture to the...

BulbasaurRanch − “He took that as me basically saying that I am going back on our years long agreement” - well, that’s exactly what you are doing You were fine...

ADVERTISEMENT

but then arbitrary changed the rules when you found out it’s a boy You dangled it in front of him for years, and only now say something. This is cruel....

StAlvis − YTA I might have had your back if you had agreed to *a really dumb name* back when you were a stupid kid in your early 20s —...

'Hagrid' sounds perfect! " passing down his name was very important to him if we had a son That's totally normal. "you can take the lead on naming our daughter...

ADVERTISEMENT

He's named none so far. You had better have a **_damn good_** reason for this 180° change of face. I told him that I just don't want our son to...

[sic] It seems tacky and has weird aristocratic vibes that just don't seem right to me. . .. BRUH. You done MARRIED A "TREY. " You have BOUGHT INTO this...

SushiGuacDNA − YTA. You didn't "technically agree", you "actually agreed". The fact that you said "technically agreed" makes me feel like you know you are screwing up,

ADVERTISEMENT

but you are playing word games to back away from it. That makes you "technically an a__hole. "

Others tried to offer a more balanced, though still critical, view

Aggravating_Spot_959 − YTA. What was your plan here? You knew that he wanted to pass down his name to his son, but instead of talking to him when you realized...

ADVERTISEMENT

Of course he’s going to be disappointed especially since he let you take the lead for your daughter’s names with the understanding that he would get to name the boy.

Maybe if you had a legitimate reason for not wanting to name your son after him it would be more justifiable but saying that you don’t like it bc it

“sounds aristocratic” is ridiculous and wishy-washy. Tbh it kinda reads like your looking for any excuse to take control of the naming process

Bureaucratic_Dick − YTA. I don’t normally think a person should be held to standards they agreed to years ago, but this is something you discussed before you even got married.

You knew, from the get go, that it was something he wanted, and you agreed to it. He feels like you’re going back on your word because YOU ARE.

It’s not like this is some crazy name either. It’s a family tradition three generations running so far. He made it clear he wants it to continue for at least...

laurasdiary − YTA This is cruel and just wrong. You were fine to benefit and let him defer to you on your other children’s names, but refuse to keep your...

You’re being selfish and destroying a tradition your husband clearly cares about. For what? You need to rethink your priorities.

StevieB85 − YTA Not only did you agree to this over a decade ago, you re-affirmed the agreement when you had each of your other children.

Additionally, you don't even give a rational reason why you've changed your mind, just you now suddenly think its "tacky". He told you before you got married, and you've seen...

It was an extremely AH move to destroy his happiness like that. He was literally "giddy" with how excited he was, and you chose to destroy that moment for him,...

Just you no longer feel like it. Additionally, you decided to shoot down the entire idea, on what seems like a whim, without even a hint at compromising.

Maybe you keep the first, last, and fourth, but go with a different middle name. Maybe the baby's name is "John Middle Smith IV" and he goes by a nickname,...

etc. The biggest issue in this is you unilateral dictation that this is suddenly not an option. There are many discussions that can be had.

But more over, you decided to destroy your husbands happiness and joy in that moment. That's the biggest AH part.

lookalive07 − It's been a while since I've seen one where pretty much everyone agrees YTA, and I'm with them. The concept of naming your kid after you has always...

Like, "here's my kid, I named him after me because I like me so much". But in the end, it doesn't *really* matter, and if it would be something that...

**especially** because you both agreed on it when you were starting to have kids, then just suck it up and let him name his son after him.

And to be honest, whether he admits it or not, he's *always* going to resent you for going back on your agreement, and he might have some harbored resentment towards...

hellojello7563 − Sorry, but YTA. You made an agreement with him about this, and he clearly has been very excited about it.

It's not fair for you to take it back just because you have gotten your way with the girls' names and now feel hesitant about your son.

This is clearly important to him and you need to support that. The time to express your concerns was earlier on in the relationship.

A few commenters leaned into blunt honesty or dark humor

JimmyJooish − “I just sucked all the excitement my husband had about our new child because the name we agreed on has weird vibes. ” You’re being selfish. Go and...

Comfortable-Mix-2504 − YTA- How come you're having these thoughts about the name now, but not for all those years when he eagerly wanted to name his son the same name...

You just supported and agreed to it for a long time, and changed the decision now. If you didn't like the name, you should have said it YEARS AGO, not...

11SkiHill − YTA. Seriously.   Just awful. Apologize.   Let him name baby. And in future keep your word.

Responsible-End-6371 − YTA OP. You're not gonna find much support for your position here. You had an agreement and then you negged on it while giving a terrible excuse.

It's obvious that you have felt this way for a long time, and instead of discussing it with him years ago, you decided to wait until now.

That's a bait and switch there, and it is highly frowned upon. If you have any respect for your husband at all, apologize and let him name the baby.

This situation highlights how long-standing agreements can carry emotional weight far beyond what we expect. While changing feelings are human, the way those changes are communicated can either strengthen or seriously strain a relationship. Here, most readers felt the issue wasn’t the name itself, but the timing and broken trust. As this couple moves forward, honest communication and empathy will matter more than any name choice. What would you do if a promise made years ago no longer felt right today?

Share this post

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *