Search the whole librarySearch and tags
Advanced AI Library. Three Ways to Use It.
Plug it in as a prompt to get an answer. Set it as a goal to complete a complex task. Turn it into a reusable skill for your library.
Each resource is structured for all three.
Category counts cover all available entries.
Choosing a category or subcategory updates the results. Search and tag filters stay selected.
Validation Methods
Entries tagged Validation Methods across the library, including matching entries from the original collection.
Explore entries
Design an Experiment Framework for Validating Product Changes
Use as a prompt to get your answer, a goal to complete a complex task, or a reusable skill for your library.
This prompt aids product teams in establishing experiment design frameworks that validate causal relationships between product changes and outcomes. The aim is to support evidence-based product development through controlled experiments. The approach involves defining test variables, setting up control groups, and analyzing results to confirm causal links. By employing this method, product teams can make informed decisions based on reliable data, reducing uncertainty and enhancing product effectiveness.
{
"role": "You are a product analytics expert specializing in designing and conducting experiments to validate product hypotheses.",
"goal": "Create an experiment design framework for [product] that tests the impact of [specific changes] on [desired outcomes] using controlled testing methods.",
"context": [
"Identify the key variables and metrics that need to be measured.",
"Define control and experimental groups to ensure valid comparisons.",
"Include statistical methods for analyzing the data and determining significance.",
"Consider potential confounding factors and how to mitigate them."
],
"output": [
"A detailed experiment plan outlining variables, control groups, and testing procedures.",
"Methods for data collection, analysis, and interpretation.",
"Criteria for evaluating the success of the experiment.",
"Recommendations for iterative testing and validation."
],
"toneStyle": "Analytical, precise, and data-driven.",
"constraints": [
"Ensure the framework adheres to ethical guidelines and data privacy regulations.",
"Avoid overly complex statistical methods that may be difficult to interpret."
],
"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 an experimental comparison or success criterion. Do not repeat answered questions. Do not defer essential starting questions. If no useful follow-up is needed, omit the questions.",
"successCriteria": [
"Define variables, control and treatment groups, procedures, and outcome measures for the specified changes.",
"Explain confounder mitigation and appropriate analysis with clear success criteria and uncertainty.",
"Respect ethical and privacy requirements and distinguish planned testing from observed results.",
"Check the result against these criteria before presenting it. Briefly identify any unmet criteria or items requiring verification."
]
}Design a Proof-of-Concept Plan for Technical Feasibility
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 managers in designing a proof-of-concept plan to validate the technical viability of new products. It includes steps for identifying key technical questions, selecting appropriate validation methods, and planning resource allocation to demonstrate feasibility. The goal is to provide confidence in technical assumptions before scaling.
{
"role": "You are a product development consultant specializing in technical feasibility assessments.",
"goal": "Create a proof-of-concept plan for [product] to validate its technical viability by addressing [key technical questions] and utilizing [validation methods].",
"context": [
"Consider the product's core functionalities and technical challenges.",
"Include steps for identifying critical technical questions that need validation.",
"Outline validation methods such as prototyping, simulations, or experiments.",
"Plan resource allocation, including time, budget, and personnel requirements."
],
"output": [
"A list of key technical questions and assumptions to test.",
"Detailed description of selected validation methods and their rationale.",
"Resource plan outlining necessary budget, personnel, and timeline.",
"Criteria for success and metrics for evaluating proof-of-concept outcomes."
],
"toneStyle": "Analytical, strategic, and pragmatic.",
"constraints": [
"Ensure the plan is feasible within the existing resource constraints.",
"Avoid overly complex validation methods that may not be practical."
],
"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 technical test or success threshold. Do not repeat answered questions. Do not defer essential starting questions. If no useful follow-up is needed, omit the questions.",
"successCriteria": [
"Make key technical questions and assumptions testable through the supplied validation methods.",
"Explain each method's rationale and measurable proof-of-concept success criteria.",
"Keep the resource and timing plan feasible and separate planned validation from established viability.",
"Check the result against these criteria before presenting it. Briefly identify any unmet criteria or items requiring verification."
]
}End of results.
Load more