Catalog feedback is arriving faster than its evidence can be compared.
PMs need recurring shopper problems to be visible without turning unreviewed clusters into roadmap decisions.
Who you’d be doing this for
“I spent ten minutes opening item cards and still had to guess what would work for dinner.”
Dulce Hernandez · Household grocery shopper
Uses item cards and filters to choose groceries for a household with dietary and budget constraints.
What is at stake
PMs cannot yet distinguish a recurring catalog attribute problem from a loud set of isolated reports. You have to weigh faster evidence synthesis against keeping every product decision reviewable.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- faster feedback synthesis vs. PM judgment
- theme recurrence vs. source-level evidence
- operational throughput vs. review depth
- cluster coverage vs. precision
Why Instacart
Product attributes shape the filters, item card badges, dietary safety signals, and health personalization used across the grocery shopping app.
Written with these in mind
Not your kind of problem? 41 more at Instacart, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.