The discovery sprint: cheap certainty before expensive tooling.

Hardware punishes optimism. Software teams can ship a wrong guess and patch it Thursday; a wrong guess in hardware is cut into tool steel, ordered in volume and shipped in cartons. Yet most programs still start the expensive part — CAD, prototypes, tooling conversations — on the strength of a pitch deck and collective enthusiasm.

The expensive default

The default failure mode isn't building the product badly. It's building the wrong product well. Teams fall into execution because execution feels like progress: geometry grows, suppliers respond, the burn chart moves. Nobody is assigned to the questions that actually decide the outcome — who exactly buys this, what it must do that incumbents don't, what it can be built for, and which physics problem will dominate the program.

What a sprint answers

A discovery sprint takes those questions and runs them hard for two to four weeks: a structured pass over the market and the technology, conversations with real operators in their real environment, and a feasibility read that puts honest ranges on cost and risk. Not a workshop. Not a vision document. A short program of work that ends in artifacts — a framed opportunity, explicit success criteria, an architecture recommendation and a risk register ranked by consequence.

The kill-list is the product

The most valuable page in a sprint readout is usually the list of directions we recommend not funding, with reasons. Every killed direction is tooling not cut, months not spent, capital not converted into inventory nobody wants. A good sprint should feel slightly disappointing — it trades imagined possibilities for a smaller set of real ones. That trade is the point.

When not to sprint

If the decision is already made and no evidence would change it, don't pay for theatre — and be honest that you're not doing discovery, you're doing execution. If credible research already exists, a sprint should audit and extend it, not repeat it for the invoice. We've told teams on the first call that they don't need one. That's part of the service too.

Discovery sprints are the front door of our strategy & research practice — fixed fee, fixed length, real artifacts — and the first loop of the evidence-loop process every larger program runs on.