liveBook · Manning

Antipattern

As explained in The AI Pocket Book

A commonly repeated but harmful approach that looks plausible yet tends to produce bad outcomes.

An anti-pattern is a plausible-looking approach that keeps getting repeated even though it tends to cause bad outcomes. Here, it means building around a vision first and customer needs second: the “if you build it, they will come” mentality. section 4.2

The core problem is weak validation. When a team starts from “a great idea” and assumes the product will sell itself, it can ignore real customer problems, miss product-market fit, and end up with something nobody wants. section 4.2

The treatment points to a customer-centric alternative:

  • build a minimal product early, like a prototype or mock-up, to learn what customers actually need. section 4.2
  • go back to the drawing board when AI is trendy, and check whether AI is really the right solution. section 4.2
  • use product validation before going all-in on a solution. section 4.2

The warning is blunt: unless the work is pure research or similarly noncommercial, putting AI before the customer is usually a bad bet. section 4.2

How The AI Pocket Book covers it

How deep it goes
Defines the anti-pattern, explains its cause and failure mode, and suggests a customer-centric alternative.
Examples
Uses “if you build it, they will come,” prototypes, mock-ups, and the case of AI being trendy.
What it assumes
Assumes basic familiarity with customer needs and product validation, and explains the anti-pattern from zero.
What you can do after
Diagnose/debug with it by checking whether a project serves customers first or just chases an AI solution.
How it connects
Links entrepreneurship, innovation, lean movement, product-market fit, and customer-centric approach.

Also explained in

Compare how 5 books explain antipattern →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of The AI Pocket Book. The section links point to the parts of the book it draws on.