liveBook · Manning

Customer problem

A customer problem is a difficulty, unmet need, requirement, or desired outcome experienced by a product or service’s intended customers.

How 7 Manning books explain it

Lead Developer Career Guide

A capability, outcome, or condition required by the people who use a software system.

How it is used
Frames client conversations and proposed technical approaches around the challenge software must address.
How deep it goes
Explains how to distinguish wants from needs and investigate users’ experiences, stopping short of a formal requirements method.
Examples
Uses an over-engineered B2B system, end-user focus groups, and a table pairing requested features with underlying needs.
What you can do after
Practice/perform client and end-user conversations to test whether a proposed solution addresses the underlying need.

Read how Lead Developer Career Guide explains customer problem →

Architecture Modernization: Socio-technical alignment of software, strategy, and structure

A user need is a requirement, problem, or desired outcome experienced by a person who uses a product or service.

How it is used
Anchors modernization choices in what users value and gives Wardley value chains a starting point.
How deep it goes
Provides mapping steps and discovery practices, while warning that interviews do not yield perfect requirements.
Examples
Uses an online food delivery marketplace, contact with real users, and an interview question about abandoned requests.
What you can do after
Practice/perform user-need discovery and mapping to inform modernization priorities.

Read how Architecture Modernization: Socio-technical alignment of software, strategy, and structure explains customer problem →

The Design of Web APIs, Second Edition

A user need is a desired outcome or capability that a product or interface is expected to satisfy for its users.

How it is used
Guides API designers from user needs toward versatile capabilities that satisfy consumers without exposing provider internals.
How deep it goes
Explains scope validation, perspective checks, outcome filtering, and why-questioning, then defers programming interface representation.
Examples
Uses the Kitchen Radar, social-network actions, online shopping scope, car rental, and banking API flows as concrete cases.
What you can do after
Apply the API Capabilities Canvas to identify user-focused use cases and operations before designing an interface.

Read how The Design of Web APIs, Second Edition explains customer problem →

Design for Developers

A user need is a problem, goal, constraint, or desired outcome experienced by a product's user.

How it is used
Defines the problem a website or application should solve before research, design, and development begin.
How deep it goes
Establishes problem statements, validation, requirements, solution design, and iterative evaluation without specifying implementation internals.
Examples
Uses Google Glass, user need statements, interviews, analytics, qualitative studies, quantitative studies, prototypes, and feedback cycles.
What you can do after
Evaluate/understand customer problems by defining hypotheses, validating them with research, and iterating designs against user needs.

Read how Design for Developers explains customer problem →

Tech Startup Toolkit

A customer need is a problem, requirement, preference, or desired outcome that a customer seeks a product or service to address.

How it is used
Guides target-market selection, value delivery, and differentiation during early startup planning.
How deep it goes
Works through research questions and a spreadsheet segmentation-chart output rather than prescribing a product solution.
Examples
Uses discovery calls, demos, customer conversations, and a horizontal segment spreadsheet as working artifacts.
What you can do after
Apply it via a spreadsheet to compare segments, needs, trends, and market attractiveness.

Read how Tech Startup Toolkit explains customer problem →

Effective Conversational AI

A user pain point is a specific difficulty, frustration, or unmet need experienced by a user during an interaction with a system or service.

How it is used
Guides chatbot improvement by focusing teams on user difficulties that hinder performance and success.
How deep it goes
Identifies problems through metrics, conversation logs, surveys, and transcripts, while cautioning against acting on isolated reports.
Examples
Uses vaccine eligibility, appointment scheduling, response delays, and generic banking advice as examples of user difficulties.
What you can do after
Diagnose chatbot deficiencies by combining direct user feedback with conversation transcripts and checking whether problems recur.

Read how Effective Conversational AI explains customer problem →

The AI Pocket Book

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

How it is used
Guides choosing whether AI is appropriate by clarifying the customer’s need before selecting an implementation.
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.

Read how The AI Pocket Book explains customer problem →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.