Facilitator & Program-Owner One-Pager

Status: How to run this curriculum without turning it back into theater.

The only success measure that matters

Decision quality and owned outcomes. Not seats filled, not modules completed, not satisfaction scores, not certificates issued. If the people who went through the program do not decide better and own their outcomes when something goes wrong, the program failed — regardless of how it looked on the dashboard.

How to use the verification rubrics

The Verification Rubrics are the standard for every artifact. You are the enforcement mechanism.

• Score against the six criteria: Clarity, Grounding, Accountability, Verification, Uncertainty, Decision quality.
• Passing means at least Acceptable on every row and Strong on Accountability and Verification.
• Anything less is incomplete — send it back, once, with the specific criterion named.
• Review the artifact, not the person. Name the gap; do not grade the personality.

How to treat Core Judgment as a hard gate

Core Judgment is required. That is not a scheduling suggestion.

• No one enters an Applied Pack without passing the Core Judgment gate.
• "They need the pack for a project next week" is not a reason. The pack assumes Core; skipping it means the pack's content is wasted on them.
• If a senior person wants to skip it, the answer is the same. The gate exists precisely for the people whose mistakes cost the most.

How to keep Applied Packs modular

Do not force all of them.

• Packs are chosen by the decision the person actually needs to make next — one, sometimes two, never all six at once.
• The cohort should be small enough that artifacts get real review. Thirty people through five packs is attendance; eight people through one pack is a program.
• Capture real examples and failure cases from each cohort. Those become the enablement material for the next one.

How to handle evidence review without creating bureaucracy

Evidence review is the program. Keep it light and keep it honest.

• Sample, do not rubber-stamp. Review every artifact at the Core gate; sample with named criteria at pack gates.
• A review board that meets monthly is a delay with a calendar. One named reviewer per gate, with the rubrics, is enough.
• "I do not have enough evidence" is a complete answer at any gate. Accept it and move on. Pretending otherwise is the real failure mode.

What to do when someone wants to skip Core or treat completion as competence

The script is short:

• "Core is required." No debate about the person; the pack assumes the prerequisite. Skipping it wastes their time and yours.
• "Completion is not capability." A certificate proves presence. The gate proves judgment. If they want the certificate and not the gate, they want the theater, and the program does not sell that.

The implementation phases

Prepare → Core → Applied Packs → Governance → Enablement → Steady State.

1. Prepare (1–2 weeks) — name the owner, make Core required, set the evidence standard, pick the first pack.
2. Core Judgment (3–5 weeks) — everyone who influences AI decisions goes through it. No one advances without the gate.
3. Applied Packs (4–8 weeks) — one or two packs matched to real needs, small cohorts, artifacts reviewed properly.
4. Governance (parallel or after) — inventory, classify, own, contract, measure, review. See the governance reference.
5. Enablement (ongoing) — grow capability beyond the first cohort. Durable judgment stable; tool content as replaceable overlays.
6. Steady State — new people pass Core before significant AI responsibility. The measure stays decision quality and owned outcomes, not headcount trained.

See the Implementation Timeline for the full rollout.