What Even Is Social Security?

We talk about Social Security all the time.

It shows up in conversations about retirement. About disability. About work. About Medicaid.

But most people interacting with it don’t actually know what it was built to do.

And that matters more than it sounds like it should.

Where it started

Social Security was created in 1935, during the Great Depression.

At the time, there wasn’t a national system for retirement income. If you stopped working, you were relying on whatever you had—or whoever you had.

And when the economy collapsed, a lot of that disappeared.

So the government built something new.

What it was designed to do

At its core, Social Security was designed to do one thing: Provide income when work ends.

You work. You pay into the system. You receive a monthly benefit later.

That was the whole job.

Not to replace everything. Not to make you financially whole. Just to create a baseline—something to prevent people from having nothing at all.

What it wasn’t built to do

It wasn’t designed to be a full support system.

It wasn’t designed to coordinate healthcare.

It wasn’t designed to respond to complex or changing needs.

It was designed around a single moment: when work ends, income stops, and something needs to replace part of it.

What happened next

Over time, more got added.

Disability benefits. Connections to other programs. Layers of rules and eligibility.

But those didn’t replace the original design.

They were built on top of it.

Why this still matters

Because now, we’re often asking one system to do a lot more than it was originally built to handle.

And when it doesn’t quite fit—when things feel disconnected or harder to navigate than they should, that’s not coming out of nowhere.

It’s coming from the structure underneath it.

In the coming weeks, I’m going to be exploring where these systems came from—and how those original decisions still shape what it’s like to use them now.

Next
Next

Support Exists—But It’s Not a System