Farah’s note on our onboarding path density chart was a single sentence: “You’re celebrating speed through a step customers hate.” We redesigned the step the next sprint.
Flagship course
Journey Signal Studio
A six-week build-and-critique program where you construct the visualization layer of a customer journey analytics platform — and document what it still cannot see.
Learning outcomes
- Define a journey event taxonomy that resists vanity inflation.
- Design path-density and time-to-recover views stakeholders can read in under two minutes.
- Instrument cohort comparisons that separate seasonality from product change.
- Present a limitation slide that earns trust instead of burying gaps.
Modules
What you build each week
Week 1 — Route inventory
Audit existing funnels, interview snippets, and support macros. Produce a candidate event list with owners.
Week 2 — Signal grammar
Chart patterns for branches, loops, and silence. Critique common donut-chart journey anti-patterns.
Week 3 — Path density studio
Build your first interactive path view using your own sample export (CSV or warehouse extract).
Week 4 — Cohort storytelling
Layer retention and recovery metrics without turning the board into a spreadsheet wallpaper.
Week 5 — Stakeholder readout
Practice a 12-minute narrative with a forced limitation section. Peers score clarity, not polish.
Week 6 — Platform handoff
Package queries, visual specs, and monitoring notes so your internal platform team can maintain the route.
Instructor
Farah Lim
Farah led journey analytics for a Southeast Asian commerce group before joining APIRoute Center. She focuses on visual explanations that survive legal and finance review — and will stop a demo if the chart implies certainty the data cannot support.
FAQ
Which tools do we use?
Concepts are tool-agnostic. Demos rotate across spreadsheet prototypes, a BI example, and lightweight notebook sketches. Bring the stack your company already funds.
Is this suitable for beginners?
You should be comfortable joining tables or explaining metrics to a product manager. Absolute beginners in SQL may struggle in weeks 3–4.
What is a real limitation of the course?
We do not provide a turnkey SaaS platform. You leave with designs, queries, and critique habits — not a hosted product you can white-label. Teams without access to event data will hit a ceiling quickly.
Can my whole squad join?
Yes — see Atlas Cohort on the pricing page for private facilitation.
★★★★☆
Strong on narrative structure. The homework load spikes in week 3; block real calendar time or you will skim.