The Grey
Take one change that needs a sign-off. Not a typo fix, a real one that someone has to approve before it ships. Time it from the moment someone picks it up to the moment it’s done, and colour the bar by what was happening.
The yellow bit is the build. The grey is everything else: waiting for review, waiting for QA, waiting for a sign-off, waiting for the person who does the sign-off to come back from their holidays.
The yellow bit is what AI fixed. The build went from days to hours, and I’ve watched that happen in both of my worlds. The grey didn’t move an inch. If anything it got wider, because code got cheap to write and expensive to read. Review time is up at Whitespace and it’s up in my own work. The industry spent billions of dollars making the yellow bit smaller.
Here’s the part I can’t stop thinking about. I have one client at night that’s properly governed. Same factory, same models, same me. Their work moves at the governed team’s pace, not mine. So the AI isn’t what sets the speed.
The obvious reaction is to go after the grey with a stick: fewer approvals, fewer people, fewer meetings. That’s wrong too. Some of that grey is the only thing standing between a bug and someone’s worst day, and you should keep it on purpose.
So the real question is which grey to keep and which to bin, and how you decide for a thousand changes a week without a meeting about each one.
That’s Saturday, 11:30, Room 1B. It turns out to be two questions.