How it works
The flow is deliberately linear on paper but overlaps in practice so reading, building, and review never drift too far apart.
-
01 — Intake calibration
You confirm tooling, timezone anchor, and baseline skills. Learner success issues lab credentials and the documentation pack for week zero.
-
02 — Build sprints
Each sprint ends with a tangible artifact: flow package, portal slice, integration matrix, or handoff note. Rubrics precede due dates so expectations stay visible.
-
03 — Mentor review windows
Mentors batch feedback twice weekly. Late submissions still receive notes, but may miss the live clarification block.
-
04 — Defense-ready packaging
Final weeks compress documentation into client-tone bundles: risk language, rollback stories, and walkthrough scripts suitable for delivery rooms.
Before
Slides-heavy training with vague “hands-on day” promises.
After
Artifact-first cadence with mentor markup tied to named programs.