Case Study — Hero Component

Role

PM & AI Practitioner

Team

Solo · 6 participants

Duration

9 weeks

Status

Discovery complete · Evaluation complete

Sensory Sprout / AI meal planning system

A system for making dinner reliable for families with selective eaters.

A meal planning system designed around what actually gets eaten. Sensory Sprout models what each person can tolerate, then helps turn that understanding into a meal that can be prepared, adapted, and served.

Sensory Sprout preview

6

Parent interviews across autism, ARFID, and sensory differences

4

Adaptive conversation flows for different eater types

15 / 2 / 0

Pass / Partial / Fail on the strongest prompt config

Case Study — Content Component
Overview

A strong section headline that carries the point of view.

This is your main body content. Use this area for the section story: what the project was, what you learned, what mattered, or how the system worked.

A second paragraph can add nuance without making the layout feel too dense.

A subheading that groups related content within a section.

Use h3 when a section has distinct sub-topics that benefit from a clear header. It reads as a continuation of the section, not a new one.

Inline label

Use h4 as a tight label above a specific piece of content — a finding, a constraint, a named concept. It's quiet but anchoring.

Image / Graphic

Placeholder for screenshot, diagram, prototype, or system graphic

Optional caption. Use this to explain what the image shows and why it matters.

Problem

Section headline goes here.

Describe the problem, constraint, or opportunity that framed this work.

Reframe

Section headline goes here.

Explain how you reframed the problem or shifted the lens of the work.

Product

Section headline goes here.

Describe what you built — the core product or design artifact.

System Design

Section headline goes here.

Walk through the systems, structure, or architecture behind the design.

Key Design Decisions

Section headline goes here.

Highlight the pivotal choices that shaped the outcome and why you made them.

Evaluation

Section headline goes here.

How did you test, validate, or measure the work?

Reflection

Section headline goes here.

What would you do differently? What did this project teach you?

Outcomes

Section headline goes here.

Results, impact, and what happened after the work shipped or concluded.

Component Library
Component — Eyebrow
Section Label
Component — Quote

I have to make 3 different meals every night… and sometimes they won't eat more than two bites.

Anonymous · Local mom's Facebook group
Component — 2-col text
Insight one

Memory for recall, not reliving

People want to look back and remember important things, rather than re-experiencing them.

Insight two

Surface relevant suggestions

Users want personalized prompts, reminders, and tasks — both in the moment and as a recap at the end of the day.

Component — 3-col text
Productivity Tools

Targeting students

Massive AI adopters, with a familiar form factor.

Home Devices

Less competitive space

Fewer constraints on battery life and data plans.

Wearables

On-the-go form factors

Fit for mass adoption.

Component — 4-col text
Step 1

Discover

Map the problem space.

Step 2

Define

Frame the right question.

Step 3

Design

Explore solutions.

Step 4

Evaluate

Test and measure what works.

Component — 2-col image
Image

Caption describing what this image shows.

Image

Caption describing what this image shows.

Component — 3-col image
Image

Caption one.

Image

Caption two.

Image

Caption three.

Component — 4-col image
Image
Image
Image
Image
Component — 2-col bordered card
Profile

Turn inputs into a decision model

Constraints, patterns, and execution rules are structured for decision-making — not storage.

The system can treat hard rules differently from softer tendencies.

Ranking

Choose meals that can work

Meals are ranked by viability, not appeal: structure, branchability, adaptability, and familiarity matter more than ingredient match alone.

Component — 3-col bordered card
Profile

Turn inputs into a decision model

Constraints, patterns, and execution rules are structured for decision-making — not storage.

Ranking

Choose meals that can work

Meals are ranked by viability, not appeal: structure, branchability, and familiarity matter most.

Confidence

Rank with confidence, not certainty

Strong signals can guide decisions without overcommitting to weak or early inferences.

Component — 2-col stat card

6

Parent interviews conducted

4

Adaptive flows for different eater types

Component — 3-col stat card

6

Parent interviews conducted

4

Adaptive conversation flows designed

15/2/0

Pass / Partial / Fail on strongest config

Component — Full-width image
Image / Graphic

Optional caption. Use this to explain what the image shows and why it matters to the narrative.