Waranya made us stop counting a lesson as done when the video ended. Our “completion” fell by almost a third. The tutors finally recognised the chart.
Siriwan Meesuk, head of product Secondary maths app
Flagship programme
Cohort Signal Lab
Eight weeks with one live learning product. You leave with a renamed event dictionary, cohort windows that match how the subject is taught, and a short brief a curriculum lead can mark up in red.
Who this desk is for
Product managers, analysts, and founding tutors who already have an event stream and a nagging feeling that “active users” is lying. You do not need a warehouse engineer on the call, but someone must be able to export a table.
Teams in Thailand often arrive between term breaks, when the charts look calm and the real questions are about next semester’s unit order. Remote seats are the default; two optional studio days run on Poochaosamingprai Rd.
What you will be able to do
- Write event names that distinguish video end, check submit, hint, skip, and revisit.
- Define a cohort by teaching week rather than install month.
- Show drop-off between lesson n and n+1 without blaming “motivation.”
- Separate instructor-facing telemetry from learner-facing telemetry.
- Present three findings a head of studies can veto in everyday English.
Modules
-
01
Event grammar for learning products
We inventory every event your app fires during a single lesson. Ambiguous names get retired. You leave week one with a one-page dictionary and a list of events you will stop trusting.
-
02
Windows that match pedagogy
Calendar months are a poor proxy for a unit. We align cohorts to teaching weeks, mock exams, and the quiet stretch after a certificate. Thai term dates are used as working examples, not decoration.
-
03
Drop-off between lesson n and n+1
The interesting loss is rarely install-to-day-1. We draw the step after a hard item, after a paywall, and after a weekend. You practice writing the sentence that names the step without moralising.
-
04
Two audiences, two telemetry skins
What a tutor needs on Monday morning is not what a PM needs in a board pack. We split instructor-facing signals from learner-facing ones and stop mixing them on one dashboard.
-
05
The academic stakeholder brief
Final week is a short written brief plus a live walkthrough. If a curriculum lead cannot argue with it, it is rewritten. This is the assignment most teams underestimate.
People who sat this desk
★★★★☆ 4.3
Clear on windows. Dry humour. Homework is real tables, not slides.
Platform-style note from a 2025 remote seat
I wanted a warehouse rebuild. This is not that. It is a reading course. Once I accepted the scope, the brief we took back to our academic board was the first one they did not send back unread.
Arthit Nonthaburi
Questions we hear before people request a seat
Do you build us a new analytics platform?
No. This lab will not replace your warehouse engineer. We work from exported event tables and the product analytics tools you already have. We do not stand up a new data platform during the eight weeks. If your pipes are broken, we will say so early and suggest pausing the seat rather than pretending otherwise.
Can a curriculum lead join without writing SQL?
Yes. At least one person on the seat should be able to export or screenshot tables. The academic partner is expected in the final brief, not in every query.
Is the fee refundable if a term suddenly starts?
Read the refund page. Withdrawals before the second live session are treated differently from mid-lab exits. We would rather move you to the next desk than keep a distracted seat.
English or Thai in the room?
Materials are in English. Discussion can move between English and Thai when the table needs it. Written briefs for this offering are delivered in English unless we agree otherwise in writing.