Customer problem
A customer problem is a need, difficulty, constraint, or desired outcome experienced by an intended user or customer that a product or service may address.
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.
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 the identification of API capabilities before operations receive programming representations.
- How deep it goes
- Develops a procedure for checking scope, outcome usage, perspectives, and underlying reasons; defers programming interface design.
- Examples
- Uses a microwave oven, online shopping, address updates, and car rental to distinguish user goals from unsuitable capabilities.
- What you can do after
- Practice/perform needs analysis to select versatile operations and challenge unnecessary or provider-driven steps.
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.
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.
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.
Also covered in
- Collaborative Software Design: How to facilitate domain modeling decisions
- Interview Speak
- Think Like a CTO
- The Art of AI Product Development
- The Well-Grounded Data Analyst
- Test Driven: Practical TDD and Acceptance TDD for Java Developers
- BDD in Action, Second Edition
What to know first
- clientA client is a person, organization, device, or software component that receives or uses a product, service, resource, or functionality provided by another party or system.
- userA user is a person or other principal that interacts with a system or is represented by it.
- user experienceUser experience is a person’s overall perceptions and responses resulting from interacting with or using a product, service, or system.
- target audienceA target audience is the intended person, group, or system that a product, service, program, or communication is designed to serve or reach.
Related concepts
- capabilityaddressed by · A capability is an ability or defined authority that enables an entity to perform an action, provide a function, or achieve an outcome.
- failure modecontrasts with · A failure mode is a distinct way in which a system, component, process, or operation can fail or produce an undesirable result.
- roadmapused by · A roadmap is a time-oriented planning artifact that communicates intended goals, initiatives, milestones, capabilities, or changes and their sequence.
- software engineeringaddressed by · Software engineering is the disciplined application of engineering principles, methods, and tools to the specification, development, operation, and maintenance of software.
- user-centric designaddressed by · User-centric design is an approach that shapes products, services, or processes around users’ needs, goals, behaviors, constraints, and experiences.
Questions about customer problem
What is customer problem?
A customer problem is a need, difficulty, constraint, or desired outcome experienced by an intended user or customer that a product or service may address.
Which Manning books explain customer problem?
Lead Developer Career Guide, Architecture Modernization: Socio-technical alignment of software, strategy, and structure, The Design of Web APIs, Second Edition, Design for Developers, Tech Startup Toolkit, Effective Conversational AI and The AI Pocket Book.
What should I know before learning customer problem?
Manning books that teach customer problem usually introduce client, user, user experience and target audience first.
What is the difference between customer problem and client want?
A customer problem is a need, difficulty, constraint, or desired outcome experienced by an intended user or customer that a product or service may address. A feature, design element, or outcome that a client prefers or requests, whether or not it is necessary for the project.
What is customer problem also called?
Customer problem is also called pain point, user need or customer need.
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.






