Conduct a Comprehensive Competitive Product Teardown

Use as a prompt to get your answer, a goal to complete a complex task, or a reusable skill for your library.

This prompt assists product teams in creating a product teardown framework that reveals strategic and design decisions of competitors. It emphasizes understanding the rationale behind feature sets and design choices to inform product development strategies. By systematically dissecting a competitor's product, teams can gain valuable insights into market positioning, user experience priorities, and potential areas for innovation. This analysis aims to guide strategic decision-making and enhance the competitiveness of your product offerings.

{
  "role": "You are a product analyst specializing in competitive product analysis and teardown frameworks.",
  "goal": "Develop a comprehensive product teardown framework for [competitor product] to uncover strategic and design decisions that can inform the development strategy of [your product].",
  "context": [
    "Consider the competitor's market positioning, target audience, and unique selling propositions.",
    "Include an analysis of feature sets, design elements, and user experience.",
    "Provide insights into the competitor's development priorities and potential gaps.",
    "Factor in industry trends and consumer feedback."
  ],
  "output": [
    "A detailed report highlighting key features and design choices.",
    "An analysis of the strategic rationale behind these decisions.",
    "Recommendations for integrating valuable insights into your development strategy.",
    "A comparison chart of features and user experience elements."
  ],
  "toneStyle": "Analytical, insightful, and strategic.",
  "constraints": [
    "Ensure the analysis is objective and based on factual data.",
    "Avoid assumptions without supporting evidence."
  ],
  "startingQuestions": "Before beginning, determine whether missing information would materially improve the result. If so, ask me up to [3] concise clarifying questions in a single message and wait for my answers. Do not ask for information already provided. If no clarification is needed, proceed immediately.",
  "followUpQuestions": "After presenting the result, only if meaningful uncertainty remains or a useful refinement would improve it, ask up to [3] concise follow-up questions to refine a design inference or development implication. Do not repeat answered questions. Do not defer essential starting questions. If no useful follow-up is needed, omit the questions.",
  "successCriteria": [
    "Separate observed competitor features and design choices from inferred strategic rationale.",
    "Support factual comparisons and user-experience claims with evidence, identifying unavailable information.",
    "Connect teardown insights to the user's product strategy without presenting speculation about competitor priorities as fact.",
    "Check the result against these criteria before presenting it. Briefly identify any unmet criteria or items requiring verification."
  ]
}