Problem
Product flows are often documented as boxeas and arrows while the exchange beneath them remains implicit. Teams can optimize a step without understanding what the organization is asking, what the end users believes, or how the organization will interpret their response.
Purpose
Conversation Mapping makes both sides of the product conversation visible. It helps a team inspect whether the exchange is clear, reciprocal, and capable of learning.
Components
- Organizational expression: the claim, request, promise, rule, or choice the product presents.
- User's context: the goal, knowledge, constraints, and degree of agency brought to the exchange.
- Behavioral reply: what the user does, avoids, repeats, abandons, or works around.
- Organizational interpretation: how the organization reads that behavior and what it may misunderstand.
- Response: the product, policy, or operational change that closes the loop.
How to use it
Choose one consequential product moment. Write the exchange in plain language from both perspectives. Add observed evidence where it exists and mark assumptions where it does not. Look for one-way demands, missing explanations, false choices, and replies the organization records but cannot act upon.
Example
A collaboration product promises that an upgrade enables unlimited teamwork. A user invites several colleagues, discovers that each invitation creates another paid seat, and cancels the upgrade. The cancellation is the final reply, but the earlier invitation and pricing checks show where the product's promise and the user's interpretation diverged.
Limitations
The map is an interpretive tool, not a substitute for research. Behavior can have several explanations, and organizational intent does not determine how a message is received. Validate the map with people and operational evidence.