Flagship programme

Device Signal Studio

Eight evening weeks for teams who share one connected app and still argue about what “online” means. You leave with a telemetry contract, not a slide deck of aspirational KPIs.

Multiple monitors showing operational dashboards in a dim room

Learning outcomes

  • Write a versioned telemetry contract that firmware and the companion app can both honour.
  • Build activation and habit funnels that remain comparable across OTA cycles.
  • Detect payload drift in MQTT topics before a dashboard silently lies.
  • Separate ops uptime views from product habit views without splitting identifiers.
  • Run a small experiment on a constrained device without pretending it is a web A/B test.

Informational fee

THB 34,200 per organisation for three named seats, invoiced after a scoping call. Recordings of live sessions are included; they are not sold separately during an active cohort. This page cannot check out.

Who teaches

Portrait of instructor Nalinee Srisawat

Nalinee “Lin” Srisawat

Former product-analytics lead at a Bangkok IoT logistics company. Lin still reviews redacted payload dumps for alumni and refuses to grade dashboards that cannot name their firmware dimension.

Modules

  1. Telemetry as a promise. Naming, types, nullability, and who is allowed to change a field.
  2. Event taxonomy for device + app. One identifier story across gateway, firmware, and companion screens.
  3. Funnel leakage across OTA. Why activation resets, and how to freeze a cohort window.
  4. Retention by firmware line. Weekly cohorts that survive sleep modes and buffered uplinks.
  5. MQTT topic hygiene. Payload drift, boolean-to-string accidents, and a first-week checklist.
  6. Ops desk vs product desk. Two dashboards, shared keys, contradictory questions.
  7. Experiments on constrained hardware. Sample rates, ethics of remote flags, and when not to experiment.
  8. Capstone. Instrument a fictional ASEAN fleet or a redacted slice of your own. Critique is public to the cohort.

A few voices from this syllabus

“Lin would not look at our Grafana until we listed every MQTT topic. Annoying. Then useful. The capstone forced ops and product to sit in the same row.”

Somsak Jittrakul, handheld scanners

The firmware-cohort week changed our Q3 narrative. I still think module five moves too quickly if you have never versioned a schema.

Pimchanok W., Bangkok

★★★★☆

Eight weeks is long. We used all of them. Would not send only the intern.

Client in industrial HVAC

Questions we actually get

What is a real limitation of this studio?

We do not teach warehouse modelling, Spark jobs, or vendor-specific BI certification. If your bottleneck is a broken data platform rather than a broken event contract, Device Signal Studio will feel sideways. We also cannot invent cellular coverage: rural buffered gateways still make same-day funnels unusable, and we will say so in week four instead of drawing a fake real-time chart.

Do we need to travel to Khlong Toei?

Evening sessions run in the Bangkok studio when enough seats are local; otherwise critique is remote. The capstone review is live either way.

Can one person attend alone?

Yes, but the dual-dashboard module is weaker without a counterpart from the other desk. We would rather you bring firmware and product, even if one seat is mostly listening.

How do refunds work?

See the refund page. Desk Notes recordings after download are treated differently from unused studio seats.

Enquire about a seat

Name the companion app and firmware lines. We will say if Desk Notes is enough.