AI assistants are all the rage, but this guy says that AI teams need to relearn “the Clippy lesson” that he learned years ago.
“This guy” is Krishna Mukherjee, a pioneering Microsoft technologist and software architect whose career spans the arc of modern computing and who contributed to the company’s intelligent features in Microsoft Office, including its proofing tools, AutoCorrect, and AutoFormat. He also invented the Intelligent Filing Manager (INTELLIFM) in the late 1990s, an AI expert system that automates document workflows and remains in production use today!
Impressive. Alas, he was also at Microsoft when they released their Office Assistant, the much-maligned “Clippy”, a cartoon paperclip that was designed to provide user assistance.
In his article The Clippy Lesson Every AI Team Is About to Relearn (available here), Krishna points out how Clippy “was built on rigorous research into Bayesian inference and user modeling, and it represented a sincere attempt to answer a real question: millions of people were using powerful software while tapping only a fraction of its capabilities. What if the software could notice what you were trying to do and offer to help?”
As he notes: “A quarter century later, that’s precisely the promise of every AI copilot, agent, and assistant now being funded, built, and shipped. Which is why the reasons Clippy failed deserve close study — because they were never really about a cartoon paperclip, and they haven’t gone away,” noting that “[T]he convenient story is that Clippy failed because the technology was primitive.”
But he says the convenient story is wrong. “Clippy didn’t fail because it was dumb. It failed because of its behavior. It presumed to know your intent.”
“Type the word ‘Dear’ and it concluded you were writing a letter, whether you were or not. It insisted on being noticed — animated, front and center, tapping on your screen’s glass. And it was hard to dismiss. Turning it off felt like a negotiation.”
Conversely, “AutoCorrect quietly became one of the most widely used intelligent features in software history. It made billions of corrections without a mascot, without an announcement, without demanding credit. The contrast is the whole lesson: the assistance that endured was the assistance you forgot was there — until the moment it helped you.”
Comparing to today’s AI assistants, Krishna says that “large language models add a failure mode Clippy never had: they can be wrong while sounding completely certain. Clippy at least looked like a cartoon. Today’s assistants speak in the polished prose of an expert, whether or not an expert is home.”
He adds: “Users respond to overreach the same way they always have. They disable the feature. They ignore it. Or they quietly resent the product that contains it. In enterprise settings, I’ve watched this play out at scale: an AI capability gets switched off across an entire organization not because it lacked power, but because it lacked manners. Adoption dies not in the benchmark but in the thousandth small interruption.”
And he relates how his invention of INTELLIFM relates as well – firms initially blocked the component for security reasons and use resumed only after he explained exactly what the component did and how it could be downloaded and operated safely. As he states: “The capability never changed. What changed was trust.”
Krishna’s article includes four tips for how to build AI assistance users actually keep on. Here they are, including the first sentence of each paragraph:
- Earn trust through restraint. Surface help in response to a real signal, not a guess about what someone is doing.
- Make dismissing or overriding the assistant effortless. One click, one keystroke, one clearly honored “no.”
- Calibrate confidence. Don’t let the system sound certain when it isn’t. (This is a big one, in my opinion, for AI models)
- Respect attention and timing. The right help at the wrong moment is still an interruption.
Krishna states: “None of this limits ambition. It channels it. The teams that internalize these principles will build assistants that people keep enabled, rely on daily, and eventually stop noticing — which, counterintuitively, is the highest compliment intelligent software can earn.”
Highly intelligent developers would be well advised to keep in mind the Clippy lesson when creating their AI assistants.
So, what do you think? Do you think AI developers are keeping the Clippy lesson in mind in developing AI assistants? Please share any comments you might have or if you’d like to know more about a particular topic.
Hat tip to Jeff Brandt for highlighting this article on PinHawk!
Image created using ChatGPT, using the term “robot annoyed at the sight of a cartoon paperclip on its computer workstation display.
Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by my employer, my partners or my clients. eDiscovery Today is made available solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Today should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.
Discover more from eDiscovery Today by Doug Austin
Subscribe to get the latest posts sent to your email.
