★★★★★
The Pipeline Signal module forced us to drop three charts that looked impressive and said nothing. Our Friday ops review is now half as long.
Reviews
Notes from people who sat through the labs
We keep glowing quotes and the mild reservations — both help the next cohort decide.
“4.2 / 5 — strong mentoring, homework denser than the brochure implied.”
★★★★☆
Narrative Metrics clinic was the highlight. I still struggle applying the same discipline to batch windows that only run monthly — the examples lean toward continuous pipelines.
Anonymous client in fintech: we used the Retry Storm worksheet during a real incident week. It did not magically fix the queue, but it stopped us from restarting workers blindly.
★★★★★
Yoon-ah’s comments on my portfolio brief were specific — she circled where I claimed causation from a single deploy marker. That sting was useful.
Short and true: Automation Health Notes gave our junior ops writers a weekly skeleton they still use.
Case studies
Regional marketplace — quieter deploy Fridays
A Jeonju-based marketplace team joined Pipeline Lens after executives demanded “automation ROI slides.” Instead of inventing a composite score, they shipped a two-metric pack: failed job rate tied to checkout error budget, and median queue age for inventory sync.
Within six weeks, Friday deploy reviews stopped reopening every yellow panel. The team still notes that legacy Windows agents remain poorly covered — a gap the curriculum flags rather than hides.
Logistics API guild — shared language across vendors
Three squads used different tracing vendors. After Telemetry Insight Lab they adopted a shared claim template: observation, window, confidence, next experiment. Cross-squad postmortems began citing the same fields.
They rate the experience 4.3 overall; the reservation is pacing — week five landed during a peak shipping season and felt compressed.