Part 3 workflow/SOP progression. Course path note: Part 3 workshop page for enrolled learners.
Part 3 | Practice workshop
Break the workflow into ordered steps with purpose, actor, input used, output produced, and review/stop point.
A teammate understands the workflow input and output but asks what actually happens in the middle.
The trap is writing vague phases. D64 breaks the workflow into concrete steps, decision points, evidence checks, and stop rules.
“Steps: gather information, generate summary, review.”
The weak version contains gather information, generate summary, review, no stop rule.
A concrete action.
Where a human chooses.
When the workflow must not continue.
Use this rule before filling the build table. The goal is a decision-ready artifact, not a broad summary.
A concrete action.
Where a human chooses.
When the workflow must not continue.
The input/output contract is clear, but the team still runs the work from memory. The worker breaks it into operational steps without making a bloated SOP.
Break the workflow into ordered steps with purpose, actor, input used, output produced, and review/stop point.
Writing a high-level checklist that hides who does what and where the workflow can stop.
Core: 3 rows; Deep: improve the same 3 rows with stronger evidence, limits, and stop rules. Each step must show actor, input, output, timing/review signal, and exception/stop detail.
Timing/exception requirement: Each step must expose timing/review signal and exception/stop detail; do not bury this inside generic step language.
Previous artifact: D63 workflow_io_definition.md
Next artifact: D65 handoff_spec.md
Learning checkpoint: Keep the handoff useful to the next lesson by naming evidence, limitation, owner, and stop rule.
This page keeps Day 64 connected to the surrounding course path. Use the previous artifact as working input, produce today's artifact, and hand it to the next lesson with limitations visible.
A teammate says, 'I check accounts and send a note.' Repair it into collect accounts, verify renewal dates, tag risk, draft summary, confirm owner, send. The hidden decision is whether risk is evidence-backed or needs review.
Find the step where judgment changes the path. If no human decision is named, the process map is only a checklist.
Use these cards before the wide table so the example does not depend on horizontal scrolling.
Messy process to ordered steps
Find the step where judgment changes the path. If no human decision is named, the process map is only a checklist.
| No. | Step no. | Step name | Actor | Input used | Action | Output produced | Review / stop signal | D65 handoff need |
|---|---|---|---|---|---|---|---|---|
1 | 1 | Collect source packet | Sales ops worker | CRM risk fields, account notes, renewal date | Pull current source rows into one view | Source packet | Stop if renewal date or latest note missing | Hand source packet to verification step owner |
Core: 3 rows; Deep: improve the same 3 rows with stronger evidence, limits, and stop rules. Each step must show actor, input, output, timing/review signal, and exception/stop detail. Blank required fields create export warnings.
| No. | Step no. | Step name | Actor | Input used | Action | Output produced | Review / stop signal | D65 handoff need |
|---|---|---|---|---|---|---|---|---|
| 1 | ||||||||
| 2 | ||||||||
| 3 |
Use this pass to find the row that would make the artifact look ready while hiding evidence gaps, unclear owner decision, missing exception, or weak handoff.
Weak row: Step list: gather, generate, review.
Repair move: Add exact action, owner, evidence check, decision point, and stop rule.
Better row: Step 1 check CRM freshness; Step 2 draft risk reason from source; Step 3 manager approves; stop if source older than 30 days.
Choose the row you would be comfortable carrying into the next day.
Choose the row most likely to fail before AI use.
Sentence starter: The weak row is weak because ___. I will repair it by adding ___ before using AI.
This file is today’s work receipt. It should show the exact decision or handoff that the next day can use, not just that you filled a table.
What this artifact proves: This file proves the learner can break a workflow into executable steps with decision and stop rules.
Weak export: Step list: gather, generate, review.
Good export: Step 1 check CRM freshness; Step 2 draft risk reason from source; Step 3 manager approves; stop if source older than 30 days.
Click Generate Markdown to create step_breakdown.md.
Built from your course work.