What a run does
- The Explorer signs in with the test account you saved, or arrives as a stranger, and uses every screen and form on the way in. A control that did nothing when pressed and a form that errored when submitted are filed as defects with a repro.
- Each seat on the panel names the screen where it would stop and leave, judging from the map. The report and every department page show the quit strip: each screen in the order a visitor meets it, with the share who stop there.
- The Design brief lists the confusion in the panel’s words. The Engineering brief lists what is broken on the screens people quit at.
- The Lab takes where they stop as the sign-up stage and prices a fix per screen, as an upper bound: some who stop there would stop at the next screen.
On a live product
Without your say-so the Explorer submits nothing on a live product: forms are mapped, not submitted, and the run screen says so. Turn on writes in Settings for a staging copy, or save a test account and let it sign in, and the forms are submitted with obvious test data.
How to start
Point it at the front door. The map is free and takes minutes. The panel runs when a model key is held and shows its price first.