pol-probe-advisor

Choosing a product validation method requires evaluating your hypothesis type, risk focus, available resources, and timeline constraints to determine whether you need a low-cost or high-fidelity approach to elicit honest user insights.

Validating technical feasibility versus user adoption involves identifying your primary risk focus, which directs you toward either a feasibility spike to test build capability or a task test and narrative prototype to gauge real user interaction.

You should use low-fidelity prototyping, such as narrative prototypes or synthetic data simulations, when resources are constrained and timeline is short, reserving high-fidelity validation for scenarios requiring deeper user interaction.

Stakeholder buy-in is evaluated as a specific risk focus during validation selection, guiding you toward appropriate proof-of-life probes that align modeling and simulation efforts with stakeholder expectations and resource constraints.

Synthetic data simulations are recommended for product validation when your focus is modeling without risk, allowing you to test hypotheses and validate assumptions efficiently before engaging in real user contact.