People sign up for a course and expect to receive knowledge. People sign up for a workshop and, in the version we run, help build something that did not exist before they walked in.
Those are different transactions. Confusing them is the fastest way for both sides to feel let down.
What a course is
A course is a curriculum. Someone decided in advance what you need to know, sequenced it, filmed it or wrote it down, and now you sit with it. The best courses are excellent (Class E). Coursera, edX, and the university tradition they inherit have moved a lot of knowledge into more hands than any prior model (Class E).
A course optimizes for scalable transmission. One expert, many learners, a fixed body of material. The trade is intentional: you get depth and structure, and you give up the chance to change what is being taught while it is being taught.
What an IamHITL workshop is
A workshop, in the version we run, is a small group (typically six to twelve) working alongside a facilitator on a real artifact the group actually needs. The facilitator brings the method. The participants bring the problem, the context, and the constraints only they can see.
The output is not "you now know a thing." The output is a working artifact, a documented decision, or a running piece of infrastructure that carries your fingerprints, not a template stamped with your name.
Human-in-the-loop is not a slogan here. It is the structural claim: the person doing the work stays inside the decision at every step, and the facilitator's job is to keep the loop closed, not to hand you a finished thing on the way out.
What that looks like in practice
A course session runs to a script (Class C). A workshop session has a starting artifact, an intended shift, and a stopping condition, and inside those three fences the room decides where the time goes.
A course grades your comprehension. A workshop asks a harder question: did the artifact get better, and can you show why? Both answers should be defensible before you leave the room.
A course scales by adding students. A workshop scales by getting sharper, running more of them, and by the artifacts and receipts previous groups leave behind for the next one.
What a workshop is not
It is not therapy, and it is not a clinical intervention of any kind. We are trauma-informed in posture (we do not push, we do not shame, we do not rush), and we are explicit that we are not treating anything.
It is not a certification. You leave with an artifact and a set of notes, not a credential someone else recognizes.
It is not a guarantee that your specific problem gets solved in the time we have. Some do. Some become clearly-scoped follow-on work. Some reveal that the real problem is upstream of what you brought in, and that finding alone is worth the day (Class U, this is the part we cannot promise in advance).
Why the distinction matters
If you show up to a workshop expecting a course, you will be frustrated that no one told you what to think.
If you show up to a course expecting a workshop, you will be frustrated that no one listened to what you actually needed.
Both formats are useful. Neither is a fraud when it is correctly labeled. Our contribution to that clarity is small and specific: we call the thing we run a workshop, and we say what it does and does not do, on the page, before you book.
How to know which one you want
Pick a course if you want structured exposure to a body of knowledge you do not yet have, on someone else's schedule, at a lower price point.
Pick a workshop if you have a specific artifact, decision, or system that needs to move, and you would rather work on the real thing with a facilitator in the room than read about the general case alone.
Read next
- The workshop page, where the format, cadence, price, and what you take home are laid out plainly.
- Workshop as a shared build, on why the artifact belongs to the group and not to the facilitator.
- What you take home from a workshop, a specific list of the things that leave with you.