A living event dictionary
Not a spreadsheet graveyard. A one-page contract plus examples from your own product, reviewed by faculty.
Flagship · 8 weeks · Bangkok & remote
Interaction Trace
A studio course for people who own content inside an app and are tired of dashboards that celebrate opens while the actual read remains a rumour.
What you work on
Each week you instrument a fictional but stubborn product: a bilingual news reader, a short-form video shelf, and a serialized audio show. The datasets are small on purpose. The argument is about evidence, not sparkle.
You will write an event dictionary, a sampling contract, and a Monday report that an editor can mark up in red. Capstone reviews happen live, with one faculty member playing the unimpressed newsroom lead.
Who it fits
Product analysts, editorial data partners, and research managers who already know a BI tool and want language for content interaction tracking. You do not need to be an engineer. You do need patience for SQL joins and for saying “we do not know yet.”
This track does not cover paid acquisition, MMP setup, or store-console metrics. Those sit outside the studio’s brief.
Modules
- 01Signal inventory. Walk a content surface and list interactions that a human would recognise: open, pause, skip, save, share, return. Drop anything that only exists because an SDK offered it.
- 02Taxonomy without sprawl. Object, action, property. Naming rules that survive a re-org and a Thai–English glossary.
- 03Mixed signals. Scroll depth, dwell, tap, and audio heartbeat as corroboration, not as four separate truths.
- 04Cohort windows. Serial content needs time boxes that match how a desk plans covers, not how a warehouse partitions tables.
- 05Sampling for high-volume feeds. Design a contract that still finds outliers when you cannot keep every impression.
- 06Reporting editors will use. One page, Monday, with a claim, a caveat, and a next experiment.
- 07Privacy and retention. What not to keep when the content is political, medical, or aimed at young readers.
- 08Capstone. Instrument one surface end to end and defend it in a live critique.
Outcomes
A sampling memo
Written so engineering and editorial can both sign it. Includes what you will miss on purpose.
A Monday report shape
Reusable template that starts with a claim about content, not a screenshot of a funnel.
Critique stamina
Practice defending a metric when someone in the room still wants unique opens as the headline.
Instructor
Araya Wongsawat
Araya spent a decade inside regional news and audio products before opening the studio. She still reviews event dictionaries the way a copy editor reviews headlines: slowly, and with a pencil. Office hours are held in Sai Mai on Tuesdays and Thursdays.
Fee (informational)
฿24,500 / seat · Interaction Bench
The flagship runs inside the Interaction Bench fee. Studio Residency adds private critique. There is no checkout on this site; write to us to reserve a seat. See all published fees.
Questions we hear before week one
Do I need to be an engineer?
No. You should be comfortable opening a SQL editor and reading a join. We do not teach mobile SDK installation.
What is a real limitation of this course?
We do not cover advertising attribution, store consoles, or marketing mix models. If your main problem is paid user acquisition, this track will feel incomplete — by design. We stay inside in-app content surfaces.
Can my whole desk join?
Yes. Private runs for three or more seats are billed under Studio Residency. Remote students join the same ICT afternoon block.
What if I miss a live session?
Recordings stay available for 30 days. Critique sessions are live only; missing the capstone means waiting for the next cohort.
Notes from past seats
The mixed-signals week changed how we labelled “finished chapter” in the reader. We now require dwell plus a return within 48 hours before we call it a completed issue. Niran S. · learning product, Bangkok
Useful, occasionally stern. Araya would not let us keep `content_view` as a name. Fair. Anonymous client in magazine apps · ★★★★☆