The practice behind the readouts

Three people in Johor Bahru who spent years arguing with live titles before they started writing those arguments down for other rooms.

Tool Meadow Core started because too many Malaysian studios were quoting a D1 that belonged to last month’s tutorial. Aisha Rahman had been sitting in live-ops rooms in Johor Bahru and KL, watching producers defend a funnel to a publisher while the designer in the corner knew the first session had changed twice. The practice is the place those arguments get written down before the next patch.

We work as a small room, not a department. Gaming app analytics here means sitting with the event list, the store week, and the people who can still change the build. It does not mean a product you log into after we leave.

How we came to this work

Aisha spent eight years on casual and hybrid-casual titles that launched first into Malaysia and Indonesia. She learned that a “clean” event name is often a lie about when it fires. Wei Jun came from a mid-core live team that mixed ads and IAP in the same session and kept two spreadsheets that never agreed. Priya had been the person who typed the post-mortem nobody read; she now runs the workshop notes so the room cannot pretend it decided something else.

Johor Bahru is the base because the teams we sit with can reach Level 7 without a flight, and because evening playtest hours here still match how the title actually behaves after office close.

How a sit-in feels

We ask for the event list before opinions. We will say when a number cannot be read. We would rather end a week early than invent a chart. Clients keep the written readout; we do not keep a copy of their player logs after the engagement unless the contract says otherwise.

The people