Flagship engagement

Full journey audit

A complete walk of one primary task, from first open to a finished action, with a screen-by-screen map and a written account of stalls.

Full journey audit

Ten working days · George Town studio or remote walkthrough · Fixed fee from RM 8,400

The flagship offer is a full journey audit for product owners who already have a live app and a task they care about: opening an account, placing an order, booking a visit, or filing a claim. Page Meadow Hub is hired to walk that task as a first-time visitor would, then as a returning one, and to write what actually happens on each screen.

Who it is for

Teams in Malaysia who can grant a test login, a staging build, or a supervised walk of the production app. Typical clients are a product lead, a small design pair, and someone who can answer why a field exists. You do not need a research department. You do need a task that a real person is supposed to finish.

Result

You receive a journey map (screens in order, with branches) and a written audit that names stalls, dead ends, confusing copy, and moments where the app asks for something the person cannot yet know. The map is a document, not a login to software we host. Your team keeps it and can reprint it on a wall.

Scope

Included:

  • One primary task and one secondary return path
  • Up to twelve observed sessions (recorded with consent, or live beside a colleague who already uses the app)
  • A wall mapping session of half a day in George Town, or the same session on a shared board if you work elsewhere in Malaysia
  • A written audit of eight to twelve pages
  • A ninety-minute readout

Excluded:

  • Building or redesigning screens
  • Writing code
  • Recruiting paid research participants beyond your own staff and a small circle you introduce
  • Marketing copy for app stores

Who leads it

The audit is led by a journey analyst from Page Meadow Hub, usually Mei Lin Tan, with a second pair of eyes on the map before the readout. Work happens in English. Malay can be used in sessions when that is the language of the app.

Process

  1. Intake call to name the task, the audience, and the constraints (time, language, device).
  2. Access check: test account, devices, and any legal notice your users already see.
  3. Observed walks and note-taking.
  4. Mapping day: screens become cards; arrows become taps, waits, and abandonments.
  5. Draft audit for your comments on facts only.
  6. Readout with the map on the table.

Timeline and place

Ten working days from access granted to readout. Mapping can be at Level 10 in George Town or remote. Observation of public-facing screens can happen on ordinary phones; we do not require a lab.

Preparation

Send the current app name, the task in one sentence, and three examples of people who should be able to finish it. If the app is bilingual, say which language a first-time visitor is likely to meet first.

Constraints

We will not audit a task that requires real money movement in a live account. Use a sandbox or a supervised dummy purchase. We also will not record sessions without the person’s knowledge.

Fee

Fixed fee from RM 8,400 for one task in a single app. Extra languages, extra tasks, or a second product line are quoted after intake. A thirty percent booking deposit holds the dates. See Fees for what changes the number.

Next step

Write to the desk with the app name and the task. If a mapping day is a better first meeting, look at how a mapping day runs.

Ask about this work