Compression as a method
A method that keeps showing up across the lab's projects, often unannounced: compression. Take a messy thing, cut it down, force a choice.
Narrative by Design is the most explicit case. The workshop's center is a sequence: paragraph → sentence → single word. Each step strips something out and forces the student to decide what to keep. The word at the end isn't a brand; it's a decision tool, and the compression is the exercise.
The Career Design Lab does the same thing in its OneWord tool, but the surrounding sequence is six tools long. Identity Mapping Studio starts wide: every experience, sorted across four dimensions. By the time the program reaches OneWord, the cohort has been compressing for weeks. The single word is the last act of a long pull-down.
Threshold inherits compression from somewhere else entirely: architectural studio critique. A studio crit is itself a compression exercise, five minutes to defend three months of work, which means deciding which two ideas are the project. Threshold ports that move from design education to career deliberation. The same move, applied in a different domain.
The shared structure is worth naming. In each case, compression is forced prioritization with a witness. The student would not, on their own, decide that this experience matters more than that one. The deadline (90 minutes, one card, one word) does the deciding for them. They produce, then defend, then re-do.
The card-sort tools that recur in the lab (Knowdell Career Values, CliftonStrengths, Motivated Skills, all in NBD) are also compression, choose your top 10, then your top 5, then your top 3. Same shape, different surface. Maybe compression is the lab's actual core method, with everything else being a domain-specific application of it.
Open thread. The pair-witness piece keeps coming up. Solo compression produces abstractions that sound impressive and mean nothing; compression in pairs produces specific, often uncomfortable, language. The peer is doing some work the format alone can't do. Next term in CDL the plan is to run the same compression exercise in solo and in pairs, in adjacent sessions, and read the written outputs side by side. If the difference is real, the practical implication is that compression tools shouldn't be built as solo apps.