Flagship course
Instrumentation Studio
A live 11-week cohort for people who already ship an app and need the event layer to stop lying. You arrive with a messy dictionary. You leave with a versioned one and a QA list engineering will run.
Learning outcomes
- Write an object–action taxonomy that survives screen renames and bilingual clients.
- Separate actors from actions so guest checkout can join a logged-in order without stuffing PII on the event.
- Detect false funnel drop-off caused by events firing on view instead of entitlement.
- Specify warehouse types, null policy, and late-event behaviour so dbt models do not invent metrics.
- Run a release QA checklist a mobile engineer can finish in under twenty minutes.
Who it is for
Product analysts, mobile leads, and data partners who own a tracking plan. You should have shipped at least one production event stream. Absolute beginners are steered to Atlas Reader first.
Informational fee
฿48,500 per Studio Seat, exclusive of VAT where it applies. House Account quotes start separately. Enrolment is by note to the desk — see seat types.
Modules
Dictionary archaeology
You import the live list. We mark duplicates, vanity events, and properties that cannot be joined. No new events until week three.
Objects before screens
Name the nouns the business actually sells or grants. Screens are allowed to change; objects should not.
Actions and versions
Object–action pairs, version fields, and a written ban list. Engineering can start implementing after this week.
Checkout clinic
A slow, stubborn pass on one funnel — usually checkout or subscription start. This week is deliberately unhurried.
Identity without over-collection
Anonymous IDs, login joins, and what never belongs on a client event under PDPA-minded practice.
Where inherited schemas break
Most students discover a silent mismatch here: a property that changed meaning without a version bump.
Funnel integrity
Fire conditions, actors, and why “drop-off” is often an instrumentation error, not a UX one.
Mobile and web parity
Same object, different SDKs. We compare iOS, Android, and web payloads from the same user journey.
Warehouse types
BigQuery-flavoured examples for timestamps, decimals, and late events. Other warehouses adapt the patterns.
Release QA
A checklist sized for a pull request, not a 40-page PDF nobody opens.
Public critique
Redacted dictionary review with the cohort. You leave with comments, not a trophy slide.
Instructor
Kanya Srisawat
Kanya led product analytics at a Bangkok marketplace before opening the Charoennakorn studio. She still reviews House Account dictionaries herself. She does not teach vendor certification tracks.
Notes from this syllabus
Week four’s checkout clinic was slower than I wanted — we spent two sessions on one funnel — but I still pull that worksheet when a PM asks for ‘just one more event.’
Mira D. · product analytics, Manila
Warehouse week assumed BigQuery. We are on Redshift. I translated the type examples myself. The QA checklist still ships with every release.
Arthit Phan · mobile lead, Chiang Mai
I came in thinking it would be SQL. It was mostly naming fights. Our Mixpanel project had 400 events and 40 that anyone trusted.
Priya S. · analytics manager, Singapore
Questions
Do I need to fly to Bangkok?
No. Sessions run hybrid from the Charoennakorn studio. Remote students use the same critique queue. On-site days are optional and booked separately for House Accounts.
What is a real limitation of this course?
We do not cover vendor-specific SQL for every warehouse. Week nine uses BigQuery examples. Redshift, Snowflake, and Databricks students adapt the type and late-event patterns themselves. That gap is intentional: the studio is about the event contract, not a particular SQL dialect. If you need a warehouse-only intensive, ask the desk — it is a different program.
Can two people from one company share a seat?
No. A Studio Seat is one participant in critique. A second colleague should take a seat or join via House Account. Silent observers confuse the review queue.
What if our tracking plan is confidential?
Bring a redacted export. Class critique never uses live customer identifiers. You may keep identity examples synthetic for the whole cohort.
Ask about this cohort
Include the app surface that hurts and whether you prefer remote or the Bangkok room. A coordinator replies within two working days.