Package the Workflow as a Reusable Template
Unit ID: PAW-M12-U05 Estimated active time: 25-30 minutes
The test of the whole course
Hand the package to a colleague who was not involved. If they can run the task without asking you anything, it is finished.
If they have to ask, whatever they asked about is the missing piece.
What goes in the package
WORKFLOW TEMPLATE — (task name) v__ (date) owner: (name)
1 WHEN TO USE THIS and when not to
2 CANVAS the filled design canvas
3 PROMPT current version, with reason notes on odd rules
4 OUTPUT SPEC format and required sections
5 RUBRIC the criteria used to score
6 WORKFLOW MAP eight steps, with owners and times
7 GATES privacy, review, stop conditions, approver
8 RECORD FORMAT the handoff note
9 KNOWN FAILURES what goes wrong, and the guard
10 IMPROVEMENT LOG what changed, when, and why
11 RETIRE WHEN the condition that makes this obsoleteWrite "when not to use this"
It is the most-skipped section and the most useful.
Someone will apply your template to a task it was not built for. Two lines saying what it does not cover prevents that better than any amount of instruction on what it does.
Hand it over and watch
Give it to a colleague and let them run it once without helping.
Note every question they ask and every place they hesitate. Fix those, and only those — resist rewriting the parts that worked.
Then use it, and keep the log
A template is not finished when it is written. It is finished when it has survived four or five real uses with only small changes.
Keep the improvement log running. That is what stops it drifting into a set of rules nobody remembers the reason for.
What you have at the end
A canvas, a versioned prompt, a rubric, a workflow map, a gate sheet, a record format, and a log — for a task you actually do.
That is the portfolio this course promised, and it is the thing worth keeping. The individual prompt is the least durable part of it.