Agriculture Product Sense: Choosing a Farmer Segment, Core Pain Point and MVP

Design a product for farms and the people who run them. ```hint Narrow the farm "Farms" spans family plots and industrial agribusinesses in very different countries. Settle on one kind of farmer and one job they struggle with before you think about features. ``` ### Clarifying Questions - Should the product build on Meta's existing apps (WhatsApp, Facebook, Instagram, Marketplace), or is a standalone product equally open? - Which farms are in scope: smallholder family farms in emerging markets, or large commercial operations in places like the US and Europe? - Is the customer the farmer, the buyers of the harvest, or the businesses that sell to farms (seeds, equipment, credit)? - Is the goal social impact, revenue, or engagement on Meta's apps? ### What a Strong Answer Covers - A clear choice of farm segment and user, justified by the size of the need and the fit with the builder's strengths - The farmer's season mapped end to end, with the most painful moments identified (inputs, crop health, weather, selling, credit) - Solutions prioritized by impact and feasibility, with an MVP that works within the chosen users' constraints - Success metrics tied to farmer outcomes rather than usage alone, with guardrails - Risks such as harmful advice, misinformation, fraud and loss of trust ### Follow-up Questions - How would you know whether the product raised farmers' income or cut their crop losses, rather than only being used? - If your product gives farmers advice, and the advice turns out wrong in one region and harms a harvest, how do you respond and what safeguards would you build? - How would you make money from this without exploiting low-income users?