Person reviewing notes beside a laptop in a bright room

Method

Path reviews

A path review at Service Routepoint is a written reconstruction of one conversion sequence. It is the artefact we leave behind after a Conversion Path Audit, and the object of a Path Readout Session. This page is the method, not a gallery of dashboards.

What the document contains

  1. Screen order. The live sequence, including prompts, restores, and back-stack returns. Stage labels such as “consideration” do not appear unless the team already uses them internally, and even then they sit beside the screens.

  2. Event names. Which event marks which screen, and which names are too broad to reconstruct the path. If a restore and a fresh open share a name, that is written as a gap.

  3. Evidenced stalls. Each stall cites a screen and a range of recordings or a pattern in the events. If we cannot evidence a popular internal theory, the review says the theory is untested.

  4. Disagreements. If the readout argues, the revision pass keeps the argument. A smoothed path is less useful than one a designer and an engineer can still dispute.

What it does not contain

A single conversion score for a board pack. A redesign of every screen. A recommendation to buy a particular analytics vendor. Those requests belong somewhere else.

How to commission one

If you already know the sequence is messy, book a Conversion Path Audit. If you only know the painful screen, start with a Drop-off Clinic. If event names cannot reconstruct anything yet, start with Event Mapping.