Building the wrong thing, faster.
I spent six months inside an insurtech company where AI agents were writing most of the code. We moved fast, and for a while I couldn’t tell if the work we were doing was creating any value for the company.
This is the part nobody warns you about, and the short version of how we found out.
So nobody treats it like one. You don’t see what it costs until the bill arrives at the end of the month, and by then the capacity is already spent.
Somebody still has to decide what’s worth building. Somebody still has to read everything the agents hand back. Neither of those got faster.
We didn’t actually know until we tried to align all of our work to the company’s objectives. One in five items aligned with the strategy, and half of that work was fixing bugs.
The thing I didn’t expect. The same agents that made it easy to spend the capacity turned out to be the fastest way to see where it had gone.
Every month or so I send out a real case study, one small thing you can put to work that week, whatever I've written lately, and where I'll be teaching and speaking next. That's it, and you can leave whenever you want.
Thanks! The next one goes out when I've got something worth sending.
Email info@lilagilemonster.com and I'll add you by hand.
The flow and forecasting discipline underneath this is what I teach in my accredited ProKanban.org courses.
See upcoming classes →