How Motion Core ships a cohort
We alternate focused live blocks with async labs so platform engineers can keep shipping while learning. Each week ends with a mentor review that scores artifacts, not vibes.
Before / after the desk
Before
- Heroics rewarded; quiet prevention invisible.
- Dashboards sprawl; ownership for signals fuzzy.
- Runbooks stale; rollbacks narrated in chat only.
After
- Drills produce dated artifacts tied to services.
- SLIs mapped to journeys with named owners.
- Runbooks include verification gates and rollback cards.
Six beats inside a block
01
Anchor
Pick the service graph slice and paging story for the block.
02
Model
Mentors demo patterns with sanitized data from similar stacks.
03
Build
Async labs apply templates to your repos with review threads.
04
Score
Rubric feedback on clarity, safety, and measurability.
05
Rehearse
Micro-drills or tabletop bridges with observer notes.
06
Ship
Merge artifacts into your internal wiki with freshness owners.