The questions people actually ask before enrolling in SLOP1241, answered the way we'd answer them in person rather than in the safe, hedged voice most FAQ pages default to.
Frequently asked questions#
What background does this course actually assume?#
Less than the domain list makes it look like. You don’t need to know software, construction, aerospace or law going in — each week teaches you enough of its own domain to follow the argument, not enough to practise it. What the course does assume is that you’ve personally watched something get 90% finished and then die there — yours or someone else’s — because if you haven’t, week one’s argument is abstract instead of familiar, and the rest of the semester is built on that recognition landing.
Why does the course jump to a completely different domain every week#
instead of picking one and going deep?
Because the claim being tested is that this pattern shows up everywhere, and the only way to actually test that is to keep changing the domain and checking whether the pattern still holds. A software-only course could teach you that shipped code rots at the edges; it couldn’t tell you whether that’s a fact about software or a fact about finishing anything at all. Twelve domains is the minimum needed to make that distinction honestly, and week 8 and week 11 exist specifically to find the places where a single fixed explanation stops working.
What does the assessment actually involve, concretely?#
You apply the framework to a real unfinished thing, not summarise the lectures back at us. That thing can be yours (a project you’ve been meaning to finish) or one you go find (someone else’s unshipped feature, an unfinished building, a stalled thesis) — but it has to be real, specific, and still unfinished when you pick it, because the whole point is diagnosing an actual last mile rather than describing a hypothetical one. See the Assessment pages for the two graded pieces and how each is marked.
Isn’t this just repackaged productivity advice about not procrastinating?#
No, and the distinction matters enough to spell out. Productivity advice is about you finishing faster. This course is about why the last stretch of almost anything costs more than the rest put together — a claim about the structure of the work, not about your discipline. Week 5’s filing deadline and week 9’s certificate of occupancy don’t get easier if you try harder; they’re gated by an external threshold that doesn’t care how motivated you are. If the fix this course offered was “manage your time better,” half the weeks wouldn’t need to exist.
Do I need to already have an unfinished project of my own to take the#
course?
Not to start it — but you’ll need one, or a good candidate for one, by the time the assessment is due, so it’s worth keeping an eye out from week one rather than scrambling in week eleven. If nothing comes to mind immediately, that’s rarer than it sounds, not a sign you’re not qualified: most people are sitting on at least one 90%-done thing they’ve stopped mentioning.
Week 11 argues against the course’s own thesis — is that a mistake?#
No, it’s the week we take the most seriously. Every other week says finishing costs more than you think, so budget for it. Week 11 says that advice has a limit, and past that limit the same finishing instinct starts subtracting value instead of adding it. A course that spent twelve weeks insisting “always finish more” without ever testing where that breaks would be worse evidence for its own argument, not better — so week 11 is there on purpose, not as a hedge.
Why does only week 1 get a slide deck, and not the rest?#
Week 1 is the one session that has to land as a live, presenter-led argument for the whole semester — everything after it leans on that framing being already in place. From week 2 on, each week’s argument lives on its own page next to that week’s interactive mechanic, which does something a slide deck can’t: let you drag a cost curve, click through a process diagram, or watch a target move away from you as you approach it. That’s a better way to argue “the last mile is expensive” than another slide would be.
Who is this course a bad fit for?#
Anyone hoping for a checklist of finishing habits, a project-management certification, or a guarantee that applying this framework will actually get their own unfinished thing shipped. This course diagnoses why the last mile is expensive in a given domain; it doesn’t promise to make yours cheap. If what you want is a fix rather than an argument, this isn’t that course.