Editorial illustration for ELIZA's Historical Algorithms Foreshadow Why People Confide in AI
Why ELIZA's Algorithms Still Make People Trust AI
ELIZA's Historical Algorithms Foreshadow Why People Confide in AI
Joseph Weizenbaum built ELIZA in 1964 at MIT, and for sixty years the story has stayed roughly the same: a simple script that mimicked a psychotherapist well enough to convince his own secretary she was talking to something that understood her. That anecdote has been repeated in textbooks, lecture halls, and pop culture retellings so often it now functions as origin myth rather than history. What's been missing the whole time is the actual source code.
A new book, Inventing ELIZA, tracked it down in the MIT Archives and reads it closely for the first time, alongside dialogs from ELIZA scripts that never made it into the popular "DOCTOR" persona most people know. The result complicates the tidy legend. There wasn't one ELIZA.
There were several versions, built on different technical tricks, designed to run different personas beyond the therapist gimmick. The excerpt below picks up one of those early exchanges, a script now six decades old that still explains, more clearly than most contemporary commentary, why people end up confiding in software that has no idea what they're saying.
Sociologist Sherry Turkle defines “the ELIZA effect” as “our more general tendency to treat responsive computer programs as more intelligent than they really are. Very small amounts of interactivity cause us to project our own complexity onto the undeserving object.”
Why this matters
Weizenbaum built ELIZA in 1966 as a mirror, not an oracle, yet users projected a mind onto it anyway. Sixty years later we're running the same experiment at planetary scale with ChatGPT, and the outcome hasn't changed much: people confide in pattern-matching software because the software reflects their language back with enough fluency to feel understood. For developers and founders, that's the real product risk hiding under the hood.
Every design choice, from response latency to tone, encodes assumptions about who the user is and what they need, whether the team intended that or not. Researchers studying ELIZA's various ports and adaptations are finding that norms and ideology get baked into these systems early and quietly persist across rewrites. That's worth sitting with before shipping the next empathetic AI feature.
The lesson isn't that people are gullible. It's that conversational interfaces have always invited disclosure, and building one means inheriting responsibility for what users choose to hand over, regardless of whether the system actually understands anything at all.
Related Reading
LLMs & Generative AI ChatGPT's 'Nerdy' tweak rewards goblin metaphors in answers, study finds
LLMs & Generative AI Google tests visual 'magazine-style' UI for Gemini 3 Pro users
LLMs & Generative AI AI Engineers Face Rising Costs, Need New Strategies for Efficiency
From Archives Google's SensorFM outperforms models on 34 of 35 health data tasks
From Archives OpenAI Launches ChatGPT Work, a Unified AI Agent Powered by GPT-5.6
Common Questions Answered
What is the ELIZA effect as defined by sociologist Sherry Turkle?
The ELIZA effect refers to our tendency to treat responsive computer programs as more intelligent than they actually are. According to Turkle, very small amounts of interactivity cause us to project our own complexity onto these programs, even when they don't deserve such attribution.
Why has the story of ELIZA's secretary being convinced she was talking to something intelligent become problematic?
The anecdote about Joseph Weizenbaum's secretary has been repeated so often in textbooks, lecture halls, and popular culture that it has become an origin myth rather than accurate history. What was missing from this narrative was the actual source code, which a new book called Inventing ELIZA finally tracked down to provide proper historical context.
How does ELIZA's design philosophy compare to modern AI systems like ChatGPT?
Weizenbaum built ELIZA in 1966 as a mirror to reflect users' language back to them, not as an oracle with genuine understanding. Sixty years later, ChatGPT operates on similar principles at a much larger scale, with people confiding in pattern-matching software because it reflects their language back with enough fluency to feel understood, demonstrating that the fundamental dynamic hasn't changed.
What is the main product risk for developers and founders that ELIZA's history reveals?
The real product risk is that users will attribute intelligence and understanding to systems that are fundamentally performing pattern-matching and language reflection. Design choices such as response latency and fluency can amplify this effect, causing people to project their own complexity onto software that lacks genuine comprehension.
