Future & Innovation
What People Actually Ask AI — And What It Reveals
A conversation on the surprising shape of mass AI usage and what it tells us about work, learning, and trust
Across the public usage studies from the last 18 months — OpenAI's own, Anthropic's economic index, large surveys from Pew and the Reuters Institute — the dominant categories are remarkably consistent. They are not what the press tends to highlight. Writing help. Drafting emails, polishing messages, rewriting in a different tone. This is consistently the single largest category of usage,…
By Capio Pro — Executive AI advisory.
Chief Product Officer (CPO)
I'm trying to understand the real shape of consumer AI usage before we redesign our own product. What is the most common thing people actually ask AI? Not the marketing answer — the real one.
AI Leadership Agent — Future Strategy Advisory
Across the public usage studies from the last 18 months — OpenAI's own, Anthropic's economic index, large surveys from Pew and the Reuters Institute — the dominant categories are remarkably consistent. They are not what the press tends to highlight.
- Writing help. Drafting emails, polishing messages, rewriting in a different tone. This is consistently the single largest category of usage, often a third or more of all prompts.
- How-to and explanation questions. "How do I do X in Excel," "explain this contract clause," "what does this error mean." Essentially: search, but answered.
- Coding assistance. Even outside professional developers — formulas, scripts, debugging small things.
- Personal advice and reflection. Career questions, relationship dilemmas, health worries, parenting. Quietly enormous, and growing fastest.
- Learning and study. Students explaining concepts back to themselves, adults learning new fields, language practice.
The most common thing people ask AI is not "build me something." It is "help me say this better" and "help me understand this." AI's killer app, so far, is articulation and explanation.
Chief Product Officer (CPO)
What does that pattern tell us about what people actually need? I want to design product around the underlying need, not the surface query.
AI Leadership Agent — Future Strategy Advisory
Three underlying needs sit beneath those categories, and they are the real product opportunities:
- Lowering the cost of articulation. Most people have ideas they cannot express well, and that gap costs them socially and professionally. AI compresses that gap. Any product that makes a user sound more competent than they are will win.
- Lowering the cost of asking. People will not interrupt a colleague to ask something small or embarrassing, but they will ask a machine. The market opportunity is in domains where people previously suffered in silence — medical, legal, financial, emotional.
- Lowering the cost of trying. AI lets people prototype an email, a plan, a piece of code, a conversation. The first draft has become free. The strategic implication is that the value moves from production to judgment about what to keep.
Design for the user who is about to do something they're slightly afraid of. That is who is actually using AI today, in numbers no one is publishing.
Chief Product Officer (CPO)
And what should worry me about this pattern? What's the dark side of AI being mostly a writing and asking assistant?
AI Leadership Agent — Future Strategy Advisory
Three things are worth taking seriously — not panicking about, but designing around:
- Erosion of independent thinking. If the first draft is always AI's, people lose the muscle of forming their own first thought. The most thoughtful AI products will deliberately preserve user-first-draft moments.
- Outsourcing emotional labor. People are asking AI about grief, conflict, and intimate decisions. That can be net positive — or it can short-circuit the human connections that make us resilient. The product question is when to gently redirect.
- False confidence in unfamiliar domains. AI confidently answers questions about law, medicine, and finance to users who can't evaluate the answer. The responsibility for friction, citations, and "talk to a human" pathways sits squarely with product teams.
Designing for the most common question — "help me with this" — also means designing for what people deserve, not just what they request.