12 Jul 2026 · Nalinee Srisawat

When a tap is not a step

Phone in hand while marking which taps count as steps

Product reviews love motion. A tap fired, a screen advanced, a funnel step ticked green. In User Journey Mapping for Apps that reflex is expensive. It teaches the room that activity is progress. It is not.

In Path Cartography Studio we use a blunt test: did this interaction change the person’s next option? Opening a tooltip does not. Dismissing a coach mark does not. Expanding an FAQ accordion on a KYC screen does not. Those taps may be useful for support analysis. They are not steps on a journey map.

Permission dialogs look like commitment

Allowing notifications, or denying them, can be a real step if the next screen actually branches. Often it does not. The app continues identically. Counting the dialog as onboarding “completion” inflates the first-week story. We mark it as a side door and keep it off the spine of the map unless the branch is real.

How we mark decoration

On paper we draw the spine in one colour and decorative taps as small ticks beside it. The warehouse can still store those events. The review script is not allowed to mention them as evidence that people are “engaged.” Funnel Grammar for Mobile Screens spends a whole week practising this split, because most imported funnel templates never learned it.

If your activation number only holds when decorative taps are included, you do not have an activation number. You have a fidget count. Bring that honesty to the next critique, or do not bother hanging the map.

Back to the journal