Estimate a Research Spike
Estimate discovery work by defining the evidence output and bounding the timebox.
Estimate a pricing feasibility spike. The team needs enough evidence for a go/no-go decision, not a full pricing launch plan. Evidence output -> reference spikes -> scope boundary -> range -> stop condition The common shortcut is to say 'quick spike' and start researching. That hides the question being answered and lets the scope expand until someone runs out of patience. Define output Output: a one-page go/no-go memo listing billing constraints, customer willingness signal, and the next decision. Discovery estimates need a concrete evidence product. Otherwise the work has no natural finish line. Select reference class Prior feasibility spikes took…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in