Lesson 12 · Activity 01

Scope & Map Your Pipeline

Every good pipeline starts with a boring, frequent task and a clear "done." Here you’ll pick your bottleneck and map the stages — this becomes the backbone of your capstone.

Work through it

0 of 4 done

Name the bottleneck (the recurring task that eats your time).
Define the outcome — what "done" looks like.
Map the stages your pipeline needs (drop the ones it doesn’t).
Note what data it touches and what must be de-identified.

Your bottleneck

The outcome ("done" looks like…)

Map your stages

Fill in only the stages your pipeline needs. Saved on this device.

Stage	What happens in your pipeline (or "skip")
Gather / Research
Extract
Connect / Analyze
Assemble
Verify
Sign off
Deliver

Data touched / what to de-identify

Saved automatically on this device.

Reveal a worked exemplar

Bottleneck: hand-compiling a weekly program digest. Outcome: one accessible post with this week’s updates and de-identified success metrics.

Stages: Gather (scoped scan of program pages, L8) → Extract (key updates into a table, L9) → Analyze (de-identified metrics in a sandbox, L10) → Assemble (standard template) → Verify (recompute one number) → Sign off (you approve) → Deliver (WCAG-checked post). De-identify: the metrics export lists individual students — reduce to aggregate counts before analysis.

Takeaway: a strong capstone target is narrow and recurring. If you can’t state the outcome in one sentence, the scope is still too big.