Notes

What people actually wrote down.

These are edited for length, not for shine. At least one reservation is left in on purpose. Names appear as the writer allowed.

8.2 / 10 · cohort survey

Edge Event Design taught our rider app when to wait for a quiet upload. The live wall still lies during BTS rush hour; at least we now label that as network flap instead of “churn.”

Pim · mobile · Pathum Wan

I wanted Retention Signal Mapping to hand me a magic week-four predictor. It handed me a shorter list and a longer argument with marketing. That was the useful part.

Anonymous client in fashion retail

“Mute rules from the Lab Seat went into our on-call doc the same week. Naming homework took three reviews. I would still sit it.”

Kittisak R., data · Nonthaburi

★★★★☆

Cohort Pulse Workshop is too short if your funnel is a mess. We should have done the Live Usage Lab first. The drift charts were still clearer than our Tuesday export.

Sofia · Phuket (flew in)

Nalinee told us on day one that sockets would not replace BigQuery. We almost left. Staying meant we stopped paging the warehouse team for “live drop-off” that was just land time.

Client in last-mile logistics · Khlong Toei

Film-strip evening on the rider session: I still pause before I argue. The PromptPay module in the lab was the first time finance and product used the same sentence for “paid.”

Mira K., product ops · Bangrak

Case study · Khlong Toei dispatch

Team meeting around a table with notebooks

A last-mile desk ran Floor Cohort after a month of paging on a red “live abandonment” chip. The chip was a socket consumer trailing by nine minutes during rain peaks. Warehouse land time was another twenty.

Work: shared naming ledger for dispatch_offered and rider_accepted; mute rule that forbids paging when consumer lag exceeds four minutes; film-strip night on a single flooded-road evening. Result they reported: on-call volume down, not because the product got calmer, but because the page finally meant “the offer path broke,” not “the chart is red.”

Told with permission · identifiers withheld

Case study · remote payments seat

Sunlit workspace with laptops during a workshop

A Chiang Mai payments engineer sat Lab Seat remotely. Their checkout_paid fired on wallet intent. PromptPay callback arrived later, sometimes not at all when the user cancelled.

Critique piece renamed the live chip to checkout_intent and added a second event after callback. Finance stopped celebrating a number that included ghosts. The writer still flags that critique week felt rushed across timezones — a fair complaint we have not fully solved.

Arthit P. · allowed attribution