Two ways to find out what a stalled AI rollout is actually costing you
ABOUT THIS TOOL
I built this after noticing a pattern: managers absorb new, invisible work every time a tool or process changes, and almost nobody has a structured way to make that visible. Nothing gets fixed because nothing gets counted.
There are two people who need to count it, and they need different things. A leader needs a number and a decision. A manager needs a way to raise it without sounding like a complaint. So this tool has two paths. Take the one that matches where you sit.
Both take about ten minutes. Both are built to be filled in with your own situation, because headcount, tools, and how far the rollout got are different everywhere and a generic answer would be useless.
You own a budget, a P&L, or a function. You bought or inherited an AI tool. Usage is lower than you expected and you are not sure what that is costing you.
What you will have at the end: a defensible estimate of what the stall is costing per year, and one clear first move.
The cost does not land evenly, and this is the thing most leaders get wrong. Review burden follows adoption. The managers carrying the most invisible work are the ones whose teams actually took up the tool, not the ones whose teams ignored it.
Fill in:
That last number is your carrier count. It is usually much smaller than your total manager count, and that is the point.
Ask three to five of your carriers one question. Ask it in a way that makes an honest answer safe, because the honest answer sounds like a complaint and they know it.
"Since we rolled this out, roughly how many hours a week do you spend checking AI-drafted work before it goes out, or answering questions about whether the output is right? I am not looking for a problem. I am trying to find out whether we created work nobody accounted for."