A practice in Johor Bahru

Webgardenhub started because too many readout meetings in this country treated a telecom customer app as if it were a content feed. The app is where a prepaid balance is topped up, a family bill is opened, and a Johor commuter buys a Singapore roaming pack. If those acts are counted wrongly, commercial, product, and the call centre argue from three different stories.

Why Johor Bahru

The office is here on purpose. The causeway commute, the mix of Bahasa and English in the same household, and the Android models still common in southern stores are not edge cases for us. We travel to the Klang Valley when a team wants the sitting there. The written work can be done remotely once test accounts exist.

How we work

We take one live app at a time. We ask for event catalogues, store listings, and test accounts that can actually reload or pay a bill in a non-production environment. We walk the journeys on hardware that matches the base. We write in named screens, not in slogans. If a gap needs a vendor or a core billing change, we say so instead of dressing it as an app task.

We do not sell a login for a measurement product. We do not run paid install campaigns. We do not fix radio quality. Those jobs belong elsewhere, and mixing them with a measurement review is how findings get lost.

Values that show up in the document

• The same journey in three languages is still one journey; the event names should match.
• A success event waits on billing confirmation, not on a tap.
• Store-typical devices are in scope, not only the phones in the product room.
• A mild disagreement in the readout is preferable to a polite document nobody can act on.

If that matches how you already argue inside the company, write to us. If you need a vendor to implement the events, we can name the gaps; we will not pretend to be that vendor.