Product Sense: Design a Fintech Offering for Children, From Age Segment to MVP

Come up with a financial product whose users are children, and walk through how you would design it. ```hint Two customers, many ages A child uses the product, but an adult usually pays for it and controls the money, and a child's money life changes a lot with age. Map both before choosing whom to build for. ``` ### Clarifying Questions - What age range do we mean by "kids", or is that for me to define? - Should the product move real money, such as an account or a card, or is a learning product with no real money also in scope? - Which country do we launch in first, given that rules for minors' accounts and for children's data differ by market? - Are we a new company, or part of an existing business with assets we can build on? ### What a Strong Answer Covers - A chosen age band and the reasoning, given how much money children of different ages handle and control - The child as user and the parent as buyer and gatekeeper, with the needs of each - Prioritized pain points and solution options compared on impact and effort, leading to an MVP with explicit cuts - Success metrics that show whether children's money habits or understanding actually improve, plus guardrails - Risks particular to minors and money: safety, privacy, regulation and manipulative engagement design ### Follow-up Questions - How does the product keep a child who joins at 9 once they turn 14? - A parent wants to see every purchase, and the child wants some privacy. How do you design for both? - How would you make money from the product without advertising to children?