Standardize Solutions from the same functional domain

But each shop chooses its own Solutions according to different criteria: it is a very mixed IT landscape for the Baker.

The Baker realizes that he's not generating any economies of scale with IT and that each shop will develop different practices...

It is recommended to standardize our Solutions by domain to establish a coherent IT landscape for the Baker and lead to economies of scale. After all, the shops are not that different from each other, especially regarding the administrative processes...

The baker asks his transformation unit not only to invent new types of bread, but also to chose a single Solution per domain. The budgets decrease.

In a decentralized Group, each Organizational unit decides how it wants to Operate.
This means that the Organizational unit chooses its Model and especially the IT Solution that goes with it, whether it be to manage the Distribution, Production, Resources, or management. It is far simpler for the director of the Group, who does not have to get involved in these choices, and more motivating for each decentralized Organizational unit, which gains in autonomy. This is why many Groups have historically preferred to multiply decentralized Solutions.

But this approach has limitations:

It is therefore recommended that we choose Solution Models that are as close as possible for the different Organizational units. We have to learn how to maximize the common part and minimize the specific part.
We go

Therefore we can only recommend extreme vigilance on this point: each time an Organizational unit would like to choose a specific Solution, we must ask it to justify how its mission is different to the other Organizational units and in what way the standard Solution will not enable it to carry out its mission.
It is not a simple task as certain Organizational units are likely to highlight their specificities to keep their specific Model and their autonomy.

Licence Creative Commons
The story of George the Baker is made available under the terms of the
Creative Commons Attribution - NoDerivatives 4.0 International license.
Table of Contents


comments powered by Disqus