Your Kanban Board Ends Too Early
Most Kanban boards stop at release, which quietly teaches teams that deployment is success. If you want impact, make outcome and impact visible in the flow.
Insights Topic
AI creates speed, not automatic value. Your operating model decides whether that speed becomes business impact.
Most AI initiatives are swimming in activity but starving for business results. Below, I’ve mapped out my core perspectives on how to resolve the operational bottlenecks that prevent AI from driving top-line or bottom-line value.
Start here · Cornerstone read
Most AI projects fail not because the models are wrong — but because the management operating system isn't built for high-uncertainty work. How agility principles change the odds.
Read the full articleWe are accelerating the wrong parts of the system. In engineering, we use AI to dramatically speed up the inner loop—writing code or drafting documents. The problem is that the downstream outer loop, where reviews, security validations, and integration happen, remains slow and unchanged.
When you push a faster inner loop into a constrained outer loop, you do not get more business throughput. Instead, you get "acceleration whiplash." Work piles up in queues, creating massive amounts of unreleased inventory. Realizing impact requires shifting focus from local developer productivity to end-to-end system flow.
AI Theater is what happens when organizations measure success through activity metrics. You will see dashboards boasting about the number of licenses purchased, workshops completed, or hackathons held. These are input metrics, and they create the illusion of progress without solving any actual customer or business friction.
Escaping this theater means shifting to outcome-oriented steering. We need to stop mandating tools top-down and start focusing on pull-based adoption. Teams should adopt AI capabilities because it demonstrably reduces their lead times or solves specific operational constraints.
Treating AI as a simple IT rollout is a fundamental mistake. Realizing value requires treating internal AI capabilities—and the organizational context surrounding them—as products. This means applying Lean Startup techniques, building in small incremental steps, and managing flow economics.
Start by identifying the actual constraint in your business, whether that is customer onboarding or sales enablement. Fund experiments in stages, releasing investment only as teams demonstrate sponsor-ready evidence of real value.
AI Theater is when an organization measures AI success by activity—such as seats allocated, prompts typed, or demos built—rather than actual business outcomes. It creates the appearance of progress without driving revenue, cost savings, or cycle-time improvements.
Measure AI value by tracking system-level outcomes: end-to-end cycle time, release frequency, change failure rates, and customer value indicators. Avoid local productivity metrics like lines of code generated, which ignore downstream review and testing bottlenecks.
Because value is constrained by the slowest part of the end-to-end stream. If engineering speeds up but product discovery, code reviews, deployment, or customer adoption remain slow, you simply pile up work-in-progress (WIP) and create longer queues, not faster value delivery.
Insights Database
Browse the complete archive of articles and case studies related to ai activity to impact.
Most Kanban boards stop at release, which quietly teaches teams that deployment is success. If you want impact, make outcome and impact visible in the flow.
Most of your scaling apparatus is now optional. Your first principles are not. A companion for leaders running SAFe while adopting AI-native, spec-driven development, and trying to tell the difference.
Is Scrum still relevant when agents write the code? Yes, and more than before, provided you are willing to customize it. A companion to the Scrum Guide walking the accountabilities, events, artifacts, and values for a team running an AI-native, spec-driven lifecycle.
A companion to the Kanban Guide for Scrum Teams for AI-native product teams. What changes in your Definition of Workflow, WIP limits, flow metrics, and Scrum events once agents do the building, and what happens to scaling when the old dependencies start dissolving.
Starting numbers for active work and queues, covering solo and multiplayer spec-driven development, pod topology, flow buffers, and replenishment cadence.
AI agents write code faster than ever, but the bottleneck moved to human decision latency and review capacity. Here is the operating system that closes it.
AI work pays off when it starts from a real business constraint, not a tool wishlist. Run a small test and check the problem is worth solving.
Most AI efforts start with tools and demos. Better to use product discovery to aim AI at a real business constraint and test the riskiest assumption first.
AI speeds up delivery and thins out team-level dependencies. Scaling framework mechanics become optional; flow and WIP first principles matter more.
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.
AI isn't killing Scrum. It's shrinking teams from cross-functional squads to 1-3 people — and that descaling collapses a lot of org complexity with it.
Why the rise of Forward Deployed Engineering is the next agility problem — and how to scale "unreasonable agility" without it eating itself.
Spec-driven development looks like a step backward if you read it as requirements theater. The better frame: the spec is a higher-level language for intent.
Claude's /goal feature lets agents work until a completion condition is met. Most examples are output-oriented: tests pass, backlog empties. Outcome is missing.
AI coding can make engineering dramatically faster. The business does not follow automatically — the constraint moves to deciding what is worth building.
Most AI efforts are still stuck in personal productivity. Zoetis CTO Kumar Venugopal on what it takes for AI to change the process itself.
Plenty of pilots, training, tools, and output but not enough business traction? The problem may not be AI. AI may be improving the wrong part of the system.
Spec-driven development can be a smarter way to steer AI coding agents, or waterfall with more tokens. The difference is whether the spec creates learning.
Moving from chatting with AI to unleashing agentic AI is not just a productivity boost. It changes leadership work — humans move up a level.
AI vibe coding gets frustrating inside the wrong operating system. It gets traction when the organization can turn experiments into business results.
Most AI portfolios suffer from the same disease: too many pilots, too many ideas, not enough kill criteria. Portfolio flow beats AI idea theater.
A conversation with Dave West at Scrum.org about the 95% AI failure rate and why organizations need a different management operating system for AI work.
95% of AI projects fail — not because the models are wrong, but because organizations run high-uncertainty AI work in project mode.
AI initiatives die in the proof-of-concept stage when run as fixed-scope projects. Clemens Adolphs and I unpack why AI work needs real product discovery.
Scattering AI initiatives without finding your bottleneck wastes effort. A Theory of Constraints lens helps you aim GenAI at the right problem first.
Adopting AI, Agile, or OKRs out of FOMO usually ends in JOMO. Five questions that tie any initiative to your most expensive problems first.
AI context — system prompts, knowledge bases, tool configs — is a product you keep discovering and improving. Product thinking applied to AI enablement.
AI tools promise to speed up product discovery — but do they? A close look at where AI actually helps, and where the bottleneck is still human judgment.
Practical patterns for using AI across the product development flywheel — from discovery and validation to faster build cycles and better feedback loops.
Every tech wave has a cart-before-the-horse phase. What product-led AI looks like instead: start with customer outcomes and explore problems before solutions.
GenAI is a classic VUCA challenge — high uncertainty, fast-moving, multi-disciplinary. How to steer AI investments without drowning in the hype.