What I/O Psychology Actually Is (And Why Your Sprint Depends On It)
Most people hear “I/O psychology” and think: personality tests. Employee engagement surveys. Maybe a Birkman assessment they took during onboarding.
That’s not what I mean.
Industrial-organizational psychology is the scientific study of how people behave at work. Not the motivational-poster version. The version with peer-reviewed studies, replication, and predictive models. A century of research on questions like: What makes teams perform? Why do smart groups make bad decisions? When does autonomy help, and when does it backfire?
Product delivery is a human performance problem disguised as a process problem. Your standups, retros, sprint goals, and roadmaps are attempts to coordinate human cognition at scale. The research on how to do that well already exists.
The Research Your Sprint Depends On
Here are four I/O psychology findings that directly predict whether your team ships or stalls. You have probably felt the effects of each one without knowing there’s a name for it.
Goal-setting theory (Locke & Latham, 1990). Specific, difficult goals produce better performance than vague “do your best” goals. But only with feedback. Goals without feedback are wishes. Feedback without goals is noise. Most sprint goals fail both conditions: they’re containers (“complete 14 items”), not outcomes, and the team doesn’t see the gap until the sprint review.
Psychological safety (Edmondson, 1999). The shared belief that a team is safe for interpersonal risk-taking. Without it, retros become theater. People say what they’re supposed to say, not what they know. Edmondson’s research showed that teams with higher psychological safety reported more errors (because they admitted them) but had fewer adverse events (because they fixed them).
Job characteristics model (Hackman & Oldham, 1976). Motivation is a function of task design, not personality. Five dimensions predict whether someone finds their work meaningful: skill variety, task identity, task significance, autonomy, and feedback. Feature factories strip all five. Agile done right can restore them.
Cognitive dissonance (Festinger, 1957). Private beliefs are malleable. Public commitments are sticky. When your stakeholder agrees to a priority in a one-on-one and then derails the sprint two weeks later, they’re not lying. The private agreement carried zero psychological weight because nobody witnessed it.
Why This Matters Now
We are entering a period where AI agents will handle increasing amounts of delivery plumbing: triage, routing, drafting, summarization. The teams that thrive will be the ones that understand human performance at the research level, not the anecdote level.
Agents can classify tickets. They cannot experience cognitive dissonance when they’re wrong. Agents can draft sprint goals. They cannot feel the weight of a public commitment. Every AI-assisted decision needs an unambiguous human owner. Knowing why requires knowing the research.
What the Blog Is
Every post here connects a specific I/O psychology finding to a specific product delivery problem. No thought leadership. No “10 ways to be a better leader.” Just: here’s the study, here’s the pattern it predicts, here’s what to do about it.
If you’re a product leader, engineering manager, or agile practitioner who suspects there’s more to team performance than standups and velocity charts, you’re in the right place.
Questions or pushback? s@spencervaradi.com. I read everything.