Reviews

After the critique, not after the recap email.

These notes came from people who sat Signal Architecture, Event Taxonomy, or an Atelier Desk. We asked them to mention a specific module. We also left in the reservations.

“Kritsada’s event grammar week stopped us inventing a new property every time growth launched a campaign. Our schema still has scars, but the new contract is readable.”

Ploy Rattanakul, Product Analyst · Event Taxonomy Design
★★★★☆

Studio Seat, week 6: the alerting vs reporting split finally gave our on-call a reason to ignore the weekly canvas. I wanted more SQL. They were honest that it is not that class.

Jordan · platform-style note after cohort 14

Anonymous client in grocery delivery: “The so-what panel on the Telemetry Canvas exercise is now the only thing our regional GM reads. The rest of the dashboard still exists for the analysts.”

“I came for visualisation. I left arguing about activation windows. Fair, but book it knowing the first two weeks are almost entirely naming and decisions.”

Somsak, PM · Phuket, worked remotely into the hybrid seat

Case study

Marketplace squad, Bangkok — unfinished errands

Product lead presenting to colleagues

A seven-person product pod at a multi-service app joined Studio Seat with a home dashboard that opened on daily active users, session length, and a rainbow of funnel steps. Leadership meetings routinely skipped the dashboard and opened a spreadsheet someone had built the night before.

In the decision-inventory module they listed the actual arguments: Are riders finishing the job they opened the app to do? Is support volume a product failure or an ops failure? Is a new vertical stealing attention from the profitable one?

They cut the first screen to three panels and renamed the north star “unfinished errands.” Retention moved to page two. Elena Voss, sitting as guest critic, asked them to add a single annotation field so a PM could leave a sentence for next week’s reader. That field is still there eight months later.

They did not hire us afterwards. They sent a second PM to the next cohort.

Case study

Subscription audio, remote Atelier Desk

A four-person product team outside Thailand bought an Atelier Desk because they could not freeze eight Tuesdays. Their problem was not missing charts. It was three dashboards that disagreed about trial conversion depending on which event fired at account create.

We spent the first three private sessions only on the event contract. Visual composition waited. By week five they had one canvas and a written rule: trial_started is emitted once, by billing, never by the client. The mild cost: their designer felt underused until week six. We should have said that out loud on day one.

If you want a similar private calendar, read Atelier Desk and write from the contact page.

Portrait of a product manager in a studio setting