kanban_skill

Overview

This skill helps teams visualize and optimize workflow using Kanban boards to limit work-in-progress (WIP) and improve delivery flow. It guides setting WIP limits, identifying bottlenecks, and running continuous improvement experiments. The outcome is more predictable delivery, reduced cycle times, and clearer team priorities.

How this skill works

I map your current workflow into board columns, set sensible WIP limits, and collect basic metrics (lead time, cycle time, throughput). I then analyze where work accumulates, recommend targeted actions to relieve bottlenecks, and propose experiments to validate improvements. Regular feedback loops and explicit policies ensure changes stick and evolve over time.

When to use it

• Managing team work and task prioritization across stages
• Identifying and resolving recurring bottlenecks
• Improving delivery predictability and reducing cycle time
• Balancing team capacity with incoming demand
• Implementing continuous improvement without major process overhaul

Best practices

• Start with the existing process; change incrementally and measure impact
• Make WIP limits visible and enforce them; adjust based on observed flow
• Track lead time, cycle time, throughput and review trends regularly
• Define explicit entry/exit criteria for each stage to reduce ambiguity
• Use daily board reviews and periodic retrospectives to surface improvements

Example use cases

• Software team reduces average delivery time by lowering WIP and swarming blocked items
• Content team discovers a design bottleneck and builds templates to cut handoffs
• Support operations visualizes hidden work and sets WIP limits to improve response time
• Product teams run short experiments (change batch size or WIP) and measure throughput changes