Module 1 — Questions before metrics
Inventory decisions that stall today. Translate each into a signal you can observe without new tooling theater.
Flagship course
Pipeline Visibility Studio
Six weeks of guided practice building application analytics that make code delivery legible—from commit waiting time to release narratives stakeholders trust.
Live + recordings
6 weeks
₩820,000 informational
Learning outcomes
- Select a small set of delivery signals tied to decisions you already make.
- Draft a visibility map covering commit, review, build, deploy, and observe.
- Facilitate a weekly narrative that names friction without personal scorekeeping.
- Retire at least one vanity metric with a documented replacement.
Informational pricing
₩820,000 / learner
Included under the Signal Circle tier. No payment is processed on this website. Contact us for cohort dates, invoices, and team seating.
Contact enrollmentModules
What we work through
Module 2 — Waiting-time anatomy
Break lead time into queues humans control: review, environment, approval, and verification.
Module 3 — Handoff heatmaps
Plot friction between roles and systems. Practice explaining idle time without blaming individuals.
Module 4 — Instrumentation honesty
Mark where telemetry is incomplete. Learn to communicate confidence bands instead of false precision.
Module 5 — Release narratives
Script a thirty-minute stakeholder review that opens with risk and waiting, not vanity totals.
Module 6 — Sustainment rituals
Install lightweight cadences, alumni critique habits, and a retirement plan for decaying charts.
Instructor
Hae-won Choi
Hae-won coached delivery analytics for product platforms across Korea and remote APAC teams. She favors small signal sets, plain-language narratives, and dashboards that can survive a messy Monday standup.
Learner notes
“Module 3’s heatmap made our approval lag impossible to ignore. We still struggle with overnight batch jobs, but the conversation finally has a shape.”
★★★★☆
“Clear coaching. I would have liked deeper coverage of trunk-based edge cases in Module 4.”
FAQ
Do I need a mature observability stack?
No. You need enough history to discuss reality. Incomplete data is expected; Module 4 teaches how to present confidence limits.
Is this a tool-training course?
No. We stay tool-agnostic. Concepts transfer across common CI, issue, and analytics platforms.
What is a real limitation of this studio?
We cannot remediate years of missing instrumentation in six weeks. Teams with almost no event history will practice on sample datasets first, then apply methods when their pipelines catch up.
How are refunds handled?
See our refund policy for windows and non-refundable items. Enrollment itself happens offline after contact.