At the beginning they were ignoring measures, just looking at odd graphs.
But one day they had turn-over in their team, and as the new joiners were being trained, and the CFD showed immediately a bottleneck.
We experienced most of the behavioral changes listed above and our cycle time was reducing.
But we reached a limit: we were depending on a technical support team.
They were not focusing on their lead time, they used a tasks management tool focusing on who is responsible for what and managing queues without limit or flow measurements.
We were also not satisfied with the way we all were working and coordinating our clients.
Thus one day we decided to automatically measure their Cumulative Flow Diagram (CFD) and make it visible.
My goal here is not to cover all those patterns again, which mainly are still a work in progress, but to share a specific story about measuring flow.
In 2010-2011, I was in charge of a software development team located in Paris and Mumbai.