Once the strategy is developed the relationship model must evolve to represent that implementation appropriately sequenced. There is a also a video
for this insight which is a component of the Effective Problem Solving Course
The strategy is actually a set of structural changes that have to be made by the stakeholders to create patterns of behavior which move the situation in the direction of the ideal alternative.
Policy for no resource raiding - delay this for some period of time to allow Support to catch up. Once support catches up resource raiding will be encouraged.
Expand Support’s responsibility - Hire more people so there is excess resources in Support for other organizations to raid. Support is responsible for Customer Support and Qualified Resource Availability
Migrate to self-service support - The organization has to let go of the idea that it is solely responsible for providing support
Engineer support requirements out of the products - Provide information back to engineering as to what aspects of the product are responsible for the greatest demand on Support
Integrate Customers into support system - The organization has to let go of the idea that it is solely responsible for providing support
While this provides a conceptual sequencing of the elements of the strategy it is important to note that there is a limit to what one can infer from a static diagram. Questions regarding how much, how long, when, etc. will have to be answered though a spreadsheet or simulation model.