Measure Twice, Vibe Once.
In the software engineering models that most organizations adopted in the past few decades, product owners and product managers sat between the business teams and engineering teams. These product teams had many roles: organizing backlogs, prioritizing features, handling communications, and translating business requirements for development teams. But one subtle role that the product teams filled was managing KPIs. Many companies have adopted AI and vibe-coding tools that enable their business teams to innovate and automate without the organizational overhead of product teams and software engineering teams. While this reduced friction can lead to great outcomes, it can also lead to inefficiencies when decisions on what and how to automate aren’t made effectively. To effectively make these decisions, even vibe coders should measure KPIs. ...