← Field record
Fig. 05 — Point of use
Fig. 05a — The deliverable
Fig. 05b — The fix
The $38k wrong question.
One week of research. The real need was print-at-point-of-use — not another report builder.
A report builder was months into build. Scientists still printed batch results and taped them to the bench. One week of user research reframed the ask before more code shipped — the real need was print-at-point-of-use.
Discuss a similar problem- Services
- Industries
- Challenge
- Stop an expensive build from answering the wrong question. Scientists needed results at the bench, not another report builder.
- What we did
-
- 01Ran one week of user research before any further engineering spend.
- 02Found the real workflow: print batch results, tape them next to the physical sample.
- 03Reframed the ask from “better report UX” to print-at-point-of-use.
- 04Replaced months of wrong-direction work with a fix that matched how the lab operates.
- Outcome
- The wrong question cost $38,000. The right one was a print button.