Flagship course

QA Reporting Analytics Lab

A six-week studio for building application analytics for QA automation reporting — from export hygiene to a calm weekly board and a narrative pack your stakeholders will actually open.

Request next cohort See access tiers

Laptop displaying financial-style analytics charts

What you will leave with

  • A documented metric garden: primary, secondary, and archived signals
  • A living dashboard template tuned for automation pipelines
  • A weekly narrative ritual (15 minutes) for product and engineering syncs
  • A flake impact scorecard you can defend in prioritization meetings
  • Language for uncertainty that does not sound evasive

Informational pricing

₩890,000 per seat

Includes live labs (KST evenings), recorded catch-ups, critique office hours, and template kit. No payment is collected on this site — enroll via contact.

Modules

Six weeks, one coherent board

  1. 01

    Export Hygiene & Source Trust

    Normalize CI exports, tag ownership, and decide what never enters the dashboard.

  2. 02

    The Metrics Garden

    Plant only signals that change decisions; prune vanity pass rates with kindness and data.

  3. 03

    Flake Clusters & Blast Radius

    Group intermittent failures, score stakeholder impact, and present a remediation queue.

  4. 04

    Coverage Drift Without Drama

    Visualize silent losses and draft the email that gets engineers curious, not defensive.

  5. 05

    Narrative Pack Studio

    Write the one-pager, the stand-up card, and the leadership footnote from the same source of truth.

  6. 06

    Ritual Design & Handoff

    Install a weekly cadence, assign caretakers, and document how the board evolves after the cohort.

Portrait of course instructor Haeun Park

Instructor

Haeun Park

Former platform QA lead for a Busan commerce stack, now based near our Daegu studio. Haeun designs reporting rituals for teams who are tired of red-wall dashboards and wants metrics that feel readable at 9 a.m.

Learner notes

Recent voices from this lab

Module 02 forced us to delete seven charts. Painful in the moment; stand-ups got shorter by nine minutes.

Sora K. · Automation engineer · Incheon

Templates are gentle on the eyes. I still needed help wiring our custom runner tags in week one — office hours covered it, but plan for that friction if your toolchain is unusual.

Client in healthcare SaaS · ★★★★☆

FAQ

Straight answers

Do I need a BI tool already?

No. We work in spreadsheet-friendly exports and a lightweight dashboard kit. If you already use a BI suite, you can map the same metric garden there.

Is this only for Korean teams?

Live sessions favor KST evenings, and many examples reference Korea-based product orgs. Recordings and async critique welcome remote learners elsewhere.

What is a real limitation of this course?

We do not rebuild your CI architecture. If pipelines cannot emit consistent tags or durations, you will spend extra time on export hygiene before the analytics layer feels smooth — we teach the workarounds, but we cannot invent missing telemetry.

Can my whole squad join?

Yes. Team seats are available through our Pipeline Empathy Sprint packaging — start via contact.