liveBook · Manning

Customer problem

As explained in The AI Pocket Book

A genuine problem or requirement that a product can satisfy for its intended users.

Start with the problem, not the technology. Understand what customers genuinely need, then choose the most reliable way to solve it; AI may be useful, but it is not the default. section 4.11

A practical test

For an AI assistant, ask whether you can describe the task clearly and validate its output easily. Translating hotel reviews may tolerate occasional hallucinations; a task where errors are unacceptable may require another approach. An existing open-source tool may also beat an AI-based reinvention. section 4.11

A real customer problem changes how a product should be judged:

  • Check whether users care about accuracy, explainability, scalability, or small details before building. section 4.11 section 5.9
  • Treat a prototype as evidence-gathering when its purpose is to test whether a real need exists, not as the final product. section 5.9

How The AI Pocket Book covers it

How deep it goes
Frames problem-first evaluation through task clarity, output validation, error tolerance, explainability, and existing alternatives.
Examples
Uses hotel-review translation, open-source coding tools, no-code prototypes, and logistics operations to illustrate differing needs.
What you can do after
Evaluate whether a customer problem warrants AI, another tool, a prototype, or a more demanding engineered solution.
How it connects
Connects customer problems to AI assistants, hallucinations, explainability, prototypes, and mission-critical applications.

Also explained in

Compare how 7 books explain customer problem →

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.