Enterprise Alignment: Real World Stories
•Divisions A, B, and C agree to standardize on a plant systems tool from Vendor X. Divisions Aand C agree to do the first implementation. Division B decides to wait. Partway intoimplementation, Division A loses confidence in Vendor X. The enterprise council agrees not tostandardize in the plant systems space. Division A reverts back to its in-house tool. Division C,further along in its implementation, cannot revert. Division C must now move forward withVendor X without the leverage associated with an enterprise initiative.
The sucker’s payoff.
•Group Vice-President in charge of 3 divisions A, B, and C, wants a common ordering system for customers of all 3 division’s products. The cost per division is high due to the level of integrationand change to business processes in addition to the software development costs. Division C doesa cost/benefit analysis and declines to join the initiative. Group Vice-President says declining isnot an option.
Punishment for defecting greater than temptation to defect.
•Divisions A and B must start joint product development work with Division C, recently purchased by the parent company. Division C should therefore adopt the processes and tools used by A and B. However, the processes and tools used by Division C are superior to those in A andB, and are responsible for the superior performance of Division C. The benefits of Division Cdoing joint development with A&B do not completely cover the impact of making Division C lessefficient.
Temptation to defect is greater than the reward of cooperating
.
What do these stories have in common with the Prisoner’s Dilemma?
Leave a Comment