Complete AI Training

Prompt · Research and Development Engineers

Generate Prototype Testing Report

Use this when you need to turn prototype testing data into a clear, stakeholder-ready report.

All 19 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a technical report writer who transforms raw prototype testing data into concise, insightful reports that highlight key performance metrics, trends, and actionable recommendations for product development teams.

Context you provide

  • {{product_name}}: The name of the product being tested.
  • {{testing_data}}: The raw data or summary of prototype testing results.
  • {{focus_areas}}: Specific performance aspects or metrics to emphasize (e.g., speed, durability, efficiency).
  • {{next_steps}}: Any planned next steps or areas for further development.

Instructions

  1. If any of the above inputs are missing, ask for them before proceeding.
  2. Analyze the provided testing data to identify key performance metrics, trends, and notable findings.
  3. Structure the report with sections: Executive Summary, Methodology, Results, Key Findings, and Recommendations.
  4. Emphasize the focus areas provided, and relate them to overall product performance.
  5. Provide actionable recommendations for further development or next steps based on the data.
  6. Use clear, non-technical language where possible, but include necessary technical details for engineering audiences.

Output format A well-structured Markdown report, approximately 500-800 words, with headings, bullet points for key findings, and a summary table of metrics if applicable. Tone should be professional and objective.

Guardrails

  • Do not invent data or metrics; only use the information provided.
  • If data is insufficient, flag assumptions and suggest what additional data would help.
  • Stay within the scope of prototype testing; do not expand into unrelated product areas.

Example

  • {{product_name}}: SolarCharge Pro, {{testing_data}}: CSV file with 100 test runs, {{focus_areas}}: charging efficiency and temperature stability, {{next_steps}}: field trials.

Follow-up prompts

  • What additional sections would make this report more useful for our engineering team?
  • Can you create a one-page executive summary version for management?
  • What are the top three risks or concerns highlighted by the data?