# Product Critique A product critique is a way to evaluate a product from different angles, like how easy it is to use, its design, functionality, accessibility, and profitability. It involves doing tests, analyzing feedback, and checking its quality and design. This evaluation can be done with customers or within a team. ### **Problem Statement** You are asked to conduct a product critique on your favorite product. The purpose of this critique is to evaluate the strengths and areas for improvement of the product. While solving the problem statement, try to address the following questions: 1. What user problems does the product solve, and how do users interact with it? 2. Which features are most popular among users, and what are the reasons behind their popularity? What are the strengths and weaknesses of the product? 3. How does your favorite product stand out among similar ones? 4. What changes can be made to improve usability? 5. Is there potential for new product offerings? 6. What strategies can you develop to optimize the product? Think about their reach and impact as well. 7. What are the risks and trade-offs involved in pivoting or simplifying the app? ### **Guidelines** * Limit your slides to a PPT of ≤10 slides with a clear focus on users, research insights, and structure. * Include wireframes/mockups wherever necessary to support your analysis. (HINT: identify user touch points. Use Balsamiq/Figma.) * Ensure to include prioritization of the solutions suggested. ### **Evaluation criteria** 1. Depth of the research 2. Structure of the solution 3. Impact of the solution proposed 4. Innovation 5. Presentation skills --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://iam.highonproduct.com/project-ideas/product-critique.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.