 The next one is a large real-to-all organization. And this is kind of interesting, because back in 2013, this organization was the very first organization I actually did present IT for IT2. I didn't do much with it. I didn't actually stay with that company and work with them on a day-to-day basis. It was more or less presented it and walked away and did other things. They were pretty competent. And what I found out in 2015, end of 2015, was that they did some pretty miraculous things with IT for IT. They changed their entire operating model for their IT shop. So what I will show you is sort of what came out of that. What I learned, and they started to communicate to their vendors that they wanted their vendors to map their stuff to IT for IT. What is it for? Why is it there? Can you qualify that? And this is basically what they did. And they internalized it. Just similar to what Rick talked about earlier, they internalized it. And they created their own sort of view and branding for IT for IT. And you'll notice that build and acquire was changed. It used to be just build. They said, we don't want to just build our services. We want to acquire them too. And they added an executive direction layer, which they said, that's really their strategy process. And then their support layer, which are also very similar to what IT for IT describes. So they changed it around. They mapped it to what they actually are doing. And another piece of information about this, there's a little bit of feedback that did come in. While I was supporting, once in a while, I would get a call from this company. They would ask a few questions, Mark, what does this mean? Oh, I'll explain it to them. Or if I didn't know what that function meant or certain element of the standard meant, I would ask some of the peers, the folks that are in this room even, and say, hey, where is this function? Why isn't this represented in the standard and get some good answers? And some of that feedback in that dialogue, even though they're not here, they're not public, that feedback in that dialogue still came through me. And you'll see there were some changes made to the standard as a result. So some of the lesson learned is that we may not know the use cases that are happening now that the standard is out there in the wild. I think the best stories are still to be discovered, to be honest. But this was a very interesting one. And I think it took two years to see this result, but it shows you the value and how it got institutionalized within companies.