I work with a lot of organizations and it's really really important to have good data and often we're hearing about it from the product point of view. "I want adoptive adoption data, I want usage data, I want cycle time data, I want response time data, I want to know how long it took to make that cookie and how long it took to eat it and how long it spent in the packet", right. Data everywhere, this is really really important because that gives us transparency about the effectiveness of the product, whether it fits the client's needs or not. But how effective we are as an organization at delivering those cookies, we need the same data. So we need total transparency on our delivery organization as much as we need total transparency around the product and how the product is used. It's vital that you invest in that because that will help you see what's going on. That will help you see where your bottlenecks are. The whole reason we do value stream mapping is to actually understand where these things are and you shouldn't just do it once. Often I'd see an organization they'll do value stream mapping at the beginning of the transformation and then that's done. Three years later they haven't looked at their value streams because it's done. Everything in agile is not done. You're never done. It's never over. It's not complete. You're never at the very best you can be because there's always something else you can try. So collect the data, analyze the data, take the time away from the noise, take the time away from the chaos and look, can I optimize my development value stream, even can I optimize my product value stream but do it on a regular basis.