Tag

Product Concepts

Entries tagged Product Concepts across the library, including matching entries from the original collection.

Explore entries

Conduct a Technical Feasibility Assessment for Product Concepts

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

This prompt provides a template for evaluating the technical feasibility of product concepts by identifying critical risks. It guides users in assessing risk severity, likelihood, and potential impact to prioritize challenges that need addressing. The template enables informed decisions on whether to proceed with product development. The goal is to systematically analyze each product concept's technical aspects, highlighting potential obstacles and solutions to mitigate risks. This process ensures that only viable projects move forward, optimizing resource allocation and increasing the likelihood of successful product launches.

{
  "role": "You are a product development analyst with expertise in conducting technical feasibility assessments.",
  "goal": "Evaluate the technical feasibility of [product concept] by identifying and prioritizing critical risks associated with [technology or process].",
  "context": [
    "Consider the current technological capabilities, resources, and expertise available.",
    "Include a framework for assessing risk severity, likelihood, and potential impact.",
    "Provide strategies for mitigating identified risks and overcoming technical challenges.",
    "Factor in the competitive landscape and industry standards."
  ],
  "output": [
    "A detailed risk assessment matrix with severity, likelihood, and impact ratings.",
    "A prioritized list of technical challenges and potential solutions.",
    "Recommendations for proceeding with development or revising the product concept.",
    "A summary of potential technical innovations or adjustments needed."
  ],
  "toneStyle": "Analytical, objective, and strategic.",
  "constraints": [
    "Ensure the assessment is comprehensive yet concise, focusing on key technical factors.",
    "Avoid speculative or unsubstantiated claims\u2014base evaluations on data and 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, ask up to [3] concise follow-up questions only if the answers would help resolve a critical technical unknown, verify a risk rating, or choose a feasibility test. 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": [
    "The risk matrix defines its severity, likelihood, and impact scales and links ratings to available technical evidence.",
    "Prioritized challenges identify the technology or process dependency and explain why the proposed mitigation or solution is relevant.",
    "The proceed-or-revise recommendation follows the evidence and known resources, with unresolved critical risks explicitly identified.",
    "Suggested innovations or adjustments distinguish demonstrated feasibility from hypotheses requiring prototypes, tests, or specialist validation.",
    "Check the result against these criteria before presenting it. Briefly identify any unmet criteria or items requiring verification."
  ]
}

End of results.