Shared research study link
The Kitchn Home Cook Study
Understanding how home cooks engage with food media and recipe websites
Study Overview
Updated Jan 21, 2026
Research question: We studied how home cooks engage with food media and recipe websites to learn where they go, what builds trust, what frustrates them, and what would drive repeat use or payment.
Research group: Six US home cooks (ages 25–54) across CA/MO/AR, including a Spanish‑speaking caregiver, a culturally attuned diaspora cook, a price‑sensitive budget cook, a rural connectivity‑constrained engineer, and a data‑driven optimizer. What they said: Participants prefer video‑first, practical content for discovery paired with a concise, printable written recipe for execution; trust hinges on precise, testable details (grams, temps, pan sizes, realistic time ranges), clean cook‑friendly UX (jump‑to‑recipe, print/cook‑mode, minimal ads), community validation (real “cooked‑it” comments and creator replies), and localized substitutions.
Main insights and divergences: They reject content‑farm signals (autoplay, long SEO memoirs, stock imagery, vague “medium heat,” implausible timelines, duplicated/AI‑slurried recipes); segments vary in needs-some want macros, cost‑per‑serving and CSV/Notion export, others require Spanish‑language/community distribution, cultural provenance, and fast offline access. Takeaways: Ship a fast, ad‑light core: Jump‑to‑Recipe and one‑page Print/PDF; Cook Mode (stay‑awake, big next, optional audio); grams toggle with required fields (yields, pan sizes, internal temps); explicit substitutions plus storage/reheat; Spanish labels; comment triage with “cooked‑it” surfacing and visible version history; and PWA/offline readiness.
Monetization and guardrails: Keep basics ungated, test one‑time printable packs for price‑sensitive users, and offer an optional Pro tier for power users (macros, local cost presets, batch‑scaling, CSV/Notion export) while enforcing “real kitchen” video guidelines and transparent sponsorships to sustain trust.
Research group: Six US home cooks (ages 25–54) across CA/MO/AR, including a Spanish‑speaking caregiver, a culturally attuned diaspora cook, a price‑sensitive budget cook, a rural connectivity‑constrained engineer, and a data‑driven optimizer. What they said: Participants prefer video‑first, practical content for discovery paired with a concise, printable written recipe for execution; trust hinges on precise, testable details (grams, temps, pan sizes, realistic time ranges), clean cook‑friendly UX (jump‑to‑recipe, print/cook‑mode, minimal ads), community validation (real “cooked‑it” comments and creator replies), and localized substitutions.
Main insights and divergences: They reject content‑farm signals (autoplay, long SEO memoirs, stock imagery, vague “medium heat,” implausible timelines, duplicated/AI‑slurried recipes); segments vary in needs-some want macros, cost‑per‑serving and CSV/Notion export, others require Spanish‑language/community distribution, cultural provenance, and fast offline access. Takeaways: Ship a fast, ad‑light core: Jump‑to‑Recipe and one‑page Print/PDF; Cook Mode (stay‑awake, big next, optional audio); grams toggle with required fields (yields, pan sizes, internal temps); explicit substitutions plus storage/reheat; Spanish labels; comment triage with “cooked‑it” surfacing and visible version history; and PWA/offline readiness.
Monetization and guardrails: Keep basics ungated, test one‑time printable packs for price‑sensitive users, and offer an optional Pro tier for power users (macros, local cost presets, batch‑scaling, CSV/Notion export) while enforcing “real kitchen” video guidelines and transparent sponsorships to sustain trust.
Participant Snapshots
6 profiles
Cory Andres
I’m in a reset phase: a 25-year-old San Diego renter with no current income, optimizing for runway, comfort, and low-friction routines. I research hard, buy for durability over signaling, and favor sustainable work and health habits over intensity.
Shontae Villalvazo
I’m a practical, bilingual wife in Compton, managing a paid-off home, family needs, and church ties on a tight budget. I default to price, ease, and trust, and I tune out hype, hassle, and messaging that feels judgmental.
Jean Mitchell
I’m a 54-year-old married renter in Burbank, trained in social work and currently out of the workforce. I live carefully on a tight budget, stay active, and prefer plain facts, fair prices, and things that genuinely work.
Chancelor Mullen
I’m a 29-year-old software developer in rural Missouri, married, analytical, and practical about spending. I prefer durable, low-friction tools, trust evidence over hype, and balance remote screen work with regular activity while managing asthma, depression…
Ryan Tagle
I’m a practical, tech-minded homeowner in Indio living on stability more than income. Faith, routine, and clear cost guide my choices; I compare options, avoid hype, stay active, and watch spending closely because I’m uninsured.
Crystal Montana
I’m a 44-year-old healthcare account manager in Jonesboro: married, LDS, organized, and budget-aware. I value clear pricing, reliable service, practical routines, and staying active, while managing everyday health and household decisions without much patien…
Cory Andres
I’m in a reset phase: a 25-year-old San Diego renter with no current income, optimizing for runway, comfort, and low-friction routines. I research hard, buy for durability over signaling, and favor sustainable work and health habits over intensity.
Shontae Villalvazo
I’m a practical, bilingual wife in Compton, managing a paid-off home, family needs, and church ties on a tight budget. I default to price, ease, and trust, and I tune out hype, hassle, and messaging that feels judgmental.
Jean Mitchell
I’m a 54-year-old married renter in Burbank, trained in social work and currently out of the workforce. I live carefully on a tight budget, stay active, and prefer plain facts, fair prices, and things that genuinely work.
Chancelor Mullen
I’m a 29-year-old software developer in rural Missouri, married, analytical, and practical about spending. I prefer durable, low-friction tools, trust evidence over hype, and balance remote screen work with regular activity while managing asthma, depression…
Ryan Tagle
I’m a practical, tech-minded homeowner in Indio living on stability more than income. Faith, routine, and clear cost guide my choices; I compare options, avoid hype, stay active, and watch spending closely because I’m uninsured.
Crystal Montana
I’m a 44-year-old healthcare account manager in Jonesboro: married, LDS, organized, and budget-aware. I value clear pricing, reliable service, practical routines, and staying active, while managing everyday health and household decisions without much patien…
Participant Profile
0 participants
Sex / Gender
Race / Ethnicity
Countries
Occupations
Age
Demographic Overview
No agents selected
| Age bucket | Male count | Female count |
|---|
Participant locations
No agents selected
Participant Incomes
US benchmark scaled to group size
| Income bucket | Participants | US households |
|---|
Source: U.S. Census Bureau, 2022 ACS 1-year (Table B19001; >$200k evenly distributed for comparison)
Media Ingestion
Connections appear when personas follow many of the same sources, highlighting overlapping media diets.
Questions and Responses
3 questions
Response Summaries
3 questions
Word Cloud
Question Summary
Preparing summary…
Summary
Themes
| Theme | Count | Example Participant | Example Quote |
|---|
Outliers
| Agent | Snippet | Reason |
|---|
Analyzing correlations…
Generating correlations…
Taking longer than usual
Persona Correlations
Analyzing correlations…
Overview
Respondents converge on a single clear product need: low-friction, trustworthy recipe experiences that pair short technique-forward video for discovery with a concise, printable written recipe for execution. Trust is built by practical precision (measures, pan sizes, temps, failure modes), realistic presentation (real kitchens, process visibility), and cook-friendly UX (jump-to-recipe, cook-mode, printable/PDF). Distinct demographic contexts change priority order: Spanish-speaking, community-centered cooks prioritize bilingual, store-aware content and social distribution; younger technical cooks treat recipes as data and want exportable, grams-first workflows; rural/low-connectivity cooks prioritize speed and offline access; lower-income cooks foreground cost signals and one-page printables. These differences point to a core product that should be modular and locally adaptable rather than one-size-fits-all.
Total responses: 18
Key Segments
| Segment | Attributes | Insight | Supporting Agents |
|---|---|---|---|
| Spanish-speaking, midlife stay-at-home caregivers |
|
Prioritize bilingual video-first discovery delivered via community channels and recipe content that includes store-specific substitutions and simple volumetric measures; community validation and creator replies in Spanish materially increase adoption and trust. | Shontae Villalvazo |
| Older, culturally-attuned home cooks (diaspora/heritage focused) |
|
Content should surface provenance and respectful naming, include headnotes that teach the 'why', and use real-kitchen visuals; perceived cultural slippage or heavy UX friction triggers quick abandonment among these users. | Jean Mitchell |
| Lower-income, price-sensitive cooks with community discovery |
|
Design lightweight, one-page printable recipes with explicit cheap-swap guidance, clear leftover/reheat instructions and store-aware ingredient lists; avoid login walls and recurring-subscription friction-this group favors one-time purchases or free, low-friction access. | Ryan Tagle |
| Younger, highly technical/data-oriented cooks |
|
Treat recipes as systems: deliver grams-first measures, macros, internal temps, batch-scaling tools and export (CSV/Notion) integrations; this cohort will pay modest subscription fees if the product replaces multiple tools and saves workflow time. | Cory Andres |
| Rural, connectivity-constrained technically-minded cooks |
|
Offline capability, tiny-download assets (fast PDFs), PWA/cook-mode and minimal autoplay/tracking are prioritized above bells-and-whistles; rigorous testing notes and failure-mode guidance help compensate for limited access to follow-up content. | Chancelor Mullen |
| Mid-career, pantry- and budget-focused cooks in smaller cities |
|
Surface aisle-grouped shopping lists, equipment toggles (slow cooker/air fryer), clear ingredient sizes and budget signals, and place jump-to-recipe/printable cards prominently; short captioned videos help discovery and accessibility. | Crystal Montana |
Shared Mindsets
| Trait | Signal | Agents |
|---|---|---|
| Video-first discovery + written execution | Short technique videos (texture, timing cues) are the primary discovery medium; users then rely on a concise, printable written card for execution-both formats must complement each other. | Shontae Villalvazo, Jean Mitchell, Cory Andres, Chancelor Mullen, Crystal Montana, Ryan Tagle |
| Distrust of content-farm signals | SEO-driven long headnotes, stock photography, autoplay ads and unrealistic timelines prompt rapid abandonment across demographics-authenticity and practicality beat viral aesthetics. | Jean Mitchell, Chancelor Mullen, Cory Andres, Crystal Montana, Shontae Villalvazo, Ryan Tagle |
| Demand for practical precision | Clear measures (grams and cups), pan sizes, internal temps and failure modes are universal trust-builders; vague or aspirational language reduces conversion and reuse. | Cory Andres, Chancelor Mullen, Jean Mitchell, Crystal Montana, Shontae Villalvazo, Ryan Tagle |
| Cook-friendly UX expectations | Features like jump-to-recipe, printable one-pager/PDF, cook-mode (stay-awake, large navigation, audio) and fast load times are repeatedly requested and increase task completion. | Shontae Villalvazo, Chancelor Mullen, Jean Mitchell, Crystal Montana, Ryan Tagle, Cory Andres |
| Localization and pantry-aware swaps | Substitutions that reference locally available stores/ingredients and budget-aware swaps reduce friction and increase perceived usefulness across income levels and geographies. | Shontae Villalvazo, Ryan Tagle, Crystal Montana, Jean Mitchell, Cory Andres |
| Community validation matters | Comments with real cook photos, creator replies, and moderated notes (altitude, equipment differences) serve as strong adoption signals and reduce perceived risk of trying a recipe. | Jean Mitchell, Shontae Villalvazo, Crystal Montana, Ryan Tagle, Cory Andres |
Divergences
| Segment | Contrast | Agents |
|---|---|---|
| Spanish-speaking, midlife caregivers | Preference for Spanish-language, community-distributed content and store-specific substitutions vs. the default English-first, generic substitution approach favored by many mainstream recipe sites. | Shontae Villalvazo |
| Younger, technical cooks | Wants grams-first measures, exportable CSV/Notion workflows and macro data vs. older users who expect cups/tablespoons and headnote-driven guidance; younger users are willing to pay for integrated workflow tools. | Cory Andres |
| Lower-income, price-sensitive cooks | Strong aversion to subscription models and login friction preferring one-time downloads or free access vs. some younger/technical users willing to accept modest recurring fees for export and workflow value. | Ryan Tagle |
| Rural / connectivity-constrained cooks | Prioritizes offline/PWA and tiny-download assets above rich media vs. urban users who accept heavier video experiences and cloud-first interactions. | Chancelor Mullen |
| Culturally-attentive diaspora cooks | Elevates provenance, correct naming and cultural respect as trust factors beyond technical precision, causing rejection of content that renames or 'simplifies' traditional dishes. | Jean Mitchell |
Creating recommendations…
Generating recommendations…
Taking longer than usual
Recommendations & Next Steps
Preparing recommendations…
Overview
Home cooks want a low-friction, video-first + printable recipe experience that is precise (grams, temps, pan sizes, realistic times), culturally respectful, and community-validated. The fastest ROI path is to ship a clean Jump-to-Recipe, a one-page Print/PDF, and a simple Cook Mode (stay-awake, big next button, optional audio). Layer in grams toggle, storage/reheat, and substitution fields, then add Spanish labels and real-kitchen short clips. Keep pages fast (no autoplay, minimal trackers) and show trust signals (author replies, version history). Monetize via one-time printable packs for price-sensitive users and an optional Pro tier for data-driven cooks (macros, cost-per-serving, CSV/Notion export)-never gate basics.
Tailoring to Claude (Ditto API test): externalize all recipe copy, labels, and bilingual strings to manage via Ditto; ship i18n and versioned content through a structured recipe schema so future teams can scale categories and locales without rework.
Tailoring to Claude (Ditto API test): externalize all recipe copy, labels, and bilingual strings to manage via Ditto; ship i18n and versioned content through a structured recipe schema so future teams can scale categories and locales without rework.
Quick Wins (next 2–4 weeks)
| # | Action | Why | Owner | Effort | Impact |
|---|---|---|---|---|---|
| 1 | Add Jump-to-Recipe and clean one-page Print/PDF | Directly addresses top friction (SEO fluff, pop-ups) and converts saves into actual cooking. | Product + Eng + Design | Low | High |
| 2 | Cook Mode v0 (stay-awake, big next/prev, step timers) | Phone-in-kitchen usability is a universal need; reduces abandonment mid-cook. | Eng + Design | Med | High |
| 3 | Grams toggle and critical fields (pan size, temps, yields) | Builds trust through precision without alienating cups-first users. | Content Ops + Eng | Low | High |
| 4 | Spanish labels and buttons (bilingual affordances) | Captures Spanish-speaking segment; quick win with Ditto-managed strings. | Design + Content Ops | Low | Med |
| 5 | Comment triage + pin ‘cooked-it’ notes | Surface real-world results and creator replies; boosts perceived reliability. | Community + Content Ops | Med | Med |
| 6 | Remove autoplay, reduce trackers; hit LCP < 1.5s | Speed is a dealbreaker across segments; removes ‘content farm’ red flags. | Eng | Low | High |
Initiatives (30–90 days)
| # | Initiative | Description | Owner | Timeline | Dependencies |
|---|---|---|---|---|---|
| 1 | Structured Recipe System v1 | Define CMS schema and UI to capture weights (grams + cups), internal temps, pan sizes, realistic time ranges, substitutions, storage/reheat, and version history. Render with schema.org/Recipe for SEO and trust. | Product + Content Ops + Eng | 4–6 weeks | CMS updates, Schema.org Recipe markup, Ditto integration for copy and i18n |
| 2 | Hybrid Media Pipeline | Produce 60–90s technique-first clips in real kitchens with captions; pair each clip to a concise printable recipe. Establish creator guidelines (authentic visuals, failure modes, sponsorship transparency). | Video + Content | 6–8 weeks | Creator contracts, Captioning workflow, CDN/asset pipeline |
| 3 | Localization & Accessibility | Bilingual UX (ES/EN) for key surfaces: Jump-to-Recipe, Cook Mode, ingredients/steps; accessible Cook Mode with larger type, TTS/audio step readout, and high-contrast themes. | Design + Eng + Content Ops | 6 weeks | i18n framework via Ditto, TTS/audio provider, Accessibility QA |
| 4 | Offline/PWA + Export | Installable PWA with offline-ready Cook Mode and one-click PDF; export shopping lists to SMS/plain text; add CSV/Notion export for power users. | Eng | 8–10 weeks | Service worker + manifest, Local storage strategy, Notion/Share integrations |
| 5 | Community Trust Layer | Moderation tools and UX to highlight cooked-it comments with photos, author replies with SLA, and visible changelogs/provenance. Filter notes by altitude/equipment. | Community + Content Ops + Eng | 6–8 weeks | Moderation tooling, Lightweight auth (optional), Media storage |
| 6 | Pricing Experiments (Ad-light Basics, Pro & Packs) | Keep basics free and ad-light. Test: (a) one-time printable packs (no login), (b) Pro bundle with macros, cost-per-serving with local presets, batch-scaling, CSV export. No gating of core recipe details. | Product + Growth + Finance | 4–6 weeks (post-core features) | Payments, Price data (Aldi/Walmart presets), Analytics + A/B infra, Legal/Tax |
KPIs to Track
| # | KPI | Definition | Target | Frequency |
|---|---|---|---|---|
| 1 | Recipe First Meaningful Render | Median time from page load to visible ingredients block (ms). | < 2000 ms (mobile) within 60 days | Weekly |
| 2 | Cook Mode Adoption | % of recipe sessions entering Cook Mode and median time in mode. | >= 25% adoption; >= 4 minutes median session | Weekly |
| 3 | Print/PDF Engagement | % of recipe sessions generating a print or PDF. | >= 15% of sessions | Weekly |
| 4 | Trust Coverage Index | % of live recipes with grams, pan size, internal temp, substitutions, storage/reheat, and version date populated. | >= 80% within 90 days | Biweekly |
| 5 | Comment Quality Ratio | Share of comments marked ‘cooked-it’ or with photos, and creator reply rate within SLA. | >= 30% quality comments; >= 80% replies < 48h | Weekly |
| 6 | Return Cook Rate (30d) | % of users who cook (print/Cook Mode) and return to cook again within 30 days. | >= 35% | Monthly |
Risks & Mitigations
| # | Risk | Mitigation | Owner |
|---|---|---|---|
| 1 | Feature creep dilutes speed and clarity, recreating ‘content farm’ bloat. | Enforce a Basics stay free and simple rule; design guardrails; ship small vertical slices. | Product |
| 2 | Video production cost and cadence may lag content needs. | Start with real-kitchen shorts; template shot list; pilot with 2–3 creators; reuse across recipes. | Video Lead |
| 3 | Revenue shortfall if ads are reduced before Pro/pack revenue ramps. | Stage ad reduction; run pricing experiments in limited geos; set floors for RPM; add one-time packs early. | Finance + Growth |
| 4 | Localization or cultural missteps erode trust. | Use native ES editors; add provenance/attribution fields; creator guidelines on naming and credit. | Content Ops |
| 5 | Offline/PWA introduces caching bugs or SEO regressions. | Staged rollout; service-worker versioning; SEO QA on canonical links; clear cache-busting. | Eng |
| 6 | Data and privacy limitations reduce marketing analytics. | Adopt privacy-first metrics (event-based, aggregated); prioritize task completion KPIs over user tracking. | Analytics |
Timeline
0–30 days: Quick wins (Jump-to-Recipe, Print/PDF, page-speed fixes, grams toggle, Spanish labels), Cook Mode v0, comment pinning.
31–60 days: Ship Structured Recipe System v1 (subs, storage/reheat, version history), Hybrid Media pilot (10–15 clips), accessibility upgrades.
61–90 days: Community Trust Layer (moderation, cooked-it photos, changelogs), PWA/offline alpha + exports, pricing experiments (printable packs + Pro beta).
31–60 days: Ship Structured Recipe System v1 (subs, storage/reheat, version history), Hybrid Media pilot (10–15 clips), accessibility upgrades.
61–90 days: Community Trust Layer (moderation, cooked-it photos, changelogs), PWA/offline alpha + exports, pricing experiments (printable packs + Pro beta).
Research Study Narrative
The Kitchn Home Cook Study: Objective & Context
Objective: Understand how home cooks engage with food media and recipe websites to inform product, content, and monetization decisions. Across six participants, patterns converged on a single mandate: deliver a low-friction, video-first + printable experience that is precise, authentic, and community-validated. Respondents spanned Spanish-speaking community cooks, culturally-attuned heritage cooks, price-sensitive and rural users, and highly technical, data-driven cooks.
What We Learned (Grounded in Cross-Question Evidence)
- Hybrid usage wins: Short, technique-first video for discovery + concise written card for execution. Jean Mitchell: “Both together is ideal - watch once, then cook off a quiet page that doesn’t jitter with ads.” Shontae Villalvazo goes “primero a YouTube” for step-by-step in Spanish, then seeks longer video and a clean page to cook from.
- Precision builds trust: Grams-first, pan sizes, internal temps, yields, ranges, and failure modes. Cory Andres: “Weights in grams… salt in grams per pound, doneness temps, pan size.” Vague cues like “medium heat” or cups-only undermine credibility.
- Low friction is non-negotiable: Intrusive ads, autoplay, pop-ups, login walls, and long SEO headnotes are dealbreakers. Cory: “If a recipe page burns more than 15 seconds with pop-ups and autoplay, I’m gone.” Ryan Tagle wants a “one clean page… Downloadable PDF. Big font. No login.”
- Authenticity matters: Real-kitchen visuals and cultural respect signal competence. Jean: “Real kitchens - not glossy studio islands.” Chancelor Mullen flags duplicated/AI-slurried content as a trust red flag.
- Community validation reduces risk: Useful comments, photos, and creator replies. Crystal Montana: “Receipts in the comments… author replies and fixes errors fast.”
- Localization elevates usability: Simple substitutions that map to local stores and bilingual clarity. Shontae: “Sustituciones simples… Northgate o El Super.”
- Utility beyond the cook: Storage/reheat guidance and export/offline support are repeatedly requested (air fryer/microwave paths; one-click PDF; PWA/offline).
Persona Correlations & Demographic Nuance
- Spanish-speaking caregivers (Shontae): Bilingual, video-first discovery via community channels; store-aware swaps; creator replies in Spanish increase adoption.
- Culturally-attentive heritage cooks (Jean): Provenance, respectful naming, and real-kitchen visuals; heavy UX friction triggers abandonment.
- Price-sensitive, community-discovery cooks (Ryan): One-page printables, explicit cheap swaps, leftover/reheat guidance; prefers one-time purchases over subscriptions.
- Technical/data-oriented cooks (Cory): Treat recipes as systems; wants grams, macros, cost-per-serving, scaling, and CSV/Notion export; will pay modestly if workflows consolidate.
- Rural, connectivity-constrained (Chancelor): Prioritizes fast pages, offline/PWA, and rigorous testing notes; rejects autoplay/trackers.
- Budget/pantry-focused mid-career (Crystal): Aisle-grouped lists, equipment toggles (air fryer/slow cooker), and short captioned clips.
Recommendations
- Ship friction-killers now: Jump-to-Recipe, clean one-page Print/PDF, and Cook Mode v0 (stay-awake, large next/prev, step timers, optional audio). Directly addresses top pain points while supporting kitchen use.
- Codify precision: Grams toggle, pan sizes, internal temps, realistic time ranges; add substitutions and storage/reheat fields per recipe.
- Hybrid media pipeline: 60–90s technique-first clips in real kitchens, captioned; pair each with a concise printable card; require provenance and sponsorship transparency.
- Localization & trust: Spanish labels/buttons and creator reply SLAs; triage and pin “cooked-it” comments with photos; visible version history/changelogs.
- Monetization fit: Keep basics free; offer one-time printable packs for price-sensitive users and a Pro tier for macros/cost/CSV/Notion export.
- Enablement: Externalize copy/i18n via Ditto; implement a structured recipe schema (weights, temps, subs, storage, versioning) for scale.
Risks & Guardrails
- Feature creep → content-farm bloat: Enforce “basics stay free and simple”; ship small vertical slices.
- Video cost/cadence: Start with real-kitchen shorts; template shot lists; pilot with 2–3 creators.
- Ad revenue dip during transition: Stage ad reduction; test pricing in limited geos; add printable packs early.
- Localization missteps: Use native ES editors; add provenance/attribution fields; creator guidelines on naming.
- Offline/PWA regressions: Staged rollout; service-worker versioning; SEO QA on canonicals.
Next Steps & Measurement
- 0–30 days: Launch Jump-to-Recipe, Print/PDF, page-speed fixes, grams toggle, Spanish labels, Cook Mode v0, and comment pinning.
- 31–60 days: Ship Structured Recipe System v1 (subs, storage/reheat, version history), Hybrid Media pilot (10–15 clips), accessibility upgrades (large type, TTS).
- 61–90 days: Community Trust Layer (moderation, cooked-it photos, changelogs), PWA/offline alpha + exports (SMS/CSV/Notion), pricing experiments (packs + Pro beta).
- KPIs: First Meaningful Render to ingredients < 2000 ms (mobile, 60 days); Cook Mode adoption ≥ 25%, median time ≥ 4 min; Print/PDF in ≥ 15% sessions; Trust Coverage Index ≥ 80% of recipes with grams/pan/temps/subs/storage/version (90 days); Comment Quality Ratio ≥ 30% cooked-it or photos and ≥ 80% creator replies in 48h.
Recommended Follow-up Questions
Updated Jan 21, 2026
-
If a recipe website offered additional features beyond the free experience, which pricing model would you prefer?single select Guides packaging and monetization strategy (freemium vs subscription vs one-time), informing paywall design and revenue mix.
-
Which devices do you typically use during each stage: discovering recipes, meal planning, grocery shopping, and cooking?matrix Prioritizes responsive design, cook mode, print/PDF, and offline support by context and stage.
-
Which integrations with other tools or services would be most valuable to you on a recipe website?maxdiff Informs partnership and roadmap focus (grocery delivery, shopping lists, calendars, nutrition trackers, notes apps).
-
How do you currently save and organize online recipes you want to cook later?multi select Shapes library, collections, tags, and export features to match real organization behaviors.
-
How acceptable are the following ad formats on a free recipe website?matrix Sets guardrails for ad types and density to balance revenue with user experience and retention.
-
When narrowing down recipe results, which filters are most important to you?rank Directs search and metadata investments toward the highest-impact filters for faster discovery.
For matrix/maxdiff items, randomize lists. Example items: ad formats (static banner, inline sponsor label, pre-roll video, sticky footer, interstitial), integrations (Instacart, Apple/Google Reminders, Notion, MyFitnessPal, Calendar), filters (time, ingredients on hand, cuisine, diet, skill, appliance).
Study Overview
Updated Jan 21, 2026
Research question: We studied how home cooks engage with food media and recipe websites to learn where they go, what builds trust, what frustrates them, and what would drive repeat use or payment.
Research group: Six US home cooks (ages 25–54) across CA/MO/AR, including a Spanish‑speaking caregiver, a culturally attuned diaspora cook, a price‑sensitive budget cook, a rural connectivity‑constrained engineer, and a data‑driven optimizer. What they said: Participants prefer video‑first, practical content for discovery paired with a concise, printable written recipe for execution; trust hinges on precise, testable details (grams, temps, pan sizes, realistic time ranges), clean cook‑friendly UX (jump‑to‑recipe, print/cook‑mode, minimal ads), community validation (real “cooked‑it” comments and creator replies), and localized substitutions.
Main insights and divergences: They reject content‑farm signals (autoplay, long SEO memoirs, stock imagery, vague “medium heat,” implausible timelines, duplicated/AI‑slurried recipes); segments vary in needs-some want macros, cost‑per‑serving and CSV/Notion export, others require Spanish‑language/community distribution, cultural provenance, and fast offline access. Takeaways: Ship a fast, ad‑light core: Jump‑to‑Recipe and one‑page Print/PDF; Cook Mode (stay‑awake, big next, optional audio); grams toggle with required fields (yields, pan sizes, internal temps); explicit substitutions plus storage/reheat; Spanish labels; comment triage with “cooked‑it” surfacing and visible version history; and PWA/offline readiness.
Monetization and guardrails: Keep basics ungated, test one‑time printable packs for price‑sensitive users, and offer an optional Pro tier for power users (macros, local cost presets, batch‑scaling, CSV/Notion export) while enforcing “real kitchen” video guidelines and transparent sponsorships to sustain trust.
Research group: Six US home cooks (ages 25–54) across CA/MO/AR, including a Spanish‑speaking caregiver, a culturally attuned diaspora cook, a price‑sensitive budget cook, a rural connectivity‑constrained engineer, and a data‑driven optimizer. What they said: Participants prefer video‑first, practical content for discovery paired with a concise, printable written recipe for execution; trust hinges on precise, testable details (grams, temps, pan sizes, realistic time ranges), clean cook‑friendly UX (jump‑to‑recipe, print/cook‑mode, minimal ads), community validation (real “cooked‑it” comments and creator replies), and localized substitutions.
Main insights and divergences: They reject content‑farm signals (autoplay, long SEO memoirs, stock imagery, vague “medium heat,” implausible timelines, duplicated/AI‑slurried recipes); segments vary in needs-some want macros, cost‑per‑serving and CSV/Notion export, others require Spanish‑language/community distribution, cultural provenance, and fast offline access. Takeaways: Ship a fast, ad‑light core: Jump‑to‑Recipe and one‑page Print/PDF; Cook Mode (stay‑awake, big next, optional audio); grams toggle with required fields (yields, pan sizes, internal temps); explicit substitutions plus storage/reheat; Spanish labels; comment triage with “cooked‑it” surfacing and visible version history; and PWA/offline readiness.
Monetization and guardrails: Keep basics ungated, test one‑time printable packs for price‑sensitive users, and offer an optional Pro tier for power users (macros, local cost presets, batch‑scaling, CSV/Notion export) while enforcing “real kitchen” video guidelines and transparent sponsorships to sustain trust.
Awaiting responses…
Usually takes — seconds
Taking longer than usual
Question
0 responses
Waiting…
| Participant | Response | Actions |
|---|