Woman Used the Baby Name She Had Told Her Sister About First, Even After Her Sister Used a Variation of It for Her Own Newborn

Photo credit: AI-generated image created using ChatGPT. Illustrative only.

Two sisters were pregnant at the same time, and what should have been a sweet, overlapping season turned into a family naming standoff. One sister had been talking up her plan for months: a daughter named after both grandmothers, with a nickname she already loved.

But after the older sister gave birth first—and revealed a surprise that changed everything—the younger sister went ahead with the name anyway. Now, in the original post, she’s wondering if keeping her baby’s name was a fair follow-through or a move that unnecessarily escalated the tension.

The plan was set long before the births

The mom at the center of the dispute is 35 and welcomed her first daughter in September. During her pregnancy, her 38-year-old sister was also expecting, and the two pregnancies overlapped in a way that usually builds closeness—sharing symptoms, swapping updates, and counting down together.

While she was pregnant, the younger sister says she told her sister exactly what name she intended to use. She wanted to honor her own mother, Colette, and her husband’s mother, Coral. Because both names start with “Co,” she also had a nickname in mind: “Coco.”

It wasn’t a vague idea, either. She describes it as a plan she talked about throughout her pregnancy, enough that her sister would have known it was coming and not a last-second choice.

A “surprise name” turned into something bigger

The older sister, meanwhile, kept her own baby name plans close. She told her family the name was a surprise and she didn’t want to reveal it until the baby arrived.

Then August came—and so did the surprise. The older sister didn’t just have a boy. She had twins: a boy and a girl, something she’d kept under wraps because she thought it would be fun for everyone to find out at the birth.

When the twins were born, she named them Cole and Lettie. To the younger sister, it landed as “really cute and sweet,” and she interpreted it as an obvious nod to their mom, Colette, split into two names.

At the time, she says she didn’t make much of it. The twins had their own identities, and in the whirlwind of new babies, it may have felt like a coincidence that wouldn’t matter outside the immediate family bubble.

She used the original name anyway—and the overlap became real

A month later, in September, the younger sister’s daughter arrived. She went forward with the name she’d been saying all along: Colette Coral. And at home, she says they “almost exclusively” call the baby Coco.

That’s when the older sister’s reaction shifted from mild annoyance into a recurring complaint. The older sister is now “very annoyed” that the younger sister didn’t change course, and she brings it up often—framing it as ridiculous that three children in the same close family “practically share a name.”

The younger sister doesn’t deny there’s confusion, especially when full names are used. With Cole and Lettie sounding like a split version of Colette, and with Colette being used outright, it’s easy to imagine the awkward moments at family gatherings, on cards, and in group texts where names have to be clarified.

But her point is simple: she told her sister first. She says she repeated the plan throughout pregnancy and even had items made with the name. To her, the twins’ names came without warning, because her sister insisted the name choice was a secret until birth.

The argument turned into a “who was first” scorecard

Instead of cooling down after the births, the dispute hardened into a timeline fight. The older sister, the younger sister says, makes sure “everyone knows her babies were born first,” as if birth order settles the question of naming rights.

It also puts the younger sister in a corner socially. If the older sister keeps telling relatives the twins came first, it can subtly suggest the younger sister copied or intentionally caused duplication—even though she believes she had been transparent for months.

That dynamic is part of what makes this feel bigger than a baby-name disagreement. It’s not just what’s written on birth certificates. It’s the ongoing narration in front of family members, and the pressure to accept blame to stop the comments.

The younger sister even admits that, had she known the plan earlier, she would have reconsidered. She says that if her sister had told her months ago she was planning Cole and Lettie, she “probably would’ve pivoted.” Even just “Cole,” she says, would have triggered a re-evaluation. But she wasn’t given that chance.

Changing the name now would be a legal and emotional mess

Now she’s considering a fix that goes beyond nicknames: legally swapping the order of her daughter’s names, making Coral the first name and Colette the middle. The idea isn’t because she dislikes Colette—it’s to “keep the peace” and reduce the sense that the three kids share one recycled name.

But she’s torn, because making a legal change feels like admitting she did something wrong. She’s also already built emotional and practical momentum around the name: baby items made with it, a nickname they use daily, and the meaning tied to two grandmothers.

There’s also the everyday reality that legal name changes aren’t just a quick redo. It’s paperwork, updates, and years of correcting records. Even with a simple “swap,” it’s the kind of step parents usually take only when something feels truly unworkable.

And from her perspective, the name isn’t the only issue. The bigger problem is that her sister kept her own choices secret, then acted upset when the younger sister didn’t magically adjust after the fact.

Most reactions centered on notice and follow-through

The post itself is labeled “Not the A-hole,” reflecting the general judgment where it was shared: the younger sister wasn’t wrong for using the name she announced first. The logic is straightforward—if you tell someone your plan and they choose something extremely similar without warning, you can’t reasonably expect them to absorb the consequences alone.

Another thread running through reactions was practicality. Even with hurt feelings, many people tend to see nicknames and context as the real-life fix: families rarely use full legal names day to day, and “Coco” is distinct from Cole and Lettie in normal conversation.

At the same time, the younger sister’s admission about confusion suggests this won’t vanish on its own. If extended family members use “Colette” when addressing both a grandmother reference and a child’s full name, it could create repeating moments of friction—especially if the older sister keeps highlighting the overlap as a grievance.

For now, the younger sister seems stuck between two unappealing options: keep the name and accept the ongoing commentary, or change it and feel like she validated her sister’s version of events. Either way, the babies are already here, the names are already in use, and the family will have to decide whether this becomes a long-running score to settle—or just a strange footnote from the year two sisters had three newborns between them.