For Novel Products, Start With Vibes — Not Evals
Countering the popular 'get good at evals' advice, Howie says for a completely novel product experience you should start with vibes, not evals. Evals require you to define what 'good' looks like in advance, which constrains you before you've discovered the useful cluster of use cases. Only after you've converged on the form factor do evals become useful for programmatically iterating toward improvement.
- For a novel form factor, throw stuff at the wall ad hoc rather than defining evals up front
- Evals require pre-defining what 'good' looks like, which can constrain discovery too early
- First discover empirically which use cases the capability handles well
- Once the form factor has converged, evals become useful for measured, AB-tested iteration
“you should actually not start with Evals and you should start with Vibes, right?”
“EVLs can constrain you too early.”