Technical PASS is not Product PASS
What a working document prototype did — and did not — prove about Exam Workbench, and why technical feasibility and product demand need separate gates.
Journal
We share product decisions, engineering lessons, launches, postmortems, and experiments drawn from work we have done ourselves, with enough first-hand context to be useful.
What a working document prototype did — and did not — prove about Exam Workbench, and why technical feasibility and product demand need separate gates.
Why we kept the useful parts of the old site's public footprint, dropped its SaaS runtime assumptions, and proved the replacement on isolated Cloudflare staging.
Editorial standard
Implementation details, screenshots, benchmarks, deployment facts, observations from use, or properly anonymized data.
Why a choice was made, what alternatives were considered, and what evidence changed the decision.
A method someone else can apply, along with the situations where it does not fit.