Flagship course
Instrumented Session Quality
Six weeks to design capture you can audit, a score you can defend, and a readout that does not collapse reliability, completion, and respect into one ring chart.
Learning outcomes
By the end of the cohort you will be able to:
- Write an event contract that engineering and research can both sign.
- Separate reliability, completion, and respect in Session Quality Analytics.
- Publish a versioned score charter with an expiry date.
- Present limitations without undermining the entire programme.
- Choose when replay is evidence and when it is illustration.
Who it is for
Product operations, analytics, research, and platform engineers who already have some telemetry or a replay vendor, and who must explain quality to leadership. You do not need to write production code, but you must be willing to read event schemas.
If your only access is a marketing dashboard, start with Observer Desk recordings or wait until someone can share a warehouse extract.
Modules
-
Session as a unit of meaning
Where a session starts and ends in mobile, web, and hybrid wallets. Ghost sessions, background tabs, and why “user” is the wrong grain for most quality work.
-
Instrumentation that does not lie
Event contracts, clock skew, duplicate fires, and PII that should never enter replay. You will mark up a real schema from the studio archive.
-
Quality scores without vanity
Charter first, formula second. Composite indices only if each component can stand alone. Versioning and retirement rules.
-
Replay sampling ethics
Consent, redaction, and the difference between a stratified sample and a highlight reel. Light touch; Cohort Replay Analysis goes deeper.
-
Bangkok field traces
Production-like datasets from Thai-language checkout and bill-pay flows (anonymised). Payment-switch timeouts, font fallback jank, and month-end load.
-
Communicating quality to product leadership
A twenty-minute readout, a one-page caveat, and a Q&A with a visiting reviewer. Graded on specificity, not confidence.
Instructor
Arunwadee “Wadee” Srisuk
Wadee led observational research at a Bangkok payments network before joining Cloudpacketbase as principal faculty. She still sits on two partner squads each year so the flagship does not drift into theory. She teaches in English and takes questions in Thai.
Guest reviewers rotate from platform and CX teams; they are named on the cohort welcome note.
Fee (informational)
A Cohort Seat is THB 18,800 per person. Observer Desk access to recordings of this course is THB 4,900. Studio Partnerships that include this material are billed quarterly at THB 62,000. There is no checkout on this website. See Fees and Refunds.
Reviews of this course
Wadee would not let us keep the health ring. Annoying in week two. Correct by week five.
I wanted more SQL. The charter writing was slower than I expected and I almost dropped. I am glad I stayed; our internal wiki now has a score that expires.
FAQ
Do I need production access?
No. The studio provides anonymised datasets. They are cleaner than most production messes. If you can bring a redacted extract under NDA, the work gets sharper, but it is optional.
Will this teach me to build a session-replay product?
No. That is a real limitation. We use existing capture tools and warehouse extracts. You will not leave with a recorder SDK, a storage pipeline, or a vendor-replacement architecture. If that is your goal, this is the wrong programme.
How much time per week?
One live evening (two hours, ICT) plus roughly four hours of artefact work. Week three is heavier. Several alumni have said it collided with release freezes; wait for a quieter quarter if you can.
Is the fee refundable?
See the refund policy. Live seats cancelled more than fourteen days before the first session are treated differently from seats cancelled after week two.