Stage Loss Lanes
Zeigen Sie, wo Leute aussteigen — und welches Leck Sie zuerst stopfen.
Zeigt, wo Leute wirklich aus einem Funnel aussteigen: Jede Stufe lässt die Verbleibenden weiterziehen, während eine Nebenspur die Aussteiger abführt, beschriftet mit dem Grund, warum sie gegangen sind.

In 3 Schritten installieren
Keine Anmeldung. Keine CLI-Tools. Wählen Sie Ihre AI, kopieren Sie eine Zeile und fügen Sie sie ein.
Lieber selbst machen? Kaufen Sie den Skill ($4.99), laden Sie die ZIP-Datei aus Ihrer Kaufbestätigung herunter, entpacken Sie sie in das oben angezeigte Verzeichnis und starten Sie Ihre AI-Sitzung neu — gleiches Ergebnis. Haben Sie ihn schon gekauft? Ihr AI-Assistent kann ihn für Sie herunterladen.
Was ist enthalten
Eine SKILL.md (die Anleitung) + eine Startvorlage. Eine Vorschau:
Stage Loss Lanes
When to use
- You're walking through a funnel — signups, onboarding, checkout, applications — and the headline conversion rate hides where the real bleeding happens
- Your audience keeps asking "where do we lose people?" and the answer is a bar chart that shows totals but not the exits
- You're reviewing a process (hiring pipeline, sales pipeline, course completion) where each stage loses people for a different reason and the reasons matter more than the counts
- You're presenting an audit or post-mortem and need the audience to see, stage by stage, which leak to fix first
- You want a funnel visual that works in a video, not just a slide — one where the flow is visible over time
Workflow
- Define the stages (input: process + data → output: 3–6 stages with counts)
Name 3–6 stages in the audience's language, not the database's: "Visited pricing," "Started trial," "Added payment," "Still active after 30 days." Each stage gets two numbers: how many entered, how many moved on. The gap between them is the loss for that stage. If you have more than 6 stages, merge the ones with tiny losses — a funnel with 11 stages is a spreadsheet with arrows. Every number needs a date range and a source ("product analytics, March 1–31") — a funnel without a date range is a rumor with boxes. - Name the loss reason per stage (input: stage gaps → output: one loss reason per stage)
For each stage, write the single most common reason people left, in plain words: "Price shock at the paywall," "Form asked for a phone number," "Never got the confirmation email." One reason per stage, the biggest one — not a list of five. If you genuinely don't know why people left a stage, label it "Unknown — needs investigation" rather than inventing a reason. An honest unknown is more useful than a confident guess, because it tells the team what to measure next. - Build the main flow (input: stages + counts → output: forward flow)
Draw the survivors' path as a horizontal flow, left to right, with one block per stage. Block width is proportional to the number of survivors — a stage that keeps 80% of people is visibly wider than one that keeps 30%. Animate the flow as moving dots or a stream: a steady trickle of dots entering stage one, thinning as they pass each stage. The thinning must be visible — if the stream barely changes width, the funnel has no story and you should say so rather than exaggerating the drop. - Branch the loss lanes (input: stage gaps + reasons → output: side lanes per stage)
At each stage, a side lane branches off — downward for losses that are recoverable (abandoned cart, unconfirmed email), upward or to a muted gray lane for losses that are final (unqualified, churned). Each lane carries a label with the count and the reason: "—214 · Price shock." Animate each lane's branch as dots peeling off the main stream over 0.6s, timed to the voiceover naming the loss. Lane thickness is proportional to the loss count, same scale as the main flow — a lane drawn thicker than its numbers is a lie told in geometry. - Rank the leaks (input: loss lanes → output: fix-first ranking)
After all lanes are drawn, highlight the single biggest recoverable leak — a brighter lane, a ring around its label, or a "fix this first" tag. The ranking rule: biggest recoverable loss first, not biggest loss overall. A huge lane of unqualified visitors is not a fix; a medium lane of people who abandoned at the phone-number field is. State the ranking in one sentence in the voiceover: "If you fix one thing, fix the phone-number field — that's 214 people a month who wanted in." - Hold the full picture (input: ranked funnel → output: 3–4s final hold)
Hold the complete diagram — main flow, all lanes, labels, ranking — for 3–4s at the end so viewers can screenshot it. Add the date range and data source as a small line under the diagram for the full hold. Never animate anything new during the hold: the hold is for reading, and motion during reading is noise.
Vorschau der Startvorlage
Stage Loss Lanes — Funnel Template
One funnel per process per period. Fill in the numbers before drawing.
Process: {name} | Period: {date range} | Data source: {e.g. product analytics}
Stages (3–6, audience-language names)
Merge rule: {more than 6 stages → merge the ones with tiny losses}
Diagram build
Main flow: {horizontal, left → right, block widths proportional to survivors, moving dots/stream} Loss lanes: {one per stage, branch over 0.6s, thickness on same scale as main flow} Lane direction: {downward = recoverable · muted/gray = final} Lane label format: "{—214 · Price shock}"
Fix-first ranking
Das Skill-Paket selbst (SKILL.md + Vorlage) ist auf Englisch verfasst.


