I think you can't do a multi-workstream 
program, strategic or not, without the   different components understanding how their 
bodies of work impact one another and kind of   having these functions on the top to ensure that 
those conversations are happening. So often we're   only focused on the little box that I'm working 
on as a specialist across the platform. Like,   I'm just gonna do my piece of work and that's 
gonna be good. But when you get into these   multi-workstream programs, you're really looking 
at a machine and things have to work together.   And there are components that are directly 
impacting one another and making sure that   someone is helping to string those conversations 
along and paint that picture so that it's not a   surprise and everybody knows what's coming. And 
the customer also understands how those pieces   fit together so that as they operationalize these 
different components, they really know how their   organization is architected. Because moving on 
into operations, they'll have the same types of   interactions between their platform components, 
same as we do during an implementation phase.