Turn customer conversations and buying behaviour into clearer decisions about the problem, segment and offer.
A useful invitation names the situation you want to understand, the time requested and how the conversation will be used. It gives the recipient a straightforward way to decline.
Read field noteA recent purchase gives you a concrete sequence to investigate: the trigger, alternatives, people involved, trade-offs and outcome. A question about what someone might buy often produces a polite prediction.
Read field noteThe user experiences the workflow, the buyer manages the purchase and the approver can authorize or block it. One person may hold several roles in a small business.
Read field noteUse an evidence table that preserves the participant's context, the event described and your interpretation separately. A tidy collection of quotes can conceal inconsistent segments or contradictory accounts.
Read field noteA leading question embeds the answer you hope to hear, frames one choice as obviously better or introduces your solution before understanding the experience. Neutral prompts ask about a specific event and allow disagreement.
Read field noteStart narrow enough that participants share a recognizable situation, task and decision context. Industry alone may not be sufficient.
Read field noteAsk for recent occurrences and reconstruct their timing rather than relying on words such as often or constantly. Frequency matters alongside consequence: a rare failure can be severe, while a daily irritation can remain tolerable.
Read field noteThe workaround reveals how the customer currently allocates effort, money and risk to solve the problem. A spreadsheet, manual message or extra employee may offer advantages your product overlooks.
Read field notePresent a concrete offer, a clear price or price range and an honest description of availability. Ask for a next step that reflects genuine effort, such as a scoped pilot discussion.
Read field noteCompare the context behind the requests before choosing a compromise. Opposite feedback can reflect different roles, business stages, workflows or frequency of use.
Read field noteA short sprint should reduce uncertainty about one decision and leave an evidence record for the next test. It is not a promise to validate an entire business in five days.
Read field noteThe brief should name the segment, the triggering situation, the current workaround, the consequence and the evidence still missing. It gives product, sales and operations a common starting point without prematurely committing them to a feature.
Read field note