“A computer system should make us feel smarter, not dumber and work seamlessly with us, like a human partner.”
Computer scientist Barbara Grosz has spent decades studying dialogue, collaboration, and the ways intelligent systems can work with people. Her 2014 statement sets a human-centered benchmark for artificial intelligence. Technical sophistication is not enough if users leave confused, dependent, or unable to question a result. A good system should extend a person’s capacity while fitting the shared activity. “Like a human partner” does not mean pretending that software is a person. It means designing for coordination: each participant contributes what it does well, communicates relevant information, and adjusts when plans change.
Partnership is different from automation. Automation asks which task can be transferred to a machine. Partnership asks how responsibilities should be divided and how both sides will maintain a useful model of the work. A medical assistant might search records and surface patterns while a clinician integrates symptoms, patient preferences, and consequences. A writing tool might generate alternatives while the writer determines purpose, evidence, and voice. The human remains more than an approver at the end of a pipeline. Meaningful collaboration gives people opportunities to direct, inspect, and revise the process.
This approach requires communication about uncertainty. Systems often present a single answer because interfaces reward apparent simplicity. A partner should reveal when evidence is weak, what assumptions shape a recommendation, and which alternatives deserve consideration. It should request clarification when the goal is ambiguous and make correction inexpensive. Explanations must be suited to the user’s actual decision, not produced as decorative technical detail. The aim is calibrated reliance: people should know when the tool is dependable, when verification is needed, and when human expertise should override it.
Grosz’s standard also helps organizations evaluate productivity claims. Saving minutes is valuable, but not if workers lose skills, customers cannot appeal, or accountability becomes impossible to locate. A system that makes people “feel smarter” should increase real competence and situational awareness, not merely confidence. That means involving affected users in design, measuring outcomes beyond speed, and preserving routes for human judgment. AI becomes a partner when it supports shared goals without quietly redefining those goals around what the machine can easily measure. The partnership test is admirably concrete: after using the system, can the person understand more, choose more wisely, and recover from error? If not, seamless automation may have concealed a transfer of control instead of creating genuine collaboration. Better interfaces alone cannot repair a relationship built around obedience. Partnership requires shared direction.
A partner divides responsibilities according to complementary strengths and keeps the person involved throughout the work.
The goal is expanded human capability, not a ceremonial approval step after the machine has already decided.
Useful systems disclose uncertainty, assumptions, alternatives, and moments when more information is needed.
People can then decide when to rely on a result, verify it, revise it, or use human expertise instead.
Efficiency gains can hide lost skills, weaker accountability, and processes that are harder to contest.
Human-centered evaluation asks whether people understand more, retain agency, and achieve better substantive outcomes.
Explore more "Quotes of The Day"
Continue exploring how writers, thinkers, artists, and advocates have described the choices that shape an everyday life.