Identity
“What plant is this?”
Identification uncertainty blocks care before it begins.
Bloom explores one focused promise: identify a plant, adapt generic guidance to the home, and create reminders the owner can change as life and conditions change.
Role
Research · Product design
Research
Survey n=10 · Interviews n=3
Core loop
Identify → plan → care
Validation
3 iterative feedback rounds
Personal concept. Research is directional and based on a small convenience sample.



01 · Research signal
A survey of ten classmates and three follow-up interviews suggested three recurring barriers. The sample is too small and narrow for market claims, but it was enough to frame a first prototype.
Identity
Identification uncertainty blocks care before it begins.
Context
Generic advice ignores light, travel, and routine.
Consistency
Care disappears when reminders cannot adapt.
02 · Product scope
Add a plant quickly and leave with a care plan that is understandable, editable, and easy to act on. Everything else is secondary until this loop demonstrates repeat use.
MVP loop
Identify
Confirm context
Edit plan
Act on reminder
Deferred
03 · Care-plan flow
The screens below are concept artifacts. The important story is the handoff of control at each step.

Signal
A single incorrect result asks the user to trust the model blindly.
Response
Show ranked matches, confidence, visual cues, and manual search fallback.
Value
The owner chooses what enters the collection.

Signal
Long setup forms create work before the app has delivered value.
Response
Pre-fill known plant needs, then ask about light, pot, and the owner's routine.
Value
Less setup with visible reasons for every question.

Signal
A fixed schedule ignores travel, weather, plant condition, and personal routine.
Response
Create an editable schedule with complete, snooze, skip, and reschedule actions.
Value
Guidance stays useful without becoming authority.
04 · Iteration
Three rounds cannot validate a broad product, but they can expose navigation, trust, and setup friction. I used each round to narrow the loop rather than keep adding features.
“I sometimes get lost.”
Simplified navigation and made the add-plant path explicit.
Findability
“The identified plant is wrong sometimes.”
Replaced one answer with ranked matches and manual fallback.
Calibrated trust
“Some details should be auto-filled.”
Pre-filled known care needs and made the rest optional or editable.
Progressive disclosure



05 · Flexible care states
Plant care is variable. The interaction model supports uncertainty and missed tasks without silently changing the plan or pretending to diagnose plant health.
06 · Reflection
Research generated many appealing ideas—community, milestones, recommendations, and photo timelines. Product judgement meant separating delight from the promise that needed proof first.
The scope narrowed from a broad lifestyle app to identification, editable care planning, and recurring action.
A three-person feedback loop cannot establish retention, horticultural accuracy, or recommendation quality.
Run a two-week diary study with new owners and measure setup completion, reminder action, overrides, and repeat care.
Explore the interaction model
Identification, setup, care actions, and deferred V3 explorations.