From History to UX: How Studying Society Made Me a Better Designer

When people hear that I studied History and Political Science before moving into UX design, the reaction is usually polite confusion.

“How did you go from that to this?”

For a long time, I didn’t know how to answer that clearly. Now I do.

Studying society made me a better designer.

History Trains You to See Systems, Not Events

In History, you don’t just study dates. You study systems. Power structures. Cultural shifts. Social consequences.

You learn that no event exists in isolation. Every decision has context. Every outcome has layered causes.

That way of thinking stayed with me.

In UX, it translates into something critical: users do not exist in isolation. A frustrated click is rarely just a bad button. It is usually the result of assumptions, constraints, expectations, and invisible pressures around the user.

History taught me to look beyond the interface and ask:

What system produced this behavior?
What pressures shape this decision?
What unseen factors influence this interaction?

That perspective changed how I design.

Political Science Taught Me About Power and Bias

Political Science forced me to examine institutions, policies, representation, and inequality. It trained me to ask uncomfortable questions:

Who benefits from this system?
Who is excluded?
Whose voice is missing?

UX often talks about “the user” as if that user is universal. But users are shaped by language, culture, economic reality, and access.

When I design now, I think about power.

Who controls the defaults?
Who absorbs the risk?
Who carries the cognitive burden?

Design is never neutral. It distributes power, attention, and friction.

That awareness came long before I opened Figma.

Understanding Behavior Before Tools

Before I learned Photoshop, before I learned HTML, before I worked on enterprise systems, I learned to read patterns in human behavior through texts, debates, and case studies.

History trained me to sit with complexity. To resist quick conclusions. To understand that human behavior is rarely linear.

That skill has been more valuable in UX than any tool.

Tools change every few years. Human patterns do not.

From Humanities to Product Thinking

When I eventually transitioned into design and later into UX, I realized something surprising.

The humanities background that once felt unrelated was actually foundational.

It helped me:

See user journeys as narratives
Understand friction as a systemic issue, not a cosmetic flaw
Recognize bias in flows and defaults
Design with awareness of context, not just screens

When I later worked on healthcare and enterprise systems, that systems thinking became even more important. These were not apps for casual browsing. They were platforms influencing decisions, workflows, and outcomes.

You cannot design responsibly in those environments without understanding social systems.

UX Is About People, Not Pixels

UX is often described as a discipline of research, usability, and interaction design. All of that is true.

But at its core, UX is about people navigating systems.

Studying History and Political Science did not teach me wireframing. It taught me something deeper: how systems shape behavior, and how decisions ripple outward.

That awareness shapes every design choice I make today.

From button labels to onboarding flows to information architecture, I try to remember:

Every interface exists inside a larger social context.

And good design respects that.