What makes a membership worth keeping?
A four-method study designed to find the moments that earn continued use of a wearable membership - and the moments where that value quietly stops arriving.
- Role
- Research designer - sole author
- Context
- Subscription hardware products can keep usage steady while perceived value erodes. Usage data shows the erosion late; it does not explain it.
- Business question
- Which member needs should be prioritized to sustain perceived value and reduce avoidable disengagement?
- What I owned
- The brief and decision framework
- Hypotheses and sampling plan
- All four method protocols
- Participant instruments
- Synthesis framework and prioritization rule
- Methods
- Social media scan
- 10-day photo diary
- 45-minute product demo
- 60-minute generative journey mapping
Independent, unaffiliated, and not yet fielded. This is a proposed study I designed on my own initiative. I have no affiliation with Oura, no access to internal or proprietary data, and no relationship with the company. No fieldwork has been conducted. Every worksheet shown is blank. There are no participants, no findings, no quotes, and no outcomes on this page - only the design that would produce them.
Identify the moments that earn continued use.
I want to learn when members get enough understanding, reassurance, or practical support to keep valuing the product - and when that connection weakens. This is framed as an opportunity to investigate, not as evidence that a retention problem exists. That distinction matters: research designed to confirm a problem tends to find one.
Value worth keeping
What continues to justify membership after the novelty fades?
Friction worth fixing
Which trust, interpretation, or real-life barriers weaken perceived value?
Investment worth testing
Which product or lifecycle changes deserve validation first, and for whom?
| Question | What the research must establish | Decision it informs |
|---|---|---|
| B1 - What sustains value? | Which recurring benefits matter after three or more months: learning, reassurance, practical action, or passive awareness? | Which benefits to reinforce in ongoing education and membership communication. |
| B2 - What weakens value? | Where the experience breaks down: trust, clarity, fit with real action, effort, or a change in the member's own needs. | Whether to fix comprehension, navigation, guidance, or expectation-setting. |
| B3 - What to test first? | Which unmet needs recur, matter deeply, and hold up across methods. Which differ by member context. | Which opportunity and audience lead the next product or message test. |
Every method exists to close a specific decision gap. If it doesn't, it doesn't run.
Four methods, sequenced deliberately: capture ordinary use before probing deeply, diagnose specific episodes inside the product, then use those episodes to ground future-state mapping. The same members move through all three primary methods, which is what links a real moment to its later interpretation.
Four methods, one chain of evidence.
- 01
Social media scan
Closes: what value and friction language should we investigate at all? Public first-person accounts, captured with enough context to understand the episode. Output: a search log and contrasting themes.
- 02
10-day photo diary
Closes: when is value experienced or lost in everyday life? Ten days balances ordinary routines against weekends and interruptions. Missing entries are evidence too. Output: member timelines with context.
- 03
45-minute product demo
Closes: is the barrier finding, understanding, trusting, or applying the information? Four very different problems with four different owners inside a company. Output: observed paths and workarounds.
- 04
60-minute generative journey map
Closes: what support would make the greatest difference, and why? Built from the member's own recent episodes rather than a prescribed "correct" journey. Output: current and ideal maps, plus member-ranked priorities.
Sample the conditions that shape value, not just the people.
Optionally, four to six former members in separate retrospective interviews - people who stopped within the past year. They would not complete a current-use diary.
Variation is built in deliberately: length of use, daily versus occasional checking, health goals, satisfaction, comfort with data, and the work, travel, and caregiving constraints that shape whether anyone acts on what they see. Screening asks about original expectations, recent use, the features they return to, other wearables owned, and whether they have considered leaving.
Stated sampling boundary
Weekly-use eligibility deliberately excludes the least engaged members - the people most likely to churn. This sample cannot estimate churn rates and is not designed to.
The member's daily evidence.
The diary worksheet is built to capture interpretation, not behavior alone. The sequence - expectation, observation, meaning, action, obstacle - is what separates a member who understood the information and could not act from one who never understood it. Those two members need opposite interventions.
Daily entry
One short entry about the usual check-in, plus up to three additional meaningful moments across the ten days.
- Before checking, how did you feel?
- What did you notice, and what did you think it meant?
- Did it match your experience? How?
- What did you feel or decide next?
- What helped, or got in the way?
Later reflection: what actually happened? Did your view of the information
change?
Usefulness: 1 not useful - 5 extremely useful. Explain the rating in your own
words.
| When | Participant | Researcher |
|---|---|---|
| Day 0 | 20-minute onboarding and practice entry | Explain consent, cropping, privacy; record baseline |
| Days 1–10 | One short entry per usual check-in | Neutral reminders; log missing entries and context |
| Day 5 | 10-minute midpoint check-in | Ask whether documenting is changing app use |
| Days 3, 6, 10 | Brief evening reflection | Compare the intended action with what happened |
Participants are never asked to check more often or change health behavior. A diary still influences attention, so that limitation is recorded as part of the data rather than assumed away.
Diagnosing the barrier inside the experience.
Forty-five minutes, within three days of the diary closing. The member controls their own phone and chooses what to share. The purpose is to watch interpretation happen rather than to hear it recalled.
| Time | Task | Prompt |
|---|---|---|
| 5 min | Opening and permission | Show only the screens you are comfortable sharing. |
| 10 min | Normal check-in | Where do you start? What do you skip? |
| 10 min | Revisit a diary moment | Show me a match or a mismatch. How did you interpret it? |
| 10 min | Action and workaround | Show an insight you followed, adapted, or ignored. Why? |
| 10 min | Value and reflection | What would you show a friend to explain the value? |
Captured throughout: task, path, interpretation, confidence, emotion, friction, workaround, and value moment - with observation recorded separately from retrospective explanation.
Building the ideal journey with the member, not for them.
Sixty minutes, within a week of the demo. Twenty-five minutes mapping the current experience, twenty designing the ideal one, ten choosing three priorities, five on what a healthy relationship with the product would look like. The current map is photographed before anything is changed, so the comparison survives.
Moments
- Review a score
- View a trend
- Ignore the app
- Add your own
Emotions
- Reassured
- Confused
- In control
- Add your own
Actions
- Adapted the advice
- Sought more context
- Took no action
- Add your own
Needs
- Understand why
- Fit my real day
- Use less effort
- Add your own
Fig. 01 - Vocabulary cards. Blank cards are introduced first; these examples provide language without prescribing the answer.
Capture the need behind a requested feature. A participant's idea is input for design, not proof that a solution will work. Participants may reject, rename, or reinterpret any card, and that rejection is recorded as data.
Separating what the evidence establishes from what I would infer.
Every method has a ceiling. Naming those ceilings in advance is what stops a vivid quote from becoming a company-wide conclusion.
| Evidence source | What it can establish | What it cannot establish alone |
|---|---|---|
| Social scan | Public language, episodes, and contrasting opinions | How common a view is among all members |
| Photo diary | Reported moments, context, and intended or completed actions | Unobserved behavior or causal effect |
| Product demo | Observed navigation and interpretation during the session | Normal behavior across all situations |
| Journey maps | Member priorities, meanings, and desired support | Whether a proposed change will improve retention |
How evidence is handled
- Compare within each participant first, then across participants
- Record counterexamples explicitly rather than smoothing them out
- Label social signals, self-report, observation, and researcher inference separately
How it becomes a decision
Evidence → pattern → need → opportunity. The chain is written down for each finding so a reader can see exactly where interpretation entered.
I also track my own assumptions about health data, action, and engagement - because member evidence may support a very different definition of value than mine.
A stated rule for what moves forward.
The study ends with choices, not a long list of feature requests. Four tests, applied consistently, with the scoring logic fixed before any data exists.
| Test | Evidence examined | Decision rule |
|---|---|---|
| Member importance | How consequential is the issue in the member's own account? | Give depth of impact weight alongside recurrence. |
| Evidence confidence | Diary episode, demonstrated behavior, explanation, and counterexample | Advance well-supported needs; investigate weak explanations. |
| Business relevance | Connection to ongoing usefulness or perceived membership value | State the plausible mechanism without claiming retention lift. |
| Actionability and risk | Addressable barrier, team ownership, dependencies, possible harm | Define the smallest useful test and its guardrails. |
Two or three priority opportunities - plus what I would defer, and why.
No scoring totals are assigned before data collection. Product feasibility would require input from internal teams I do not have access to, and the brief says so.
The format every recommendation takes
A template, not a completed finding.
- For [member context], prioritize [need] at [moment], because [evidence].
- Test [product or lifecycle change].
- Evaluate [member outcome] and [business outcome].
- Watch for [trade-off or unintended effect].
Each recommendation carries source IDs, contrary evidence, a confidence level, the likely owner, and the next test.
What success would look like - and what it would not prove.
| Business goal | Near-term signal to test | Later outcome and safeguard |
|---|---|---|
| B1 - Sustain value | Can a member name a personally useful benefit and explain why it matters? | Observed continuation or renewal - with stated intent held separate from behavior. |
| B2 - Resolve friction | Can the member find and accurately explain the relevant information? | Sustained usefulness, monitoring confusion, effort, and unwanted pressure. |
| B3 - Prioritize support | Does a targeted change help the intended audience in realistic situations? | A controlled test of product or lifecycle impact, with segment differences. |
The limit of the method, stated in the deliverable
Qualitative research explains needs and mechanisms. It does not establish causal retention impact or support a financial forecast. Any revenue claim would require internal data and a subsequent controlled test.
Nine weeks from scope to decision brief.
Consent, private storage, participant IDs, and separate permission for any portfolio image. No health advice is given at any point in the study.
Pilot the prompts, record study reactivity, keep contrary cases, and preserve source and app-version context so a finding can be traced back to the conditions that produced it.
What this version represents.
What exists today
A complete, ready-to-field research design: business brief, decision framework, hypotheses, recruitment plan, four method protocols, blank participant instruments, a synthesis framework, a prioritization rule, and a nine-week execution plan.
What does not exist
Fieldwork has not been run. There are no participants, no findings, no member quotes, no completed journey maps, and no outcomes. Counts and durations on this page are planning choices, not results.
Notes & sources
- Affiliation. Independent portfolio project. No relationship with Oura Health Oy. No internal, proprietary, or partner data was used or requested. Product feature references are drawn from publicly available documentation and would be re-verified for app version and availability before fieldwork began.
- Instruments. All worksheets reproduced here are blank templates. No member data appears anywhere on this page.
- Ethics. Consent, private storage, participant IDs, and separate portfolio-image permission are built into the protocol. The study gives no health advice and does not ask participants to change health behavior.