Page
How an audit week is paced
Five days with the app in someone’s hand, not a slide about ‘visibility’. This is the rhythm we keep unless a campaign freeze forces a split week.
Monday — walk the shop as a shopper
A merchandiser holds the phone. We start on the home grid they actually merchandised last week, not a staging skin. We add a SKU, apply a voucher, try guest checkout, and attempt store pickup if the chain offers it. The point is to feel which screens exist before anyone opens an event list.
Tuesday — name what fired
We sit with the current event names and replay Monday’s path. Guest versus member, list price versus voucher residual, pickup versus home delivery each get a row. If “purchase” fired on a declined FPX return, it is written down in plain language for finance.
Wednesday — the awkward paths
Returns to bag, out-of-stock taps, Bahasa search queries, and bundle SKUs. These are the paths that never appear in a tidy funnel drawing and always appear in a Malaysian catalog. We only go as deep as the brief; a grocery app with wet-market substitutions is a different Wednesday than a fashion app with size charts.
Thursday — draft the pack
The pack is a screen map, a list of events a Monday meeting may use, and a shorter list of events that should be retired or split. We do not invent a backlog of fifty engineering tickets. We write the ten that change a merchandising decision.
Friday — readout
Ninety minutes. Merchandising first, then product, then finance if they want the failed-payment distinction. Questions that need a second look are scheduled; we do not pad Friday with a second product.
If this pacing matches the question on your desk, request a briefing or read the app funnel audit in full.