Learning paths
From first office hours to confident facilitation
New members usually arrive with scattered templates and heroic individual contributors. Across a few seasons they move into shared rehearsal language—where controls, evidence, and tone stay aligned even when tools change. The path is conversational on purpose: you should feel peers beside you, not a broadcast.
Midway, cohorts trade facilitation duties so quiet voices practice narrating risk. Later modules emphasize briefings for steering forums, where clarity beats volume. Graduates often stay inside office hours to stress-test one another’s drafts long after certificates are filed.
Typical progression
- Orientation on vocabulary, evidence hygiene, and how we handle masked samples.
- Framework-to-practice labs that tie abstract clauses to tickets and change records.
- Simulation rounds with rotating leads and written feedback on tone, not just findings.
- Executive briefing drills with timers, dissent capture, and bounded mitigation language.
Member identity
A shared bench for people who care how assurance sounds in the room
- • You rehearse language before steering forums, not after.
- • You trade facilitation duties so ownership spreads beyond one lead.
- • You keep drafts inside office hours until they feel defensible.
Membership is less about badges and more about belonging to a serious circle that practices calm critique. We welcome assurance partners, IT governance leads, and operators who want structured rehearsal without performative urgency.
Shared identity here means you recognize each other’s cadence: how someone pauses before naming a dependency, how another asks for the ticket ID instead of the story. That mutual recognition is what makes the community durable when release pressure returns Monday morning.
Event calendar
Pick a rhythm: online studio nights or Seoul meetups
Tabs keep the tone friendly—online blocks favor deep work and chat moderation, while local meetups favor whiteboards and walking distance snacks. Both tracks stay opinionated and small.
- June 6 — Async critique window for ISO mapping drafts (UTC+9 evening block).
- June 13 — Fishbowl alumni Q&A on vendor questionnaires with live chat moderation.
- June 20 — Office hours for cohort facilitators swapping facilitation roles mid-program.
- June 27 — Closed-door rehearsal for steering briefings with timer drills.
Press mentions
Momentum, told as a slow build
- 2023 — Seoul Tech Weekly noted our facilitation style for cross-functional audit readiness sessions.
- 2024 — APAC Governance Quarterly cited our vendor rehearsal labs as unusually blunt about procurement reality.
- 2025 — Busan Digital Policy Salon interviewed alumni on how office hours changed their briefing tone.
- 2026 — Learning Guild Podcast featured our admissions lead on cohort curation without artificial scarcity.
We list mentions chronologically because the story is steadiness, not hype cycles. Each wave added a different lens—press, policy salons, podcasts—yet the throughline stayed the same: rehearse before the room gets loud.
Forum preview
Category hallways stay moderated and slow
The forum is not a megaphone; it behaves more like a quiet reading room with occasional raised hands. Category stewards pin orientation threads, remind people about redaction norms, and archive posts that drift into legal advice territory. Threads stay short on purpose—long debates move to office hours where tone can be coached live.
New members often start in “Evidence tone” where peers comment on anonymized paragraphs. “Vendor voice” focuses on declining boilerplate answers without sounding hostile. “Steering nerves” collects dry-run transcripts with time stamps so facilitators can suggest sharper handoffs.
Moderators rotate weekly to avoid hero fatigue, and each category page links to a full-view archive for alumni. Search is intentionally literal—no semantic tricks—so people trust what they find. When a thread goes unanswered for a few days, stewards nudge gently rather than bumping artificially.
- 1. “Footnotes that hide exceptions” — 14 replies
- 2. “Passive voice in findings” — 9 replies
- 3. “Screenshots vs. exports” — 21 replies
- 1. “SOC prose vs. artifacts” — 17 replies
- 2. “Subprocessor reopen cadence” — 11 replies
- 3. “Procurement-friendly nudges” — 8 replies
- 1. “Timer drills that felt rude” — 13 replies
- 2. “When CFOs interrupt” — 19 replies
- 3. “Handoff lines that work” — 6 replies
Partners & alumni employers