Matching Structure to Task Type

Definition

A single, uniform value stream (BACKLOG → DOING → DONE) works well for typical discrete tasks, but several common categories of work don't fit that shape and will clog or misrepresent it if forced in: recurring daily tasks, large multi-stage projects, genuine emergencies, and small unimportant-but-accumulating chores. Rather than prescribing one board layout, the book treats the value stream itself as a variable to be redesigned per task category — "there are endless ways to visualize, interact with, and learn from your work" — while keeping the underlying discipline (visualize it, limit what's in flight) intact.

In the Book

Appendix A develops this through Jessica, a single mother juggling two jobs, a professional certification, and triathlon training, whose board combines several purpose-built patterns rather than one generic list. The Sequestering Approach pulls recurring tasks (daily calorie count, vitamins, workouts) out of the main WIP into their own checkbox-style tracker, because turning them into fifteen ordinary sticky notes a week would be "waste." The Large Project Approach collapses a months-long effort (writing a book, training for a triathlon) into a single "roll-up" card in the main flow while tracking its actual sub-stages in a separate swim lane beneath it. The Emergency Response Approach, illustrated by the seven tornadoes that leveled the author's hometown of Grand Island, Nebraska, replaces the standard columns with states built for tasks that can't be finished serially — BEGUN, ASSEMBLING, ASSEMBLED, ACTIVE, COMPLETE — because a disaster forces "controlled multitasking" that a normal WIP limit would only misrepresent. The Time Capsule Approach handles the buildup of many small, easy-to-defer tasks by batch-processing them through a stripped-down READY → DOING → DONE sequence in one sitting, "sweating out" the backlog before it spawns a real crisis. The Balanced Throughput Approach front-loads a fixed quota of small tasks before larger ones each day, deliberately capping both categories so quantity of small wins never substitutes for progress on what matters.

Why It Matters

A workflow system that forces every kind of work through the same shape will systematically misrepresent some of it — burying repetitive tasks in noise, hiding a long project's real progress behind one static card, or making a genuine emergency look like a WIP-limit violation instead of the different animal it is. This concept generalizes past personal task boards: any process design that assumes one uniform unit of work will eventually meet a category — a recurring obligation, a multi-year initiative, a crisis, a pile of small debts — that needs its own state model, not a forced fit into the default one. The transferable move is recognizing which shape a given category of work actually has before choosing how to track it.