← BACK TO NOTES
29 / IDEAS · AI · 8 MIN

What AI still can't do, and why that's the interesting part.

The limits of current AI are more useful to product thinking right now than its capabilities are.

AI still struggles with judgment under genuine ambiguity, accountability for a decision, and knowing what it doesn’t know — and those limits, not its capabilities, are what should shape good product design right now. Most conversations about AI focus on what it can now do, because that list keeps growing and is genuinely exciting to talk about. The more useful product question, at least for anyone trying to build something people will actually trust, is what it still can’t.

Judgment under real ambiguity

Current AI is strong at pattern completion and weak at judgment calls where the right answer genuinely depends on context nobody wrote down — the unstated exception, the specific relationship history, the thing an experienced person would just know without being told. It can suggest options well, drawing on patterns from everything it’s seen before. It’s far less reliable at knowing when a situation calls for breaking its own pattern entirely, because the situation in front of it doesn’t actually resemble the ones the pattern was learned from.

This gap matters most in exactly the situations where getting it right matters most — the edge cases, the exceptions, the moments that don’t look like the common case. Those are disproportionately the moments where trust is either earned or lost.

Accountability for a decision

AI can produce a recommendation. It can’t be accountable for the outcome the way a person can — there’s no one on the other end of the recommendation who bears the consequence of it being wrong, who can be asked to explain their reasoning after the fact, or who has a reputation at stake in getting it right. That distinction matters enormously in any workflow involving money, health, legal exposure, or anything with real consequences attached.

This isn’t a criticism of the technology so much as a structural fact about what accountability actually requires. Accountability needs a party that can be asked “why did you decide this,” held responsible for the answer, and trusted to improve based on the consequence. Building that structure around an AI system is a design problem the product has to solve — it doesn’t come for free with the model.

Knowing what it doesn’t know

Perhaps the most product-relevant limit: current systems are often unreliable at signaling their own uncertainty. A wrong answer can arrive with exactly the same confidence as a right one, delivered in the same tone, with the same apparent fluency. That equal confidence is genuinely dangerous in a product context, because it shifts real design responsibility onto the product around the model — the interface has to do the work of signaling uncertainty that the model itself doesn’t reliably signal on its own.

Why this shapes what we build

Knowing where the limits are isn’t a reason to avoid AI. It’s the design brief for where the human stays in the loop, and where the product has to earn trust rather than assume it. A product that’s honest about these limits — that shows its reasoning, flags uncertainty, and keeps a human in the loop for consequential decisions — will generally earn more durable trust than one that papers over the limits with a confident interface.

Common questions

Does this mean AI shouldn’t be used for any consequential decisions at all? Not necessarily — it means consequential decisions need a design that accounts for these limits, typically by keeping a human accountable for the final call rather than letting the system decide unsupervised.

Will these specific limitations disappear as models improve? Some may narrow over time. The accountability limit in particular is more structural than technical — it’s about who bears responsibility for an outcome, which isn’t purely a capability question a better model can solve on its own.

How can a product signal AI uncertainty honestly to users? Show confidence levels or reasoning where possible, flag when a request falls outside common patterns, and design an easy path for a human to review or override rather than presenting every output with uniform authority.

Takeaway: the interesting product work right now is designing for AI’s limits, not just its capabilities.

03 / THE NEXT STONE

Have an idea worth exploring?

MAKE THE NEXT MOVE →