Sequences that lie about abandon
A missing mid-path tool event invents drop-off that product never caused.
Product meetings escalate when a usage sequence chart shows a steep cliff between adjacent tools. Sometimes that cliff is real. Often the second tool never fired after a permission prompt, or only fired on one platform.
Before rewriting the toolbar, walk the path on 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-sequence. Pattern Diagnostic exists to catch that before the roadmap absorbs the wrong story.