User value research
User value research is the qualitative work of learning what users actually care about, in their own terms rather than the team's. The methods are user-facing: interviewing users, asking them open-ended questions by email, and reading the support tickets of users trying to find success. The conversations stay focused on what users are trying to accomplish in their lives, with the product treated as one tool among many they might use to get there.
Definition
The qualitative discipline of learning what users actually value, on user terms.
The epistemic shape
User value research runs against specific quantitative evidence about a cohort, with a specific question: this cohort registered in the data; what were they caring about that produced that registration? Multiplier analysis findings are the canonical entry point — a candidate behavior surfaces a cohort, and user value research investigates the why.
The evidence base is asymmetric. The multiplier evidence pre-confirms that something was being cared about by users in the cohort — the disproportion in the data is itself evidence of differentiated user-side investment. The qualitative work fills the content gap: what specifically did they care about? Quantitative on the existence of caring, qualitative on the content of caring.
This framing changes what counts as a productive interview. A conversation that surfaces detailed user backstory and life context but doesn't ladder back to "why did this cohort engage in this behavior at this rate" hasn't completed its job. A conversation that surfaces "I came to do X, and this part of the offering delivered X for me in a way other tools didn't" is productive — the user-care content is named, and it ladders back to the quantitative finding that triggered the investigation. Without the pre-existing evidence as a keel, user value research drifts toward feature requests, satisfaction ratings, and general impressions.
What it produces
The work produces a grounded picture of the transition users are pursuing, captured in their own vocabulary and framing, with the offering treated as one source of affordances among many they marshal. The framing, sequence, and vocabulary the user supplies are themselves part of the data — they're how the cohort actually thinks, and downstream apparatus (sorting hat questions, copy, path design) operates on that framing rather than the practitioner's reframing of it.
The methods
Three methods serve user value research, distinguished by data shape:
- User interviewing: live conversational data-gathering, typically structured by the situation explorer.
- Email inquiry: open-ended emails to recent customers asking about context, situation, or reasons for engaging. The replies themselves are data; replies that warrant deeper exploration become entry points to phone follow-up.
- Starting-churn CS ticket pattern analysis: reading early-lifecycle support tickets as in-pursuit articulations of what users were trying to do, surfaced by the friction they hit.
The methods are general capabilities that adapt to the investigation question. Multiplier-cohort intent is the dominant commercial application; sustained customers, churned customers, and missed conversions become the relevant populations when the question shifts to long-arc value, failure modes, or recovery opportunities.
Governing disciplines
A handful of disciplines apply across the methods:
- Transition focus: ask about the user's transition, not the offering itself. The offering is one set of affordances among many the user marshals; conventional offering-feedback questions produce offering data rather than transition data.
- Listen-don't-talk: the interviewer is there to have their mind shaped, not to shape the interviewee's. Preserves the interviewee's vocabulary, sequence, and connections.
- Hand-sent feeling: outreach reads as a personal inquiry from a real person, not mass-blast or marketing automation.
- Scalpel-not-sledgehammer recruitment: small batches with iteration, aiming for ~50 subjects per project.
- Question-dependent recruitment: the cohort to recruit from depends on the investigation question.
Example
A productivity tool runs multiplier analysis on its signup cohort and finds users who connected a Slack integration in their first week converted at 4.2x baseline. The number tells you something was cared about by that cohort; it doesn't tell you what.
User value research starts the next step. Pull 30-50 users from the Slack-integration-plus-converted cohort, send hand-sent-feeling email inquiries asking what they were trying to do when they signed up, and follow up with phone interviews on the replies that warrant deeper exploration. The situation explorer worksheet structures those interviews around sought state, prior states, and what comes after. Listen-don't-talk keeps the interviewer from contaminating the interviewees' accounts with their own framing.
The output is intent content — "I wanted my team to see project updates without having to log into another tool" — that explains the multiplier and feeds downstream decisions about which paths to invest in, what to put in onboarding copy, and how the sorting hat should classify future signups.