Notes

From freeze calendars, silent screens, and stubborn Monday charts.

Short pieces from the practice. They are written for analytics leads and product owners who still ship an old client, not as general essays on “change”.

A person holding a phone, the kind of device a legacy app still lives on
2026-03-12 · Lina Tan

What actually goes dark the week you leave a legacy app

Store downloads keep arriving. Almost everything else — funnels, retention cohorts, even the meaning of a session — can fail silently if the destination build was instrumented from a vendor template.

Read the note
Open notebook and papers on a desk used to reconcile two reporting periods
2026-01-21 · Hafiz Rahman

Keeping a year-on-year chart honest after the app changes address

A cutover is a break in the series. You can still talk about the business, but you should stop pretending the line is continuous unless the identifiers and the event names survived.

Read the note
A handwritten checklist of tasks spread across a notebook
2025-11-04 · Lina Tan

Inventory the screens before anyone picks the destination SDK

Vendor comparisons eat the calendar. The list of screens and the names they already have in the live app is the work that actually protects Monday’s report.

Read the note
Colleagues talking through a plan at a bright office table
2025-08-19 · Mei Ling Ong

A three-week baseline with a George Town product team

They still ran a hybrid wrapper from 2018. Leadership wanted the new native clients compared with last year’s Ramadan campaign. The old campaign lived in event names nobody had listed.

Read the note
Handwriting in a notebook during a planning conversation
2025-05-07 · Hafiz Rahman

Questions an analytics lead should ask engineering before freeze

Not a vendor checklist. Five questions about identifiers, clocks, background events, and the screens that will still exist when the old binary is gone.

Read the note