Path charts need device proof, not another meeting
A silent miss on one OS invents a cliff the product never caused.
When a path chart shows a steep drop between adjacent steps, product meetings escalate. Sometimes the drop is real. Often the second step never fired after a permission prompt, or only fired on one OS version.
Before rewriting onboarding, walk the path on the devices your users hold and watch the live stream. Note every silent miss. Ask whether the step is client-only, server-confirmed, or both.
Identity resets between web and app are another quiet culprit. Users who continue on a second device look like new entrants who abandoned mid-path.
A Path Verification Walkthrough stays narrow on purpose: one journey, deep QA, a script you can rerun after every release.