People really hate AI, so why can’t they get enough?

The recent surge in AI adoption, despite widespread public skepticism, presents a nuanced challenge and opportunity for how technology is built and presented. This MIT Technology Review piece highlights a fundamental tension: users are increasingly reliant on AI-powered tools for practical benefits, even as they express general distrust or discomfort with the technology itself. The core argument is that utility often trumps perception, driving usage even when underlying sentiment is negative. This dynamic directly impacts how developers, founders, and operators should approach their AI integrations and product messaging. For instance, an indie SaaS founder developing a content scheduling tool in Austin, Texas, might find that promoting "AI-powered content generation" alienates some users, while advertising "faster, more effective social media campaigns" using an embedded AI system is highly attractive. Similarly, a small e-commerce shop owner in Portland, Oregon, seeking to automate customer service might initially balk at a "chatbot solution" but readily adopt a "24/7 personalized shopping assistant" that uses identical underlying AI. The key is to emphasize tangible outcomes and direct user benefits, rather than the technology itself, to overcome apprehension. Understanding this paradox allows for more effective product positioning and feature prioritization. A logistics startup in Chicago, Illinois, looking to optimize delivery routes could leverage AI for efficiency gains. Instead of branding it as an "AI-driven route planner," they might present it as a "Smart Logistics Optimizer" that guarantees X% faster delivery times and Y% fuel savings, with the AI functioning as an invisible, performance-enhancing engine. This strategy capitalizes on the undeniable utility AI offers while mitigating the public's complex relationship with the term itself. To capitalize on this insight, consider a small, practical experiment this week. For any new feature or product you are developing that uses AI, draft two distinct marketing or user onboarding messages. One should explicitly mention "AI" or "machine learning," while the other should focus purely on the functional outcome and user benefit, omitting any direct reference to the underlying technology. Observe which approach resonates more positively with early testers or internal stakeholders, and be prepared to iterate based on that feedback.