Tag

Empirical Analysis

Entries tagged Empirical Analysis across the library, including matching entries from the original collection.

Explore entries

Develop a Framework for Prototype Testing and Insight Generation

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

This prompt is designed to assist product development teams in creating a comprehensive framework for testing prototypes. The focus is on gathering actionable insights through objective and empirical analysis, which will inform subsequent product development stages. By defining clear objectives and metrics, selecting appropriate testing methods, and analyzing results, teams can refine their concepts based on data rather than assumptions. This approach ensures that the product is developed with a strong foundation of evidence, leading to more successful outcomes.

{
  "role": "You are a product development expert specializing in prototype testing and insight generation.",
  "goal": "Create a framework for testing [product prototype] to gather insights that will guide the development of [product version].",
  "context": [
    "Identify the key objectives and metrics for prototype testing.",
    "Choose testing methods that align with the product's goals and constraints.",
    "Analyze test results to extract actionable insights.",
    "Consider the target audience's needs and preferences during the analysis."
  ],
  "output": [
    "A list of defined objectives and metrics for the testing phase.",
    "A selection of testing methods appropriate for the prototype and goals.",
    "A detailed analysis of test results with insights and recommendations.",
    "A plan for iterating on the prototype based on gathered data."
  ],
  "toneStyle": "Analytical, strategic, and data-driven.",
  "constraints": [
    "Ensure the framework allows for flexibility in testing methods.",
    "Avoid subjective interpretations; focus on data-driven insights."
  ],
  "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, ask up to [3] concise follow-up questions only if the answers would help clarify a testing objective, obtain missing results, or choose the next evidence-supported iteration. Use them to address unmet success criteria or meaningful uncertainties. Do not repeat questions already answered or defer essential starting questions until this stage. If no useful follow-up is needed, omit the questions.",
  "successCriteria": [
    "Testing objectives and metrics relate to the prototype's intended users and the decisions needed for the next product version.",
    "Chosen methods explain their suitability, necessary participants or evidence, and relevant prototype constraints.",
    "Any results analysis is grounded in supplied test data; when data is absent, the response provides an analysis approach without fabricating findings.",
    "Iteration recommendations follow the evidence or are labeled as conditional, with uncertainty and further validation needs identified.",
    "Check the result against these criteria before presenting it. Briefly identify any unmet criteria or items requiring verification."
  ]
}

End of results.