How to Calculate Kanban WIP Limits in the AI Age
Starting numbers for active work and queues, covering solo and multiplayer spec-driven development, pod topology, flow buffers, and replenishment cadence.
Starting numbers for active work and queues, covering solo and multiplayer spec-driven development, pod topology, flow buffers, and replenishment cadence.
The best time to solve a feature adoption problem is before development. Talk about the user's project, look for real pull, and don't build on polite interest.
An AI coaching prompt from my "Product Orientation Through LPM" talk: pressure-test one real initiative, find the real gap, and get one experiment to run.
Most organizations execute projects well and realize value poorly. Reframe discovery as de-risking — plus a decision rule and an interactive tool to try it.
Value and risk are correlated almost everywhere. You cannot remove the risk that comes with real value, but you can de-risk it efficiently. That is agile.
When AI coding raises the arrival rate of pull requests, telling reviewers to work faster is the wrong move. Fix reviewability and end-to-end flow instead.