Design a Gift Registry Experience for Engaged Couples and Their Guests

Design a wedding registry: the product a couple uses to list the gifts they would like, and that their guests use to buy them. ```hint Two customers, one gift A registry works only when the couple building it and the guests buying from it both succeed. Decide whose problem you solve first, and look at what goes wrong for them between the engagement and the thank-you notes. ``` ### Clarifying Questions - Should I design this as a product built on Amazon's existing catalog, checkout and delivery network, or rethink a registry from a blank page with no platform assumptions? - Is the main goal gift sales, winning newly formed households as long-term customers, or the couple's satisfaction with the experience? - Are cash funds, experiences and items from other retailers in scope, or only products sold on the platform? - Is the design for one market such as the US, or for wedding gifting traditions across many countries? ### What a Strong Answer Covers - A stated goal for the registry and how it ties to the business - A clear choice among couples, guests and the family members who help plan, with pain points specific to wedding gifting - A small set of prioritized solutions, with impact-versus-effort reasoning and an explicit first-release cut - Success metrics that capture both the couple's side and the guest's side, plus guardrails such as returns - Registry-specific risks, such as exposing the couple's address, fraud on cash gifts and gifts arriving late ### Follow-up Questions - How would you persuade couples who already started a registry elsewhere to move it to yours? - If cash funds take off but product purchases fall, is that a win or a problem, and how would you decide? - How would you adapt the design for cultures where cash is the customary wedding gift?