1 · Choose the journey
Scope one microservice path, inventory existing signals, and name the customer-visible moments.
Flagship course
Service Signal Studio
A six-module journey through application analytics for microservices API experience — built for engineers and product partners who share one service path.
Learning outcomes
- Draft a latency budget that product and platform both accept
- Annotate traces so non-engineers can follow the story
- Build a reusable analytics canvas for one customer journey
- Spot vanity metrics that hide API experience regressions
- Facilitate a 20-minute briefing using your own dashboards
Informational pricing
Included in Pulse Sketch (recordings) and Trace Atelier (live critique). See pricing for seat amounts. No payment is processed on this website.
Modules
2 · Latency budgets that survive mesh hops
Allocate time across gateways, sidecars, and core handlers without inventing precision you cannot measure.
3 · Narrating spans for PMs
Translate waterfalls into decision language; practice with annotated screenshots.
4 · Product-facing dashboards
Design three charts that belong in a roadmap review — and retire five that do not.
5 · When metrics disagree
Reconcile success rates, traces, and support tags when they tell conflicting stories.
6 · Studio briefing
Present your canvas live; receive redlines and a 30-day follow-up checklist.
Instructor
Yoon Seo-hyeon
Former platform lead for a Busan commerce stack; now focuses on teaching application analytics for microservices API experience. Seo-hyeon still consults on trace sampling strategies and writes the studio’s canvas templates.
Learner notes
“Module 3 forced us to delete half our Grafana panels. Painful, then liberating.”
Elena · Berlin
“Useful, though Module 5 assumes you already have distributed tracing — we spent an extra week instrumenting first.”
Client in insurance tech
FAQ
Do I need OpenTelemetry already?
Helpful but not mandatory for Pulse Sketch. Trace Atelier expects at least one instrumented path; without it, critique stays conceptual.
Is there a real limitation I should know?
Yes: we do not teach vendor-specific APM configuration in depth. If your blocker is licensing or agent install quirks, we will point you to docs rather than diagnose your account live.
Can product managers join alone?
Yes, if they pair with an engineer for homework screenshots. Solo PMs succeed when they already have read-only access to traces.
Language of instruction?
English materials and live sessions. Optional Korean clarifications during Busan evening clinics when the cohort requests them.