Kanban is Nice to Humans

Boyd Hemphill argues that a kanban board offers far more than a simple list of tasks, and that its value depends on the rituals built around it. He frames the core problem for security teams as constant reaction: urgent interrupts pull people off planned work, and vague task definitions cause items to stall or move backward across the board.

The talk walks through a sample board for a small application security and cloud team. Reading it statically exposes unclear done criteria, oversized tasks and ambiguous dates, while watching cards move reveals stalled reviews and external dependencies. Hemphill replaces round-the-room status updates with a short task-by-task stand-up, where the lead asks what each in-progress item needs and teammates help unblock it. Interrupts get their own swim lane so their load becomes visible, and work discussions move out of direct messages into team channels.

A weekly meeting uses a lean-coffee style vote to pick topics, and decisions become tickets prioritized in the backlog rather than meeting notes. Improvement items from stand-ups and incident retrospectives flow through the same board, so they compete for capacity like any other work. The practical takeaways: make work visible, cap work in progress, and use regular rituals to balance interrupts against planned improvements.