How we teach
We optimize for artifacts your org can paste into existing rituals — not theatrical reveals on the last day.
-
01 — Pre-flight packet
You receive a short checklist: sample segments, current lifecycle map, and three examples of “stuck” contacts. Missing pieces become explicit risks rather than silent blanks.
-
02 — Facilitated collisions
Live sessions mix sketching, small-group reads, and mentor critiques. We intentionally surface disagreements early so they show up in diagrams instead of midnight Slack threads.
-
03 — Async tightening
Between sessions, mentors annotate your files asynchronously. You see pencil marks, not vague praise, pointing to the next edit.
-
04 — Receipt bundle
The cohort closes with a zipped bundle: diagrams, rubrics, RACI updates, and a dated changelog. Optional office hours extend for two weeks for clarifying questions only — not new scope.
Before / after ritual
Before
- Segments debated verbally without shared drawings
- Approvals tracked in ad-hoc chat threads
- Creative reviews subjective and exhausting
After
- Geometry-first sketches attached to program decks
- Governance console routes risky edits
- Rubric language shortens ESP QA loops