What Completion Means
Most corporate training defines completion as watched the videos, passed the quiz, collected the certificate. This program does not. Nobody's job improves because a progress bar reached 100% — and your company is not paying for watch time. Completion here means one thing: AI is measurably improving real workflows, with named owners, and the evidence exists to prove it.
This lesson defines that evidence up front, so every participant, manager, and sponsor is measuring the same thing from day one.
The three artifacts
Every participant produces three concrete things. They are built inside the sessions — not as extra homework — and each one is checked against a published standard:
| Artifact | Built in | It exists when |
|---|---|---|
| A tested Claude Project | Phase 1 | A colleague can use it cold and get a result that meets its quality bar |
| A department workflow prototype | Phase 2 | It runs on real inputs, has a recorded baseline, and has a named owner |
| A capstone in controlled release | Phase 3 | It passed the go-live gate and its 30-day review is on the calendar |
The lesson checkpoints — Ready to move on and Definition of done — are the gates between artifacts. They are self-checks with teeth: facilitators verify them by looking at what you built, not by asking what you remember. The exam, in other words, is your workflow.
The measurement spine
Every workflow in this program carries four numbers, introduced in the lessons where you create them:
- A baseline — the before-number (time, volume, rework, error rate), recorded before anything launches.
- A target sentence — "For [user], improve [workflow] from [baseline] to [target] while preserving [quality or control]."
- A balanced scorecard — use, outcome, quality, risk, and experience, tracked together so one flattering metric cannot hide a problem.
- A 30-day review with a stop condition — a scheduled decision to expand, revise, or kill, agreed before launch.
Northstar's support team makes it concrete: baseline 25 minutes per first response and a 12% reopen rate; target under 10 minutes with the escalation rate preserved; scorecard reviewed at day 30. That is what a completed outcome looks like — a sentence a CFO can audit, not an adoption percentage.
What the sponsor should see
- Day 1: every department has a bounded workflow candidate and a baseline plan.
- Mid-program: working prototypes with owners; the first honest scorecards, including the failures — a workflow stopped by its own stop condition is the process working.
- Day 30 after capstone: measured deltas against baselines on the piloted workflows, plus a decision log: expanded, revised, or stopped, each with evidence.
Just as important is what we do not promise: no "transformation," no company-wide automation in week six, no metric theater. A small portfolio of workflows with proven deltas beats forty demos — and it is what compounds in Phase 4.
Ready to move on
You can name the three artifacts, the four numbers every workflow carries, and what your sponsor should be shown at day 30 — before the first Foundations lesson begins.