RecipeRoots - Family Recipe Preservation

👤 Persona #1: Memory Keeper Mary

Age Range: 45-55 | Location: Suburban | Occupation: Stay-at-home mom | Income Level: $60K-$80K | Tech Savviness: Medium | Decision-Making Authority: Individual

Background Story: Mary has spent the last 30 years raising her children and preserving her family’s traditions. She often reminisces about her mother’s cooking, especially during family gatherings. As her parents age, she worries about losing their recipes and the stories behind them. Mary dreams of creating a family cookbook that can be passed down to her children, ensuring their culinary heritage is preserved for future generations.

Current Pain Points:

1. Fading Recipes: Her mom's handwritten recipes are fading and hard to read, leading to frustration while cooking.
2. Lost Stories: Family stories tied to recipes are forgotten as her parents age, making the meals feel less connected.
3. Fragmented Tools: She uses different apps and paper to manage recipes, making it hard to find what she needs.
4. Time-consuming Process: Organizing recipes takes hours, leaving her feeling overwhelmed.
5. Difficulty in Sharing: She struggles to share recipes with family members, leading to missed opportunities for connection.

Goals & Desired Outcomes:

• Primary Goal: To preserve and share family recipes in a meaningful way.
• Secondary Goals: Create a legacy for her children, strengthen family bonds through cooking.
• Emotional Outcome: Feel proud and connected to her heritage.
• Success Metrics: Number of recipes stored, family members using the app.

Current Solutions & Alternatives:

Mary currently uses a mix of handwritten notes, a basic recipe app, and a physical binder. These methods are inadequate, as the app lacks personalization, and the binder is difficult to organize. She spends about $20 monthly on ingredients and tools to recreate meals she can’t remember clearly.

Buying Behavior:

• Trigger: A family gathering or the passing of a loved one.
• Research Process: She reads reviews online and consults with friends before making a decision.
• Decision Criteria: Ease of use, storytelling features, price.
• Budget: Up to $10/month for a solution.
• Adoption Barriers: Concerns about the app's complexity and data security.

👤 Persona #2: Culinary Historian Henry

Age Range: 50-65 | Location: Urban | Occupation: Genealogy researcher | Income Level: $80K-$100K | Tech Savviness: High | Decision-Making Authority: Individual

Background Story: Henry has dedicated his life to uncovering his family's history and heritage. He enjoys cooking traditional family meals but finds it challenging to gather and document recipes from relatives. Henry is passionate about preserving culinary histories and often shares his discoveries in community classes.

Current Pain Points:

1. Scattered Information: Family recipes are scattered across various platforms, making it difficult to compile them.
2. Lack of Context: Many recipes lack the history and significance behind them, which diminishes their value.
3. Time Constraints: Researching and documenting recipes takes time away from his other projects.
4. Difficulty in Collaboration: He finds it hard to collaborate with family members on documenting recipes.
5. Insufficient Tools: Current genealogy tools do not incorporate culinary elements.

Goals & Desired Outcomes:

• Primary Goal: To create an organized digital archive of family recipes and their histories.
• Secondary Goals: Share culinary traditions with his community, teach others about food heritage.
• Emotional Outcome: Fulfilled by preserving family history and sharing it with others.
• Success Metrics: Number of recipes documented, community engagement levels.

Current Solutions & Alternatives:

Henry uses a genealogy website and a simple document editor to store recipes, but he finds these tools lacking in storytelling features. He spends several hours a week managing this documentation, and often loses track of recipes he wishes to include.

Buying Behavior:

• Trigger: Attending genealogy events or family reunions.
• Research Process: Engages with online forums and peers for recommendations.
• Decision Criteria: Integration with genealogy tools, ease of sharing, storytelling capabilities.
• Budget: Willing to spend up to $15/month for a comprehensive solution.
• Adoption Barriers: Reluctance to switch from existing tools due to time investment.

Scenario #1: "Sunday Dinner Prep" - Mary

Context: Mary is preparing for a family dinner on Sunday afternoon. She wants to cook her mother's famous lasagna but struggles to find the recipe.

Current Experience (Before Solution): Mary opens her kitchen drawer filled with old recipe cards and notes. She finds a crumpled card with her mother’s handwriting but can hardly read it. After spending 30 minutes flipping through the cards, she finally locates the lasagna recipe, but it’s missing key instructions. Frustrated, she calls her sister for clarification and spends another 20 minutes gathering the ingredients. The process takes over an hour, and she feels overwhelmed and anxious about getting everything right before guests arrive. The lasagna turns out well, but the ordeal leaves her exhausted.

