spike

To validate an idea before building, you can decompose it into independent feasibility spikes. This structured approach uses throwaway experiments to surface risks and deliver a clear verdict to guide real-build decisions.

A feasibility spike is a throwaway experiment used to validate an idea or assess risk early. You should use spikes during early-stage product exploration or architecture scoping to check viability without committing to production work.

You can plan multiple spikes by decomposing your idea into two to five independent experiments. Aligning and planning these spikes before coding optimizes effort and reduces waste by documenting Given/When/Then verdicts for each approach.

Yes, throwaway prototypes are ideal for early-stage product exploration. They support a lightweight workflow with deterministic steps, allowing you to iterate with minimal runnable artifacts and conclude with a verdict to guide next steps.

The best way to structure a spike is to create a new directory with a descriptive name, include a README.md, and build a minimal runnable artifact. Run it to observe results and document the outcome using Given/When/Then framing.

You should not use throwaway experiments when you need production-ready code or permanent features. Spikes are designed for lightweight risk assessment and feasibility checks, delivering a verdict to guide real-build decisions rather than final implementations.