A few years ago I took over the agile practice of a global engineering structure, a direct-to-consumer operation with an aggressive roadmap for the year, that had no way to answer the most basic management question: are we keeping up? This essay is about how I mapped that structure, designed four flow KPIs (Workload, Team Overhead, Productivity, and Efficiency) and implemented the process that kept them alive. It’s a field report for Service Delivery Managers, enterprise agilists, and any manager or specialist who needs to build visibility where today there is only opinion - and to land practices in a structure that resists them.

You know the scene. A 47-page contract arrives for approval, with annexes A through F and clauses referencing other clauses. Or a 40-slide deck where the only piece of information that matters - the project is going to be late - sits buried on slide 31, behind three “synergy” charts. We start reading with good intentions. By the third paragraph, our eyes glaze over. We scroll to the bottom, sign, approve, move on with the day.

That is a fair question, but is it really what bothers us?

It seems necessary to investigate what precedes this doubt in our minds. Because is that really all we want to know?

Delegating to AI the homework, the understanding of a long email thread, or the creation of a new algorithm… It kind of feels like a form of cheating, right? At the end of the day, was it me who solved the problem or was it the AI? Where is my ability in all this? What did I learn from it?