👤 Persona #1: Urgent Preserver Sarah

Background: Sarah is a busy mother of two teenagers. Her mother was recently diagnosed with early-onset dementia. Sarah realizes that her mother’s famous lasagna recipe—served at every family holiday for 30 years—exists only on a stained, index card in her mother’s kitchen. Sarah feels a ticking clock to capture not just the ingredients, but the stories her mother tells while cooking.

Pain Points:

• Fear of losing the recipe when her mother passes or can no longer cook.
• Vague measurements ("a handful of cheese") that she can't replicate.
• Recipes currently scattered across emails, texts, and physical cards.

Buying Behavior: Triggered by her mother's diagnosis. She values ease of use (speed) and security (privacy) over cost. Willing to pay for "peace of mind."

👤 Persona #2: Genealogy George

Background: George has spent the last decade building a massive family tree on Ancestry.com. He has names, dates, and death certificates, but he feels the "soul" of the family is missing. He wants to digitize the 100+ recipe cards inherited from his grandmother to create a "Culinary Family Tree" for his grandchildren.

Pain Points:

• Physical cards are crumbling and fading (archive anxiety).
• Current genealogy platforms don't support media-rich recipe stories.
• Difficulty organizing recipes by family branch or origin.

Buying Behavior: Researches extensively. Looks for integration with Ancestry. Price sensitive but willing to pay for "archival quality" storage and printing features.

👤 Persona #3: New Chef Noah

Background: Noah recently moved away from home for the first time. He wants to learn to cook the meals he grew up with to feel connected to his family. However, his father cooks by feel and refuses to write recipes down. Noah is frustrated by failed attempts to recreate these dishes over FaceTime.

Pain Points:

• "Cook until it looks right" is impossible for a beginner.
• Generic cooking apps don't have his specific cultural dishes.
• Wants to record his dad cooking but lacks a tool to organize the video clips with the recipe.

Buying Behavior: Mobile-first user. Expects a seamless, app-like experience. Triggered by moving out or hosting first dinner party. High adoption of "freemium" models.

Context: Christmas Eve, 4:00 PM. Sarah is hosting the family dinner for the first time. Her mother is present but confused and unable to help cook.

Experience: Sarah frantically searches the kitchen drawer for the lasagna recipe. She finds the card, but a grease stain has obscured the amount of salt for the tomato sauce. She tries to call her aunt, who doesn't answer. She Googles "Grandma's lasagna," but the results are generic and don't taste right.

Panicked, she tries to ask her mother, who gets agitated because she can't remember the specifics. Sarah ends up guessing. The dinner is edible, but the flavor is "off." The family politely eats, but Sarah feels a profound sense of failure and loss—feeling she has failed to preserve the family legacy. She spends the evening texting cousins, begging them to check their own recipe boxes, resulting in a fragmented, confusing group chat.

Context: A rainy Saturday afternoon. George is organizing his study.

Experience: George pulls out the tin box containing his grandmother's recipe collection. He notices that the ink on the 1940s-era cards is fading significantly. He worries that if he doesn't do something soon, they will be unreadable.

He tries to take photos with his iPhone, but the glare from the plastic sleeves makes them hard to read. He creates a folder in Google Drive, but it quickly becomes a disorganized mess of filenames like "IMG_4922.jpg" and "Scan001.pdf." He realizes that just digitizing the image isn't enough—he needs the text to be searchable. He spends 4 hours typing out three recipes, his hands cramping, before giving up. The box goes back on the shelf, still vulnerable to time and decay. He feels guilty for not protecting his heritage better.

Job #1: Rescue Fading Heritage

"When I notice an old recipe card is degrading, I want to permanently digitize it, so that I never lose that part of my family history."

• Functional: High-quality scan, OCR, cloud backup.
• Emotional: Relief, security, peace of mind.
• Social: Seen as the responsible family steward.

Job #2: Decode Vague Instructions

"When I try to cook a generational recipe, I want to translate 'a pinch' into specific measurements, so that I can successfully recreate the taste."

• Functional: AI conversion, scaling tools, video guidance.
• Emotional: Competence, connection to the past.
• Social: Ability to host authentic family meals.

Job #3: Bridge the Generational Gap

"When my kids ask about family history, I want to show them our food stories, so that they understand where they come from."

• Functional: Easy sharing, mobile view, story playback.
• Emotional: Pride, belonging, nostalgia.
• Social: Passing the torch to the next generation.

Before/After Comparison

Before/After Comparison