DevTech Engine

Process

How we run cohorts without losing the plot

A transparent sequence so your PMO, marketing, and partner leads know what happens before plane tickets enter the chat.

  1. 01 — Intake diagnostics

    Short async survey plus a 30-minute alignment call. We confirm data access, legal redlines, and which artifacts must exist on day one.

  2. 02 — Pre-work packets

    Reading, anonymized examples, and a Miro board seeded with your categories — nothing graded, but skipping it weakens critiques.

  3. 03 — Live intensives

    Facilitated drills, simulations, and mentor scoring. Phones away during critique blocks; breaks are real breaks.

  4. 04 — Artifact lock

    Teams freeze v1 of deliverables, run a cross-functional readout, and log decisions in a shared changelog we template for you.

  5. 05 — Office hours arc

    Three weeks of async mentor access for clarifications — not unlimited rework, but enough to catch handoff bugs.

  6. 06 — Graduation handoff

    PDF + Notion export, exec summary slide, and a retro survey that feeds the next cohort’s curriculum tweaks.

Before / after the sequence

Before

  • Launch decks with unnamed owners
  • Channel plans that list every surface
  • Critiques ending in “make it punchier”

After

  • RACI snapshots attached to each artifact
  • Channel atlas with proof depth tags
  • Critiques tied to rubric rows and dates