Pain Points Highlighted: Time wasted searching for recipes, lack of clarity leads to anxiety, and emotional distress due to uncertainty.

Scenario #2: "Family Reunion Recipe Sharing" - Henry

Context: Henry is at a family reunion and wants to gather recipes from relatives to add to his genealogy project.

Current Experience (Before Solution): At the reunion, Henry approaches family members to ask about their favorite dishes. He jots down notes on paper, but some relatives provide only vague instructions. After the reunion, he spends hours trying to recall details and organizing the recipes. He feels frustrated by the lack of clarity and connection to the recipes' origins. The process feels incomplete, and he knows he missed key stories and insights that could enrich his project.

Pain Points Highlighted: Incomplete information gathered, time-consuming documentation, emotional connection lost due to vague memories.

Job #1: Preserve Family Recipes

When: I want to document recipes before family members pass away.

I want to: Use a simple tool to capture recipes and their stories.

So I can: Ensure our family culinary heritage is not lost.

Functional Aspects: Capturing, storing, and sharing recipes.

Emotional Aspects: Feeling secure about preserving family memories.

Social Aspects: Being seen as the family historian.

Current Alternatives: Handwritten notes, generic recipe apps.

Underserved Outcomes: Lack of storytelling and personal connection in existing solutions.

Job #2: Share Recipes with Family

When: I want to prepare meals for family gatherings.

I want to: Easily share recipes with my relatives.

So I can: Ensure everyone can recreate the family favorites.

Functional Aspects: Sharing, collaboration, and feedback on recipes.

Emotional Aspects: Feeling connected and collaborative with family.

Social Aspects: Being recognized as a central part of family traditions.

Current Alternatives: Emailing documents or sharing on social media.

Underserved Outcomes: Difficulty in having a private space for sharing family recipes.

Job #3: Learn Cooking Techniques

When: I want to learn how to cook traditional family recipes.

I want to: Access video snippets or voice recordings from family members.

So I can: Master the techniques that make the dishes special.

Functional Aspects: Video tutorials and audio guidance.

Emotional Aspects: Feeling supported and connected to family while learning.

Social Aspects: Being part of a family tradition and legacy.

Current Alternatives: Cooking classes or YouTube tutorials.

Underserved Outcomes: Lack of personalized instruction from family members.

Job #4: Create a Family Cookbook

When: I want to compile family recipes into a single volume.

I want to: Easily format and publish a cookbook.

So I can: Share it with family members as a keepsake.

Functional Aspects: Formatting and publishing options.

Emotional Aspects: Feeling pride in creating a family legacy.

Social Aspects: Being known for contributing to family traditions.

Current Alternatives: Self-publishing services or traditional print options.

Underserved Outcomes: Difficulty in personalizing cookbooks with family stories.

Job #5: Backup Family Recipes

When: I worry about losing recipes due to disasters (fire, flood).

I want to: Ensure recipes are stored safely in multiple locations.

So I can: Feel secure that my family's recipes are safe.

Functional Aspects: Cloud storage and offline access.

Emotional Aspects: Feeling reassured and protected.

Social Aspects: Being the guardian of family heritage.

Current Alternatives: Physical copies or generic cloud storage.

Underserved Outcomes: Lack of easy access to recipes when needed.

Scenario #1: "Sunday Dinner Prep" - After Solution

With Solution Experience: Mary opens the RecipeRoots app and types “lasagna” into the search bar. Instantly, she finds her mother’s recipe, complete with a story about its origins. She taps on the voice note icon, listening to her mother’s instructions as she cooks. The app suggests ingredient substitutions for items she’s missing. In just 15 minutes, she’s ready to cook, feeling confident and connected to her family’s history. The dinner is a success, and she feels proud to share the story behind the dish with her family.

Before/After Comparison:

Scenario #2: "Family Reunion Recipe Sharing" - After Solution

With Solution Experience: At the reunion, Henry uses the RecipeRoots app to record family members as they share their favorite recipes. The app prompts them with questions to capture the stories behind each dish. After the reunion, he can easily compile all the recipes and their narratives into a beautifully formatted digital cookbook. Henry feels accomplished, knowing that he has preserved not just the recipes but also the memories tied to each dish.

Before/After Comparison: