About the studio
We started because launch threads were outrunning the evidence.
Cloudeventgrid grew out of product reviews in Bangkok where a feature could be called “adopted” if anyone clicked it once. That was not a measurement problem alone. It was a teaching problem.
Mission
Our mission is narrow on purpose. We help product, analytics, and design partners in Thailand and the wider region read Feature Adoption Analytics well enough to brief a roadmap without inflating a single percentage. We are not a general data school. We do not sell dashboards. We teach the reading: what exposure means, when first value actually happened, and how to write down that a feature has failed quietly.
The studio name is literal. Events sit on a grid — release, cohort, surface, language, device — and most teams only look at one cell. We train people to look across the grid before they celebrate.
Pedagogy
Every seat works on a live product, not a toy dataset. If your event names are a mess, that mess becomes the first week. Instructors do not rescue you with a cleaned warehouse; they sit with the dirt until you can name first value in language your PM and your analyst both accept.
Clinics mix short lecture with artefact critique. You leave with an uptake map, a cohort contract, and a retirement brief — documents, not slide wallpaper. Remote participants submit the same artefacts. We will not pass a pretty chart that hides a broken denominator.
Thai and English both show up in our rooms. Labels, in-app copy, and support macros often disagree; activation curves split when you ignore that. Pedagogy here includes sitting with bilingual surfaces instead of pretending every user reads the English string.
A week in the flagship
- Bring one shipped feature and its event list, however ugly.
- Write exposure, first value, and “quietly dead” in plain sentences.
- Rebuild the cohort window to match how you actually release.
- Critique another team’s map; defend yours to a sceptical reader.
- Revise. The second draft is the one that goes to leadership.
Community
Alumni stay in a low-noise list. We do not run a hype Slack. People post uptake maps, ask for a second reader on a retirement brief, and sometimes invite a former classmate into a Bangkok review. Once a quarter we open a public reading night at the Lat Krabang studio — tea, printed charts, no pitch deck.
If you complete Feature Uptake Measurement, you may sit in on later Cohort Retention Studio critiques as a guest reader. That is the community loop: you learn by having your work read, then by reading others.
Student journey
Most people arrive after a painful launch: a feature that “did well” on day seven and vanished by day forty. They start in Reading Room or Pulse Seat if they only need language, or they join Signal Bench if a whole squad can show up with the same event catalogue.
During the twelve-week flagship you pick one feature and refuse to switch. Mid-cohort, many students discover the feature was never exposed to the segment they thought. That discovery is the point. After close, we ask for a 90-day note: did the uptake map change a roadmap decision? About two-thirds of surveyed alumni said yes; the rest said the map clarified a kill they still could not get through politics. We count both as honest outcomes.
Visitors are welcome by appointment at Street: 222/6 Gp 1 Onnuch-Ladkrabang Lardkrabang Lat Krabang; City: Bangkok; State/province/area: Bangkok; Zip code: 10520; Country: Thailand. Call 27380476 or write info@cloudeventgrid.digital.