What I/O psychology won't say about itself

I often find it frustrating to explain the field that I'm in. Unlike "accountant" or "doctor," it never feels straightforward to answer the question that comes up within the first few minutes of meeting someone.

"What do you do for work?"

"Consultant" is too vague. "I/O psychologist" is technically correct and lands like a brick — usually followed by a polite nod, or some version of "oh, so like HR?" Neither answer captures what the field actually does, or why it matters.

Over time my explanation has gotten more polished, but it still doesn't land with the impact I expect. That's left me with a question: is this a problem with how I'm explaining the work, or does the hesitation come from something deeper?

A branding problem, or something deeper?

I/O psychology has a branding problem. That part isn't controversial — articles, conference panels, and LinkedIn posts all acknowledge it. The more interesting question to me is why no one seems responsible for fixing it. Is this diffusion of responsibility, where everyone agrees it's an issue but no one owns it? Or is the task simply too entrenched in institutional history to address?

The name itself traces back to World War I, when "industrial" meant measurement and performance, and "organizational" was added later to acknowledge that people work inside social systems, not just tasks. Historically, the name makes sense. Practically, it's become a barrier — and the field now operates under a dozen-plus alternate names depending on who's asking.

Licensure that doesn't fit the work

Licensure raises a similar question. SIOP's guidance on the topic emphasizes doctoral training and clinical-style supervised practice — models borrowed from clinical psychology, not the applied, systems-level work most I/O practitioners actually do. Unless you intend to provide therapeutic services, it's hard to see how that framework protects or supports the work I/O psychologists are trained for.

If licensure is one of the primary markers of professional legitimacy, what does it say about a field when its licensing process appears borrowed from another discipline?

For practitioners with a master's-level education — the majority of the field — this creates a gray zone in how we describe our own work and how organizations perceive what our credentials actually signal.

Helpful, but not necessary

Here's the harder problem. Leadership, culture, and workplace motivation are easy to agree are important. The harder question is what we mean by important. Organizations already have leaders, systems, and cultures before an I/O psychologist ever shows up — and those systems got them this far. That makes the work feel additive rather than essential. Helpful, but not strictly necessary.

I keep coming back to two scenarios. An organization doing well can always ask: if things are working, why bring someone in at all? An organization that's struggling asks the blunter version: how can we afford this when we're barely staying afloat? Selling into either case is hard — and the deeper issue isn't market conditions. It's how clearly we connect our work to outcomes leadership actually cares about, rather than wrapping it in frameworks, decks, and process that look rigorous but don't move the needle.

The I/O Psychology Collective

This project is an attempt to address that directly and imperfectly. Not another professional organization with membership fees or certification ladders — a space where I/O psychologists and adjacent professionals can share insight openly, test ideas in public, and talk honestly about what works and what doesn't, without needing permission.

Welcome to the I/O Psychology Collective.