About the studio
Judgement before dashboards
Devqueuebase exists because Thai product teams were drowning in event volume and still could not agree whether a session had gone well. We teach the evaluation, not another tracking plan template.
Mission
We want analysts who can sit with a product manager, play thirty seconds of a recording, and say — without theatre — what the user accomplished, where the product failed them, and what evidence would change that call.
That skill does not come from a vendor certification. It comes from watching many ordinary sessions from apps people actually use in Thailand: bill pay, grocery, transit top-up, hospital booking.
Pedagogy
Classes are small. A typical Integrity Lab seats sixteen. Each week has a desk assignment: score ten sessions with a written limitation. In the room we argue about two of those scores until the disagreement is specific — “the KYC retry is recoverable” versus “the user already abandoned after the second OTP.”
We ban vanity language in write-ups. “Engaged,” “healthy,” and “drop-off” are not allowed unless they are defined against a job-to-be-done. Students learn to separate a completed job from a long dwell, and a rage tap from a curious double-tap on a map pin.
English is the working language because most analytics tools and event names arrive in English. Thai is welcome in discussion when a local UX pattern needs a local name — PromptPay confirmation sheets, 7-Eleven barcode hops, National ID OCR stalls.
Community
Alumni stay in a quiet circle. It is not a public Slack full of job ads. Once a quarter we host a replay night at the Sukhumvit studio: one anonymised session from a volunteer company, ninety minutes, no slides. People come from Chiang Mai and Hat Yai as much as from Sathorn.
We also publish the Journal so practitioners who will never take a seat can still steal a method. If an essay helps a two-person startup in Khon Kaen, that counts.
Student journey
Most students arrive after a painful quarterly review: conversion “looked fine” and support tickets said otherwise. They start on Desk Access or jump into the Lab if they already have replay tooling.
Week one is unglamorous. You reconstruct a single checkout path from events only, then watch the recording. The mismatch is usually embarrassing. Week four you write a quality charter for your own app. Week eleven you present a limitation-aware readout to a sceptical guest PM.
We do not promise a title change. We do expect you to leave able to defend a session score in a room that would rather look at a big number.