spike

A throwaway spike is a short, focused experiment used to validate the feasibility of a new software idea. It decomposes concepts into disposable tests to surface unknowns and gather actionable insights before committing to a real build.

To validate a new software idea, you can run a feasibility spike to test its core assumptions. This structured workflow yields a documented hypothesis set, identified risks, and a final verdict to guide your development plan.

A feasibility spike handles risk assessment by breaking down new ideas into 2-5 independent feasibility questions. It uses short experiments to surface unknowns, producing structured artifacts like documented risks and a final verdict.

You should use a spike during early-stage concept validation before committing to an MVP build. It answers specific feasibility questions through disposable experiments, whereas an MVP is a production-bound product requiring real development resources.

Yes, you can use a spike for early-stage MVP planning. By running focused experiments to validate feasibility and surface risks, the spike provides a documented verdict that directly informs and de-risks your MVP development plan.

Throwaway experiments are limited to early-stage concept validation and feasibility assessment, yielding documented hypotheses and risks rather than production code. They should not be used when a real build or production-ready MVP is immediately required.