How a review week actually runs
A release readiness review is a sequence of measurements, not a slide deck about “health.” Here is the order we keep so product and engineering argue about the same screen.
Monday freeze
Nothing is timed until the candidate build is named. If a new binary arrives on Wednesday, the clock restarts for that listing. We would rather lose two days than mix crash traces from two versions in one paragraph.
The bench
Phones sit on a wooden tray, not in a rack of glowing tiles. Mid-range Android sets sold in Mid Valley and one current iPhone cover most of the complaints we hear. We charge to 50 percent before a battery pass so the run resembles a late afternoon, not a fresh unboxing.
The commute pass
One of us rides a public route with a Celcom or Maxis SIM and the three journeys written on a card. Timings are spoken into a voice note, then typed. We do not film other passengers. GPS stays approximate and is deleted after the note is agreed.
The workshop
Findings are read aloud in screen order. Engineering may challenge a number; we replay the take if the file still exists. Product may challenge priority. We do not average those debates into a score. The PDF keeps the disagreement if it is still live at the end of ninety minutes.
Aftercare
Factual corrections are welcome for two days. New symptoms are a new booking. If you want us back for the next listing, say so on the intake form — we do not invent a subscription.