People who married in the 1970s and 1980s often didn’t have the language for what they needed — and many of them made it work anyway, in ways their children are still trying to understand

You’ve probably wondered how they did it. If you grew up watching people who married in the seventies or early eighties and are still together, you may have noticed something that doesn’t quite compute: their communication, by today’s standards, often looks incomplete.

They don’t always talk about their needs in the ways we’ve been told needs should be talked about. They don’t have the vocabulary for it. And yet here they are, forty-odd years later, still a unit.

This is not a coincidence or a mystery. It is, however, worth understanding — not to romanticize an era that had real and serious problems, but because what these couples were working with, and what they weren’t, tells us something that the current abundance of relationship language hasn’t fully replaced.

What exactly weren’t they working with?

The list of tools unavailable to a couple who married in 1974 or 1983 is longer than most people realize.

Gary Chapman’s Five Love Languages — the framework that gave millions of couples a shared vocabulary for how they give and receive affection — wasn’t published until 1992. Emotionally Focused Therapy, developed by psychologist Sue Johnson and now considered among the most evidence-based approaches to couples work, launched in 1985 — and even then took decades to filter from clinical practice into mainstream awareness. The concept of adult attachment styles — the secure, anxious, and avoidant patterns that now populate every relationship column and podcast — wasn’t introduced to research until Hazan and Shaver published their first study in 1987. “Emotional labor,” coined by sociologist Arlie Hochschild in 1983, didn’t enter the domestic conversation until around 2015. Emotional intelligence as a popular framework arrived with Daniel Goleman’s 1995 book. The term “gaslighting” as a relationship concept only went mainstream in the late 2010s.

A couple who married in 1978 was working without all of it. No shared language for attachment needs. No framework for identifying whether they were anxious or avoidant. No named categories for the different ways people show love or what they need to feel it. They had to figure out what they needed, and what their partner needed, largely from scratch.

What were they working from instead?

The 1970s and 1980s were not a stable, unchanging time for marriage. According to historian Stephanie Coontz, whose research traces the transformation of marriage across centuries, “all these restraints on individual choice collapsed between 1960 and 1980” — the economic dependence, the social stigma, the legal obstacles that had kept marriages together regardless of whether they were good. Those things were gone. At the same time, the emotional expectations people brought to marriage were rising sharply, for the first time in history.

Coontz describes this as a paradox at the center of modern marriage: “The very factors that have made marriage more satisfying in modern times have also made it more optional.” The couples who married in the 1970s and 1980s were navigating this transition without the benefit of either the old constraints or the new therapeutic vocabulary. They were in a gap — free enough to leave, but without language for staying.

What many of them had instead was a more practical orientation. You fixed what was broken. You showed up even when the conversation would have been hard to have. You did things rather than named things. Community also played a role that it plays less now — family, neighbors, religious communities provided external structures that supported marriages through difficulty without asking the marriage itself to be the source of everything.

None of this is an argument for the constraints of that era. It’s simply an account of what the landscape looked like.

See Also

What Bloggers Can Learn From Teddy Goff’s Approach to Digital Strategy

Does the language actually make the difference?

This is the harder question, and the honest answer is: it helps, but not as cleanly as we’d like.

Having words for something matters. Being able to tell a partner “my primary love language is quality time and I feel disconnected when we don’t have it” is genuinely more efficient than years of vague disappointment. Being able to recognize anxious attachment patterns in yourself can explain behaviors that would otherwise seem irrational. The language creates a shared frame, and shared frames help.

But the language also creates new categories of failure. A relationship can now fall short on attachment style compatibility, love language alignment, emotional labor distribution, communication patterns, and boundary respect — categories that largely didn’t exist as such in 1978. The more precisely we can name what we need, the longer the list of unmet needs becomes. That’s not a reason to abandon the vocabulary. It is a reason not to treat it as if it’s the whole picture.

Sue Johnson, who has spent decades helping couples find their way back to each other, describes the core of what couples actually need to communicate in terms that don’t require any terminology at all: “Can I count on you? Are you there for me? Will you respond to me when I need, when I call? Do I matter to you?” These are the questions at the heart of every long marriage. A couple who married in 1978 couldn’t name their attachment style. But they could, over time, answer those questions in action — or fail to — and the ones who answered them consistently are often the ones still together.

This isn’t relationship advice, and none of it is meant to suggest that the vocabulary we have now doesn’t matter. It does. A good therapist is worth more than any article or framework. What it is, is a reminder that the thing the language is trying to point toward — the felt sense of being known and counted on by the person you chose — was possible before anyone had found the words for it. Their children are still trying to understand how. The answer is probably simpler, and harder, than any framework can fully capture.