[TOC] ## Problem Validation | Question | DRI | Answer | | ------ | ------ | ------ | |What is the problem? |PM| Our purchase flows are US centric with value options like "State", for example. Ideally, we would use more inclusive language. Let's use this epic to cohesively evaluate where we have opportunities for improvement. | |Who does the problem impact? |PM| | |When does the problem occur? |PM| | |Why does the problem occur? |PM| | |What are the benefits to solving the problem? |PM| | ### Exit criteria from problem validation section - [ ] The team understands the problem, who it affects, when and why, and how solving the problem maps to business needs and product strategy. ## Design | Question | DRI | Answer | | ------ | ------ | ------ | |What are the potential solutions to this problem? |PM / ENG / UX| | |What purchasing/sign-up flows are impacted by this change? | UX | | |What is the anticipated customer experience? |PM / UX| | |Do any of our solutions require design work? |UX| | |Are our solutions technically feasible? |ENG| | ### Exit criteria from design section - [ ] The team has scoped potential solutions and have validated what design work would be needed and if potential solutions are technically feasible. ## Solution Validation | Question | DRI | Answer | | ------ | ------ | ------ | |What solution do we want to pursue? |PM / ENG / UX| | ### Exit criteria from solution validation section - [ ] The team has high confidence that the the problem statement can be fulfilled by the proposed solution ## Operations | Question | Answer | | ------ | ------ | | Do we have any timeline constraints to delivery this solution? | | ## Stakeholder Input ### Resources - https://gitlab.slack.com/archives/C03UHGX4F1P/p1670807449324559 - https://gitlab.com/gitlab-org/gitlab/-/issues/385474#note_1206541937